| View previous topic :: View next topic |
| Author |
Message |
elpuma
n00b
Joined: 27 Oct 2004
Posts: 19
|
 Posted: Mon Dec 27, 2004 3:32 pm Post subject: mkisofs and Joliet |
 |
|
Hi, this is my problem:
Building an iso image with rockridge and joliet extensions yields a perfect image to use in Linux, however, when I try to read it under Windows, everything is OK except for the special Spanish characters (i.e. an 'í' is displayed as 'Ã-'). What can be happenning?
Thanks in advance...
P.S.: excuse my poor English
_________________
"Because a life in the bathroom / is not a cleaner life" |
|
| Back to top |
|
 |
bennettp
Guru
Joined: 22 Feb 2004
Posts: 335
Location: on my back and tumbling
|
| Posted: Mon Dec 27, 2004 10:33 pm Post subject: |
|
|
It looks like there's a problem with the font you're using. IIRC, Joilet uses unicode to store filenames. The console usually uses ISO8859-1, or something similar. I have no idea how you would fix this. I have similar problems with ntfs: the latin charaters look different in KDE than in the console: the console uses ISO8859-1, and KDE uses unicode (i think!).
The other possibility is that your filenames are not using iso8859-1, but mkisofs is. This should be easier to fix: look up the manpage for mkisofs, and look for an option to tell it what character encoding to use.
_________________
Registered Linux User #363420 |
|
| Back to top |
|
|
elpuma
n00b
Joined: 27 Oct 2004
Posts: 19
|
| Posted: Tue Dec 28, 2004 1:42 am Post subject: |
|
|
| bennettp wrote: | It looks like there's a problem with the font you're using. IIRC, Joilet uses unicode to store filenames. The console usually uses ISO8859-1, or something similar. I have no idea how you would fix this. I have similar problems with ntfs: the latin charaters look different in KDE than in the console: the console uses ISO8859-1, and KDE uses unicode (i think!).
The other possibility is that your filenames are not using iso8859-1, but mkisofs is. This should be easier to fix: look up the manpage for mkisofs, and look for an option to tell it what character encoding to use. |
Thanks for the reply!
1st thing: I see those strange names in windows, not the console...
I also found out that mkisofs uses iso8859-1 as the default for the -input-charset option. The problem is that all my files use utf8, and there's no utf8 among the possibles for -input-charset. ¿Any suggestion?
_________________
"Because a life in the bathroom / is not a cleaner life" |
|
| Back to top |
|
|
elpuma
n00b
Joined: 27 Oct 2004
Posts: 19
|
| Posted: Tue Dec 28, 2004 5:26 am Post subject: |
|
|
Now I noticed something else (these are two examples):
é is replaced by é
ô is replaced by ô
é octal representation in UTF-8 is \303\251
ô octal representation in UTF-8 is \303\264
à octal representation in UTF-8 is \303\203
© octal representation in UTF-8 is \302\251
´ octal representation in UTF-8 is \302\264
So, basically, this takes "...\303\264..." and replaces it by "..\303\203\302\264..." or whatever, always inserting the sequence "\203\302" in between.
Any help? Any guidelines towards writing a patch for cdrtools?
_________________
"Because a life in the bathroom / is not a cleaner life" |
|
| Back to top |
|
|
Bepcyc
Tux's lil' helper
Joined: 07 May 2004
Posts: 130
Location: Moscow, Russia
|
| Posted: Sun Jan 09, 2005 12:56 am Post subject: |
|
|
I asked this question in different forums - nobody answered me
I googled the internet - found nothing
I have read then man page for mkisofs but found only that Microsoft's Joliet format uses UTF-16 to represent symbols and
| Quote: | Note that there is no support for 16 bit UNICODE (UTF-16) or 32 bit
UNICODE (UTF-32) coding because this coding is not POSIX compliant.
There should be support for UTF-8 UNICODE coding which is compatible to
POSIX filenames and supported by moder UNIX implementations such as
Solaris.
|
As we can see Microsoft did their best again to make our life better... ;( |
|
| Back to top |
|
|
|
Other Things Gentoo
