search for: iso_convert_name

Displaying 3 results from an estimated 3 matches for "iso_convert_name".

2013 Mar 26
5
Allowed code pages and encodings to write f0.txt through f1.txt?
Hi there. Slackware's installer, that I am internationalizing, makes use of ISOLINUX. I want to give instructions to users in other languages than US English, e.g. which code to type to see installation messages in their native language. So my question are: (1) Which character encodings can be used in message.txt and f1.txt through f1O.txt? (2) Is UTF-8 allowed? (3) I'm guessing that
2013 Apr 25
1
[syslinux:rockridge] iso9660.c did not copy terminating 0 of Rock Ridge name
...:37 +0200 > Committer: Matt Fleming <matt.fleming at intel.com> > CommitDate: Thu, 25 Apr 2013 14:59:08 +0100 > > iso9660.c did not copy terminating 0 of Rock Ridge name > > I noticed that the trailing 0-byte is not copied to the result of > iso_readdir(). The function iso_convert_name() does append a trailing 0. > > --- > core/fs/iso9660/iso9660.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > Would it be possible for a (broken) disc to have a non-null-terminated name here? I'm wondering if it would be better to instead do: > diff --git a/c...
2013 Mar 28
9
Rock Ridge. Was: Allowed code pages and encodings to write f0.txt through f1.txt?
Hi, i began to implement a common lookup function for SUSP and Rock Ridge entries: /* Obtain the payload bytes of all SUSP entries with a given signature. @param fs The data source from which to read CE blocks. @param dir_rec Memory containing the whole ISO 9660 directory record. @param sig Two characters of SUSP signature. E.g. "NM", "ER", ...