[Pkg-lirc-maint] Bug#443270: lirc: General update after the debconf review process

Christian Perrier bubulle at debian.org
Wed Oct 10 05:16:22 UTC 2007


Dear Debian maintainer,

On Thursday, September 06, 2007, I sent you a notification about the beginning of a review
action on debconf templates for lirc.

Then, I sent you a bug report with rewritten templates and announcing
the beginning of the second phase of this action: call for translation
updates.

Translators have been working hard and here is now the result of their efforts.

Please consider using it EVEN if you committed files to your
development tree as long as they were reported.

The attached tarball contains:

- debian/changelog with the list of changes
- debian/control with rewrites of packages' descriptions
- debian/<templates> with all the rewritten templates file(s)
- debian/po/*.po with all PO files (existing ones and new ones)

As said, please use *at least* the PO files as provided here,
preferrably over those sent by translators in their bug reports. All
of them have been checked and reformatted. In some cases, formatting
errors have been corrected.

The patch-nopo file contains a patch for the templates and control file(s).

Please note that this patch applies to the templates and control
file(s) of your package as of Thursday, September 06, 2007. If your package was updated
in the meantime, I may have updated my reference copy....but I also
may have missed that. This is indeed why I suggested you do not
modified such files while the review process was running,
remember..:-)

It is now safe to upload a new package version with these changes.

Please notify me of your intents with regards to this. 

There is of course no hurry to update your package but feel free to
contact me in case you would need sponsoring or any other action to
fix this.



-- 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch.tar.gz
Type: application/octet-stream
Size: 54448 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-lirc-maint/attachments/20071010/f98067dd/attachment-0001.obj 
-------------- next part --------------
--- lirc.old/debian/lirc-modules-source.templates	2007-09-05 06:09:02.867100598 +0200
+++ lirc/debian/lirc-modules-source.templates	2007-09-20 07:06:07.353127800 +0200
@@ -1,3 +1,12 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-english at lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
 Template: lirc-modules-source/drivers
 Type: multiselect
 Choices: atiusb, bt829, cmdir, gpio, i2c, igorplugusb, imon, it87, mceusb, mceusb2, parallel, sasem, serial, sir, streamzap
@@ -10,7 +19,7 @@
   i2c:         TV cards from Hauppauge and PixelView
   igorplugusb: Igor Cesko's USB IR Receiver
   imon:        Soundgraph iMON MultiMedian IR/VFD
-  it87:        ITE IT8705/12 CIR ports (e.g. on the ECS K7S5A or Asus DigiMatrix)
+  it87:        ITE IT8705/12 CIR ports (ECS K7S5A, Asus DigiMatrix...)
   mceusb:      Windows Media Center Remotes (old version, MicroSoft USB ID)
   mceusb2:     Windows Media Center Remotes (new version, Philips et al.)
   parallel:    Home-brew parallel-port receiver
@@ -22,23 +31,27 @@
 Template: lirc-modules-source/use_lirc_hints
 Type: boolean
 Default: true
-_Description: Try to automagically select support for your hardware?
- You have installed and configured LIRC. It is possible to guess what kernel
- modules are needed and their parameters from your previous answers.
+_Description: Try to automatically select hardware support options?
+ Your previous answers can be used as a basis for guessing the list of
+ kernel modules that should be built, along with their parameters.
+ .
+ Please choose whether this should happen.
 
 Template: lirc-modules-source/not_needed
 Type: note
-_Description: You don't need any additional kernel modules
- Unless you want to build LIRC kernel modules for some other system, you
- can probably remove this package.
+_Description: Additional kernel modules not needed
+ Unless you want to build LIRC kernel modules for another system,
+ this package is useless on this system.
 
 Template: lirc-modules-source/what_next
 Type: note
-_Description: How to build the binary modules package
- For instructions on how to build the binary modules debian package read:
- /usr/share/doc/lirc-modules-source/README.Debian
+#flag:translate!:4
+_Description: Binary modules package build instructions
+ For instructions on how to build the binary modules package, please
+ read the /usr/share/doc/lirc-modules-source/README.Debian file.
  .
  Quick walkthrough:
+ .
   cd /usr/src/
   tar -xzf lirc-modules.tar.gz
   cd modules/lirc
@@ -47,34 +60,31 @@
 
 Template: lirc-modules-source/it87_type
 Type: select
-_Choices: Standard, DigiMatrix
+#flag:translate:1
+__Choices: Standard, DigiMatrix
 Default: Standard
 _Description: Type of ITE8705/12 CIR port to support:
- The following list includes short descriptions of the different options
- available:
+ Please choose the supported ITE8705/12 CIR port chip:
  .
-  Standard:   Standard setup chip
-  DigiMatrix: Setup for Asus DigiMatrix onboard chip
+  Standard:   Standard setup chip;
+  DigiMatrix: Setup for Asus DigiMatrix onboard chip.
 
 Template: lirc-modules-source/serial_type
 Type: select
-_Choices: ANIMAX, IRDEO, Other
+#flag:translate:3
+__Choices: ANIMAX, IRDEO, Other
 Default: Other
-_Description: Type of serial device to support
- The following list includes short descriptions of the different options
- available:
+_Description: Serial device to support:
+ Please choose the supported serial device type:
  .
-  ANIMAX: Anir Multimedia Magic
-  IRDEO:  IRdeo
+  ANIMAX: Anir Multimedia Magic;
+  IRDEO:  IRdeo;
   Other:  Any other supported device.
-   
- If you don't know what the other devices are, you should probably choose
- "Other".
 
 Template: lirc-modules-source/serial_transmitter
 Type: boolean
 Default: true
-_Description: Is your serial IR device a transmitter?
+_Description: Is the serial IR device a transmitter?
 
 Template: lirc-modules-source/serial_softcarrier
 Type: boolean
@@ -84,66 +94,67 @@
 Template: lirc-modules-source/serial_port
 Type: string
 Default: 0x2f8
-_Description: IO port of your IR serial device:
+_Description: IR serial device I/O port:
 
 Template: lirc-modules-source/serial_irq
 Type: string
 Default: 3
-_Description: IRQ of your IR serial device:
+_Description: IR serial device IRQ:
 
 Template: lirc-modules-source/sir_type
 Type: select
-_Choices: ACTISYS_ACT200L, TEKRAM, Other
+#flag:translate:3
+__Choices: ACTISYS_ACT200L, TEKRAM, Other
 Default: Other
-_Description: What type of SIR device should be supported?
- The following lists are short descriptions of the options to show what
- they mean.
+_Description: Type of supported SIR device:
+ Please choose the supported SIR device type:
  .
-  ACTISYS_ACT200L: Actisys Act200L dongle.
-  TEKRAM:          Tekram Irmate 210 (16x50 UART compatible serial port)
+  ACTISYS_ACT200L: Actisys Act200L dongle;
+  TEKRAM:          Tekram Irmate 210 (16x50 UART compatible serial port);
   Other:           Any other supported device.
 
 Template: lirc-modules-source/sir_port
 Type: string
 Default: 0x2f8
-_Description: IO port of your SIR device:
+_Description: SIR device I/O port:
 
 Template: lirc-modules-source/sir_irq
 Type: string
 Default: 3
-_Description: IRQ of your SIR device:
+_Description: SIR device IRQ:
 
 Template: lirc-modules-source/parallel_port
 Type: string
 Default: 0x378
-_Description: IO port of your parallel IR device:
+_Description: Parallel IR device I/O port:
 
 Template: lirc-modules-source/parallel_irq
 Type: string
 Default: 7
-_Description: IRQ of your parallel IR device:
+_Description: Parallel IR device IRQ:
 
 Template: lirc-modules-source/parallel_timer
 Type: string
 Default: 65536
-_Description: Timer used for your parallel IR device:
+_Description: Parallel IR device timer:
 
 Template: lirc-modules-source/do-build
 Type: boolean
 Default: false
-_Description: Try to automatically build the modules?
- It is possible to build and install your lirc kernel modules, as long as your
- current kernel's source (and gcc) are present on your computer.
+_Description: Automatically build the modules?
+ New LIRC kernel modules can be built and installed if the source and
+ build environment for the current kernel are present locally.
  .
- Even if you choose to dos so, you should build and install a binary 'kernel
+ Even if you choose this option, you should build and install a binary 'kernel
  modules' package so that the package manager can keep track of the files.
 
 Template: lirc-modules-source/kernel-source
 Type: string
 Default: /usr/src/linux/
-_Description: Where is your kernel source?
- To build lirc kernel modules, kernel sources are needed.
+_Description: Kernel source location:
+ Please enter the location of the kernel source tree, to build the
+ lirc kernel modules.
 
 Template: lirc-modules-source/kernel-source-not-found
-Type: note
-_Description: ${ksrc} is not a valid kernel source tree
+Type: error
+_Description: ${ksrc}: invalid kernel source tree
--- lirc.old/debian/lirc.templates	2007-09-05 06:09:02.867100598 +0200
+++ lirc/debian/lirc.templates	2007-09-20 07:06:07.853101798 +0200
@@ -1,95 +1,95 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-english at lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
 Template: lirc/install_devices
 Type: boolean
 Default: true
 _Description: Create LIRC device nodes if they are not there?
- LIRC needs some files under /dev/ for it to work:
+ LIRC needs the /dev/lirc, /dev/lircd and /dev/lircm files in /dev.
  .
- /dev/lirc  /dev/lircd and /dev/lircm
+ 
 
 Template: lirc/reconfigure
 Type: boolean
 Default: false
 _Description: Do you want to reconfigure LIRC?
- LIRC is already configured, reconfiguring it may spoil some of your
- handcrafted configuration in /etc/lirc/hardware.conf.
+ LIRC is already configured, reconfiguring it may overwrite the
+ existing configuration in /etc/lirc/hardware.conf.
  .
- However comments, LIRC_ARGS and other unknown code will be preserved.
+ However, comments, LIRC_ARGS and other unknown code will be preserved.
 
 Template: lirc/take_care_of_old_config
 Type: note
-_Description: You should take care of old configuration files
- Previous versions of this package didn't include any configuration file
- and expected the user to put his own /etc/lircd.conf and /etc/lircmd.conf
+_Description: Old configuration files found
+ Previous versions of this package didn't include any configuration
+ file and expected users to create their own /etc/lircd.conf and
+ /etc/lircmd.conf.
  .
  The new location for these files is /etc/lirc/.
  .
- Things will be arranged properly but, in case they can't be, please make
- sure that none of LIRC configuration files are left directly under /etc/.
+ File locations will be corrected but you should check that none of
+ LIRC configuration files are left directly under /etc/.
 
 Template: lirc/driver
 Type: string
 Description: Driver name for lircd:
- You should not see this template as it is used internally by the
- maintainer scripts, please report this as a bug.
+ for internal use only
 
 Template: lirc/modules
 Type: string
 Description: Needed kernel modules for LIRC to work:
- You should not see this template as it is used internally by the
- maintainer scripts, please report this as a bug.
+ for internal use only
 
 Template: lirc/device
 Type: string
 Description: Device node for lircd:
- You should not see this template as it is used internally by the
- maintainer scripts, please report this as a bug.
+ for internal use only
 
 Template: lirc/lircd_conf
 Type: string
 Description: Recommended configuration file for lircd:
- You should not see this template as it is used internally by the
- maintainer scripts, please report this as a bug.
+ for internal use only
 
 Template: lirc/lircmd_conf
 Type: string
 Description: Recommended configuration file for lircmd:
- You should not see this template as it is used internally by the
- maintainer scripts, please report this as a bug.
+ for internal use only
 
 Template: lirc/port
 Type: string
 Description: Hint for lirc-modules-source:
- You should not see this template as it is used internally by the
- maintainer scripts, please report this as a bug.
+ for internal use only
 
 Template: lirc/irq
 Type: string
 Description: Hint for lirc-modules-source:
- You should not see this template as it is used internally by the
- maintainer scripts, please report this as a bug.
+ for internal use only
 
 Template: lirc/timer
 Type: string
 Description: Hint for lirc-modules-source:
- You should not see this template as it is used internally by the
- maintainer scripts, please report this as a bug.
+ for internal use only
 
 Template: lirc/cflags
 Type: string
 Description: Hint for lirc-modules-source:
- You should not see this template as it is used internally by the
- maintainer scripts, please report this as a bug.
+ for internal use only
 
 Template: lirc/should-use-IntelliMouse
 Type: note
-_Description: lircmd should use the IntelliMouse protocol instead of IMPS/2
- The method lircmd uses to simulate a mouse is not compatible with IMPS/2
- protocol, so the IntelliMouse support has been added and is now the
- preferred protocol.
- .
- You ARE currently using lircmd with IMPS/2 protocol and are encouraged to
- update /etc/lirc/lircmd.conf and the configuration of any program which
- uses lircmd as a mouse to use IntelliMouse protocol.
+_Description: IntelliMouse protocol preferred over IMPS/2
+ You are currently using lircmd with the IMPS/2 protocol. This is not
+ compatible with the method lircmd uses to simulate a mouse, so IntelliMouse
+ support has been added and is now the preferred protocol.
+ .
+ You should update /etc/lirc/lircmd.conf and the configuration of any program
+ which uses lircmd as a mouse to use the IntelliMouse protocol instead.
  .
  NOTE: gpm will refuse to use lircmd as a mouse with IMPS/2 protocol.
 
@@ -97,8 +97,5 @@
 Type: boolean
 Default: true
 _Description: Delete /var/log/lircd?
- LIRC now uses syslog as a logging mechanism. This means that
- /var/log/lircd is not anymore pertinent.
- .
- If you answer 'no' to this question /var/log/lircd will be left there and
- you will have to take care of it yourself.
+ LIRC now uses syslog as a logging mechanism, so /var/log/lircd is no longer
+ relevant.
--- lirc.old/debian/control	2007-09-05 06:09:02.867100598 +0200
+++ lirc/debian/control	2007-09-17 22:00:49.155135558 +0200
@@ -30,7 +30,9 @@
 Suggests: lirc-modules-source,
           lirc-x,
           lirc-svga
-Description: Linux Infra-red Remote Control support
+Description: infra-red remote control support
+ LIRC stands for 'Linux Infra-red Remote Control'.
+ .
  This package provides the daemons and some utilities to support infra-red
  remote controls under Linux.
 
@@ -41,21 +43,13 @@
          lirc (= ${binary:Version})
 Replaces: lirc (<< 0.6.4-8)
 Recommends: xfonts-75dpi
-Description: Linux Infra-red Remote Control support (X dependent parts)
- This package provides those parts of lirc which depend on the XWindow system.
- .
- Currently:
- .
- irxevent: Allows you to control your X applications with your remote control.
+Description: infra-red remote control support - X utilities
+ LIRC stands for 'Linux Infra-red Remote Control'.
  .
- xmode2: shows the IR waveform of the remote controller without an expensive
- oscilloscope (through an X window). This is not needed for TV cards or the
- Irman.
- .
- You ***MUST*** <--- (really!) have the xfonts-75dpi package available on the
- X server, whether via files or via a font server like xfs. The lirc-x package
- only Recommends: these packages because it's possible to have them served
- remotely, but you really should install them. :)
+ This package provides X utilities for LIRC:
+  irxevent: allows controlling X applications with a remote control;
+  xmode2  : shows the IR waveform of the remote controller without an
+            oscilloscope. Unneeded for TV cards or the Irman.
 
 Package: lirc-svga
 Architecture: amd64 i386
@@ -63,13 +57,12 @@
          ${misc:Depends},
          lirc (= ${binary:Version})
 Replaces: lirc (<< 0.6.4-8)
-Description: Linux Infra-red Remote Control support (svgalib dependent parts)
- This package provides those parts of lirc which depend on svgalib .
- .
- Currently:
+Description: infra-red remote control support - SVGAlib utilities
+ LIRC stands for 'Linux Infra-red Remote Control'.
  .
- smode2: shows the IR waveform of the remote controller without an expensive
- oscilloscope (through svgalib). This is not needed for TV cards or the Irman.
+ This package provides SVGAlib utilities for LIRC:
+  smode2: shows the IR waveform of the remote controller without an
+          oscilloscope. Unneeded for TV cards or the Irman.
 
 Package: lirc-modules-source
 Architecture: all
@@ -83,12 +76,13 @@
             kernel-package
 Suggests: kernel-source
 Conflicts: lirc (<<0.6.3-1)
-Description: Linux Infra-red Remote Control support (kernel modules)
+Description: infra-red remote control support - kernel modules
+ LIRC stands for 'Linux Infra-red Remote Control'.
+ .
  This package provides the source for the kernel modules to support
  infra-red remote controls under Linux.
  .
- Please note that the kernel sources must be installed to compile these
- modules.
+ The kernel sources must be installed to compile these modules.
 
 Package: liblircclient-dev
 Architecture: any
@@ -96,11 +90,11 @@
 Depends: ${misc:Depends},
          liblircclient0 (= ${binary:Version}),
          libc6-dev
-Description: development files for LIRC client library
+Description: infra-red remote control support - client library development files
+ LIRC stands for 'Linux Infra-red Remote Control'.
+ .
  This package contains the static library and headers for
  the LIRC client library.
- .
- LIRC is Linux Infra-red Remote Control support.
 
 Package: liblircclient0
 Priority: optional
@@ -109,6 +103,9 @@
 Depends: ${shlibs:Depends},
          ${misc:Depends}
 Suggests: lirc
-Description: LIRC client library
- This library provides functions so that other programs (eg xawtv)
- can support remote controls via LIRC.
+Description: infra-red remote control support - client library
+ LIRC stands for 'Linux Infra-red Remote Control'.
+ .
+ This package provides a library with functions to support remote
+ controls via LIRC in programs such as xawtv.
+
--- lirc.old/debian/changelog	2007-09-05 06:09:02.867100598 +0200
+++ lirc/debian/changelog	2007-10-08 07:44:32.939215069 +0200
@@ -1,3 +1,22 @@
+lirc (0.8.0-13) UNRELEASED; urgency=low
+
+  * Debconf templates and debian/control reviewed by the debian-l10n-
+    english team as part of the Smith review project. Closes: #443270, #443470
+    (the latter bug is about outdated translations)
+  [Debconf translation updates]
+  * Japanese. Closes: #444091
+  * Vietnamese. Closes: #444436
+  * Galician. Closes: #444752
+  * Russian. Closes: #445426
+  * German. Closes: #445556
+  * French. Closes: #445587
+  * Finnish. Closes: #445650
+  * Portuguese. Closes: #445653
+  * Brazilian Portuguese. Closes: #445736
+  * Czech. Closes: #445655
+
+ -- Christian Perrier <bubulle at debian.org>  Mon, 08 Oct 2007 07:44:32 +0200
+
 lirc (0.8.0-12) unstable; urgency=medium
 
   * Fix bashism in rules; thanks Martin F Krafft; closes: #437530.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-lirc-maint/attachments/20071010/f98067dd/attachment-0001.pgp 


More information about the Pkg-lirc-maint mailing list