-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Peter,

Le 09/09/2012 08:16, peter green a écrit :

>> On Monday, August 27, 2012, I notified you of the beginning of a review
>> process concerning debconf templates for fpc.

>> Please review the suggested changes, and if you have any objections, let
>> me know in the next 3 days.
>>   
> 3 days seems a bit on the short side. Especially when you have made a
> load of formatting changes that obscure changes to the actual text.

Sorry, it could have been extended, a lot, if you had asked for it. You
were in copy of the whole process, in the hope you could answer to some
interrogation too.

> Anyway having looked through it I don't see any obvious problems.

That's great then, thanks for the ACK.

> I'm kinda new to this whole translations buisness. What exactly should
> I do with the po files people send me to incorporate them in the package.

Simply include them in a debian/po/ directory. along with a
debian/po/POTFILES.in containing one single line:

[type: gettext/rfc822deb] fp-compiler.templates.in

and a debian/po/templates.pot file automatically generated with
debconf-updatepo. po-debconf(7) contains more detailed information.

I can propose you a complete debdiff with all translations at the end of
the translation call. Since eight of them are aiming for 100 % debconf
screen translated, I also intend to make sure they will be up to date
(fr ru de pt sv cs es da) before the upload. Because the BTS may brake
some encoding (see #666202), please make sure no invalid-po-file lintian
warning is triggered if you include the PO files yourself (“iconv -f
latin1 -t utf8 $file | sponge $file” should be all you need to fix such
file).

Regards

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQTJ2bAAoJELgqIXr9/gnyGrQQAJzHzY84KNo00nbjwrwvd8Xx
nF/9G/tz8ajR7cXY5BCfdaTNbu9WBfhfHg1ewT4QcxW8eRSZqbZoTm8H9U2NggdB
gTlql62L01Hwr4o8BXRGf4oLLVZ3kyjHcMXJscPpR9xoIoKkmJNX69dwKx9n3RcV
pySGBXRyU3iHe2nVpTszoJO8GS5jtiadLLWOlYS5pB7443sZx+PgGX3VK+U/26VY
Nskin1ymDxUVCh7GVgfbZhBy24ReC1xCehyrS1oYpF9bSQ/lCphq2K5mIYelooLC
GOp/p50KZUdMhEjMqZGe9hv4dHMvrTbktFytKs1POuYUTh2l8dd4DBQh8iRDTpcE
zmXExQSo5m2se/2d8LnwXG4WdyV8JJ8a40ILenzmzMzAalsBzp/FzgoKFYxP9P99
dRTsiOIQcp7WpkE59jjwXWawSmA1oAJK0+y91hJwLCzJMhe6jO0VeGqJL/tuKzOI
OTYI7QUmu/KxqE7A4quOZSMr1yo1xyMk5f/gE5CNaKA8kh10X5u810tkxvRK8o+d
0BxAMgIRcjhnHTVjSA71V1ez/7G3Tl8x1AJVL6n1WdB5++bgqxHxGVkcEm/3jnYv
cYkUK6ej7iF4GzcgqVS02GzUUwYl6IrTa50RBjFyqNyy6MW83Y4XlgQZ2n5WF2hA
ln+XaDFdUGrM7tEnkoYs
=334e
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to