Package: wodim Version: 5:1.0~pre4-1 Severity: minor Tags: patch
Found some typos in '/usr/share/man/man1/wodim.1.gz' and '/usr/share/man/man1/readcd.1.gz', see attached '.diff' files. Hope this helps... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.16-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages wodim depends on: ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libcap1 1:1.10-14 support for getting/setting POSIX. Versions of packages wodim recommends: ii mkisofs 5:1.0~pre4-1 Creates ISO-9660 CD-ROM filesystem -- debconf-show failed
--- wodim.1 2006-09-06 13:39:19.000000000 -0400 +++ /tmp/wodim.1 2006-09-10 16:10:11.000000000 -0400 @@ -63,12 +63,12 @@ .I device is the device file offered by the operating system to access the recorder. On .I Linux -systems it is usualy +systems it is usually .IR /dev/hd... for IDE/ATAPI based devices and .IR /dev/sg... -for SCSI based defices. Note that sg... devices represent the access trough the -SCSI GENERIC interface and therefore the differ from the device files generaly +for SCSI based devices. Note that sg... devices represent the access through the +SCSI GENERIC interface and therefore differ from the device files generally used to open block devices (/dev/scd... or /dev/sr...). .PP In any case, the user running @@ -78,7 +78,7 @@ certain versions of Linux (kernel) limit the set of SCSI commands allowed for non-root users and also the verbosity of the returned status codes. Even if usage without root identity is possible in many cases, some device drivers -still may fail, show unexplainable problems and generaly the problems are +still may fail, show unexplainable problems and generally the problems are harder to debug. The risk for buffer-underruns is also increased. .PP The alternative and kind of "portable" way is using the @@ -701,7 +701,7 @@ than 8 MB to write a CD at a speed less than 20x from an image on a local file system on an idle machine, your machine is either underpowered, has hardware problems or is mis-configured. -If you like to write DVDs or to write CDs at higher speed, it makes sense +If you like to write DVDs or CDs at high speed, it makes sense to use at least 16\ MB for the FIFO. .sp On old and small machines, you need to be more careful with the FIFO size. @@ -2353,7 +2353,7 @@ .TP 15 Joerg Schilling ([EMAIL PROTECTED]) .br -For writting cdrecord and libscg which represent the most part of wodim's code. +For writing cdrecord and libscg which represent the most part of wodim's code. .PP .TP 15 Bill Swartz ([EMAIL PROTECTED]) @@ -2412,7 +2412,7 @@ .SH AUTHORS .B wodim -is currently maintained as part of the cdrkit project by its developers. Most of the code and this manual page was originaly written by: +is currently maintained as part of the cdrkit project by its developers. Most of the code and this manual page was originally written by: .PP .nf Joerg Schilling @@ -2421,8 +2421,8 @@ Germany .fi .PP -Though beeing the original author and deserving the most credits for -successfull result, Joerg Schilling is no longer involved into the development +Though being the original author and deserving the most credits for +successful result, Joerg Schilling is no longer involved in the development of this application and therefore he shall not be made responsible for any problem caused by it. Do not refer to this application as "cdrecord", do not try to get support for wodim by contacting the original authors.
--- readcd.1 2006-09-06 13:39:19.000000000 -0400 +++ /tmp/readcd.1 2006-09-10 15:57:01.000000000 -0400 @@ -508,8 +508,8 @@ .fi .PP -Though beeing the original author and deserving the most credits for -successfull results, Joerg Schilling is no longer involved into the development +Though being the original author and deserving the most credits for +successful results, Joerg Schilling is no longer involved in the development of this application and therefore he shall not be made responsible for any problem caused by it. Do not try to get support by contacting the original author!
