Changes between Version 1 and Version 2 of Cdrtools
- Timestamp:
- 02/13/2006 06:01:34 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Cdrtools
v1 v2 1 1 = Cdrtools = 2 2 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"):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. 4 4 5 5 {{{ … … 11 11 }}} 12 12 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.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 14 15 15 [wiki:CDWritingUtilities Up][[br]]