From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] A simple question
Date: Fri, 11 Jul 2003 08:03:20 +0200 [thread overview]
Message-ID: <00f601c34772$215ea340$b9844051@insultant.net> (raw)
In-Reply-To: <20030711064145.G7106@cackle.proxima.alt.za>
well if unicode was organised so that each language had its own
code space it would be a trivial problem.
look at latin 1 (for want of a better term): it covers a whole bunch
of languages, with different collation sequences and many of the
glyphs are not actually _real letters_.
é tells me how to pronounce it (as far as i'm concerned), but it's
not really a character (ô is probably a better example).
ö is a real character in swedish: en öl = a beer.
next prev parent reply other threads:[~2003-07-11 6:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 13:20 ron minnich
2003-07-10 3:59 ` Russ Cox
2003-07-10 5:37 ` Tad Hunt
2003-07-10 6:46 ` boyd, rounin
2003-07-10 11:14 ` ron minnich
2003-07-10 14:46 ` jmk
2003-07-10 16:32 ` Dan Cross
2003-07-10 16:37 ` boyd, rounin
2003-07-10 18:13 ` jmk
2003-07-10 19:13 ` boyd, rounin
2003-07-10 23:47 ` Bruce Ellis
2003-07-11 14:59 ` ron minnich
2003-07-10 17:15 ` Tad Hunt
2003-07-10 11:11 ` ron minnich
2003-07-10 11:31 ` Lucio De Re
2003-07-10 12:03 ` David Presotto
2003-07-10 14:14 ` boyd, rounin
2003-07-10 14:08 ` Lucio De Re
2003-07-10 14:24 ` David Presotto
2003-07-10 14:25 ` Lucio De Re
2003-07-10 15:06 ` boyd, rounin
2003-07-10 15:09 ` Jack Johnson
2003-07-11 4:41 ` Lucio De Re
2003-07-11 6:03 ` boyd, rounin [this message]
2003-07-11 6:11 ` Lucio De Re
2003-07-11 6:59 ` boyd, rounin
2003-07-11 8:13 ` northern snowfall
2003-07-11 16:10 ` Jack Johnson
2003-07-12 0:29 ` northern snowfall
2003-07-11 23:33 ` boyd, rounin
2003-07-10 15:09 ` rog
-- strict thread matches above, loose matches on Subject: below --
2002-09-19 19:36 [9fans] a " presotto
2002-09-19 19:34 Charles Forsyth
2002-09-19 18:55 yan zhao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00f601c34772$215ea340$b9844051@insultant.net' \
--to=boyd@insultant.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).