On 5/6/06, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
To perform the test, start from a text console: unset LANG unset LC_ALL export LC_CTYPE=ru_RU.KOI8-R export G_FILENAME_ENCODING="@locale" tar zxf testcase.tar.gz startx `which gnome-session` In that session, make sure that the locale settings are still the same (LC_CTYPE=ru_RU.KOI8-R) and then try burning the "testcase" directory on the CD, if you can (Nautilus CD burner complains about invalid UTF-8 sequence, although it should not use UTF-8 at all in this case). Then erase, exit the session, and retry with ru_RU.UTF-8. Then try reading the CD in Windows.
I believe it works correctly, but let me be a little pedantic so we're on the same page. With LC_CTYPE=ru_RU.KOI8-R, nautilus-cd-burner complains about "invalid Unicode" and won't burn the disc. See a screenshot of the situation here: http://anduin.linuxfromscratch.org/~dnicholson/ncdb.png With LC_CTYPE=ru_RU.UTF-8, I can burn the disc. However, in Windows, things are a little strange. This is very probably operator error since I've never played around with locale settings in Windows. In Windows Explorer, the disc shows the file and the filename is correctly displayed. I can view properties and copy it. However, when I try to open the file with other applications, it says it can't find ????.dat. Here's one such error message from ClamWin: -------------------------------------- Scan started: Sun May 14 16:29:21 2006 ERROR: Can't access file G:\????.dat -- summary -- Known viruses: 54806 Engine version: 0.87.1 Scanned directories: 0 Scanned files: 0 Infected files: 0 Data scanned: 0.00 MB Time: 5.268 sec (0 m 5 s) ------------------- Completed ------------------- Like I said, this is probably operator error. Alexander, is this behavior that I should expect? Thanks. If this is right, I'll submit the two patches today. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
