On Sun, 2008-04-13 at 03:28 +0300, Ville-Pekka Vainio wrote:
Hi,
I'm really sorry, but while committing my fi.po I also accidentally committed
a new version of release-notes.pot. That happened because I didn't specify
fi.po in the commit command. I didn't revert the change to prevent any more
damage from happening. Here's the diff compared to the previous, "correct",
version:
No reverting necessary, perhaps; see below.
Index: release-notes.pot
===================================================================
RCS file: /cvs/docs/release-notes/devel/po/release-notes.pot,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- release-notes.pot 9 Apr 2008 21:32:15 -0000 1.42
+++ release-notes.pot 13 Apr 2008 00:20:04 -0000 1.43
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2008-04-09 17:28-0400\n"
+"POT-Creation-Date: 2008-04-13 02:54+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL(a)li.org>\n"
@@ -1057,7 +1057,7 @@
msgstr ""
#: en_US/Kernel.xml:19(para)
-msgid "This section covers changes and important information regarding the
2.6.24 based kernel in Fedora 9. The 2.6.24 kernel includes:"
+msgid "This section covers changes and important information regarding the
2.6.25rc based kernel in Fedora 9. The 2.6.25rc kernel includes:"
msgstr ""
#: en_US/Kernel.xml:26(para)
As to why this happened and what changed the pot file, I have no idea. But
somehow it looks like that's the way it should be? Could someone take a look
at this?
Yesterday I updated the file en_US/Kernel.xml with the (more correct)
kernel version. The plan was to update the PO files by hand after
translators were finished. It didn't occur to me that if anyone updated
their XML files and rebuilt locally, they could generate a new POT file.
In hindsight, it would have been a good idea for me to announce the XML
change so people could ignore it.
Now that we have a changed POT committed, what is the best thing to do
in terms of:
* CVS best practice
* PO/POT best practice
Open for ideas ...
- Karsten
--
Karsten Wade, Sr. Developer Community Mgr.
Dev Fu :
http://developer.redhatmagazine.com
Fedora :
http://quaid.fedorapeople.org
gpg key : AD0E0C41