On Fri, Mar 23, 2007 at 06:33:57PM +0000, Jonathan McDowell wrote:
On Fri, Mar 23, 2007 at 06:25:35PM +0000, Eur Ing Chris Green wrote:
I suspect it may be something to do with the FC6 installation being UTF-8 by default. I have set it to ISO-8859-1 in a few places but I think there must be some more places to fix.
This is arse about tit; UTF-8 is decidedly the way forward and you'd be much better spending your time converting your usage of iso-8859-1 to UTF-8 than vice versa.
Yes, I sort of realise this but, given my work environment, trying to use UTF-8 on my Linux box in a sea of ISO-8859-1 (and worse) systems isn't viable at the moment.
Reading a UTF-8 FAQ I find things like the following:-
In UTF-8 mode, terminal emulators such as xterm or the Linux console driver transform every keystroke into the corresponding UTF-8 sequence and send it to the stdin of the foreground process. Similarly, any output of a process on stdout is sent to the terminal emulator, where it is processed with a UTF-8 decoder and then displayed using a 16-bit font.
With a mix of PCs, legacy Unix systems, Solaris 2.6, Solaris 2.8 and some Linux boxes on the same network displaying (via X and/or ssh) on each others screens it's going to be a long time before we are able to work with multibyte characters. As it is, using ISO-8859-1 is fairly reliable throughout.