On Thu, Jun 07, 2007 at 02:15:30AM +, s. keeling wrote:
When slrn has utf-8 support, I'll change. :-(
Hm, slrn depends on libslang2 in testing which has utf-8 support.
[Sorry if I spelt your name wrong, Stephan. I'm trying your
//TRANSLIT trick in mutt. Hopefully, I got enough out of
On Wed, Jun 06, 2007 at 01:24:32PM +0800, Wei Chen wrote:
Things could be easy for English speaking people, since UTF-8 is fully
compatible with ASCII. However, for people that do not speak English,
for example CJK people, using UTF-8 may mean not compatible with others
that use legacy
On Tue, Jun 05, 2007 at 09:17:32PM -0700, Kelly Clowers wrote:
On 6/5/07, Douglas Allan Tutty [EMAIL PROTECTED] wrote:
I'm in Canada speaking and writing English with a off-the-shelf North
American computer with a standard US keyboard.
Up until etch, lang was C and nothing was UTF. What are
Hi
On 6/6/07, Douglas Allan Tutty [EMAIL PROTECTED] wrote:
Could you define everything? Do you mean README text file, html,
what? If so, do you mean that if I were running with 'C' I couldn't
read them?
Everything means that (roughly spoken) UTF-8 has place enough store
every thinkable
If I write a plain text, in english, on my UTF-8 stock debian system, is
it safe to assume that it will be readable by a computer that doesn't do
UTF-8 that just has 'C'? Will that multi-lingual README written in
UTF-8 at least be readable in english on a system with just 'C'?
I don't
On Wed, Jun 06, 2007 at 12:09:20PM -0400, Douglas Allan Tutty wrote:
If I write a plain text, in english, on my UTF-8 stock debian system, is
it safe to assume that it will be readable by a computer that doesn't do
UTF-8 that just has 'C'? Will that multi-lingual README written in
US-ASCII is
On 6/6/07, Douglas Allan Tutty [EMAIL PROTECTED] wrote:
On Wed, Jun 06, 2007 at 01:24:32PM +0800, Wei Chen wrote:
Things could be easy for English speaking people, since UTF-8 is fully
compatible with ASCII. However, for people that do not speak English,
for example CJK people, using UTF-8
On Wed, Jun 06, 2007 at 06:33:58PM +0200, Stephan Seitz wrote:
US-ASCII is a subset of UTF-8, so any text written in US-ASCII is
readable in LANG=C. But the English language can have characters beside
the 7bit ASCII characters as well (e.g. ??). So you can???t say that the
English
On Wed, Jun 06, 2007 at 01:15:32PM -0400, Douglas Allan Tutty wrote:
If I view this in mutt after a LANG=C, of course I can't see your
accented character (its a ??). Interesting that your can't is also
can???t. I wonder why your editor chose to use a unicode for '.
Because I told him to do.
Wei Chen [EMAIL PROTECTED]:
On 6/6/07, Douglas Allan Tutty [EMAIL PROTECTED] wrote:
On Wed, Jun 06, 2007 at 01:24:32PM +0800, Wei Chen wrote:
Things could be easy for English speaking people, since UTF-8 is fully
compatible with ASCII. However, for people that do not speak English,
I'm in Candada speaking and writing english with a off-the-shelf North
American computer with a standard US keyboard.
Up until etch, lang was C and nothing was UTF. What are the advantages
to me of etch setting a default language en_CA.UTF-8 and other locale
settings? What are the
On 6/5/07, Douglas Allan Tutty [EMAIL PROTECTED] wrote:
I'm in Canada speaking and writing English with a off-the-shelf North
American computer with a standard US keyboard.
Up until etch, lang was C and nothing was UTF. What are the advantages
to me of etch setting a default language
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kelly Clowers wrote:
On 6/5/07, Douglas Allan Tutty [EMAIL PROTECTED] wrote:
I'm in Canada speaking and writing English with a off-the-shelf North
American computer with a standard US keyboard.
Up until etch, lang was C and nothing was UTF. What
13 matches
Mail list logo
