Hugin translation guide - Revision history

Zarl: /* Website / Release Notes */ updated links

2012-11-14T13:27:09Z

‎Website / Release Notes: updated links

Zarl: /* Website / Release Notes */ updated URL for 2011.4.0

2011-11-20T13:53:25Z

‎Website / Release Notes: updated URL for 2011.4.0

Zarl: /* Web */ "patch" hint added

2011-07-25T17:17:50Z

‎Web: "patch" hint added

Zarl: /* Website / Release Notes */ updated URL

2011-07-22T08:33:05Z

‎Website / Release Notes: updated URL

Zarl: /* Getting Started on translations */ verification hint added

2011-07-22T07:18:52Z

‎Getting Started on translations: verification hint added

Zarl: /* Common mistakes */ typo

2011-01-15T11:46:12Z

‎Common mistakes: typo

Thomas: /* Common mistakes */

2011-01-15T09:20:34Z

‎Common mistakes

Yuval: explained formatting place holders (under common mistake)

2011-01-01T21:59:07Z

explained formatting place holders (under common mistake)

Yuval: added extra check of contributed translation

2010-12-27T13:24:24Z

added extra check of contributed translation

Yuval: added msgfmt sanity check

2010-12-23T20:31:46Z

added msgfmt sanity check

@@ Line 356: / Line 356: @@
 Some translators contribute also translated release notes.  These are published on the web at http://hugin.sourceforge.net/releases/ . Usually the release manager will draft the release notes in English early on in the release process.  Even if they are not linked, you can find them in the repository at http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/tip/releases
-'''Important''': make sure you translate the file from the [http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/tip/releases repository] and not the resulting file displayed on the web, e.g. for 2011.4.0 translate the ''raw'' version of
+'''Important''': make sure you translate the file from the [http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/tip/releases repository] and not the resulting file displayed on the web, e.g. for 2012.0.0 translate the ''raw'' version of
-http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/eca3279b98d0/releases/2011.4.0/en.shtml and not http://hugin.sourceforge.net/releases/2011.4.0/en.shtml - the former is the source for the page while the latter is the resulting page after server side includes and other server side transformations.
+http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/4894a12dc2ea/releases/2012.0.0/en.shtml and not the current one from http://hugin.sourceforge.net/releases/ - the former is the source for the page while the latter is the resulting page after server side includes and other server side transformations.
 Thanks for your contributions!
 [[category:Software:Hugin]]

@@ Line 356: / Line 356: @@
 Some translators contribute also translated release notes.  These are published on the web at http://hugin.sourceforge.net/releases/ . Usually the release manager will draft the release notes in English early on in the release process.  Even if they are not linked, you can find them in the repository at http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/tip/releases
-'''Important''': make sure you translate the file from the repository and not the resulting file displayed on the web, e.g. for 2011.2.0 translate
+'''Important''': make sure you translate the file from the [http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/tip/releases repository] and not the resulting file displayed on the web, e.g. for 2011.4.0 translate the ''raw'' version of
-http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/raw-file/458a1ac79848/releases/2011.2.0/en.shtml and not http://hugin.sourceforge.net/releases/2011.2.0/en.shtml - the former is the source for the page while the latter is the resulting page after server side includes and other server side transformations.
+http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/eca3279b98d0/releases/2011.4.0/en.shtml and not http://hugin.sourceforge.net/releases/2011.4.0/en.shtml - the former is the source for the page while the latter is the resulting page after server side includes and other server side transformations.
 Thanks for your contributions!
 [[category:Software:Hugin]]

@@ Line 75: / Line 75: @@
 * Launchpad will look for duplicates.  This is good for bug reports, but for updated translations you can ignore it, scroll down to the bottom of the page and hit the "No, I need to report a new bug".
 * On the reporting form, enter a description in the "Further Information" field, then scroll to the bottom and hit the link "Extra options".
-* There you will find an Attachment field.  Hit it and browse to the .po.
+* There you will find an Attachment field. Hit it and browse to the .po file. When the bug tracker asks you if this is a patch: click yes, even though technically it isn't one. In this case it will help make developers aware of a file that needs to be reviewed and added to the codebase.
 * Click the "Submit Bug Report" button.

@@ Line 356: / Line 356: @@
 Some translators contribute also translated release notes.  These are published on the web at http://hugin.sourceforge.net/releases/ . Usually the release manager will draft the release notes in English early on in the release process.  Even if they are not linked, you can find them in the repository at http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/tip/releases
-'''Important''': make sure you translate the file from the repository and not the resulting file displayed on the web, e.g. translate
+'''Important''': make sure you translate the file from the repository and not the resulting file displayed on the web, e.g. for 2011.2.0 translate
-http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/e9990e702c7c/releases/2010.4.0/en.shtml and not http://hugin.sourceforge.net/releases/2010.4.0/en.shtml - the former is the source for the page while the latter is the resulting page after server side includes and other server side transformations.
+http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/raw-file/458a1ac79848/releases/2011.2.0/en.shtml and not http://hugin.sourceforge.net/releases/2011.2.0/en.shtml - the former is the source for the page while the latter is the resulting page after server side includes and other server side transformations.
 [[category:Software:Hugin]]

@@ Line 15: / Line 15: @@
 :Messages marked as '''fuzzy''' are actually not used in the GUI, their English counterparts are used instead. This seems to be an automagic suggestion which naturally often fails, so compare a fuzzy translation with the original phrase.
-*3 Verify your translation
+*3. Verify your translation
-:In order to test the new translation and to save some time for developers that will apply to trunk your file, it's recommanded to [http://wiki.panotools.org/Hugin_translation_guide#How_to_check_the_translated_file_for_syntax_errors check] your newly translated po file.
+:In order to test your new translation and as well save some time for the developers who apply your file to trunk it's recommanded to [http://wiki.panotools.org/Hugin_translation_guide#How_to_check_the_translated_file_for_syntax_errors check] your newly translated po file for syntax errors. It's also a good idea to [http://wiki.panotools.org/Hugin_translation_guide#Use_your_new_translation_file temporarily load] your new translation file into the latest available hugin build.
 *4. Submit your *.po file, or even better, commit your changes through Mercurial

@@ Line 46: / Line 46: @@
 * Watch out for the new line (\n) indicator at the end of the string. For example in the string:
   This is a test for a new line string\n
-:The \n symbol must remains at the end of the translated string
+:The \n symbol must remain at the end of the translated string
 * Watch out for quotation marks ". They must be quoted as \"

@@ Line 41: / Line 41: @@
 :If you take the following string:
   Open "%s" file
-:the %s must remain the same in the translated string because it is a reference to a variable (e.g. a filename, a number etc...)
+:the %s must remain the same in the translated string because it is a formatting placeholder where the code will display a  variable (e.g. a filename, a number etc...) at run time.  For example %s is a string and %0.3f is a number with three post-comma digits.

@@ Line 331: / Line 331: @@
 === Applying a contributed .po file ===
-You could just overwrite the original and commit, but this assumes the file is correctly formatted and hasn't lost any strings. Better to use '''msgmerge''' to merge the contributed .po file with the existing, and '''msgfmt''' for a quick sanity check:
+You could just overwrite the original and commit, but this assumes the file is correctly formatted and hasn't lost any strings. Better to use '''msgmerge''' to merge the contributed .po file with the existing.  Hugin has a script to test what will happen.  Use '''msgfmt''' for a quick sanity check too:
    msgmerge -o zh_CN.merged.po /tmp/zh_CN.contributed.po src/translations/zh_CN.po
    msgfmt -c --statistics zh_CN.merged.po

@@ Line 331: / Line 331: @@
 === Applying a contributed .po file ===
-You could just overwrite the original and commit, but this assumes the file is correctly formatted and hasn't lost any strings. Better to use '''msgmerge''' to merge the contributed .po file with the existing:
+You could just overwrite the original and commit, but this assumes the file is correctly formatted and hasn't lost any strings. Better to use '''msgmerge''' to merge the contributed .po file with the existing, and '''msgfmt''' for a quick sanity check:
    msgmerge -o zh_CN.merged.po /tmp/zh_CN.contributed.po src/translations/zh_CN.po
    mv zh_CN.merged.po src/translations/zh_CN.po
    hg ci zh_CN.po -m 'Edited chinese translation'
    hg push ssh://YOUR-SOURCEFORGE-USERNAME@hugin.hg.sourceforge.net/hgroot/hugin/hugin
 === Statistics ===