Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

msguntypot(1) [debian man page]

MSGUNTYPOT(1)						User Contributed Perl Documentation					     MSGUNTYPOT(1)

NAME
msguntypot - update PO files when a typo is fixed in POT file SYNOPSIS
msguntypot -o old_pot -n new_pot pofiles ... DESCRIPTION
When you fix a trivial error which surely doesn't affect translations (e.g. a typo) in a POT file, you should unfuzzy the corresponding msgstr in the translated PO files to avoid so extra work to the translators. This task is difficult and error prone when done manually, and this tool is there to help doing so correctly. You just need to provide the two versions of the POT file: before the edition and after as marked in the above synopsis, and it all becomes automatic. HOW TO USE IT
In short, when you discover a typo in one of your [english] message, do the following: - Regenerate your POT and PO files. make -C po/ update-po # for message program translations debconf-updatepo # for debconf translations po4a po4a.conf # for po4a based documentation translations or something else, depending on your project's building settings. You know how to make sure your POT an PO files are uptodate, don't you?? - Make a copy of your POT file. cp myfile.pot myfile.pot.orig - Make a copy of all your files. mkdir po_fridge; cp *.po po_fridge - Fix your typo. $EDITOR the_file_in_which_there_is_a_typo - Regenerate your POT and PO files. See above. At this point, the typo fix fuzzied all the translations, and this unfortunate change is the only one between the PO files of your main directory and the one from the fridge. Here is how to solve this. - Discard fuzzy translation, restore the ones from the fridge. cp po_fridge/*.po . - Manually merge the PO files with the new POT file, but taking the useless fuzzy into account. msguntypot -o myfile.pot.orig -n myfile.pot *.po - Cleanups. rm -rf myfile.pot.orig po_fridge You're done. The typo was eradicated from msgstr of both your POT and PO files, and the PO files were not fuzzyied in the process. Your translators love you already. SEE ALSO
Despite its name, this tool is not part of the gettext tool suite. It is instead part of po4a. More precisely, it's a random Perl script using the fine po4a modules. For more information about po4a, please see: po4a(7) AUTHORS
Martin Quinson (mquinson#debian,org) COPYRIGHT AND LICENSE
Copyright 2005 by SPI, inc. This program is free software; you may redistribute it and/or modify it under the terms of GPL (see the COPYING file). perl v5.14.2 2012-05-17 MSGUNTYPOT(1)

Check Out this Related Man Page

PO4A-UPDATEPO(1)					User Contributed Perl Documentation					  PO4A-UPDATEPO(1)

NAME
po4a-updatepo - update the translation (in PO format) of documentation SYNOPSIS
po4a-updatepo -f fmt (-m master.docE)+ (-p XX.po)+ (XX.po are the outputs, all others are inputs) DESCRIPTION
The po4a (PO for anything) project goal is to ease translations (and more interestingly, the maintenance of translations) using gettext tools on areas where they were not expected like documentation. The po4a-updatepo script is in charge of updating PO files to make them reflect the changes made to the original documentation file. For that, it converts the documentation file to a POT file, and call msgmerge(1) on this new POT and on the provided PO files. It is possible to give more than one PO file (if you want to update several languages at once), and several documentation files (if you want to store the translations of several documents in the same PO file). If the master document has non-ASCII characters, it will convert the PO files to UTF-8 (if they weren't already), in order to allow non- standard characters in a culture independent way. OPTIONS
-f, --format Format of the documentation you want to handle. Use the --help-format option to see the list of available formats. -m, --master File(s) containing the master document to translate. -M, --master-charset Charset of the files containing the document to translate. Note that all files must have the same charset. -p, --po PO file(s) to update. If these files do not exist, they are created by po4a-updatepo. -o, --option Extra option(s) to pass to the format plugin and other po4a internal module. Specify each option in the 'name=value' format. See the documentation of each plugin for more information about the valid options and their meanings. --no-previous This option removes --previous from the options passed to msgmerge. This permits to support versions of gettext earlier than 0.16. --previous This option adds --previous to the options passed to msgmerge. It requires gettext 0.16 or later, and is activated by default. --msgmerge-opt options Extra options for msgmerge. -h, --help Show a short help message. --help-format List the documentation formats understood by po4a. -V, --version Display the version of the script and exit. -v, --verbose Increase the verbosity of the program. -d, --debug Output some debugging information. --msgid-bugs-address email@address Set the report address for msgid bugs. By default, the created POT files have no Report-Msgid-Bugs-To fields. --copyright-holder string Set the copyright holder in the POT header. The default value is "Free Software Foundation, Inc." --package-name string Set the package name for the POT header. The default is "PACKAGE". --package-version string Set the package version for the POT header. The default is "VERSION". SEE ALSO
po4a-gettextize(1), po4a-normalize(1), po4a-translate(1), po4a(7) AUTHORS
Denis Barbier <barbier@linuxfr.org> Nicolas Francois <nicolas.francois@centraliens.net> Martin Quinson (mquinson#debian.org) COPYRIGHT AND LICENSE
Copyright 2002-2012 by SPI, inc. This program is free software; you may redistribute it and/or modify it under the terms of GPL (see the COPYING file). perl v5.14.2 2012-05-17 PO4A-UPDATEPO(1)
Man Page