> # SOME DESCRIPTIVE TITLE. > # Copyright (C) 2003-2008 Gerfried Fuchs <[EMAIL PROTECTED]> > # This file is distributed under the same license as the beep package. > # FIRST AUTHOR <[EMAIL PROTECTED]>, YEAR. > # > #, fuzzy > msgid "" > msgstr "" > "Project-Id-Version: beep 1.2.2-22\n" > "Report-Msgid-Bugs-To: [EMAIL PROTECTED]" > "POT-Creation-Date: 2008-07-28 19:33+0200\n" > "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" > "Last-Translator: FULL NAME <[EMAIL PROTECTED]>\n" > "Language-Team: LANGUAGE <[EMAIL PROTECTED]>\n" > "MIME-Version: 1.0\n" > "Content-Type: text/plain; charset=CHARSET\n" > "Content-Transfer-Encoding: 8bit\n" > > #. Type: select > #. Choices > #: ../templates:1001 > msgid "usable for all, usable for group audio, usable only for root" > msgstr ""
Small comment here: You may want to split out the Choices list so that it gets easier for translators to spot that this is not a sentence, but three different choices that will be presented to users as a list. So, for instance, in French, the translation should be: "Utilisable par tous, Utilisable par le groupe audio, Réservé au superutilisateur" (notice the capitals after the commas and the lack of final sentence dot) So, in the original templates file, you should replace: _Choices: usable for all, usable for group audio, usable only for root by: __Choices: usable for all, usable for group audio, usable only for root This way, each choice will go in its own string. Indeed, I just filed a BR against lintian for it to recommend the use of "__Choices" over "_Choices". *However*, if you do that, you'll break all translations. The trick to avoid this is described in po-debconf(7): Unfortunately if you decide to switch between these two forms, all translations become fuzzy. Here is an explanation to make this change without translation loss (it requires "po-debconf" >= 1.0). Suppose that we want to switch the previous example to "__Choices". You copy the templates file into a temporary file. $ cp debian/templates debian/foo Edit debian/foo and keep only "Template", "Type" and "_Choices" fields, which are in this example Template: debconf/frontend Type: select _Choices: Dialog, Readline, Gnome, Kde, Editor, Noninteractive Run debconf-gettextize with "--merge" and "--choices" flags to build PO files as if "__Choices" was written, and merge these PO files to existing ones: $ debconf-gettextize --merge --choices debian/foo Eventually you have to remove foo and manually edit debian/templates to replace "_Choices" by "__Choices" before debconf-updatepo is run. I strongly recommend checking PO files before and after the change (msgfmt -o /dev/null --statistics) . Those that were complete should still be complete. Otherwise, I'll hit you hard at DebConf..:-)
signature.asc
Description: Digital signature