Re: $assumed_charset settings (was: special chars)

2007-03-28 Thread Alain Bench
Hello Thomas, On Tuesday, March 27, 2007 at 18:10:22 -0400, Thomas E. Dickey wrote: On Tue, 27 Mar 2007, Alain Bench wrote: some terminals (Rxvt?) can display simultaneously Latin-1 and UTF-8. Something has to provide the mode-switch between UTF-8 and Latin-1. I meant *without* mode

Re: $assumed_charset settings (was: special chars)

2007-03-28 Thread Thomas Dickey
On Wed, 28 Mar 2007, Alain Bench wrote: some terminals (Rxvt?) can display simultaneously Latin-1 and UTF-8. Something has to provide the mode-switch between UTF-8 and Latin-1. I meant *without* mode switch. Something that would print (fake): | $ printf \0351 \0303\0251\n #

Re: $assumed_charset settings (was: special chars)

2007-03-27 Thread Alain Bench
On Monday, March 26, 2007 at 16:39:36 +0200, Vincent Lefèvre wrote: about files that contain both ISO-8859-1 and UTF-8, to let the user decide. [...] it can happen in diffs where some files are encoded in ISO-8859-1 and others in UTF-8. That's definitely undecidable by the

Re: $assumed_charset settings (was: special chars)

2007-03-27 Thread Thomas Dickey
On Tue, 27 Mar 2007, Alain Bench wrote: On Monday, March 26, 2007 at 16:39:36 +0200, Vincent Lefèvre wrote: about files that contain both ISO-8859-1 and UTF-8, to let the user decide. [...] it can happen in diffs where some files are encoded in ISO-8859-1 and others in UTF-8. That's

Re: $assumed_charset settings (was: special chars)

2007-03-26 Thread Vincent Lefevre
Salut Alain, On 2007-03-25 20:21:35 +0200, Alain Bench wrote: Bonjour Vincent, On Sunday, March 25, 2007 at 4:28:36 +0200, Vincent Lefèvre wrote: On 2007-03-24 16:05:08 +0100, Alain Bench wrote: Setting UTF-8 after ISO-8859-1 is useless. Any string is always valid Latin-1.

Re: $assumed_charset settings (was: special chars)

2007-03-25 Thread Christoph Berg
Re: Vincent Lefevre 2007-03-25 [EMAIL PROTECTED] Setting UTF-8 after ISO-8859-1 is useless. Any string is always valid Latin-1. UTF-8 will never be tried nor selected. Shouldn't characters 128-159 be regarded as invalid? Text should contain only printable characters and some restricted

Re: $assumed_charset settings (was: special chars)

2007-03-25 Thread Alain Bench
Hello Christoph! On Sunday, March 25, 2007 at 13:30:12 +0200, Christoph Berg wrote: CP1251 (iirc, the last digit could be different) is what windows usually uses. It is a superset of latin1, with characters in the 128-159 range, mainly some quotes. That could also be a good guess.

Re: $assumed_charset settings (was: special chars)

2007-03-25 Thread Alain Bench
Bonjour Vincent, On Sunday, March 25, 2007 at 4:28:36 +0200, Vincent Lefèvre wrote: On 2007-03-24 16:05:08 +0100, Alain Bench wrote: Setting UTF-8 after ISO-8859-1 is useless. Any string is always valid Latin-1. Shouldn't characters 128-159 be regarded as invalid? No, I don't think so,

Re: $assumed_charset settings (was: special chars)

2007-03-25 Thread Thomas Dickey
On Sun, 25 Mar 2007, Alain Bench wrote: Hello Christoph! On Sunday, March 25, 2007 at 13:30:12 +0200, Christoph Berg wrote: CP1251 (iirc, the last digit could be different) is what windows usually uses. It is a superset of latin1, with characters in the 128-159 range, mainly some quotes.

$assumed_charset settings (was: special chars)

2007-03-24 Thread Alain Bench
On Monday, March 19, 2007 at 10:10:40 +0900, Tamotsu Takahashi wrote: you can set assumed_charset=iso-8859-1:utf-8 Setting UTF-8 after ISO-8859-1 is useless. Any string is always valid Latin-1. UTF-8 will never be tried nor selected. The reversed order,