Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm looking for a ISO image creator, already tried isomaster, but it doesn't work with unicode chars, it just take it as bad chars, so what other tool can I use?

I don't need booting, just archive them. (Please don't tell me to use tar or whatever, I'm doing so for reasons)

share|improve this question
Have you tried mkisofs? – Karlson Dec 9 '12 at 8:49
@Karlson same problem, all non-ascii characters are converted to underscore, and I already specified the right encoding (utf8) – warl0ck Dec 9 '12 at 8:53
@warl0ck: did you enable any kind of extension to ISO9660? The standard does not allow much more than A-Z and underscores, which is probably why you are getting what you are getting. You probably want to enable Rock Ridge and possibly Joliet, with the -R (or -r) and -J options to mkisofs. mkisofs will, by default, create a plain ISO9660 image, which is the standard data CD format. Most of the CDs you see out there with long file names, unicode in file names and file permissions have either Joliet or RR extensions. – njsg Dec 9 '12 at 8:57
Also, look into the tool you were using for options that enable these extensions, maybe it supports Joliet and RR and you just didn't know what to look for (btw, Joliet is the Microsoft extension, RR is the UNIX one). – njsg Dec 9 '12 at 8:58
@SabreWolfy: now that the issue is clearer, I tried to reword what I said in the form of an answer – njsg Dec 9 '12 at 10:39
up vote 8 down vote accepted

The ISO9660 standard does not allow names with other than A-Z, numbers and underscores. No matter which tool you use, if it just creates a plain ISO9660 filesystem, it will likely convert all filenames to respect these restrictions, and possibly even to fit into 8.3 filenames.

Support for other characters in filenames, as well as longer filenames and other filesystem features not found in ISO9660 is usually achieved by using extensions to the standard: in the UNIX world, there is Rock Ridge. Microsoft has Joliet. Enabling one of those will likely give you what you want (I'm not sure about Joliet, but Rock Ridge has always worked with unicode filenames, even if I don't know for sure how are the names encoded).

In mkisofs, for example, you use -R to enable the Rock Ridge extensions (-r for slightly different defaults) and -J to enable Joliet. Look for similar options in isomaster. You can do well with Rock Ridge. Whether you want to enable Joliet or not depends on whether you plan to read the image under Microsoft OSes. (You can have both at the same time.)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.