Re: [Libcdio-devel] Joliet bug?

[R. Bernstein]

Burkhard Plaum writes:
 > Hi,
 > 
 > [...]
 > > I'll look at when I get back. My recolection on the iso9660_ifs_get
 > > routines is that they return fixed length strings as the ISO 9660
 > > specification has it. If the string is less than the max then there's a
 > > null if not then no null. 
 > 
 > Some "empty" fields are filled with spaces by k3b. I'm wondering if one
 > should catch this and treat such fields as empty.
 > 
 > > However I realize this doesn't explain the
 > > behavior below where there is 16-bit "ASCII".
 > 
 > Probably the CD I tried is wrong? Can it be, that k3b creates wrong joliet?
 > Will try with others too.

If k3b creates wrong joliet then either we need to alert k3b or fix
libcdio. I have the PDF I used as a guideline on pdf at home. Will
investigate when I can or if someone else can do sot great.

 > 
 > As I said, Joliet is a "black box" for me, but I know, that Microsoft
 > likes to padd things to even bytes (e.g. in AVI files). Ignoring padding
 > when reading some data structures could lead to the observed behaviour.

Okay. Thanks for the info. Will keep it in mind when I have a chance
to look at this.