| 1 |
On Tue, Jul 10, 2007 at 06:44:14PM +0300, Penguin Lover Aleksey V. Kunitskiy squawked: |
| 2 |
> This DVD-R was created under windows with nero, not by me. |
| 3 |
> I tried to set iocharset=windows-1251 but it didn't help. I know on that |
| 4 |
> windows system is windows-1251 charset. I still see ugly names, and I haven't |
| 5 |
> any ideas... Under windows this DVD reads OK |
| 6 |
|
| 7 |
This I am not sure how to work with. As far as the manpage goes, |
| 8 |
the 'iocharset' option only makes sense when mounting Joliet extended |
| 9 |
iso9660 discs (since Joliet gives a filename mapping into unicode, the |
| 10 |
iocharset option specifies how to translate the unicode filenames into |
| 11 |
your current operating charset). This seems to suggest that the way |
| 12 |
you used the 'iocharset' option is the opposite of what you intended. |
| 13 |
|
| 14 |
Google suggests that some people have tried mounting iso9660 |
| 15 |
filesystems with the 'codepage' options (see the vfat section of |
| 16 |
man mount), but AFAICT from the documentation, the codepage option for |
| 17 |
iso9660 has been talked about on LKML in 2005 but not implemented. |
| 18 |
|
| 19 |
It might be possible to read the disc properly if you run a kernel |
| 20 |
with the default NLS set to cp1251 (I think that CLE linux, a Chinese |
| 21 |
based fork of redhat, used that trick and set the default NLS to big5, |
| 22 |
allowing them to read vfat and iso9660 filesystems without specifying |
| 23 |
iocharset and/or codepage options), but to be honest, I don't know how |
| 24 |
to work with your problem, so take my suggestions with a relatively |
| 25 |
large grain of NaCl. |
| 26 |
|
| 27 |
Best of luck, |
| 28 |
|
| 29 |
W |
| 30 |
|
| 31 |
-- |
| 32 |
Love is like 2. It has irrational roots. |
| 33 |
~Daniel Jonathan Peng |
| 34 |
Sortir en Pantoufles: up 214 days, 14:49 |
| 35 |
-- |
| 36 |
gentoo-user@g.o mailing list |
Archives