I cannot speak for unknown bugs that probably are in genisoimage. Let me therefore
only mention known bugs. It is unlikely that the quoted error message from
"genisoimage" is related to specific characters in the file names.
It may have two different reasons:
1) An incorrect commandline forces to have two identical filenames in the
same target directory. This will cause even mkisofs to complain.
2) The inability of "genisoimage" to correctly handle deeply nested directories
also may cause the error message. If the bug was caused by genisoimage,
the problem will go away after upgrading to recent original software.
Note that in contrary to mkisofs, genisoimage does not support UTF-8 based
character coding.
I cannot speak for unknown bugs that probably are in genisoimage. Let me therefore
only mention known bugs. It is unlikely that the quoted error message from
"genisoimage" is related to specific characters in the file names.
It may have two different reasons:
1) An incorrect commandline forces to have two identical filenames in the
same target directory. This will cause even mkisofs to complain.
2) The inability of "genisoimage" to correctly handle deeply nested directories
also may cause the error message. If the bug was caused by genisoimage,
the problem will go away after upgrading to recent original software.
Note that in contrary to mkisofs, genisoimage does not support UTF-8 based
character coding.