James G. Sack (jim) wrote:
Christopher Smith wrote:
James G. Sack (jim) wrote:
Christopher Smith wrote:
James G. Sack (jim) wrote:
For your immediate needs, have you tried making your CD on a system with
utf-8 filesystem encoding? I guess maybe Windows uses utf-16; here
again are some simple experiments that I haven't gotten around to.
It's not UTF-16. It's the old Unicode 1.x, which is fixed-width, 16-bit
characters.
It occurs to me that some characters are reserved in both HFS+ and
Windows, so you might run in to problems there, although UTF-7 and other
solutions like it won't address that either. You probably should just
use tr and/or Perl for those specific cases.
Can you (or somebody) enlighten me on CD filesystem encoding capabilities?
All I can remember is getting confused a long time ago about rocky road
(wait that's something else) and extensions thereof.
You've got your ISO 9660. http://en.wikipedia.org/wiki/ISO_9660
Then you have your Rock Ridge Extensions.
http://en.wikipedia.org/wiki/Rock_Ridge
Then you have your Joliet extensions.
http://en.wikipedia.org/wiki/Joliet_%28file_system%29
Rock Ridge was popular with Unix folks, but everyone seems to have moved
towards Joliet.
OK, a real quick look at the first words on your joliet reference shows
it uses UCS-2 which, I think you may be referring to in your statement
about "old Unicode 1.x". UCS-2 is a subset of UTF-16, which should be
pretty serviceable (as long as you don't need to write any Linear-B
poetry [Klingon is ok] -- SJS, take note).
Guess I'll have to get around to some little experiments -- maybe in the
next few days.
Yes, USC-2 is the correct term that escaped me.
--Chris
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
