> If I use unicode on the console, I had to change the consolefont to: > consolechars --font=LatArCyrHeb-16 > then it works fine.
The filename is written differently to the disk, when ooffice is started with LC_MESSAGES defined like that. With other programs like vim, I have no problems reading and writing files like "testäöü.txt". What is the connection between LC_MESSAGES and the encoding of the filenames? Worse, if LC_MESSAGES=en_GB.UTF-8, I'm not able to open a file with characters like ä, ö or ü in its name. I played a little bit with the environment settings: If no LC_* is set, ls displays files with äöü in their names with ??? replaced. [EMAIL PROTECTED] fixes this. For ooffice this seems to make no difference. The file open box of ooffice behaves also different depending on the setting of LC_MESSAGES. I created a file testlcäöü.sxw with ooffice started with LC_MESSAGES set and a file testnolcäöü with ooffice started with LC_MESSAGES undefined. Here is how the open file dialog of ooffice displays the files when started with or without LC_MESSAGES=en_GB.UTF-8 defined: LC_MESSAGES undefined: testnolcäöü.sxw: displayed correctly testlcäöü: displayed with cryptic characters in its name, but can be opened LC_MESSAGES defined: testnolcäöü.sxw: The filename is not displayed (empty), the stats are. Cannot be opened. testlcäöü.sxw: displayed correctly, can be opened. ____________________________________________________ Aufnehmen, abschicken, nah sein - So einfach ist WEB.DE Video-Mail: http://freemail.web.de/?mc=021200
