Changes between Version 1 and Version 2 of Cdrtools


Ignore:
Timestamp:
02/13/2006 06:01:34 AM (16 years ago)
Author:
alexander@…
Comment:

[possibly illegal] added patch for proper display of cdrecord copyright notices

Legend:

Unmodified
Added
Removed
Modified
  • Cdrtools

    v1 v2  
    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 following commands to convert messages to ASCII approximations (e.g., "J<wrong or invalid character>rg Schilling" -> "Joerg Schilling"):
     3cdrecord 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.
    44
    55{{{
     
    1111}}}
    1212
    13 Note: 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.
     13The 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.
    1414
    1515[wiki:CDWritingUtilities Up][[br]]