[cl-debian] Bug#457305: Announce of an upcoming upload for the common-lisp-controller package
Dear maintainer of common-lisp-controller and Debian translators, Some days ago, I sent a notice to the maintainer of the common-lisp-controller Debian package, mentioning the status of at least one old po-debconf translation update in the BTS. The package maintainer and I agreed for a translation update round. At the end of this period, I will send him|her a full patch so that an l10n upload can happen. The full planned schedule is available at the end of this mail. The package is currently translated to: cs de es fi fr gl nl pt ru sv vi Among these, the following translations are incomplete: es nl sv If you did any of the, currently incomplete, translations you will get ANOTHER mail with the translation to update. Other translators also have the opportunity to create new translations for this package. Once completed, please send them as a bug report against the common-lisp-controller package so I can incorporate them in the build. The deadline for receiving updates and new translations is Thursday, June 19, 2008. If you are not in time you can always send your translation to the BTS. The POT file is attached to this mail. Schedule: Friday, June 06, 2008 : send the first intent to NMU notice to the package maintainer. Tuesday, June 10, 2008 : send this notice Thursday, June 19, 2008 : (midnight) deadline for receiving translation updates Friday, June 20, 2008 : Send a summary to the maintainer. Maintainer uploads when possible. Thanks for your efforts and time. -- --
Hi Christian! On Tue, 10 Jun 2008 18:10:12 +0200, Christian Perrier wrote:
The package maintainer and I agreed for a translation update round. At the end of this period, I will send him|her a full patch so that an l10n upload can happen. The full planned schedule is available at the end of this mail.
Continuing the package cleanup, I found a lintian warning about debconf: ===== W: common-lisp-controller source: translated-default-field templates: 13 N: N: You should not mark as translatable "Default:" or "DefaultChoice:" N: fields, unless explicitly needed (e.g. default country, default N: language, etc.). If this Default field really should be translated, N: you should explain translators how they should translate it by using N: brackets. For example: N: N: _Default: English[ Default language name, but not translated] N: N: Refer to the po-debconf(7) manual page for details. N: ===== It seems that the patch below is enough for lintian to be happy, but I'm not a debconf/translation expert, so I'm here looking for help. FWIW, I also included the removal of a trailing space at the end of a line. AFAIK changing a debconf template requires new checkout for the translations, I guess that combining both (lintian fix and removal) will demand less burden for translators. --8<---------------cut here---------------start------------->8--- diff --git a/debian/templates b/debian/templates index 3e67b49..d885a2b 100644 --- a/debian/templates +++ b/debian/templates @@ -10,17 +10,17 @@ Template: common-lisp-controller/short-site-name Type: string # Default site name -_Default: Unknown +Default: Unknown _Description: Short Common Lisp site name: You can configure what the Common Lisp implementations are going to use as - 'short site name'. + 'short site name'. . This is mostly unused except in some error reporting tools. Template: common-lisp-controller/long-site-name Type: string # Default long site name, just something longer than th default site name -_Default: Site name not initialized +Default: Site name not initialized _Description: Long Common Lisp site name: You can configure what the Common Lisp implementations are going to use as 'long site name'. --8<---------------cut here---------------end--------------->8--- Thx, bye, Gismo / Luca
Quoting Luca Capello (luca@pca.it):
Continuing the package cleanup, I found a lintian warning about debconf:
===== W: common-lisp-controller source: translated-default-field templates: 13 N: N: You should not mark as translatable "Default:" or "DefaultChoice:" N: fields, unless explicitly needed (e.g. default country, default N: language, etc.). If this Default field really should be translated, N: you should explain translators how they should translate it by using N: brackets. For example: N: N: _Default: English[ Default language name, but not translated] N: N: Refer to the po-debconf(7) manual page for details. N: =====
It seems that the patch below is enough for lintian to be happy, but I'm not a debconf/translation expert, so I'm here looking for help.
FWIW, I also included the removal of a trailing space at the end of a line. AFAIK changing a debconf template requires new checkout for the translations, I guess that combining both (lintian fix and removal) will demand less burden for translators.
--8<---------------cut here---------------start------------->8--- diff --git a/debian/templates b/debian/templates index 3e67b49..d885a2b 100644 --- a/debian/templates +++ b/debian/templates @@ -10,17 +10,17 @@ Template: common-lisp-controller/short-site-name Type: string # Default site name -_Default: Unknown +Default: Unknown
I think that having a translated Default here makes sense. It means that French users would for instance get "Inconnu" (French for "Unknown") as default value for that setting, which is correct. That warning could, imho, deserve a lintian override. Very often, translatable Default value do *not* make sense, that's why the lintian warning is here.
Hi Christian! On Wed, 11 Jun 2008 07:19:41 +0200, Christian Perrier wrote:
Quoting Luca Capello (luca@pca.it):
Continuing the package cleanup, I found a lintian warning about debconf:
===== W: common-lisp-controller source: translated-default-field templates: 13 [...]
I think that having a translated Default here makes sense. It means that French users would for instance get "Inconnu" (French for "Unknown") as default value for that setting, which is correct.
That warning could, imho, deserve a lintian override.
Fully ACK, done with commit 64f331fd0dba968b7ef909a51d979a9352a0e2bf: http://git.debian.org/?p=pkg-common-lisp/common-lisp-controller.git;a=commit... BTW, I now found another typo in debian/templates: --8<---------------cut here---------------start------------->8--- diff --git a/debian/templates b/debian/templates index 3e67b49..9531aa0 100644 --- a/debian/templates +++ b/debian/templates @@ -13,13 +13,13 @@ Type: string _Default: Unknown _Description: Short Common Lisp site name: You can configure what the Common Lisp implementations are going to use as - 'short site name'. + 'short site name'. . This is mostly unused except in some error reporting tools. Template: common-lisp-controller/long-site-name Type: string -# Default long site name, just something longer than th default site name +# Default long site name, just something longer than the default site name _Default: Site name not initialized _Description: Long Common Lisp site name: You can configure what the Common Lisp implementations are going to use as --8<---------------cut here---------------end--------------->8--- Could I commit it or should I wait until all the translations arrive? Thx, bye, Gismo / Luca
Quoting Luca Capello (luca@pca.it):
BTW, I now found another typo in debian/templates:
--8<---------------cut here---------------start------------->8--- diff --git a/debian/templates b/debian/templates index 3e67b49..9531aa0 100644 --- a/debian/templates +++ b/debian/templates @@ -13,13 +13,13 @@ Type: string _Default: Unknown _Description: Short Common Lisp site name: You can configure what the Common Lisp implementations are going to use as - 'short site name'. + 'short site name'.
Hmmmm, don't commit that blindly. You'll fuzzy all translations. And, *then* I'll hate you..:-) To avoid that, you need to change all translations in order to remove the extra trailing space *before* running debconf-updatepo. Or just wait for me to send you the final patch with unfuzzied PO files.
. This is mostly unused except in some error reporting tools.
Template: common-lisp-controller/long-site-name Type: string -# Default long site name, just something longer than th default site name +# Default long site name, just something longer than the default site name
That one can be applied blindly as this is just a comment.
Hi Christian! On Thu, 12 Jun 2008 20:16:18 +0200, Christian Perrier wrote:
Quoting Luca Capello (luca@pca.it):
BTW, I now found another typo in debian/templates: [...] _Description: Short Common Lisp site name: You can configure what the Common Lisp implementations are going to use as - 'short site name'. + 'short site name'.
Hmmmm, don't commit that blindly. You'll fuzzy all translations. And, *then* I'll hate you..:-)
Ehm, for sure I don't want to ;-)
Or just wait for me to send you the final patch with unfuzzied PO files.
I'll wait, it's a minor issue.
Template: common-lisp-controller/long-site-name Type: string -# Default long site name, just something longer than th default site name +# Default long site name, just something longer than the default site name
That one can be applied blindly as this is just a comment.
Since it seems that simply correcting this generates changes in every debian/po/ file, I'll commit together with the above one, no hurry. Thx, bye, Gismo / Luca
Quoting Christian Perrier (bubulle@debian.org):
To avoid that, you need to change all translations in order to remove the extra trailing space *before* running debconf-updatepo.
Or just wait for me to send you the final patch with unfuzzied PO files.
The end of the translation update round is now over. Here's a tarball with the corrected templates file and the content of debian/po with unfuzzied PO(T) files. So, I hereby consider the work on c-l-c l10n finished.
Hi Christian! On Thu, 19 Jun 2008 08:18:57 +0200, Christian Perrier wrote:
The end of the translation update round is now over.
Here's a tarball with the corrected templates file and the content of debian/po with unfuzzied PO(T) files.
The template file has been corrected [1], for the other files there are three small problems (but read below): - fr.po: line 40, char 1, byte offset 38: invalid UTF-8 code This is caused by the space before the punctuation, either we remove it or we replace with a real space. Other problems are at lines 50 (both spaces and «»), 73 (space) and 83 (spaces and «»). - nl.po: line 65, char 1, byte offset 25: invalid UTF-8 code Caused by the ï, easily replaceable. Same problem at line 104 (ë) and 119 (ï again). However, this file contains a lot of comments, which seems useless: should we remove them? - sv.po: line 33, char 1, byte offset 11: invalid UTF-8 code Caused by the ä, same at line 50-51 (ä again), 74 (å) and 84-85 (ä again). Now, these three files contain a Content-Type declaration, specifying their own charset. I'm not a debconf expert, but since UTF-8 is the default since etch, shouldn't these files be encoded in UTF-8?
So, I hereby consider the work on c-l-c l10n finished.
Thank you again for your support. Thx, bye, Gismo / Luca Footnotes: [1] http://git.debian.org/?p=pkg-common-lisp/common-lisp-controller.git;a=commit...
Quoting Luca Capello (luca@pca.it):
The template file has been corrected [1], for the other files there are three small problems (but read below):
- fr.po: line 40, char 1, byte offset 38: invalid UTF-8 code
This is caused by the space before the punctuation, either we remove it or we replace with a real space. Other problems are at lines 50 (both spaces and «»), 73 (space) and 83 (spaces and «»).
I have no such probles with my file. The file is encoded in ISO-8859-1, not UTF-8. So you can't (and must not) check them with an UTF-8 checker.
- nl.po: line 65, char 1, byte offset 25: invalid UTF-8 code
Caused by the ï, easily replaceable. Same problem at line 104 (ë) and 119 (ï again).
However, this file contains a lot of comments, which seems uselessz: should we remove them?
Ditto
- sv.po: line 33, char 1, byte offset 11: invalid UTF-8 code
Caused by the ä, same at line 50-51 (ä again), 74 (å) and 84-85 (ä again).
Now, these three files contain a Content-Type declaration, specifying their own charset. I'm not a debconf expert, but since UTF-8 is the default since etch, shouldn't these files be encoded in UTF-8?
Not necessarily. Even if files are ISO-encoded, there shouldn't be any problem
Hi Christian! On Fri, 20 Jun 2008 18:15:09 +0200, Christian Perrier wrote:
The file is encoded in ISO-8859-1, not UTF-8. So you can't (and must not) check them with an UTF-8 checker. [...] Not necessarily. Even if files are ISO-encoded, there shouldn't be any problem
So they're in [1]! Thx, bye, Gismo / Luca Footnotes: [1] http://git.debian.org/?p=pkg-common-lisp/common-lisp-controller.git;a=commit...
participants (2)
-
Christian Perrier -
Luca Capello