[Pkg-shadow-devel] Translations : upstream or not?

[Christian Perrier]

>From IRC:

20:06 < christine> xrgtn: I see - so the source pulled from alioth is the=
 stuff that's only in
                   debian? I noticed that it doesn't contain the actual s=
ource, which is in the
                   shadow source package.
20:06 < xrgtn> regarding CVS/sid -- yes, there's only debian/ stuff.
20:10 < christine> so the translations can just be updated there too?
20:10 < xrgtn> Honestly, I didn't yet realizedwhy we ought to switch to S=
VN -- I felt quite
               comfortly with good old CVS. :) SVN scares me a bit.
20:10 < xrgtn> about translations I'm not sure -- they are in upstream to=
o
20:11 < christine> yeah.
20:11 < xrgtn> but possibly we have 2 sets: upstream+patches and our own =
(old/obsolete/lost in
               space ;)?)
20:12 < xrgtn> Better ask Christian -- I know close to nothing about tran=
slations...
20:13 < christine> righto. I have no problem hanging around for an answer=
. *g*
20:14 < xrgtn> Anyway, just trace how are the translations built:
20:15 < xrgtn> some of them are just upstream + patches
20:15 < xrgtn> others are our own
20:15 < xrgtn> christine: so, former require quilt/dpatch to operate on
20:15 < xrgtn> while latter should be modified in-SVN.
20:16 < christine> hmm, guess I can look at it.

OK, it seems that was is obvious to me may be less obvious...which is
pretty logical, after all. So let's explain and  apologies for having
not explained earlier.

In shadow, we have two sets of translations:

-"upstream" translations which are the translations of the programs
 messages, error output and command-line help.

 These pertain to upstream sources. They are in the po/ directory,
 in the source build tree.

 So, they initially comes from upstream's tar.gz file

 However, in Debian, we received a lot of translation updates, and new
 translations. So, as we want to keep the original source tree intact,
 we "patch" it with patches in debian/patches, at build time

 These are the 1xx series of patches, which all apply to po/*.po files

=20
-"debconf" translations, ie the translations of the debconf screens
 shown by the packages when they are installed with APT or dpkg.
 Actually, only the passwd binary package uses debconf. Just try
 "dpkg-reconfigure passwd" to see these screens.

 These have nothing to do with upstream, and live in debian/po. This
 is some Debian-specific stuff.

So, as Alex explained, the Debian-specific stuff just have to be
commited in debian/

This means that the mg.po file you have in the bug report should be
commited in place of the one which is already here, period.

And, of course, you update the changelog, adding a new entry with the
appropriate CLoses line

And finally, you tag the bug as "pending"

PS to Alex=A0: hey, using SVN is just like CVS...but faster and more
convenient ("svn mv foo bar" rocks).

--=20