Description of problem:
Some letters on Windows drives are wrong.
I made a file in WinXP called 'TEST Ã¦Ã¸Ã¥ ÃÃÃ Ã¼Ã¶Ã¤ ÃÃÃ Ã©.txt' and in Linux the
files comes out like 'TEST ??? ??? ??? ??? ?.txt'
I'm writing this from the same linux box and as you can see, the letters works well.
Steps to Reproduce:
1. In Windows make a file called 'TEST Ã¦Ã¸Ã¥ ÃÃÃ Ã¼Ã¶Ã¤ ÃÃÃ Ã©.txt' on a FAT32 drive
2. Reboot the PC into RedHat Linux.
3. Open a terminal or use Nautilus and check the file name on the FAT32 drive
TEST ??? ??? ??? ??? ?.txt
TEST Ã¦Ã¸Ã¥ ÃÃÃ Ã¼Ã¶Ã¤ ÃÃÃ Ã©.txt
If I make the same filename in Linux it works fine (not tested on the FAT32 drive).
I'm using a Danish keyborad
Nothing to do with bash.
Try inserting one of the codepage modules (modprobe nls_cp850 for example).
or possible nls_iso8859-15
And How do I do that?
as ROOT I don't have a command called modprobe.
use "su -" not "su" if you want to access commands in /sbin or /usr/sbin
without having to type the full pathname.
Just tried to do 'modprobe nls_cp850' and 'modprobe nls_iso8859-15' and still
Find the line corresponding to your FAT32 partition in /etc/fstab, and add
`iocharset=utf8' as a mount option (third field to the right).
Ok, I changed the fstab file to this :
/dev/hdb2 /win_data vfat,iocharset=utf8 defaults 0 0
Still the same, it did not fix it :(
No, it should be as follows:
/dev/hdb2 /win_data vfat defaults,iocharset=utf8 0 0
That seemed to do the trick.
I now have the correct names in terminal and in most other programs (not Xine's
I guess the installer did not know/guess that I has a Danish FAT32 drive?
Duplicates: #79396, #107834, #107935.
This problem has been reported least three times during severn beta cycle.
#79396 is on "make cambrigde better"
#107834 has alternative fix.