-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 29 Sep 2009, Chris Lumens wrote:
Since we have to store anaconda.pot in the source tree for the
translators, make sure we update it when bumpver is run so it stays
current.
When you run 'make bumpver', you will now be checking in at least two
files but up to three:
anaconda.spec.in [required]
configure.ac [required]
po/anaconda.pot [optional, only if it needed updating]
Make sure you add all of these files for 'New version' commits.
Do you know how big the expected commits for this are supposed to be?
Are we talking tons of changes every time or not?
The changes would be dependent on what strings we change. Most of the time
it's line number reference changes in the pot file comments.
I'm trying to come up with an automated way to keep the pot file in sync with
the source code and this seemed reasonable.
I'm no i18n expert, but I'm okay with this as long as everyone knows
we're going to have to continue being very careful with our string
changes.
I don't think we have to change anything that we're currently doing. The pot
file update process brings the template in sync with the current code. So if
a string shifts up or down a few lines, the line number reference is changed
in the template file. Or if the string is changed entirely which we do on
occassion we'll pick up the new string in the template file.
- --
David Cantrell <dcantrell@xxxxxxxxxx>
Red Hat / Honolulu, HI
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkrCadUACgkQ5hsjjIy1VkmU3QCgxPxCOQb04OhA89OBO3eiYPfk
dy4AoLWEVUutPKB/akJk4HDEcq5D18Pw
=Zue2
-----END PGP SIGNATURE-----
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
