Re: mkisofs and hebrew filenames
Ilya Konstantinov wrote: On Wed, May 16, 2001 at 01:47:58PM +0300, Gavrie Philipson wrote: Hi IGLUers, I was wondering if anyone here has succeeded in burning CD-Rs with Hebrew filenames on them, that are readable on that other OS. Normally, mkisofs (with the -J option to create Joliet directories) barfs on Hebrew filenames. When adding the option '-jcharset cp862', the Windows Hebrew filenames are recognized OK, but they are reversed. This means it's not a charset problem, but probably a bidi problem. I suspect that the Joliet filenames somehow aren't processed by the Windows Bidi algorithm in the same way as 'regular' filenames. Does anyone have experience with this? Is hacking mkisofs to use a bidi algorithm for the filenames the correct way to solve this? Did you try 'iso8859-8' ? (I'd be suprised to see it work if the previous solution didn't, since both should just convert the thing into Unicode -- and the source shows no differences as well). Ilya, I didn't try, but I will. However, the filenames seems to be in CP862 format (Aleph=128) and not ISO8859-8 (Aleph=224). Is this a Windows thingie? Another possible thing might be that you'll need to include a zero-width Unicode symbol which means start bidi algorythm. POP DIRECTIONAL FORMATTING (hexadecimal 202C) should apparently do it. If that's indeed the solution, then I'd hope you'd choose the right way to patch mkisofs rather than including a bidi algorythm :) Hmm...if that works, it certainly is much better. I'll do some experiments. I'll tell you if I have answers. Thanks, Gavrie. -- Gavrie Philipson Netmor Applied Modeling Research Ltd. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: mkisofs and hebrew filenames
On Thu, 17 May 2001, Gavrie Philipson wrote: Ilya Konstantinov wrote: On Wed, May 16, 2001 at 01:47:58PM +0300, Gavrie Philipson wrote: Another possible thing might be that you'll need to include a zero-width Unicode symbol which means start bidi algorythm. POP DIRECTIONAL FORMATTING (hexadecimal 202C) should apparently do it. If that's indeed the solution, then I'd hope you'd choose the right way to patch mkisofs rather than including a bidi algorythm :) Hmm...if that works, it certainly is much better. I'll do some experiments. I'll tell you if I have answers. Sounds strange to me. Afterall, mkisofs did not create those names. Why should it care about bidi formatting? -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: mkisofs and hebrew filenames
Tzafrir Cohen wrote: On Thu, 17 May 2001, Gavrie Philipson wrote: Ilya Konstantinov wrote: Another possible thing might be that you'll need to include a zero-width Unicode symbol which means start bidi algorythm. POP DIRECTIONAL FORMATTING (hexadecimal 202C) should apparently do it. If that's indeed the solution, then I'd hope you'd choose the right way to patch mkisofs rather than including a bidi algorythm :) [snip] Sounds strange to me. Afterall, mkisofs did not create those names. Why should it care about bidi formatting? It shouldn't. The point is, that Windows could look at ISO9660 filenames in a different way than normal, on-disk filenames. It could be that Windows doesn't consider those Hebrew filenames as Hebrew, but rather as some unknown language, and doesn't use the Bidi algorithm on them. Maybe Ilya's idea will convince it ;-) Gavrie. -- Gavrie Philipson Netmor Applied Modeling Research Ltd. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
mkisofs and hebrew filenames
Hi IGLUers, I was wondering if anyone here has succeeded in burning CD-Rs with Hebrew filenames on them, that are readable on that other OS. Normally, mkisofs (with the -J option to create Joliet directories) barfs on Hebrew filenames. When adding the option '-jcharset cp862', the Windows Hebrew filenames are recognized OK, but they are reversed. This means it's not a charset problem, but probably a bidi problem. I suspect that the Joliet filenames somehow aren't processed by the Windows Bidi algorithm in the same way as 'regular' filenames. Does anyone have experience with this? Is hacking mkisofs to use a bidi algorithm for the filenames the correct way to solve this? Regards, Gavrie. -- Gavrie Philipson Netmor Applied Modeling Research Ltd. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: mkisofs and hebrew filenames
On Wed, May 16, 2001 at 01:47:58PM +0300, Gavrie Philipson wrote: Hi IGLUers, I was wondering if anyone here has succeeded in burning CD-Rs with Hebrew filenames on them, that are readable on that other OS. Normally, mkisofs (with the -J option to create Joliet directories) barfs on Hebrew filenames. When adding the option '-jcharset cp862', the Windows Hebrew filenames are recognized OK, but they are reversed. This means it's not a charset problem, but probably a bidi problem. I suspect that the Joliet filenames somehow aren't processed by the Windows Bidi algorithm in the same way as 'regular' filenames. Does anyone have experience with this? Is hacking mkisofs to use a bidi algorithm for the filenames the correct way to solve this? Did you try 'iso8859-8' ? (I'd be suprised to see it work if the previous solution didn't, since both should just convert the thing into Unicode -- and the source shows no differences as well). Another possible thing might be that you'll need to include a zero-width Unicode symbol which means start bidi algorythm. POP DIRECTIONAL FORMATTING (hexadecimal 202C) should apparently do it. If that's indeed the solution, then I'd hope you'd choose the right way to patch mkisofs rather than including a bidi algorythm :) -- Best regards, Ilya Konstantinov = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
