[Pkg-isocodes-devel] [pkg-isocodes-Bugs][314317] iso-code POT template versioning issues between TP and git
pkg-isocodes-bugs at alioth.debian.org
pkg-isocodes-bugs at alioth.debian.org
Mon Jul 1 03:40:43 UTC 2013
pkg-isocodes-Bugs item #314317 was changed at 2013-06-30 23:40 by Chris Leonard
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=413077&aid=314317&group_id=30316
Status: Open
Priority: 3
Submitted By: Chris Leonard (cjl-guest)
Assigned to: Nobody (None)
Summary: iso-code POT template versioning issues between TP and git
Part: General
Initial Comment:
Dear Maintainers,
I downloaded the latest POT files from the Translation Project website with these links (as they indicate on each of the 6 projects respective textual domain page).
http://translationproject.org/POT-files/iso_639-3.43.pot
http://translationproject.org/POT-files/iso_639_3-3.43.pot
http://translationproject.org/POT-files/iso_15924-3.43.pot
http://translationproject.org/POT-files/iso_3166-3.43.pot
http://translationproject.org/POT-files/iso_3166_2-3.43.pot
http://translationproject.org/POT-files/iso_4217-3.43.pot
I also cloned the git repo using
git clone git://git.debian.org/git/iso-codes/iso-codes.git
I then closely examined all of the POT files for word count, string count (using Virtaal properties) and version number in POT headwer (using gedit) and identified several issues.
TP iso_639_3-3.43.pot 14525 words, 9557 strings
git iso_639_3.pot 13896 words, 9278 strings
This DOES NOT match between TP and git, big problem.
iso_639.pot 774 words, 488 strings - this matches between TP and git
iso_15924.pot 329 words, 163 strings - this matches between TP and git
iso_3166.pot 1108 words, 455 strings - this matches between TP and git
iso_3166_2.pot 6650 words, 4699 strings - this matches between TP and git
iso_4217.pot 586 words, 275 strings - this matches between TP and git
There are also some declared version number discrepancies from the POT file header
TP "Project-Id-Version: iso_639 3.40\n"
git "Project-Id-Version: iso_639 3.40\n"
TP "Project-Id-Version: iso_639-3 3.39\n" <-- also string and word count diffs
git "Project-Id-Version: iso_639-3 3.43\n" <--
TP "Project-Id-Version: iso_15924 3.39\n"
git "Project-Id-Version: iso_15924 3.39\n"
TP "Project-Id-Version: iso_3166 3.42\n"
git "Project-Id-Version: iso_3166 3.42\n"
TP "Project-Id-Version: iso_3166-2 3.43\n" <-- matching string and word counts
git "Project-Id-Version: iso_3166-2 3.38\n" <--
TP "Project-Id-Version: iso_4217 3.15\n"
git "Project-Id-Version: iso_4217 3.15\n"
Please note that only one of these declares itself to be version 3.43 and in one case, there are mismatches between the declared version even when the files superficially appear similar by word count and string count.
----------------------------------------------------------------------
Comment By: Chris Leonard (cjl-guest)
Date: 2013-06-30 23:40
Message:
OK after checking the 3.43 tagged POT for iso_639_3.pot from git the word and string counts match.
You can leave this open for the header data or close it if that is not going to be addressed.
----------------------------------------------------------------------
Comment By: Tobias Quathamer (toddy)
Date: 2013-06-27 11:07
Message:
You're right, that update is not long ago. Normally, we update the POT files at TP only a few hours after the release of the iso-codes tarball, this has not been the case for this specific release.
However, if you compare the TP POT files with the corresponding POT files in the git repository (meaning you need to check out the tag iso-codes-3.43, not HEAD), I'm sure you won't find the mentioned differences.
About the header data in the POT files: You're right, we should probably update the version in that data. However, often the POT file does not change between releases of iso-codes, so our procedure has been to only update to the current version if there are actual changes in the POT file. Up to now, this had not been a problem.
Regards,
Tobias
----------------------------------------------------------------------
Comment By: Chris Leonard (cjl-guest)
Date: 2013-06-26 12:14
Message:
I may be confused about your process; but the "update" of the POT to 3.43 on the TP site was recently announced (4 days ago):
http://lists.alioth.debian.org/pipermail/pkg-isocodes-devel/2013-June/005240.html
so it does not make sense that there would be that great a difference, but maybe I am the one missing something.
In any event, it would be nice if the POT header files reflected versions correctly.
----------------------------------------------------------------------
Comment By: Tobias Quathamer (toddy)
Date: 2013-06-26 11:26
Message:
Hi,
I don't see a problem here, because the files are first updated in git, then once a month released as a tarball and uploaded to TP. In the specific case you've mentioned, ISO 639-3, we're currently updating the POT file, so that the files *must* differ between git and TP.
Or am I not getting your point?
Regards,
Tobias
----------------------------------------------------------------------
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=413077&aid=314317&group_id=30316
More information about the Pkg-isocodes-devel
mailing list