Kaixo! On Sun, Sep 07, 2003 at 12:59:53AM +0200, J.A. Magallon wrote:
> > MacOS X uses UTF-8. > > Change LC_CTYPE=en_ES.UTF-8 and you will see them. > > Tests... > > werewolf:~/t> LC_CTYPE=es_ES.UTF-8 ls > qué/ you need obviously to set your terminal to be able to display UTF-8. Note also that it uses combinaed accent 'e + acute accent' instead of a single '�' char... >> Your best solution to exchange disk space between both systems >> would be, imho, to use UTF-8 in linux. > > No shared storage. I copy the files via scp. So what I really like > woudl be an option for ext3...that looks missing. No, if you copy by scp, then the only way to handle it is trough scp protocol. You may suggest to ssh author to add an extra comand line option to tell the charset encoding at the other end, and to perform charset conversion of filename when copying. eg: scp --remote-encoding=utf-8 [EMAIL PROTECTED]:~bla/ble/bli.txt . would convert "bli.txt" from utf-8 to local encoding if needed. such a parameter could also be used by slogin to convert I/O; it would be quite useful indeed, and the mantainer may agree on adding it. His email: Damien Miller <[EMAIL PROTECTED]> > > Or manually rename them (or you can do a small script to do it, > > with iconv) > > Will look at how it works. But there is an extra difficulty, due to combining accents... it doesn't seem iconv is able to handle it; you should then first change to precomposed utf-8 strings; then convert. -- Ki �a vos v�ye b�n, Pablo Saratxaga http://chanae.walon.org/pablo/ PGP Key available, key ID: 0xD9B85466 [you can write me in Walloon, Spanish, French, English, Italian or Portuguese]
pgp00000.pgp
Description: PGP signature
