Re: [PATCH] replace 0xA0 to whitespace in plain text files (part 2)

[David Laight <david%l8s.co.uk@localhost>]

On Thu, Sep 11, 2008 at 06:57:53PM +0200, Hubert Feyrer wrote:
> 
> I can share an anecdote on that, which I recently run into with nvi 
> compiled from pkgsrc on a Debian system: When saving a file from a 
> non-default locale (say, when you've read a Latin1 file with UTF8 as 
> default), nvi starts saving the file, and aborts when it comes to the 
> Latin1 character. After that, the on-disk file is truncated, and the file 
> in the editor cannot be saved. ``Thank you for killing my file!''

That sucks big-time.
It makes me think even more that UTF-8 is completely inappropriate
for a system-wide locale on any unix system.
Clearly some documents and strings can be in UTF-8, but that has to
be a known property of the string.  It isn't appropriate that
any string a program obtains can be assumed to be UTF-8.

        David

-- 
David Laight: david%l8s.co.uk@localhost