Re: Bug#479302: Announce of the upcoming NMU for the dtc package
Hi Christian,
Please do not do any NMU concerning only translations if possible (I
don't know your imperatives, maybe you have to). If possible, please
send patches and bug reports against my package, so I can have my Git in
sync with Debian. Otherwise, it might be harder to track changes for us.
Note that our Git is always up-to-date regarding any bugs sent against
the package.
We have added lot's of improvements, and we are about to make a new
release of both dtc and dtc-xen. I will do my best so this is done soon
enough, so we have time to have a well-tested package uploaded before
Lenny. Maybe we will only send bug-fixes from Git to the current version
in order not to introduce new bugs: we would have to manage branching
then, and the translation updates would be sent there for the next
release. I hope we will find enough testers in Lenny then, as there's
quite a lot of things involved and needed to be tested.
Also, another topic more concerning the translation list. DTC is fully
internationalized, and translation of the software itself would be much
much appreciated. Our system is also using gettext, just like debconf,
so Debian translators will know how to translate. Here is a quick howto:
http://dtcsupport.gplhost.com/PmWiki/AddingTranslationToDTC
Here's the current status. The only template that is fully translated is
the French one as I'm French myself. However I'm not a good writer, so
checking would be appreciated to correct my faults. Out of currently
1298 strings:
hu_HU: 213 fuzzy, 801 not translated
it_IT: 205 fuzzy, 637 not translated
nl_NL: 74 fuzzy, 253 not translated
ru_RU: 35 fuzzy, 24 not translated
de_DE: 36 fuzzy, 27 not translated
zh_CN: 230 fuzzy, 427 not translated
pl_PL: 276 fuzzy, 560 not translated
pt_PT: 206 fuzzy, 807 not translated
es_ES: 209 fuzzy, 622 not translated
fi_FI: 39 fuzzy, 1058 not translated
zh_TW: 248 fuzzy, 685 not translated
Note that MANY of the strings are very small, and that some are only
country names. I have once found a site to help me doing translations
for them, but I didn't find it again. If you know any URL to help, let
me know.
The only difference that I saw in your attached template.po is:
-"Report-Msgid-Bugs-To: thomas@goirand.fr\n"
-"POT-Creation-Date: 2008-05-07 16:21+0800\n"
+"Report-Msgid-Bugs-To: dtc@packages.debian.org\n"
+"POT-Creation-Date: 2008-06-03 23:19+0200\n"
is that normal, and should I send this to our Git? I thought it was ok
the way it was, why should this change be made, would you mind
explaining it to me?
Thanks for your time and caring, like many, I appreciate your huge work
in Debian in general a lot.
Thomas
Christian Perrier wrote:
> Dear maintainer of dtc and Debian translators,
>
> Some days ago, I sent a notice to the maintainer of the dtc Debian
> package, mentioning the status of at least one old po-debconf translation update in the BTS.
>
> I announced the intent to build and possibly upload a non-maintainer upload
> for this package in order to fix this long-time pending localization
> bug as well as all other pending translations.
>
> The package maintainer agreed for the NMU or did not respond in two
> weeks, so I will proceed with the NMU.
>
> The full planned schedule is available at the end of this mail.
>
> The package is currently translated to:
> cs de es fi fr gl it ml nl pt pt_BR vi
>
> Among these, the following translations are incomplete: cs es it ml nl pt pt_BR
>
> 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 dtc package so I can incorporate them in the build.
>
> The deadline for receiving updates and new translations is Monday, June 23, 2008. If you
> are not in time you can always send your translation to the BTS.
>
> The POT file is attached to this mail.
>
> If the maintainer objects to this process I will immediately abort my NMU
> and send him/her all updates I receive.
>
> Otherwise the following will happen (or already has):
>
> Tuesday, June 03, 2008 : send the first intent to NMU notice to
> the package maintainer.
> Saturday, June 14, 2008 : send this notice
> Saturday, June 21, 2008 : (midnight) deadline for receiving translation updates
> Sunday, June 22, 2008 : build the package and upload it to DELAYED/2-day
> send the NMU patch to the BTS
> Tuesday, June 24, 2008 : NMU uploaded to incoming
>
> Thanks for your efforts and time.
Reply to: