Dan Nicholson wrote:
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
Correct, this is a bug in Nautilus CD Burner, and this should be noted on the
page (i.e.: CD images with non-ASCII filenames can be created only in UTF-8
locales). It is, however, possible to create such ISO images by hand:
mkisofs -rJ -jcharset koi8-r -o testcase.iso testcase
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
Like I said, this is probably operator error. Alexander, is this
behavior that I should expect?
This is not an operator error. Windows Explorer uses Unicode filenames (i.e.,
the CreateFileW() function) and thus can display any filename. Other
applications use a country-specific 8-bit charset for opening files (i.e.: open
files with CreateFileA() function and rely upon Windows to do the conversion),
and thus cannot open files with names not representable in this charset. To fix
the situation for Russian (but break accented Latin characters) in Windows XP,
go to Control Panel, Language and Regional Settings, and on the third tab,
select Russian as a language for programs that don't support Unicode (maybe you
will have to select Russian in two places on the first tab too).
In Russian version of WinXP, this is the default, that's why I am not sure if
the changes on the first tab are required. In English version, this can also be
configured during installation (I always do it this way, and there I have to
select Russian in three places).
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
