Re: Wrong encoding since fresh etch install
Roger Leigh wrote:
> "Alexandre B." <alexandre@linuxfr.eu> writes:
>
>> my /etc directory got corrupted few days ago, so I had to reinstall my
>> Debian system. I choosed to switch from sid to Etch. You must know that
>> my /home directory was not touched by the corrupt thing (it was on
>> another partition).
>>
>> But then, I couldn't see the correct names for directories in my /home.
>> So I decided to check for the locales set, and they were wrongly pointed
>> to fr_FR.UTF-8 UTF-8
>> so I unticked it and choosed
>> fr_FR@euro ISO-8859-15
>> like it was before.
>>
>> But now I still can't read filenames containing accentued character in
>> my /home, and it's even worse : I can't even type accentued character
>> with dead keys (I'm using us_intl keyboard map), all I got is 2 squares
>> like "??"...
>
> What is the output of "locale"? What are the contents of
> /etc/environment and /etc/default/locale?
$ locale
LANG=fr_FR@euro
LANGUAGE=fr_FR:fr:en_GB:en
LC_CTYPE="fr_FR@euro"
LC_NUMERIC="fr_FR@euro"
LC_TIME="fr_FR@euro"
LC_COLLATE="fr_FR@euro"
LC_MONETARY="fr_FR@euro"
LC_MESSAGES="fr_FR@euro"
LC_PAPER="fr_FR@euro"
LC_NAME="fr_FR@euro"
LC_ADDRESS="fr_FR@euro"
LC_TELEPHONE="fr_FR@euro"
LC_MEASUREMENT="fr_FR@euro"
LC_IDENTIFICATION="fr_FR@euro"
LC_ALL=
$ cat /etc/environment
LANG="fr_FR.UTF-8"
LANGUAGE="fr_FR:fr:en_GB:en"
$ cat /etc/default/locale
# File generated by update-locale
LANG=fr_FR@euro
it looks like /etc/environment hasn't been updated accordingly
> Which terminal are you using? VC, xterm, something else?
I tried with yakuake (konsole) and gnome-terminal.
Odd enough, I'm able to type accented char in virtual terminals (I use a fr
keymap there, while I use us_intl under X) and to see the names right.
> What console font and charmap/ACM are you using?
Dejavu sans mono
> Is the console in UTF-8 mode?
Dunno, but it's not only a console pb, it's a system wide pb has I can't
type anything with special char without the string to be borked :x
> Does running unicode_stop or unicode_start fix things?
$ unicode_start
Won't set unicode mode: not a VT.
And has I said, everything seems alright under VTs.
>> So my questions are :
>> 1. How can I know which encoding were used for those dir ?
>
> Try this script (dirent-encoding):
>
> --------------------8<------------------------
> #!/bin/sh
>
> set -e
>
> cd $1
>
> for file in *; do
> echo "Encoding of $file:"
> echo "$file" | file --mime -
> done
> --------------------8<------------------------
>
>
> For example:
>
> $ /tmp/dirent-encoding /tmp/
> [...]
> Encoding of zman8suFIu:
> /dev/stdin: text/plain; charset=us-ascii
> Encoding of zzzzß:
> /dev/stdin: text/plain; charset=utf-8
>
>> 2. How can I fix this encoding pb for all my system, taking into
>> account I _don't_ want to use utf-8 but latin-9 ?
>
> Once you provide the above information, it will be easier to say.
>
> There are good reasons why Unicode/UTF-8 is being made the default
> encoding for etch. While Latin-[1-15] will continue to be a supported
> configuration, you should consider converting fully to UTF-8, because
> UTF-8 is the present and future on GNU/Linux, and having a standard
> universal character set makes a lot of sense.
>
>
> Regards,
> Roger
>
Thx for your answers Roger, regarding the content of /etc/environment, I'll
give it a try by changing it back to fr_FR@euro.
I'll reboot and if I still had encoding pb, I'll get back here :)
Regards,
Alexandre
--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
Reply to: