[Pkg-cups-devel] Bug#416350: cupsys: [debconf_rewrite] Debconf templates review

[Christian Perrier]

Package: cupsys
Version: N/A
Severity: normal
Tags: patch

Dear Debian maintainer,

On Sunday, March 18, 2007, I notified you of the beginning of a review process
concerning debconf templates and package descriptions for cupsys.

The debian-l10n-english contributors have now reviewed these templates,
and the proposed changes are attached to this bug report.

Please review the suggested changes are suggested, and if you have any
objections, let me know in the next 3 days.

Please try to avoid uploading cupsys with these changes right now.

The second phase of this process will begin on Friday, March 30, 2007, when I will
coordinate updates to translations of debconf templates.

The existing translators will be notified of the changes: they will
receive an updated PO file for their language.

Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.

Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.

The call for translation updates and new translations will run until
Wednesday, April 11, 2007. Please avoid uploading a package with fixed or changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.

On Thursday, April 12, 2007, I will contact you again and will send a final patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).

Again, thanks for your attention and cooperation.


-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-4-486
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
-------------- next part --------------
--- /home/bubulle/travail/debian/rewrite/INTENT/cupsys/cupsys-1.2.7.old/debian/cupsys-bsd.templates	2007-03-20 06:13:11.636897121 +0100
+++ /home/bubulle/travail/debian/rewrite/INTENT/cupsys/cupsys-1.2.7/debian/cupsys-bsd.templates	2007-03-19 07:52:04.205054933 +0100
@@ -2,7 +2,7 @@
 Type: boolean
 Default: false
 _Description: Do you want to set up the BSD lpd compatibility server?
- This package contains a server that can accept BSD-style print jobs and
- submit them to CUPS. It should only be set up if you have other computers
- that submit jobs over the network via "BSD" or "LPR" services, and these
+ The CUPS package contains a server that can accept BSD-style print jobs and
+ submit them to CUPS. It should only be set up if other computers are
+ likely to submit jobs over the network via "BSD" or "LPR" services, and these
  computers cannot be converted to use the IPP protocol that CUPS uses.
--- /home/bubulle/travail/debian/rewrite/INTENT/cupsys/cupsys-1.2.7.old/debian/cupsys.templates	2007-03-20 06:13:09.868883592 +0100
+++ /home/bubulle/travail/debian/rewrite/INTENT/cupsys/cupsys-1.2.7/debian/cupsys.templates	2007-03-19 07:51:21.432728431 +0100
@@ -2,11 +2,12 @@
 Type: boolean
 Default: true
 _Description: Do you want CUPS to print unknown jobs as raw jobs?
- All print jobs in IPP get a MIME type. Since not all sources of print
- jobs can attach an appropriate type, many jobs get submitted as the MIME
- type application/octet-stream. Because of this, when CUPS receives a job
- with that MIME type, it attempts to guess what the format is. By default,
- if it cannot guess the proper type, it rejects the job.
+ The Internet Printing Protocol (IPP) enforces a MIME type for all
+ print jobs. Since not all sources of print jobs can attach an
+ appropriate type, many jobs get submitted as the MIME type
+ application/octet-stream. Because of this, when CUPS receives a job
+ with that MIME type, it attempts to guess what the format is. By
+ default, if it cannot guess the proper type, it rejects the job.
  .
  It is possible to cause CUPS to treat all unrecognized jobs with this MIME
  type as "raw" jobs, which causes them to be sent directly to the printer
@@ -14,7 +15,7 @@
  .
  If you will be accepting print jobs from Windows computers, you probably
  want this option set, as Windows gives all IPP print jobs processed by a
- local driver the MIME type application/octet-stream. Samba also submits
+ local driver the application/octet-stream MIME type. Samba also submits
  its print jobs this way.
 
 Template: cupsys/backend
@@ -22,10 +23,10 @@
 __Choices: ipp, lpd, parallel, scsi, serial, socket, usb, snmp
 Default: ipp, lpd, parallel, socket, usb
 _Description: Printer communication backends:
- CUPS uses backend programs for communication with printer device or port.
+ CUPS uses backend programs to communicate with the printer device or port.
  .
- Unfortunately, some backend programs cause some trouble.
- (For example, some PPC kernel crashes with the parallel backend)
+ Unfortunately, some backend programs are likely to cause some trouble.
+ For example, some PPC kernels crash with the parallel backend.
  .
  Please choose the backend program to be used by CUPS. The default choice
  should fit the most common environments.
--- /home/bubulle/travail/debian/rewrite/LCFC/cupsys/cupsys.old/debian/cupsys-bsd.templates	2007-03-20 06:13:11.636897121 +0100
+++ /home/bubulle/travail/debian/rewrite/LCFC/cupsys/cupsys/debian/cupsys-bsd.templates	2007-03-21 06:05:02.514207380 +0100
@@ -2,7 +2,8 @@
 Type: boolean
 Default: false
 _Description: Do you want to set up the BSD lpd compatibility server?
- This package contains a server that can accept BSD-style print jobs and
- submit them to CUPS. It should only be set up if you have other computers
- that submit jobs over the network via "BSD" or "LPR" services, and these
- computers cannot be converted to use the IPP protocol that CUPS uses.
+ The CUPS package contains a server that can accept BSD-style print
+ jobs and submit them to CUPS. It should only be set up if other
+ computers are likely to submit jobs over the network via the "BSD" or
+ "LPR" services, and these computers cannot be converted to use the
+ IPP protocol that CUPS uses.
--- /home/bubulle/travail/debian/rewrite/LCFC/cupsys/cupsys.old/debian/cupsys.templates	2007-03-20 06:13:09.868883592 +0100
+++ /home/bubulle/travail/debian/rewrite/LCFC/cupsys/cupsys/debian/cupsys.templates	2007-03-25 12:59:41.321730603 +0200
@@ -2,30 +2,27 @@
 Type: boolean
 Default: true
 _Description: Do you want CUPS to print unknown jobs as raw jobs?
- All print jobs in IPP get a MIME type. Since not all sources of print
- jobs can attach an appropriate type, many jobs get submitted as the MIME
- type application/octet-stream. Because of this, when CUPS receives a job
- with that MIME type, it attempts to guess what the format is. By default,
- if it cannot guess the proper type, it rejects the job.
+ The Internet Printing Protocol (IPP) enforces a MIME type for all
+ print jobs. Since not all sources of print jobs can attach an
+ appropriate type, many jobs get submitted as the MIME type
+ application/octet-stream and could be rejected if CUPS cannot guess
+ the job's format.
  .
- It is possible to cause CUPS to treat all unrecognized jobs with this MIME
- type as "raw" jobs, which causes them to be sent directly to the printer
- without processing.
+ CUPS can handle all such jobs as "raw" jobs, which causes them to be
+ sent directly to the printer without processing.
  .
- If you will be accepting print jobs from Windows computers, you probably
- want this option set, as Windows gives all IPP print jobs processed by a
- local driver the MIME type application/octet-stream. Samba also submits
- its print jobs this way.
+ It is recommended to choose this option if the server will be
+ accepting print jobs from Windows computers or Samba servers.
 
 Template: cupsys/backend
 Type: multiselect
 __Choices: ipp, lpd, parallel, scsi, serial, socket, usb, snmp
 Default: ipp, lpd, parallel, socket, usb
 _Description: Printer communication backends:
- CUPS uses backend programs for communication with printer device or port.
+ CUPS uses backend programs to communicate with the printer device or port.
  .
- Unfortunately, some backend programs cause some trouble.
- (For example, some PPC kernel crashes with the parallel backend)
+ Unfortunately, some backend programs are likely to cause some trouble.
+ For example, some PPC kernels crash with the parallel backend.
  .
  Please choose the backend program to be used by CUPS. The default choice
  should fit the most common environments.