Changes between Version 6 and Version 7 of Cdrtools


Ignore:
Timestamp:
08/01/2006 12:12:59 PM (18 years ago)
Author:
alexander@…
Comment:

Removed stuff that is already in the book

Legend:

Unmodified
Added
Removed
Modified

  • Cdrtools

    v6 v7  
    11= Cdrtools =
    22
    3 cdrecord has ISO-8859-1 characters hard-coded in its messages. Thus, they can't be displayed properly in locales using other character sets. Also, they make some UTF-8 terminal emulators upset. If you have Glibc and the de_DE locale and understand legal consequences of doing that, run the commands below to convert messages to ASCII approximations (e.g., "J<wrong or invalid character>rg Schilling" -> "Joerg Schilling"). Alternatively, apply [http://wiki.linuxfromscratch.org/blfs/attachment/wiki/Cdrtools/cdrtools-2.01-ascii-1.patch?format=raw this patch] that has the same legal consequences.
     3== Status of the mkisofs iconv patch ==
    44
    5 {{{
    6 for F in cdrecord/cdrecord.c cdrecord/diskid.c cdrecord/sector.c \
    7     readcd/readcd.c scgcheck/scgcheck.c scgskeleton/skel.c ; do
    8     LC_ALL=de_DE iconv -f ISO-8859-1 -t US-ASCII//TRANSLIT $F >tmp
    9     mv -f tmp $F
    10 done
    11 }}}
    12 
    13 The comment in cdrecord.c states that, because of GPL requirements, you are not allowed to do that (because these commands modify the copyright notices), but how can a copyright notice containing invalid byte sequences be valid? !RedHat ignores this comment and patches copyright notices.
    14 
    15 ----
    16 
    17 When creating an ISO image with Joliet extensions (for long file names on MS Windows) using unpatched mkisofs, it is necessary to specify the input filename character set with the -input-charset (or, equivalently, -jcharset) option, unless it is ISO-8859-1 (the default). The character set name passed after this switch must match the output of "locale charmap". A mismatch results in completely wrong non-ASCII characters in the filenames under MS Windows.
    18 
    19 Problem 1: unpatched mkisofs accepts only character sets listed in the "mkisofs -input-charset help" output, and UTF-8 is not in the list.
    20 
    21 Problem 2: some GUI frontends don't know that this option has to be passed, and don't allow a user to add it at all.
    22 
    23 Both problems can be solved with [http://wiki.linuxfromscratch.org/blfs/attachment/wiki/Cdrtools/cdrtools-2.01-mkisofs_iconv-10.patch?format=raw this patch]. It does the following:
    24 
    25  * Makes mkisofs accept any character set supported by iconv as the input character set
    26  * Changes the default input character set to the character set implied by the current locale
    27 
    28 The net effect is that creation of ISO images with Joliet extensions becomes possible in any locale, and the -input-charset switch becomes needed only in very exceptional situations.
    29 
    30 IMPORTANT: never report problems with charset set support directly to Joerg Schilling!
    31 
    32 ----
     5Joerg Schilling filed a [http://bugs.debian.org/361450 bug report] to Debian for including that patch. However, this patch is absolutely necessary for mkisofs to understand UTF-8 as an input encoding (and thus for creation of CDs with Windows-readable non-ASCII filenames in UTF-8 locales). Ignore that flame war, but never report problems with charset set support directly to Joerg Schilling!
    336
    347== Burn mp3s onto an Audio CD ==