Translate Toolkit & Pootle toolkit

toolkit:accelerator_accelerator

Sat, 05 Jan 2008 18:11:00 +0000

1199556500		current
Line 4:		Line 4:
	\| & \| [[guide:KDE desktop]], [[guide:Mozilla]] (when using [[toolkit:moz2po]]) \|		\| & \| [[guide:KDE desktop]], [[guide:Mozilla]] (when using [[toolkit:moz2po]]) \|
	\| _ \| [[guide:GNOME desktop]] \|		\| _ \| [[guide:GNOME desktop]] \|
-	\| ~ \| [[:OpenOffice.org]] \|	+	\| ~ \| [[guide:OpenOffice.org]] \|

toolkit:base_classes

Sat, 28 Jul 2007 20:00:17 +0000

1166195703		current
Line 24:		Line 24:
	This class represents a single conceptual string in a single language. It must know its own requirements for escaping and implement it internally. Escaped versions are only used for internal representation and only exposed for file creation and testing (unit tests, for example).		This class represents a single conceptual string in a single language. It must know its own requirements for escaping and implement it internally. Escaped versions are only used for internal representation and only exposed for file creation and testing (unit tests, for example).

-	Note that when storing different plural forms of the same string, they should be stored in this class. The main object is the singular string, and all of the string forms can be accessed in a list at x.strings. Most of the time the object can be dealt with as a single string, only when it is neccessary to deal with plural forms do the extra strings have to be taken into account	+	Note that when storing different plural forms of the same string, they should be stored in this class. The main object is the singular string, and all of the string forms can be accessed in a list at x.strings. Most of the time the object can be dealt with as a single string, only when it is necessary to deal with plural forms do the extra strings have to be taken into account

	Comments/notes could possibly be supported in this class.		Comments/notes could possibly be supported in this class.
Line 65:		Line 65:
	-- tbx		-- tbx
	</code>		</code>
-	* Clean up convertors.	+	* Clean up converters.
	* Parsing of file content needs to happen only in the storage implementation of each filetype/storage type. Currently parsing happens all over the place.		* Parsing of file content needs to happen only in the storage implementation of each filetype/storage type. Currently parsing happens all over the place.
-	* Currently there are seperate conversion programs for each type and direction to convert to, eg. po2xliff and xliff2po (24 commands with lots of duplicate code in them). Ideally conversion should be as simple as:	+	* Currently there are separate conversion programs for each type and direction to convert to, eg. po2xliff and xliff2po (24 commands with lots of duplicate code in them). Ideally conversion should be as simple as:

	<code>		<code>
Line 94:		Line 94:
	* eg the --duplicates option can move into po.py		* eg the --duplicates option can move into po.py
	* Store the meta data for a storage object.		* Store the meta data for a storage object.
-	* Can be implemented as seperate sqlite file that accompanies the real file.	+	* Can be implemented as separate sqlite file that accompanies the real file.
	* Features not directly supported by a file format can be stored in the metadata file.		* Features not directly supported by a file format can be stored in the metadata file.
	* A storage object should know all information pertaining to itself.		* A storage object should know all information pertaining to itself.

toolkit:building

Fri, 04 Apr 2008 09:38:51 +0000

1207055402		current
Line 12:		Line 12:

	Consult the README in the source distribution for the build dependencies.		Consult the README in the source distribution for the build dependencies.
		+
		+	=== Building Python packages with C extensions under Windows ===
		+
		+	In order to build modules which have C extensions, you will need either the Visual Studio C++ compiler or [[http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=240780\|MinGW]].
		+
		+	Make sure that your Visual Studio C++ or MinGW program path is part of your system's program path, since the Python build system requires this.
		+
		+	To build and install a package with MinGW, you need to execute:
		+	''python setup.py build -c mingw32 install''
		+	from the command line.
		+
		+	To build a Windows installer when using MinGW, execute:
		+	''python setup.py build -c mingw32 bdist_wininst''

	==== Building ====		==== Building ====

toolkit:checking_for_inconsistencies

Fri, 27 Jul 2007 15:06:10 +0000

toolkit:cleanup_translator_comments

Tue, 30 Sep 2008 07:58:04 +0000

1205394554		current
Line 1:		Line 1:
	====== Cleanup translator comments ======		====== Cleanup translator comments ======

-	Translate Toolkit 1.1 saw source comments being concerted to developer comments instead of translator comments.	+	Translate Toolkit 1.1 saw source comments being converted to developer comments instead of translator comments.

	This use case shows you how to get rid of the old translator comments.		This use case shows you how to get rid of the old translator comments.

toolkit:conformance

Sat, 16 Jun 2007 10:05:26 +0000

1181988294		current
Line 2:		Line 2:
	This page links to pages documenting standard conformance for different standards or file formats.		This page links to pages documenting standard conformance for different standards or file formats.

-	===== LISA standards =====	+	===== LISA and OASIS standards =====
	* [[TMX]]		* [[TMX]]
	* [[XLIFF]]		* [[XLIFF]]

toolkit:contributing

Mon, 21 Jul 2008 21:26:06 +0000

1207512437		current
Line 12:		Line 12:

	Below we give you more detail on these:		Below we give you more detail on these:
		+


Line 27:		Line 28:

	Run unit tests to see if there are any issues. You'll need the [[http://codespeak.net/py/dist/test.html\|py.test]] unit test software		Run unit tests to see if there are any issues. You'll need the [[http://codespeak.net/py/dist/test.html\|py.test]] unit test software
-	which you can download from http://codespeak.net/py/dist/download.html	+	which you can [[http://codespeak.net/py/dist/download.html\|download]] and install or install this [[http://translate.sourceforge.net/releases/testing/fedora/pylib-0.9.1-1.fc9.noarch.rpm\|Fedora RPM]]

	To run the tests you do		To run the tests you do

toolkit:copyright

Tue, 19 Jun 2007 12:16:33 +0000

1149672674		current
Line 1:		Line 1:
	====== Copyright ======		====== Copyright ======

-	The Translate Toolkit documentation (everything which is included with the Translate Toolkit and is under the toolkit/ namespace on the wiki) is released under the [[http://www.gnu.org/licenses/gpl.html\|GNU General Public License (GPL)]].	+	The Translate Toolkit documentation (everything which is included with the Translate Toolkit or is under the toolkit/ namespace on the wiki) is released under the [[http://www.gnu.org/licenses/gpl.html\|GNU General Public License (GPL)]].

toolkit:creating_a_terminology_list_from_your_existing_translations

Tue, 30 Sep 2008 08:44:14 +0000

1222764092		current
Line 9:		Line 9:
	===== Quick Overview =====		===== Quick Overview =====

-	These are the steps that we will undertake	+	This describes a multi-stage process for extracting terminology from translation files. It is provided for historical interest and completeness, but you will probably find that using [[poterminology]] is easier and will give better results than following this process.

	- Filter our phrases of more than N words		- Filter our phrases of more than N words

toolkit:creating_mozilla_pot_files

Thu, 26 Mar 2009 15:52:45 +0000

1225808902		current
Line 21:		Line 21:
	that you can use for translation or updating your existing PO files.		that you can use for translation or updating your existing PO files.

		+	There are also [[mozilla_l10n_scripts\|other scripts]] that can help with creating and updating POT and PO files for [[Mozilla]] localisation.

	===== Using CVS =====		===== Using CVS =====

toolkit:csv

Fri, 04 Jan 2008 14:33:02 +0000

1185653386		current
Line 1:		Line 1:
	====== CSV ======		====== CSV ======
-	CSV (Comma Separated Values) is a simple file format for general data interchange. It can be used in the toolkit for simple data interchange, and can be edited with most spreadsheet programs. There is no formal specification for the CSV file format, but more information can be acquired from http://en.wikipedia.org/wiki/Comma-separated_values	+	CSV (Comma Separated Values) is a simple file format for general data interchange. It can be used in the toolkit for simple data interchange, and can be edited with most spreadsheet programs. There is no formal specification for the CSV file format, but more information can be acquired from [[wp>Comma-separated values]]

	For information on more file formats, see [[conformance]].		For information on more file formats, see [[conformance]].

toolkit:csv2po

Sat, 20 Jun 2009 10:16:02 +0000

1200475377		current
Line 2:		Line 2:

	Convert between CSV (Comma Separated Value) files and the PO format. This is useful for those translators who can only use a Spreadsheet, a modern spreadsheet can open CSV files for editing. It is also useful if you have other data such as translation memory in CSV format and you wish to use it with your PO translations.		Convert between CSV (Comma Separated Value) files and the PO format. This is useful for those translators who can only use a Spreadsheet, a modern spreadsheet can open CSV files for editing. It is also useful if you have other data such as translation memory in CSV format and you wish to use it with your PO translations.
		+
		+	If you are starting out with your own CSV files (not created by po2csv), take note of the assumptions of the column layout explained below.

	===== Usage =====		===== Usage =====

toolkit:csv2tbx

Tue, 29 Sep 2009 07:52:11 +0000

1200475378		current
Line 28:		Line 28:
	===== CSV file layout =====		===== CSV file layout =====

-	The CSV file is expected in to have three columns, of which the default layout is	+	The CSV file is expected to have three columns (separated by commas, not other characters like semicolons), of which the default layout is

	^ Column ^ Data ^ Description ^		^ Column ^ Data ^ Description ^
Line 57:		Line 57:
	===== Two column CSV =====		===== Two column CSV =====

-	csv2tbx --columnorder=(source,target) foo.csv foo.tbx	+	csv2tbx --columnorder=source,target foo.csv foo.tbx

	===== Notes =====		===== Notes =====

toolkit:developers

Mon, 03 Nov 2008 08:25:17 +0000

1224082303		current
Line 41:		Line 41:
	* misc -- various helper functions		* misc -- various helper functions
	* tools -- all PO manipulation programs: [[pocount]], [[pogrep]], etc		* tools -- all PO manipulation programs: [[pocount]], [[pogrep]], etc
		+	* lang -- modules with data / tweaks for various languages
		+	* search -- translation memory, terminology matching, and indexing / searching
		+	* share -- data files

	===== Current source state =====		===== Current source state =====

toolkit:dtd

Fri, 11 Apr 2008 13:42:54 +0000

1207921374		current
Line 3:		Line 3:
	Mozilla makes use of a .dtd file to store many of its translatable elements, the [[moz2po]] converter can handle these.		Mozilla makes use of a .dtd file to store many of its translatable elements, the [[moz2po]] converter can handle these.

		+	===== References =====
		+
		+	* [[http://www.w3.org/TR/REC-xml/\|XML specification]]

	===== Features =====		===== Features =====
Line 12:		Line 15:
	===== Issues =====		===== Issues =====

-	* We don't escape character entities like <, & - this doesn't break anything but it would be nicer to see © rather then ©	+	* We don't escape character entities like <, & - this doesn't break anything but it would be nicer to see © rather than ©

toolkit:duplicates_duplicatestyle

Tue, 15 Jan 2008 15:11:17 +0000

1200409877		current
Line 5:		Line 5:
	Also affected are conversions in which the source format is empty (allowing possible translation). As the header in a PO file is identified by an empty source string, your message will appear to be a duplicate of the header. In this case duplicate removal is critical.		Also affected are conversions in which the source format is empty (allowing possible translation). As the header in a PO file is identified by an empty source string, your message will appear to be a duplicate of the header. In this case duplicate removal is critical.

-	Previously the tools used msgid_comment (KDE style comments) to disambiguate text. However, with the release of Gettext 0.15, the new msgctxt dismbiguation is now recommended, especially if you wish to use your files with other Gettext the tools. Many other pieces of software now also support this feature, and will probably become the best choice for almost all circumstances.	+	Previously the tools used msgid_comment (KDE style comments) to disambiguate text. However, with the release of Gettext 0.15, the new msgctxt disambiguation is now recommended, especially if you wish to use your files with other Gettext the tools. Many other pieces of software now also support this feature, and will probably become the best choice for almost all circumstances.

	===== merge =====		===== merge =====

toolkit:errorlevel_errorlevel

Wed, 05 Sep 2007 13:30:27 +0000

1185653660		current
Line 1:		Line 1:
	====== --errorlevel=ERRORLEVEL ======		====== --errorlevel=ERRORLEVEL ======

-	Choose the level of feedback that you need when errors occur. Mostly useful for debugging.	+	This is a parameter that can be passed to most of the programs in the translate toolkit in order to choose the level of feedback that you need when errors occur. It is mostly useful for debugging. Please report your errors to the developers with --errorlevel=traceback.

	===== none =====		===== none =====

toolkit:features

Fri, 03 Oct 2008 08:48:08 +0000

1223023092		current
Line 6:		Line 6:
	* Mozilla: .properties, DTD, XHTML, .inc, .ini, etc		* Mozilla: .properties, DTD, XHTML, .inc, .ini, etc
	* Others: Comma Separated Value, TMX, XLIFF, TBX, php, WordFast TXT, Qt .ts, txt, .ini, Windows .rc, ical		* Others: Comma Separated Value, TMX, XLIFF, TBX, php, WordFast TXT, Qt .ts, txt, .ini, Windows .rc, ical
		+	* File access through the powerful API in all the above formats, as well as .qph, .qm, .mo
	* Output VALID target file types. We make sure that your output files (eg .properties) contain all comments from the original file and preserves the layout of the original as far as possible. If your PO entry is marked as fuzzy we use the English text, not your half complete translation. The converters for OpenOffice.org and Mozilla formats will also perform simple checks and corrections to make sure you have none of those hard to find localisation bugs.		* Output VALID target file types. We make sure that your output files (eg .properties) contain all comments from the original file and preserves the layout of the original as far as possible. If your PO entry is marked as fuzzy we use the English text, not your half complete translation. The converters for OpenOffice.org and Mozilla formats will also perform simple checks and corrections to make sure you have none of those hard to find localisation bugs.
	* Our checker has over [[pofilter tests\|42 checks]] to find errors such as: missing or translated variables, missing accelerator keys, bad escaping, start capitalisation, missing sentences, bad XML and much more.		* Our checker has over [[pofilter tests\|42 checks]] to find errors such as: missing or translated variables, missing accelerator keys, bad escaping, start capitalisation, missing sentences, bad XML and much more.

toolkit:filteraction_action

Mon, 23 Oct 2006 18:05:09 +0000

1161624451		current
Line 13:		Line 13:
	Only exclude errors that are listed as serious by the convertor. All other are included.		Only exclude errors that are listed as serious by the convertor. All other are included.

-	===== exclude =====	+	===== exclude-all =====

	Exclude any message that fails a test.		Exclude any message that fails a test.

toolkit:formats

Sat, 28 Nov 2009 11:01:46 +0000

1259405926		current
Line 74:		Line 74:
	* [[wp>LaTeX]] - see [[http://plastex.sourceforge.net/plastex/index.html\|plasTeX]], a Python framework for processing LaTeX documents		* [[wp>LaTeX]] - see [[http://plastex.sourceforge.net/plastex/index.html\|plasTeX]], a Python framework for processing LaTeX documents
	* [[http://dag.wieers.com/home-made/unoconv/\|unoconv]] - Python bindings to OpenOffice.org UNO which could allow manipulation of all formats understood by OpenOffice.org.		* [[http://dag.wieers.com/home-made/unoconv/\|unoconv]] - Python bindings to OpenOffice.org UNO which could allow manipulation of all formats understood by OpenOffice.org.
-	* Trados TTX ([[http://www.tracom.de/04/EN/techdoccenter/download/TRADOS_TTX-DTD.zip\|Reverse Engineered DTD]], [[http://blogs.sun.com/timf/entry/beds_mattresses_and_open_standards\|other discussion]])	+	* Trados:
		+	* TTX ([[http://www.tracom.de/04/EN/techdoccenter/download/TRADOS_TTX-DTD.zip\|Reverse Engineered DTD]], [[http://blogs.sun.com/timf/entry/beds_mattresses_and_open_standards\|other discussion]])
		+	* Multiterm XML [[http://syntax.biz.pl/multiterm.html\|TSV to MiltiTerm conversion script]]
	* Tcl: .msg files. [[http://www.google.com/codesearch?hl=en&q=show:XvsRBDCljVk:M2kzUbm70Ts:D5EHICz0aaQ&sa=N&ct=rd&cs_p=http://www.scilab.org/download/4.0/scilab-4.0-src.tar.gz&cs_f=scilab-4.0/tcl/scipadsources/msg_files/AddingTranslations.txt\|Good documentation]]		* Tcl: .msg files. [[http://www.google.com/codesearch?hl=en&q=show:XvsRBDCljVk:M2kzUbm70Ts:D5EHICz0aaQ&sa=N&ct=rd&cs_p=http://www.scilab.org/download/4.0/scilab-4.0-src.tar.gz&cs_f=scilab-4.0/tcl/scipadsources/msg_files/AddingTranslations.txt\|Good documentation]]
	* Installers:		* Installers:

toolkit:general_usage

Fri, 27 Jul 2007 13:38:53 +0000

1149673664		current
Line 35:		Line 35:
	pomerge -t <old> <fixes> <new>		pomerge -t <old> <fixes> <new>

-	This would take the <old> files merge in the <fix>'s and output new PO files, preserving formating, into <new>. You can use the same directory for <old> and <new> if you want the merges to overwrite files in <old>	+	This would take the <old> files merge in the <fix>'s and output new PO files, preserving formatting, into <new>. You can use the same directory for <old> and <new> if you want the merges to overwrite files in <old>

	===== source2target =====		===== source2target =====

-	The convertors all follow this convention:	+	The converters all follow this convention:

-	* source = the format from which you are converting eg in oo2po we are converting from OpenOffice.org SDF/GSI	+	* source = the format from which you are converting e.g. in oo2po we are converting from OpenOffice.org SDF/GSI
-	* target = the format into which you are converteing eg in oo2po we are conveting to Gettext PO	+	* target = the format into which you are converting e.g. in oo2po we are converting to Gettext PO

	===== Getting Help =====		===== Getting Help =====

toolkit:gsi

Thu, 11 Oct 2007 12:21:32 +0000

	current
Line 1:	Line 1:
	+	====== OpenOffice.org GSI/SDF format ======

	+	OpenOffice.org uses an internal format called SDF to manage localisation text. The toolkit can successfully manage all features of this format covnerting it to XLIFF or PO format with the [[oo2po]] and [[oo2xliff]] tools.
	+
	+	===== Features =====
	+
	+	* Handles all translatable text from the SDF
	+	* Can also use 'x-comments' 'language' found in the SDF to provide translator comments

toolkit:history

Thu, 27 Mar 2008 12:30:25 +0000

1197649275		current
Line 34:		Line 34:

	As part of the WordForge project Pootling was created which in the same way that Pootle is a web-based wrapper around the toolkit so Pootling is a GUI wrapper around the toolkit.		As part of the WordForge project Pootling was created which in the same way that Pootle is a web-based wrapper around the toolkit so Pootling is a GUI wrapper around the toolkit.
		+

	===== The Future =====		===== The Future =====

	The toolkit continues to evolve with clean-up focused in various areas:		The toolkit continues to evolve with clean-up focused in various areas:
-	* Pulling features out of Pootle that should be in the Toolkit (version control, statistics)	+	* Pulling features out of Pootle that should be in the Toolkit
	* Cleaning up storage classes and converters to be XLIFF/PO interchangeable		* Cleaning up storage classes and converters to be XLIFF/PO interchangeable
	* Cleaning up the converters to use only base class features and migrating code from the converters to the storage class		* Cleaning up the converters to use only base class features and migrating code from the converters to the storage class

toolkit:html

Thu, 26 Mar 2009 09:26:29 +0000

1192104661		current
Line 3:		Line 3:
	The Translate Toolkit is able to process HTML files using the [[html2po]] converter.		The Translate Toolkit is able to process HTML files using the [[html2po]] converter.

-	The HTML support is basic so please be aware of that	+	The HTML support is basic, so please be aware of that.

	===== Conformance =====		===== Conformance =====

toolkit:html2po

Fri, 28 Nov 2008 07:21:33 +0000

1200475378		current
Line 38:		Line 38:
	\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|		\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|
	\| -wWRAP, --wrap=WRAP \| set number of columns to wrap html at \|		\| -wWRAP, --wrap=WRAP \| set number of columns to wrap html at \|
		+	\| --notidy \| don't use tidy to clean up HTML, even if installed (new in version 1.2.1) \|
	\| --fuzzy \| use translations marked fuzzy \|		\| --fuzzy \| use translations marked fuzzy \|
	\| --nofuzzy \| don't use translations marked fuzzy (default) \|		\| --nofuzzy \| don't use translations marked fuzzy (default) \|

toolkit:ical

Wed, 24 Sep 2008 16:33:47 +0000

1222266256		current
Line 40:		Line 40:
	==== Broken Lotus Notes ====		==== Broken Lotus Notes ====

-	Lotus notes creates broken iCalendar files. They include _ (underscore) is some of the property names, [A-Z0-9\-] are the only valid chars. Therefore, we require vobject >= v0.6.5 (but there is unfortunately no way to check for the version of vobject)	+	Lotus notes creates broken iCalendar files. They include _ (underscore) is some of the property names, [A-Z0-9\-] are the only valid chars. Therefore, we require vobject >= v0.6.5 (but there is unfortunately no way to check for the version of vobject). See vobject bug [[https://bugzilla.osafoundation.org/show_bug.cgi?id=12008\|#12008]] for further details.

	===== Development Notes =====		===== Development Notes =====

toolkit:ical2po

Fri, 26 Sep 2008 14:54:06 +0000

	current
Line 1:	Line 1:
	+	====== ical2po ======

	+	Converts iCalendar (*.ics) files to Gettext PO format.
	+
	+	<note>New in v1.2</note>
	+
	+	===== Usage =====
	+
	+	ical2po [options] <ical> <po>
	+	po2ical [options] -t <ical> <po> <ical>
	+
	+	Where:
	+	\| <ical> \| is a valid .ics file or directory of those files \|
	+	\| <po> \| is a directory of PO or POT files \|
	+
	+	Options (ical2po):
	+	\| --version \| show program's version number and exit \|
	+	\| -h, --help \| show this help message and exit \|
	+	\| --manpage \| output a manpage based on the help \|
	+	\| [[--progress=PROGRESS]] \| show progress as: dots, none, bar, names, verbose \|
	+	\| [[--errorlevel=ERRORLEVEL]] \| show errorlevel as: none, message, exception, traceback \|
	+	\| -i INPUT, --input=INPUT \| read from INPUT in php format \|
	+	\| -x EXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|
	+	\| -o OUTPUT, --output=OUTPUT \| write to OUTPUT in po, pot formats \|
	+	\| -t TEMPLATE, --template=TEMPLATE \| read from TEMPLATE in php format \|
	+	\| [[--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|
	+	\| -P, --pot \| output PO Templates (.pot) rather than PO files (.po) \|
	+	\| [[--duplicates=DUPLICATESTYLE]] \| what to do with duplicate strings (identical source text): merge, msgid_comment, msgctxt, keep, msgid_comment_all (default: 'msgctxt') \|
	+
	+	Options (po2ical):
	+	\| --version \| show program's version number and exit \|
	+	\| -h, --help \| show this help message and exit \|
	+	\| --manpage \| output a manpage based on the help \|
	+	\| [[--progress=PROGRESS]] \| show progress as: dots, none, bar, names, verbose \|
	+	\| [[--errorlevel=ERRORLEVEL]] \| show errorlevel as: none, message, exception, traceback \|
	+	\| -i INPUT, --input=INPUT \| read from INPUT in po, pot formats \|
	+	\| -x EXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|
	+	\| -o OUTPUT, --output=OUTPUT \| write to OUTPUT in php format \|
	+	\| -t TEMPLATE, --template=TEMPLATE \| read from TEMPLATE in php format \|
	+	\| [[--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|
	+	\| --fuzzy \| use translations marked fuzzy \|
	+	\| --nofuzzy \| don't use translations marked fuzzy (default) \|
	+
	+	===== Examples =====
	+
	+	This example looks at roundtrip of iCalendar translations. While you can do recovery of translations, its unlikely that you will ever need to do that.
	+
	+	First we need to create a set of POT files.
	+
	+	ical2po -P ical.ics ical.pot
	+
	+	The ical.ics file is converted to Gettext POT files called ical.pot. Directories of iCalendar files can also be processed.
	+
	+	Begin translating the ical.pot file by first copying it to make a PO file.
	+
	+	cp ical.pot ical-af.po
	+
	+	You are now in a position to translate the file ical-af.po in your favourite translation tool.
	+
	+	Once translated you can convert back as follows:
	+
	+	po2ical -t ical.ics ical-af.po ical-af.ics
	+
	+	Your translations found in the Afrikaans PO file, ''ical-ad.po'', will be converted to .ics using the file ''ical.ics'' as a template and creating your newly translated .ics file ''ical-af.ics''.
	+
	+	To update your translations simply redo the POT creation step and make use of [[pot2po]] to bring your translation up-to-date.
	+
	+
	+	===== Notes =====
	+
	+	The converter will only process events in the calender file, the file itself can contain many other things that could be localisable. Please raise a bug if you want to extract additional items.
	+
	+	The converter does not make use of the LANGUAGE attribute which is permitted in the format. The LANGUAGE attribute does not aid multilingualism in this context so is ignored.
	+
	+	The converter could conceivably also process [[wp>vCard]] files, but this has not been implemented for lack of a clear need. Please raise a bug with an example if you have such a file that could benefit from localisation.
	+
	+	===== Bugs =====
	+
	+	None known

toolkit:important_changes

Thu, 15 Oct 2009 11:21:02 +0000

1249447245		current
Line 13:		Line 13:
	===== trunk =====		===== trunk =====
	This section describes the changes in the (unreleased) development files. It should reflect upcoming changes in the next version of the toolkit and latest [[http://translate.sourceforge.net/snapshots/\|beta or rc release]].		This section describes the changes in the (unreleased) development files. It should reflect upcoming changes in the next version of the toolkit and latest [[http://translate.sourceforge.net/snapshots/\|beta or rc release]].
		+
		+	===== 1.4.1 =====
		+
		+	==== CSV column header names ====
		+
		+	The names given to CSV column headers have been changed. Early releases of csv2po and po2csv would name the columns "comment,original,translation". This was done mostly to make it easy for non-technical translators. However, comments in the command line help used terms like source and target. This release changes the column header names to "location,source,target", this aligns with terms used throughout the toolkit.
		+
		+	If you have CSV file generated by older versions of the toolkit then a header entry of "comment,original,translation" will be turned into a unit instead of being ignored. You can either change your CSV file to use the headers "location,source,target" or delete the header row completely. Once this is done the files will work as expected.

	===== 1.4.0 =====		===== 1.4.0 =====
		+
	==== Java and Mozilla .properties ====		==== Java and Mozilla .properties ====
	Unusual keys, separators and spacing should all be handled correctly now. Some Mozilla .properties files might now have changed. Regenerate your Mozilla l10n files from fresh POT files without any changes to your PO files to ensure that you can see and review these changes.		Unusual keys, separators and spacing should all be handled correctly now. Some Mozilla .properties files might now have changed. Regenerate your Mozilla l10n files from fresh POT files without any changes to your PO files to ensure that you can see and review these changes.

toolkit:index

Fri, 24 Jul 2009 10:41:06 +0000

1248431187		current
Line 31:		Line 31:
	* [[toolkit:using_csv2po\|Translating using only a spreadsheet]] (a look at the whole roundtrip from PO to CSV and back)		* [[toolkit:using_csv2po\|Translating using only a spreadsheet]] (a look at the whole roundtrip from PO to CSV and back)
	* [[toolkit:using_oo2po\|Creating OpenOffice.org POT files]]		* [[toolkit:using_oo2po\|Creating OpenOffice.org POT files]]
-	* [[toolkit:Creating Mozilla POT files]]	+	* [[guide:mozilla\|Translating Mozilla products]]
	* [[toolkit:checking_for_inconsistencies\|Checking for inconsistencies in your translations]]		* [[toolkit:checking_for_inconsistencies\|Checking for inconsistencies in your translations]]
	* [[Creating a terminology list from your existing translations]]		* [[Creating a terminology list from your existing translations]]
Line 37:		Line 37:
	* Using ''phase'' for the complete translation roundtrip		* Using ''phase'' for the complete translation roundtrip
	* [[Cleanup translator comments]]		* [[Cleanup translator comments]]
-

toolkit:ini

Fri, 16 Jan 2009 10:01:14 +0000

1232099956		current
Line 12:		Line 12:
	The format supports two dialects:		The format supports two dialects:

-	* default: standard iniparse handling of INI files	+	* default: standard iniparse handling of INI files
-	* inno: follows Inno escaping conventions	+	* inno: follows [[http://www.innosetup.com/files/istrans/\|Inno]] escaping conventions

	===== References =====		===== References =====

toolkit:ini2po

Fri, 13 Mar 2009 10:45:45 +0000

1222440282		current
Line 2:		Line 2:

	Converts .ini files to Gettext PO format.		Converts .ini files to Gettext PO format.
-
-	<note>New in v1.1.1</note>

	===== Usage =====		===== Usage =====

toolkit:installation

Tue, 30 Sep 2008 03:04:36 +0000

1212677875		current
Line 68:		Line 68:

	<code bash>		<code bash>
-	./setupath # Only needed the first time	+	./setuppath # Only needed the first time
	. setpath # Do this once for a session		. setpath # Do this once for a session
	</code>		</code>

toolkit:levenshtein_distance

Wed, 23 Jan 2008 09:53:15 +0000

1201081367		current
Line 1:		Line 1:
	====== Levenshtein distance ======		====== Levenshtein distance ======
-	The Levenshtein distance is used for measuring the "distance" or similarity of two character strings. Other similarity algorithms can be supplied to the code that does the matching. For more information about this, see [[http://en.wikipedia.org/wiki/Levenshtein_distance\|the Wikipedia article in your language]].	+	The [[wp>Levenshtein distance]] is used for measuring the "distance" or similarity of two character strings. Other similarity algorithms can be supplied to the code that does the matching.

	This code is used in pot2po and in the [[lookupserver]]. It is implemented in the toolkit, but can optionally use the fast C implementation provided by [[https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=260161\|python-Levenshtein]] if it is installed.		This code is used in pot2po and in the [[lookupserver]]. It is implemented in the toolkit, but can optionally use the fast C implementation provided by [[https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=260161\|python-Levenshtein]] if it is installed.

toolkit:lookupserver

Fri, 24 Jul 2009 10:24:56 +0000

1139290200		current
Line 1:		Line 1:
		+	<note>Note that lookupserver has been replaced by [[tmserver]] as the best way to provide a translation memory service. This is kept for reference only. Tmserver should be used for all work.</note>
		+
	====== lookupserver ======		====== lookupserver ======
	The lookupserver is a service that can be accessed via http and queried via XML-RPC. It can perform lookup of strings in certain storage formats.		The lookupserver is a service that can be accessed via http and queried via XML-RPC. It can perform lookup of strings in certain storage formats.

toolkit:migrating_to_firefox

Sat, 05 Jan 2008 18:19:53 +0000

1199556500		current
Line 3:		Line 3:
	This quickstart shows you how to migrate your existing translations		This quickstart shows you how to migrate your existing translations
	of the [[guide:Mozilla]] suite to the [[guide:Firefox]] web-browser. The same		of the [[guide:Mozilla]] suite to the [[guide:Firefox]] web-browser. The same
-	instructions can be used to migrate [[:Thunderbird]].	+	instructions can be used to migrate [[guide:Thunderbird]].

	Note: This guide assumes that you are or will be using PO files.		Note: This guide assumes that you are or will be using PO files.

toolkit:migrating_translations

Fri, 27 Jul 2007 14:44:49 +0000

1183963485		current
Line 2:		Line 2:

	You very often need to migrate older translations to newer template or POT files. There are a number of Gettext tools		You very often need to migrate older translations to newer template or POT files. There are a number of Gettext tools
-	that can manage this but they do not handle the situation where files have been renamed and moved. The [[toolkit:pomigrate2]]	+	that can manage this but they do not handle the situation where files have been renamed and moved. The [[pomigrate2]]
	script allows us to migrate between versions where there has been considerable change.		script allows us to migrate between versions where there has been considerable change.

Line 13:		Line 13:
	You will need:		You will need:

-	* [[toolkit:pomigrate2]]	+	* [[pomigrate2]]
-	* [[toolkit:pocompendium]]	+	* [[pocompendium]]
	* A text editor		* A text editor
	* A PO editing tool		* A PO editing tool
Line 20:		Line 20:
	===== Preparing the new POT files =====		===== Preparing the new POT files =====

-	We need the new pot files. Either download these from the project or generate them using [[toolkit:moz2po]], [[toolkit:oo2po]] or the other tools of the Translate Toolkit. The POT files are templates for the destination files that we will be creating.	+	We need the new pot files. Either download these from the project or generate them using [[moz2po]], [[oo2po]] or the other tools of the Translate Toolkit. The POT files are templates for the destination files that we will be creating.

	oo2po -P en-US.sdf ooo-20-pot		oo2po -P en-US.sdf ooo-20-pot
Line 30:		Line 30:
	We will be migrating your old PO files into the new POT files. This is a good opportunity to check for encoding errors and inconsistencies.		We will be migrating your old PO files into the new POT files. This is a good opportunity to check for encoding errors and inconsistencies.

-	We use [[toolkit:pocompendium]] to check for encoding errors:	+	We use [[pocompendium]] to check for encoding errors:

	pocompendium check.po -d ooo-113-old		pocompendium check.po -d ooo-113-old
Line 55:		Line 55:
	===== Migrate =====		===== Migrate =====

-	You are now ready to migrate using [[toolkit:pomigrate2]]. You have created your destination POT files and all your PO files are clean and ready to migrate.	+	You are now ready to migrate using [[pomigrate2]]. You have created your destination POT files and all your PO files are clean and ready to migrate.

	pomigrate2 ooo-113-old ooo-20-new ooo-20-pot		pomigrate2 ooo-113-old ooo-20-new ooo-20-pot
Line 83:		Line 83:
	pocount ooo-20-new		pocount ooo-20-new

-	This will use [[toolkit:pocount]] to count the words in your new files and you can compare the number of translate and untranslated messages from your old version.	+	This will use [[pocount]] to count the words in your new files and you can compare the number of translate and untranslated messages from your old version.

	===== Conclusion =====		===== Conclusion =====

	Your files have now been migrated and are ready for updating. If files moved they have been moved, if they changed names and you used a compendium then most likely you have most of that work translated.		Your files have now been migrated and are ready for updating. If files moved they have been moved, if they changed names and you used a compendium then most likely you have most of that work translated.

toolkit:mo

Mon, 06 Oct 2008 14:08:03 +0000

1204033642		current
Line 8:		Line 8:
	The toolkit can create .mo files from PO or XLIFF files, handling plurals and msgctxt. It can also read .mo files, allowing counting, etc and also allowing the .mo files to act as a translation memory.		The toolkit can create .mo files from PO or XLIFF files, handling plurals and msgctxt. It can also read .mo files, allowing counting, etc and also allowing the .mo files to act as a translation memory.

-	==== No hash table ====	+	Since version 1.2 of the Translate Toolkit, the hash table is also generated (the Gettext .mo file works fine without it). Due to slight differences in the construction of the hashing, the generated files are not identical to those generated by msgfmt, but they should be functionally equivalent and 100% usable. Bug [[bug>326]] tracked the implementation of the hashing. The hash is platform dependent.
-		+
-	The hash table is not implemented (the Gettext .mo file works fine without it). This might result in slower performance although the Gettext manual raises doubts about the speed gain. The hash is platform dependent. Bug [[bug>326]] is tracking implementation of hashing.	+

toolkit:moz-l10n-builder

Tue, 04 Nov 2008 12:47:43 +0000

1225802454		current
Line 33:		Line 33:

	moz-l10n-builer is not currently distributed as part of the toolkit. You can get the [[https://translate.svn.sourceforge.net/svnroot/translate/src/trunk/tools/mozilla/moz-l10n-builder\|latest version from Subversion]]		moz-l10n-builer is not currently distributed as part of the toolkit. You can get the [[https://translate.svn.sourceforge.net/svnroot/translate/src/trunk/tools/mozilla/moz-l10n-builder\|latest version from Subversion]]
-	and you will also need this [[http://translate.svn.sourceforge.net/viewvc/checkout/translate/src/trunk/tools/mozilla-l10n.patch\|minor patch]] to the mozilla source code.	+	and you will also need this [[http://translate.svn.sourceforge.net/viewvc/checkout/translate/src/trunk/tools/mozilla/mozilla-l10n.patch\|minor patch]] to the mozilla source code.

	===== Usage =====		===== Usage =====

toolkit:moz2po

Tue, 04 Nov 2008 14:55:43 +0000

toolkit:mozilla_l10n_scripts

Wed, 18 Mar 2009 15:41:41 +0000

1236613896		current
Line 7:		Line 7:
	All of these scripts are available on Subversion from [[https://translate.svn.sourceforge.net/svnroot/translate/src/trunk/tools/mozilla/\|here]].		All of these scripts are available on Subversion from [[https://translate.svn.sourceforge.net/svnroot/translate/src/trunk/tools/mozilla/\|here]].

		+	We are currently generating POT files for most major betas, RCs and releases of Firefox and Thunderbird. They are available here:
		+	http://l10n.mozilla.org/pootle/pot/
		+
		+	As a start you might want to just use these POT files and gradually learn more about the processes described below. Contact us for more help on using these.

	===== Requirements =====		===== Requirements =====

toolkit:multifile_multifilestyle

Wed, 19 Oct 2005 09:45:09 +0000

	current
Line 1:	Line 1:
	+	====== --multifile=MULTIFILESTYLE ======

	+	This options determines how the POT/PO files are spli from the source files. In many cases
	+	you have source files that generate either too many small files or one large files which you would rather see
	+	split up into smaller files.
	+
	+	===== single =====
	+
	+	Output individual files.
	+
	+	===== toplevel =====
	+
	+	Split the source files at the top level. Ie you see a number of top level files.
	+
	+	===== onefiles =====
	+
	+	One large file instead of many smaller files.

toolkit:odf

Thu, 12 Feb 2009 14:18:13 +0000

1234447323		current
Line 10:		Line 10:
	http://translate.svn.sourceforge.net/viewvc/translate/src/trunk/translate/storage/odf_shared.py?view=log		http://translate.svn.sourceforge.net/viewvc/translate/src/trunk/translate/storage/odf_shared.py?view=log

-	More complex tag uses are still needed to extract 100% correctly in the case of some spreadsheet values where the presentation form is stored along with the internal values.	+	More complex tag uses are still needed to extract 100% correctly in some complex cases. For more information, see the list of [[odf:testing\|issues from testing]].

toolkit:odf2xliff

Tue, 17 Feb 2009 11:10:18 +0000

1233844661		current
Line 55:		Line 55:
	===== Bugs =====		===== Bugs =====

-	This filter is not yet extensively used - we appreciate your feedback. See [[xliff]] to see how well our implementation conforms to the XLIFF standard. Possible issues were listed during [[odf:testing]].	+	This filter is not yet extensively used - we appreciate your feedback. For more information on conformance to standards, see the [[xliff]] or [[odf]] pages. Possible issues were listed during [[odf:testing]].

toolkit:omegat_glossary

Thu, 26 Nov 2009 13:17:56 +0000

1259241430		current
Line 21:		Line 21:
	===== Issues =====		===== Issues =====

-	* UTF-8 files works correctly.
	* There has not been extensive testing on system encoded files and there are likely to be issues in these files for encodings that fall outside of common ASCII characters.		* There has not been extensive testing on system encoded files and there are likely to be issues in these files for encodings that fall outside of common ASCII characters.
		+	* Files with additional columns are read correctly but cannot be written.

toolkit:oo2po

Tue, 08 Apr 2008 20:19:15 +0000

1207573440		current
Line 103:		Line 103:


		+
		+
		+	===== helpcontent2 =====
		+
		+	The escaping of ''helpcontent2'' from SDF files was very confusing, bug [[bug>295]] implemented a fix that appeared in version 1.1.0 (All known issues were fixed in 1.1.1). Translators are now able to translate helpcontent2 with clean escaping.

	===== Bugs =====		===== Bugs =====

-	''helpcontent2'' escaping in SDF files ares very confusing, but bug [[bug>295]] a tracked a fix that appeared in version 1.1.0. All known issues were fixed in 1.1.1.	+	None known

toolkit:oo2xliff

Fri, 04 Jan 2008 14:38:02 +0000

1199457402		current
Line 1:		Line 1:
-	~~REDIRECT>oo2po~~	+	~~REDIRECT>toolkit:oo2po~~

toolkit:personality_type

Mon, 15 Jun 2009 13:28:31 +0000

1164183351		current
Line 13:		Line 13:
	===== mozilla =====		===== mozilla =====

-	Mozilla has made slight adjustments to the Java .properties spec. Mozilla will accept UTF-8 encoded strings in the property file and thus does not need escaped Unicode. Thus the string above string - ṽḁḽṻḝ - will not be escaped. Mozilla property files are thus more useful for non-Latin languages in that they are actually readable.	+	Mozilla has made slight adjustments to the Java .properties spec. Mozilla will accept UTF-8 encoded strings in the property file and thus does not need escaped Unicode. Thus the above string - ṽḁḽṻḝ - will not be escaped. Mozilla property files are thus more useful for non-Latin languages in that they are actually readable.

	Of course this style of file is only used by Mozilla and should not be used for other projects that follow the Java spec more strictly.		Of course this style of file is only used by Mozilla and should not be used for other projects that follow the Java spec more strictly.

toolkit:phase

Fri, 04 Jan 2008 14:16:19 +0000

1199456138		current
Line 12:		Line 12:
	* [[man>diff]]		* [[man>diff]]
	* [[man>cvs]]		* [[man>cvs]]
		+


	===== Latest Version =====		===== Latest Version =====

-	phase is not currently distributed as part of the toolkit. You can get the [[http://translate.svn.sourceforge.net/viewvc/checkout/translate/src/trunk/tools/phase\|latest version from Subversion]]	+	phase is not currently distributed as part of the toolkit. You can get the [[svn>/trunk/tools/phase\|latest version from Subversion]]

	===== Usage =====		===== Usage =====

toolkit:php

Mon, 15 Dec 2008 09:48:56 +0000

1229334536		current
Line 1:		Line 1:
	====== PHP ======		====== PHP ======

-	Many [[wp>PHP]] programs make use of a localisable string array. The toolkit support the full localisation of such files.	+	Many [[wp>PHP]] programs make use of a localisable string array. The toolkit support the full localisation of such files with [[php2po]] and po2php.

	===== Example =====		===== Example =====

toolkit:php2po

Mon, 15 Dec 2008 08:50:57 +0000

1229331013		current
Line 88:		Line 88:

	* Support localisation variables using ''array'' is missing		* Support localisation variables using ''array'' is missing
-	* Proper escaping of single vs double quotes is missing. See [[bug>593]]

toolkit:po

Thu, 26 Mar 2009 09:39:51 +0000

1234773458		current
Line 11:		Line 11:
	* Obsolete messages		* Obsolete messages
	* Message Context (msgctxt)		* Message Context (msgctxt)
		+	* Language header (since gettext version 0.17)
		+	* Previous message ID and context (#\| msgid and #\| msgctxt)

	===== Supported comments =====		===== Supported comments =====
Line 18:		Line 19:
	* source location comments <code>#: sourcefile.xxx:35</code>		* source location comments <code>#: sourcefile.xxx:35</code>
	* typecomments <code>#, fuzzy</code>		* typecomments <code>#, fuzzy</code>
-	* msgidcomments <code>magid "_: within msgid\n"</code>Also know as KDE style comments as they are used by KDE for message disambiguation and comments to translators.	+	* msgidcomments <code>magid "_: within msgid\n"</code>Also know as KDE style comments as they are used by KDE for message disambiguation and comments to translators. (support for this is being phased out)
	* obsolete messages <code>#~ msgid "Blah"		* obsolete messages <code>#~ msgid "Blah"
	#~ msgstr "Bleeh"</code>		#~ msgstr "Bleeh"</code>

-	===== Unsupported Features =====	+	* previous msgid and msgctxt <code> #\| msgid "previous message"</code>


-	==== Previous msgid ====	+	===== Unsupported Features =====
-		+
-	#\| msgid "previous message"	+
-		+
-	In Gettext 0.16. While we don't do anything with these we will not destro them needlessly since the parse can now capture them.	+

	==== Alternate language ====		==== Alternate language ====
Line 36:		Line 33:
	msgid[af] "Engels"		msgid[af] "Engels"

-	Unsure of when or if this was added to Gettext.	+	(This was proposed but not yet accepted in a released version of Gettext.)

toolkit:po2csv

Thu, 10 Jan 2008 09:33:31 +0000

1121950434		current
Line 1:		Line 1:
-	====== po2csv and csv2po ======	+	~~REDIRECT>toolkit:csv2po~~
-		+
-	Converts PO files into CSV (Comma Seperated Value) files. A CSV file can be opened in most spreadsheets	+
-	which therefore allows you to [[guide:tools:spreadsheet\|translate using a spreadsheet]]	+
-		+
-	===== Usage =====	+
-		+
-	po2csv [-P] <input> <csv>	+
-	csv2po [--charset=CHARSET] [-t <templates>] <csv> <output>	+
-		+
-	Where:	+
-	\| <input> \| contains a number of PO files \|	+
-	\| <csv> \| contains the resultant CSV files \|	+
-	\| <templates> \| are the reference POT or PO files \|	+
-	\| <output> \| the newly created PO files migrated from CSV \|	+
-		+
-	Options:	+
-	\| -P, --pot \| output PO Templates (.pot) rather than PO files (.po) \|	+
-	\| --charset=CHARSET \| set charset to decode from CSV files \|	+
-		+
-	===== Examples =====	+
-		+
-	po2csv -P templates csv	+
-		+
-	Transform POT files found in //templates// into CSV files in //csv//	+
-		+
-	po2csv zulu zulu-csv	+
-		+
-	Convert PO files found in //zulu// to CSV files in //zulu-csv//	+
-		+
-	csv2po --charset=windows-1250 -t templates csv zulu	+
-		+
-	Convert CSV files found in //csv// into PO files that will be placed in //zulu// using PO files found in //template// as templates for the reconstruction of the PO files. The CSV files are also converted to //WINDOWS-1250// encoding to UTF-8.	+
-		+
-	===== Bugs =====	+
-		+
-	po2csv assumes that the file is in UTF-8, it probably should read the encoding from the PO header.	+
-	You cannot change the columns and it would probably be usefull if you could in cases where translators	+
-	have moved columns. We should probably work out how to include translator comments.	+

toolkit:po2html

Thu, 10 Jan 2008 09:34:39 +0000

		current
Line 1:		Line 1:
		+	~~REDIRECT>toolkit:html2po~~

toolkit:po2ini

Tue, 15 Apr 2008 14:51:45 +0000

		current
Line 1:		Line 1:
		+	~~REDIRECT>toolkit:ini2po~~

toolkit:po2moz

Thu, 10 Jan 2008 09:30:57 +0000

		current
Line 1:		Line 1:
		+	~~REDIRECT>toolkit:moz2po~~

toolkit:po2oo

Wed, 09 Jan 2008 19:33:19 +0000

		current
Line 1:		Line 1:
		+	~~REDIRECT>toolkit:oo2po~~

toolkit:po2php

Wed, 16 Jan 2008 09:37:56 +0000

		current
Line 1:		Line 1:
		+	~~REDIRECT>toolkit:php2po~~

toolkit:po2prop

Thu, 10 Jan 2008 09:36:51 +0000

		current
Line 1:		Line 1:
		+	~~REDIRECT>toolkit:prop2po~~

toolkit:po2rc

Sun, 06 Apr 2008 20:14:59 +0000

		current
Line 1:		Line 1:
		+	~~REDIRECT>toolkit:rc2po~~

toolkit:po2sub

Mon, 22 Jun 2009 12:24:04 +0000

		current
Line 1:		Line 1:
		+	~~REDIRECT>toolkit:sub2po~~

toolkit:po2tmx

Fri, 10 Oct 2008 09:59:41 +0000

1200475380		current
Line 31:		Line 31:
	Use the Xhosa (//xh//) translations in the PO file //browser.po// to create a TMX file called //browser.tmx//		Use the Xhosa (//xh//) translations in the PO file //browser.po// to create a TMX file called //browser.tmx//

-	===== Bugs =====	+	===== Bugs and issues =====
		+
		+	==== Markup stripping ====

	po2tmx conforms to TMX v1.4 without stripping markup. See the [[tmx]] conformance page for more details.		po2tmx conforms to TMX v1.4 without stripping markup. See the [[tmx]] conformance page for more details.

	It has not been widely tested so your mileage may vary.		It has not been widely tested so your mileage may vary.
		+
		+	==== TMX and PO in OmegaT ====
		+
		+	In some tools, like OmegaT, PO files are parsed without expanding escaped sequences, even though such tools use TMX for translation memory. Keep this in mind when using po2tmx, because po2tmx converts \n and \t to newlines and tabs in the TMX file. If such a TMX file is used while translating PO files in OmegaT, matching will be less than 100%.
		+
		+	In other tools, such as Swordfish, the PO comment "no-wrap" is interpreted in the same way as the equivalent function in XML, which may also lead to mismatches if TMXes from po2tmx are used.
		+
		+	There is nothing wrong with po2tmx, but if used in conjunction with tools that handle PO files differently, it may lead to less than perfect matching.

	===== Tips =====		===== Tips =====

toolkit:po2ts

Wed, 09 Jan 2008 08:02:42 +0000

1199865707		current
Line 1:		Line 1:
-	~~REDIRECT>ts2po~~	+	~~REDIRECT>toolkit:ts2po~~

toolkit:po2txt

Wed, 09 Jan 2008 19:35:09 +0000

		current
Line 1:		Line 1:
		+	~~REDIRECT>toolkit:txt2po~~

toolkit:po2wordfast

Fri, 13 Mar 2009 10:46:19 +0000

1200475380		current
Line 1:		Line 1:
	====== po2wordfast ======		====== po2wordfast ======
-
-	<note>Only in v1.1 of the Translate Toolkit</note>

	Convert Gettext PO files to a [[Wordfast]] translation memory file.		Convert Gettext PO files to a [[Wordfast]] translation memory file.

toolkit:po2xliff

Thu, 10 Jan 2008 09:35:53 +0000

		current
Line 1:		Line 1:
		+	~~REDIRECT>toolkit:xliff2po~~

toolkit:poclean

Wed, 16 Jan 2008 09:23:01 +0000

1180019403		current
Line 21:		Line 21:
	\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in po, pot formats \|		\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in po, pot formats \|
	\| -tTEMPLATE, --template=TEMPLATE \| read from TEMPLATE in po, pot formats \|		\| -tTEMPLATE, --template=TEMPLATE \| read from TEMPLATE in po, pot formats \|
-	\| [[--psyco=PSYCO\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|	+	\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|

	===== Examples =====		===== Examples =====

toolkit:pocommentclean

Tue, 30 Sep 2008 21:03:31 +0000

1205394365		current
Line 7:		Line 7:
	* [[man>sed]]		* [[man>sed]]

-	===== Latest Version =====

-	pocommentclean is not currently distributed as part of the toolkit. You can get the [[http://translate.svn.sourceforge.net/viewvc/checkout/translate/src/trunk/tools/pocommentclean\|latest version from Subversion]]

	===== Usage =====		===== Usage =====

toolkit:pocompendium

Tue, 30 Sep 2008 08:51:49 +0000

1205876171		current
Line 16:		Line 16:


-	===== Latest Version =====

-	pocompendium is not currently distributed as part of the toolkit. You can get the [[svn>/trunk/tools/pocompendium\|latest version from Subversion]]

	===== Usage =====		===== Usage =====

toolkit:pocompile

Tue, 26 Feb 2008 14:02:29 +0000

1200475381		current
Line 38:		Line 38:

	Create an MO file from an XLIFF file called //file.xlf// (available from version 1.1 of the toolkit).		Create an MO file from an XLIFF file called //file.xlf// (available from version 1.1 of the toolkit).
		+

	===== Bugs =====		===== Bugs =====

-	Gettext plurals and msgctxt are not handled before version 1.1 of the toolkit (as yet unreleased).	+	Gettext plurals and msgctxt are not handled before version 1.1 of the toolkit.
		+
		+	The .mo implementation does not support Gettext hash tables.

toolkit:poconflict

Thu, 03 Jan 2008 09:31:46 +0000

		current
Line 1:		Line 1:
		+	~~REDIRECT>toolkit:poconflicts~~

toolkit:poconflicts

Wed, 16 Jan 2008 09:23:02 +0000

1199353054		current
Line 23:		Line 23:
	\| -xEXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|		\| -xEXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|
	\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in po format \|		\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in po format \|
-	\| [[psyco_psyco\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|	+	\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|
	\| -I, --ignore-case \| ignore case distinctions \|		\| -I, --ignore-case \| ignore case distinctions \|
	\| -v, --invert \| invert the conflicts thus extracting conflicting destination words \|		\| -v, --invert \| invert the conflicts thus extracting conflicting destination words \|

toolkit:pocount

Tue, 21 Jul 2009 13:28:53 +0000

1245161006		current
Line 103:		Line 103:

	* There are some miscounts related to word breaks.		* There are some miscounts related to word breaks.
-	* There may be miscounts of total incomplete files in full mode.
	* When using the short output formats the columns may not be exactly aligned. This is because the number of digits in different columns is unknown before all input files are processed. The chosen tradeoff here was instanteous output (after each processed file) instead of waiting for the last file to be processed.		* When using the short output formats the columns may not be exactly aligned. This is because the number of digits in different columns is unknown before all input files are processed. The chosen tradeoff here was instanteous output (after each processed file) instead of waiting for the last file to be processed.

toolkit:podebug

Mon, 03 Aug 2009 14:24:46 +0000

1249309237		current
Line 37:		Line 37:
	\| [[--rewrite=STYLE]] \| the translation rewrite style: xxx, en, blank, chef (v1.2), unicode (v1.2) \|		\| [[--rewrite=STYLE]] \| the translation rewrite style: xxx, en, blank, chef (v1.2), unicode (v1.2) \|
	\| --ignore=APPLICATION \| apply tagging ignore rules for the given application: kde, gtk, openoffice, mozilla \|		\| --ignore=APPLICATION \| apply tagging ignore rules for the given application: kde, gtk, openoffice, mozilla \|
-	\| --hash=LENGTH \| add an md5 hash to translations \|	+	\| --hash=LENGTH \| add an md5 hash to translations (only until version 1.3.0 - see %h below) \|

toolkit:poen

Wed, 12 Nov 2008 06:47:16 +0000

1226472416		current
Line 2:		Line 2:

	<note warning>		<note warning>
-	This has been removed from Translate Toolkit > 1.2. Rather use [[podebug]] as follows:	+	poen has been removed from Translate Toolkit > 1.2. Rather use [[podebug]] as follows:
	<code>		<code>
	podebug --rewrite=en -f "" pot/ po/		podebug --rewrite=en -f "" pot/ po/

toolkit:pofilter

Mon, 11 May 2009 13:06:22 +0000

toolkit:pofilter_tests

Wed, 28 Oct 2009 09:44:43 +0000

1256722713		current
Line 350:		Line 350:
	==== xmltags ====		==== xmltags ====

-	checks that XML/HTML tags have not been translated	+	checks that [[guide:translation:html\|XML/HTML]] tags have not been translated

	This check finds the number of tags in the source string and checks that the same number are in the translation. If the counts don't match then either the tag is missing or it was mistakenly translated by the translator, both of which are errors.		This check finds the number of tags in the source string and checks that the same number are in the translation. If the counts don't match then either the tag is missing or it was mistakenly translated by the translator, both of which are errors.

-	The check ignores tags or things that look like tags that cover the whole string eg "<Error>" but will produce false positives for things like "An <Error> occurred" as here "Error" should be translated. It also will allow translation of the alt attribute in e.g. <img src=bob.png alt="Image description"> or similar translatable attributes in OpenOffice.org help files.	+	The check ignores tags or things that look like tags that cover the whole string e.g. "<Error>" but will produce false positives for things like "An <Error> occurred" as here "Error" should be translated. It also will allow translation of the alt attribute in e.g. <img src=bob.png alt="Image description"> or similar translatable attributes in OpenOffice.org help files.

toolkit:poglossary

Wed, 11 Jun 2008 12:52:34 +0000

1212530908		current
Line 1:		Line 1:
		+	<note>poglossary has been superseded by [[poterminology]]</note>
		+
	====== poglossary ======		====== poglossary ======

toolkit:pogrep

Fri, 13 Mar 2009 10:44:45 +0000

1200475384		current
Line 59:		Line 59:
	==== Unicode normalization ====		==== Unicode normalization ====

-	pogrep will normalize Unicode strings (from v1.1). This allows you to search for strings that contain the same character but that are using precomposed Unicode characters or which are composed using another composition recipe. While an individual user will in all likelihood only compose characters in one way, normalization ensures that data created in a team setting can be shared.	+	pogrep will normalize Unicode strings. This allows you to search for strings that contain the same character but that are using precomposed Unicode characters or which are composed using another composition recipe. While an individual user will in all likelihood only compose characters in one way, normalization ensures that data created in a team setting can be shared.

	===== Bugs =====		===== Bugs =====

	None known		None known

toolkit:pomerge

Mon, 11 May 2009 14:04:05 +0000

toolkit:pomigrate2

Tue, 30 Sep 2008 21:10:59 +0000

1220013149		current
Line 15:		Line 15:
	* [[man>msgmerge]]		* [[man>msgmerge]]

-	===== Latest Version =====

-	pomigrate2 is not currently distributed as part of the toolkit. You can get the [[svn>trunk/tools/pomigrate2\|latest version from Subversion]]

	===== Usage =====		===== Usage =====

toolkit:popuretext

Tue, 30 Sep 2008 21:06:40 +0000

1185806133		current
Line 10:		Line 10:


-	===== Latest Version =====

-	popuretext is not currently distributed as part of the toolkit. You can get the [[http://translate.svn.sourceforge.net/viewvc/checkout/translate/src/trunk/tools/popuretext\|latest version from Subversion]]

	===== Usage =====		===== Usage =====

toolkit:poreencode

Tue, 30 Sep 2008 21:07:15 +0000

1199456718		current
Line 8:		Line 8:


-	===== Latest Version =====

-	poreencode is not currently distributed as part of the toolkit. You can get the [[http://translate.svn.sourceforge.net/viewvc/checkout/translate/src/trunk/tools/poreencode\|latest version from Subversion]]

	===== Usage =====		===== Usage =====

toolkit:porestructure

Tue, 30 Sep 2008 08:54:08 +0000

1200475384		current
Line 26:		Line 26:
	===== Examples =====		===== Examples =====

-	See the examples for [[poconflicts#examples]] for the complete process using poconflict, porestructure, and pomerge.	+	The documentation for poconflicts has [[poconflicts#examples]] for the complete process using poconflict, porestructure, and pomerge.

	===== Bugs =====		===== Bugs =====

	None Known		None Known

toolkit:posegment

Tue, 11 Nov 2008 08:49:52 +0000

1222763512		current
Line 5:		Line 5:
	This is useful for the creation of a file that can be used as a Translation Memory (e.g. when using [[pootle:updatetm]] to create translation memory for Pootle) as you should get better matching after you have exposed translated sentences that might occur elsewhere in your work.		This is useful for the creation of a file that can be used as a Translation Memory (e.g. when using [[pootle:updatetm]] to create translation memory for Pootle) as you should get better matching after you have exposed translated sentences that might occur elsewhere in your work.

		+	Posegment won't do very advanced sentence boundary detection and alignment, but has customisations for the punctuation rules of several languages (Amharic, Afrikaans, Arabic, Armenian, Chinese, Greek, Japanese, Khmer, Oriya, Persian). For the purpose of increasing your TM (as described below), it is already very useful. Give it a try and help us to improve it even more for your language.

	===== Usage =====		===== Usage =====

toolkit:posplit

Tue, 30 Sep 2008 21:05:47 +0000

1199455783		current
Line 11:		Line 11:


-	===== Latest Version =====

-	posplit is not currently distributed as part of the toolkit. You can get the [[svn>trunk/tools/posplit\|latest version from Subversion]]

	===== Usage =====		===== Usage =====

toolkit:poswap

Mon, 21 Jul 2008 21:06:27 +0000

1200475385		current
Line 1:		Line 1:
	====== poswap ======		====== poswap ======

-	This tool builds a new translation file with the target text (translation) of the input file(s) as source language of the output file it creates. As an example, this makes it possible to have French as the source file for translation, rather than English. poswap was introduced in version 1.0 of the translate toolkit.	+	This tool builds a new translation file with the target text (translation) of the input file(s) as source language of the output file it creates.

-	Note that this requires no change in the software project and is only a manipulation of the strings in the existing files. The only requirement for this tool is a French translation.	+	This makes it possible to have French as the source file for translation, rather than English. Note that this requires no change in the software project and is only a manipulation of the strings in the existing files. The only requirement for this tool is a French translation.
		+
		+	It can also be used to convert translatable files that use logical IDs instead of source text into a format usable by human localisers.

	===== Usage =====		===== Usage =====

toolkit:pot2po

Mon, 17 Mar 2008 10:16:41 +0000

1205748831		current
Line 49:		Line 49:
	* If we cannot find a match we will first look through the current and obsolete messages and then through any global translation memory		* If we cannot find a match we will first look through the current and obsolete messages and then through any global translation memory
	* Fuzzy matching makes use of the [[Levenshtein distance]] algorithm to detect the best matches		* Fuzzy matching makes use of the [[Levenshtein distance]] algorithm to detect the best matches
		+
		+
		+	===== Performance =====
		+
		+	Fuzzy matches are usually of good quality. Installation of the [[https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=260161\|python-Levenshtein]] package will speed up fuzzy matching. Without this a Python based matcher is used which is considerably slower.
		+
		+	Install psyco for additional speedup (it is used by most toolkit tools if it is installed.)

	===== Bugs =====		===== Bugs =====

	* [[pomerge]] and pot2po should probably become one.		* [[pomerge]] and pot2po should probably become one.
-	* Versions before 1.0 were slow, but 1.0 should be much faster. Fuzzy matches are usually of good quality. Installation of the [[https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=260161\|python-Levenshtein]] package will speed up fuzzy matching. Remember to install psyco for speedup. (It is used by most toolkit tools if it is installed.)

toolkit:poterminology

Wed, 12 Aug 2009 17:35:46 +0000

1227634919		current
Line 152:		Line 152:
	While poterminology ignores XML/HTML entities and elements and %-style format strings (for C and Python), it does not ignore all types of "variables" that may occur, particularly in OpenOffice.org, Mozilla, or Gnome localization files. These other types should be ignored as well (this enhancement is tracked as "bug" [[bug>598]]).		While poterminology ignores XML/HTML entities and elements and %-style format strings (for C and Python), it does not ignore all types of "variables" that may occur, particularly in OpenOffice.org, Mozilla, or Gnome localization files. These other types should be ignored as well (this enhancement is tracked as "bug" [[bug>598]]).

-	Terms containing only words that are ignored individually, but not excluded from phrases (e.g. "you are you") may be generated by poterminology, but aren't generally useful. Adding a new threshold option --nonstop-needed could allow these to be suppressed.	+	Terms containing only words that are ignored individually, but not excluded from phrases (e.g. "you are you") may be generated by poterminology, but aren't generally useful. Adding a new threshold option --nonstop-needed could allow these to be suppressed (this enhancement is tracked as "bug" [[bug>1102]]).

	Pootle ignores parenthetical comments in source text when performing terminology matching; this allows for terms like "scan (verb)" and "scan (noun)" to both be provided as suggestions for a message containing "scan." poterminology does not provide any special handling for these, but it could use them to provide better handling of different translations for a single term. This would be an improvement over the current approach, which marks the term fuzzy and includes all variants, with location information in {} braces in the automatically extracted translation.		Pootle ignores parenthetical comments in source text when performing terminology matching; this allows for terms like "scan (verb)" and "scan (noun)" to both be provided as suggestions for a message containing "scan." poterminology does not provide any special handling for these, but it could use them to provide better handling of different translations for a single term. This would be an improvement over the current approach, which marks the term fuzzy and includes all variants, with location information in {} braces in the automatically extracted translation.

toolkit:poterminology_stopword_file

Tue, 30 Sep 2008 19:39:57 +0000

	current
Line 1:	Line 1:
	+	====== Stopword file format ======
	+
	+	The default stopword file for [[poterminology]] describes the syntax of these files and provides a good default for most applications using English source text. You can find the location of the default stopword file by looking at the output of poterminology --help, or using the following command:
	+
	+	poterminology --manpage \| sed -n '/STOPFILE/s/.(\(.\)).*/\1/p'
	+
	+	<note>New in v1.2</note>
	+
	+	===== Overview =====
	+
	+	The basic syntax of this file is line-oriented, with the first character of each line determining its function. The order of the lines is generally not significant (with one exception noted below), and the selection of function characters was made so that an ASCII sort of the file would leave it in a generally logical order (except for comment lines).
	+
	+	Apart from comment lines (which begin with '#') and empty lines (which are also ignored), there are three general types of lines, which may appear in any order:
	+
	+	* case mapping specifiers
	+
	+	* stoplist regular expressions
	+
	+	* stoplist words
	+
	+	==== Case mapping specifiers ====
	+
	+	A line beginning with a '!' specifies upper-/lower-case mapping for words or phrases before comparison with this stoplist (no mapping is applied to the words or regular expressions in this file, only to the source messages). The second character on this line must be one of the following:
	+
	+	* C no uppercase / lowercase mapping is performed
	+	* F 'Title Case" words / terms are folded to lower case (default)
	+	* I all words are mapped to lowercase
	+
	+	These correspond to the equivalent --preserve-case / --fold-titlecase / --ignore-case options to poterminology, but are completely independent and only apply to stoplist matching. You can run poterminology with -I to map all terms to lowercase, and if the case mapping specifier in the stopword file is '!C' a stoplist with "pootle" in it will not prevent a term containing "Pootle" from passing the stoplist (and then being mapped to "pootle").
	+
	+	There should only be one case mapping specifier in a stoplist file; if more than one are present, the last one will take precedence over the others, and its mapping will apply to all entries. If multiple stoplist files are used, the last case mapping specifier processed will apply to all entries in all files.
	+
	+	==== Stoplist regular expressions ====
	+
	+	Lines beginning with a '/' are regular expression patterns - any word that matches will be ignored by itself, and any phrase containing it will be excluded as well. The regular expression consists of all characters on the line following the initial '/' - these are extended regular expressions, so grouping, alternation, and such are available.
	+
	+	Regular expression patterns are only checked if the word itself does not appear in the stoplist file as a word entry. The regular expression patterns are always applied to individual words, not phrases, and must match the entire word (i.e. they are anchored both at the start and end).
	+
	+	Use regular expressions sparingly, as evaluating them for every word in the source files can be expensive. In addition to stoplist regular expressions, poterminology has precompiled patterns for C and Python format specifiers (e.g. %d) and XML/HTML <elements> and &entities; - these are removed before stoplist processing and it is not possible to override this.
	+
	+	==== Stoplist words ====
	+
	+	All other lines should begin with one of the following characters, which indicate whether the word should be ignored (as a word alone), disregarded in a phrase (i.e. a phrase containing it is allowed, and the word does not count against the --term-words length limit), or any phrase containing it should be excluded.
	+
	+	* + allow word alone, allow phrases containing it
	+	* : allow word alone, disregarded (for --term-word-length) inside phrase
	+	* < allow word alone, but exclude any phrase containing it
	+	* = ignore word alone, but allow phrases containing it
	+	* > ignore word alone, disregarded (for --term-word-length) inside phrase
	+	* @ ignore word alone, and exclude any phrase containing it
	+
	+	Generally '+' is only needed for exceptions to regular expression patterns, but it may also be used to override an entry in a previous stoplist if you are using multiple stoplists.
	+
	+	Note that if a word appears multiple times in a stoplist file with different function characters preceding it, the __last entry will take precedence__ over the others. This is the only exception to the general rule that order is not important in stopword files.
	+
	+	===== Default file example =====
	+
	+	# apply title-case folding to words before comparing with this stoplist
	+	!F
	+
	+	The fold-titlecase setting is the default, even if it were not explicitly specified. This allows capitalized words at the start of a sentence (e.g. "Who") to match a stopword "who" but allows acronyms like WHO (World Health Organization) to be included in the terminology. If you are using poterminology with source files that contain large amounts of ALL UPPERCASE TEXT you may find the ignore-case setting to be preferable.
	+
	+	# override regex match below for phrases with 'no'
	+	+no
	+
	+	The regular expression /..? below would normally match the word 'no' and both ignore it as a term and exclude any phrases containing it. The above will allow it to appear as a term and in phrases.
	+
	+	# ignore all one or two-character words (unless =word appears below)
	+	/..?
	+	# ignore words with parenthesis, typically function() calls and the like
	+	/.\(.
	+	# ignore numbers, both cardinal (e.g. 1,234.0) and ordinal (e.g. 1st, 22nd)
	+	/[0-9,.]+(st\|nd\|rd\|th)?
	+
	+	These regular expressions ignore a lot of uninteresting terms that are typically code or other things that shouldn't be translated anyhow. There are many exceptions to the one or two-character word pattern in the default stoplist file, not only with = like '=in' but also '+no' and ':on' and '<ok' and '>of'.
	+
	+	# allow these words by themselves and don't count against length for phrases
	+	:off
	+	:on
	+
	+	These prepositions are common as button text and thus useful to have as terms; they also form an important part of phrases so are disregarded for term word count to allow for slightly longer phrases including them.
	+
	+	# allow these words by themselves, but ignore any phrases containing them
	+	<first
	+	<hello
	+	<last
	+
	+	These are words that are worth including in a terminology, as they are common in applications, but which aren't generally part of idiomatic phrases.
	+
	+	# ignore these words by themselves, but allow phrases containing them
	+	=able
	+	=about
	+	=actually
	+	=ad
	+	=as
	+	=at
	+
	+	This is the largest category of stoplist words, and these are all just rather common words. The purpose of a terminology list is to provide specific translation suggestions for the harder words or phrases, not provide a general dictionary, so these words are not of interest by themselves, but may well be part of an interesting phrase.
	+
	+	# ignore these words by themselves, but allow phrases containing them, and
	+	# don't count against length for phrases
	+	#
	+	# (possible additions to this list for multi-lingual text: >di >el >le)
	+	#
	+	>a
	+	>an
	+	>and
	+
	+	These very common words aren't of interest by themselves, but often form an important part of phrases so are disregarded for term word count to allow for slightly longer phrases including them.
	+
	+	# ignore these words and any phrases containing them
	+	@ain't
	+	@aint
	+	@al
	+	@are
	+
	+	These are "junk" words that are not only uninteresting by themselves, they generally do not contribute anything to the phrases containing them.

toolkit:pretranslate

Tue, 02 Dec 2008 18:32:11 +0000

	current
Line 1:	Line 1:
	+	====== pretranslate ======
	+
	+	Merge existing translations from an old translation file to a new one as well as fill any missing translations from translation memory via fuzzy matching.
	+
	+	This functionality used to be part of pot2po and corresponds to "msgmerge" from the gettext package.
	+
	+	pretranslate works on PO and XLIFF files.
	+
	+	===== Usage =====
	+
	+	pretranslate [options] <input> <output>
	+
	+	Where:
	+	\| <input> \| is the translation file or directory to be pretranslate \|
	+	\| <output> \| is the translation file or a directory where the pretranslated version will be stored \|
	+
	+	Options:
	+	\| --version \| show program's version number and exit \|
	+	\| -h, --help \| show this help message and exit \|
	+	\| --manpage \| output a manpage based on the help \|
	+	\| [[--progress=PROGRESS]] \| show progress as: dots, none, bar, names, verbose \|
	+	\| [[--errorlevel=ERRORLEVEL]] \| show errorlevel as: none, message, exception, traceback \|
	+	\| -iINPUT, --input=INPUT \| read from INPUT in pot format \|
	+	\| -xEXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|
	+	\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in po, pot formats \|
	+	\| -tTEMPLATE, --template=TEMPLATE \| read old translations from TEMPLATE \|
	+	\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|
	+	\| --tm=TM \| The file to use as translation memory when fuzzy matching \|
	+	\| -sMIN_SIMILARITY, --similarity=MIN_SIMILARITY \| The minimum similarity for inclusion (default: 75%) \|
	+	\| --nofuzzymatching \| Disable all fuzzy matching \|
	+
	+	===== Examples =====
	+
	+	pretranslate -t zu-1.0.1 -tm zu_tm.po zu-2.0.2 zu-2.0.2-translated
	+
	+	Here we are pretranslating the PO or XLIFF files in //zu-2.0.2// using the old translations in //zu-1.0.1// and fuzzy matches from the zu_tm.po
	+	compendium. the result is stored in //zu-2.0.2-translate//
	+
	+	unlike pot2po pretranslate will not change anything in the input file except merge translations, no reordering or changes to headers.
	+
	+	===== Merging =====
	+
	+	It helps to understand when and how pretranslate will merge. The default is to follow msgmerge's behaviour but we add some extra features with fuzzy matching:
	+
	+	* If everything matches we carry that across
	+	* We can resurrect obsolete messages for reuse
	+	* If we cannot find a match we will first look through the current and obsolete messages and then through any global translation memory
	+	* Fuzzy matching makes use of the [[Levenshtein distance]] algorithm to detect the best matches
	+
	+
	+	===== Performance =====
	+
	+	Fuzzy matches are usually of good quality. Installation of the [[https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=260161\|python-Levenshtein]] package will speed up fuzzy matching. Without this a Python based matcher is used which is considerably slower.
	+
	+	Install psyco for additional speedup (it is used by most toolkit tools if it is installed.)

toolkit:progress_progress

Sat, 28 Jul 2007 20:13:15 +0000

1185653571		current
Line 3:		Line 3:
	All of the programs can give visual feedback. This options allows you to select the style of that feedback.		All of the programs can give visual feedback. This options allows you to select the style of that feedback.

-	In the examples we are converting and OpenOffice.org 2.0 sdf/gsi file into POT files using [[toolkit:oo2po]].	+	In the examples we are converting and OpenOffice.org 2.0 sdf/gsi file into POT files using [[oo2po]].

	===== none =====		===== none =====

toolkit:prop2po

Mon, 15 Jun 2009 13:26:53 +0000

1209480061		current
Line 28:		Line 28:
	\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|		\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|
	\| -P, --pot \| output PO Templates (.pot) rather than PO files (.po) \|		\| -P, --pot \| output PO Templates (.pot) rather than PO files (.po) \|
		+	\| [[--personality=TYPE]] \| set the input behaviour: java (default), mozilla \|
	\| [[--duplicates=DUPLICATESTYLE]] \| what to do with duplicate strings (identical source text): merge (default), msgid_comment, msgctxt, keep, msgid_comment_all \|		\| [[--duplicates=DUPLICATESTYLE]] \| what to do with duplicate strings (identical source text): merge (default), msgid_comment, msgctxt, keep, msgid_comment_all \|

toolkit:properties

Thu, 26 Mar 2009 09:23:47 +0000

1193560910		current
Line 1:		Line 1:
	====== Mozilla and Java properties files ======		====== Mozilla and Java properties files ======

-	The Translate Toolkit can manage Java .properties files	+	The Translate Toolkit can manage Java .properties files with the [[prop2po]] and po2prop tool. As part of the Mozilla localisation process, the [[moz2po]] tool handles the properties files along with the other files.

	===== Features =====		===== Features =====

toolkit:psyco_mode

Sat, 26 Jan 2008 21:23:38 +0000

1201382618		current
Line 7:		Line 7:
	By default it is switched on, so you can safely ignore this option and benefit from psyco optimisations anyway.		By default it is switched on, so you can safely ignore this option and benefit from psyco optimisations anyway.

-	Note psyco only work on i386 architectures.	+	Note psyco only works on i386 architectures.

	To install psyco, you can look for it in your distribution's packages, or obtain it here: http://psyco.sourceforge.net/		To install psyco, you can look for it in your distribution's packages, or obtain it here: http://psyco.sourceforge.net/

toolkit:py2web2po

Thu, 05 Feb 2009 13:26:10 +0000

1233840370		current
Line 3:		Line 3:
	Converts web2py translation files to PO files and vice versa.		Converts web2py translation files to PO files and vice versa.

-	Web2py ([[http://mdp.cti.depaul.edu]], formerly known as Gluon) is a open-source, Python-based web application framework by Massimo Di Pierro (inspired by Django and Rails).	+	Web2py ([[http://mdp.cti.depaul.edu]], formerly known as Gluon) is an open-source, Python-based web application framework by Massimo Di Pierro (inspired by Django and Rails).

	Web2py uses an internal localization engine based on Python dictionaries, which is applied with the T() lookup function. Web2py provides a built-in translation interface for the T()-engine, which is excellent for rapid application development.		Web2py uses an internal localization engine based on Python dictionaries, which is applied with the T() lookup function. Web2py provides a built-in translation interface for the T()-engine, which is excellent for rapid application development.

toolkit:qm

Tue, 24 Feb 2009 12:39:02 +0000

1188285483		current
Line 1:		Line 1:
	====== Qt .qm ======		====== Qt .qm ======
-
-	NOTE: In still to be released 1.1 of the toolkit

	A .qm file is a compiled Qt [[.ts]] file. In many ways it is similar to Gettext, in that it uses a hashing table to lookup the translated text. In older version they store only the hash and the translation which doesn't make the format useful for recovering translated text.		A .qm file is a compiled Qt [[.ts]] file. In many ways it is similar to Gettext, in that it uses a hashing table to lookup the translated text. In older version they store only the hash and the translation which doesn't make the format useful for recovering translated text.

toolkit:qt_phrase_book

Sun, 21 Sep 2008 01:45:48 +0000

1221961516		current
Line 21:		Line 21:
	There are no missing features in our support in the toolkit. The only slight difference are:		There are no missing features in our support in the toolkit. The only slight difference are:

-	* We don't focus on adding and removing items, just updating and reading	+	* We don't focus on adding and removing items, just updating and reading
-	* Comments are not properly escaped on reading, they might be on writing	+	* Comments are not properly escaped on reading, they might be on writing
-	* An XML header is output on writing while it seems that no files in the wild contain an XML header.	+	* An XML header is output on writing while it seems that no files in the wild contain an XML header.
-	* The ''<definition>'' is aimed at users, the toolkits addnote feature focuses on programmer, translators, etc comments while there is really only one source of comments in a .qph. This causes duplication on the offline editor.	+	* The ''<definition>'' is aimed at users, the toolkits addnote feature focuses on programmer, translators, etc comments while there is really only one source of comments in a .qph. This causes duplication on the offline editor.

toolkit:quoting_and_escaping

Sat, 28 Jul 2007 20:00:58 +0000

1149694565		current
Line 22:		Line 22:
	Strings are quoted using either double or single quotes. The quoting character may not occur within the string. There is no provision for escaping. XML entities can be used e.g. ''''' can be used to denote a single quote within the single-quoted string.		Strings are quoted using either double or single quotes. The quoting character may not occur within the string. There is no provision for escaping. XML entities can be used e.g. ''''' can be used to denote a single quote within the single-quoted string.

-	Some DTD files seem to have backslash-escapes, but these are anomalies: see [[http://groups.google.com/group/mozilla.dev.l10n/browse_thread/thread/58256c1f59c22798/b4bac2de4182f3e0\|discussion thread on mozilla l10n-dev]]	+	Some DTD files seem to have backslash-escapes, but these are anomalies: see [[http://groups.google.com/group/mozilla.dev.l10n/browse_thread/thread/58256c1f59c22798/b4bac2de4182f3e0\|discussion thread on Mozilla l10n-dev]]

	===== Mozilla properties format =====		===== Mozilla properties format =====

toolkit:rc

Tue, 28 Apr 2009 14:15:59 +0000

1207727651		current
Line 1:		Line 1:
	====== Windows RC files ======		====== Windows RC files ======

-	Windows .rc files, or resource files, are used to store translatable text, dialogs, menu, etc. for Windows application.	+	Windows .rc files, or resource files, are used to store translatable text, dialogs, menu, etc. for Windows applications. The format can be handled by the Translate Toolkit [[rc2po]] and po2rc.

	<note>New in v1.2</note>		<note>New in v1.2</note>

toolkit:rc2po

Mon, 23 Feb 2009 13:32:37 +0000

1209051761		current
Line 2:		Line 2:

	Converts Windows Resource .rc files to Gettext PO format.		Converts Windows Resource .rc files to Gettext PO format.
-
-	<note>New in v1.2</note>

	===== Usage =====		===== Usage =====
Line 41:		Line 39:
	\| [[--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|		\| [[--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|
	\| --charset=CHARSET \| charset to use to decode the RC files (default: utf-8) \|		\| --charset=CHARSET \| charset to use to decode the RC files (default: utf-8) \|
		+	\| --lang=LANG \| LANG entry \|
		+	\| --sublang=SUBLANG \| SUBLANG entry (default: SUBLANG_DEFAULT) \|
	\| --fuzzy \| use translations marked fuzzy \|		\| --fuzzy \| use translations marked fuzzy \|
	\| --nofuzzy \| don't use translations marked fuzzy (default) \|		\| --nofuzzy \| don't use translations marked fuzzy (default) \|

toolkit:rewrite_style

Wed, 29 Jul 2009 14:11:31 +0000

1245136320		current
Line 75:		Line 75:
	This allows a translator or programmer to test a programs ability to use Unicode message strings. By using characters in the Unicode range but that are related to the plain Latin characters that they replace we ensure that the messages are still readable.		This allows a translator or programmer to test a programs ability to use Unicode message strings. By using characters in the Unicode range but that are related to the plain Latin characters that they replace we ensure that the messages are still readable.

-	Note: The rewrite rule will also rewrite variables which will cause problems in some situations. Run [[pofilter]] as a quick method to fix up rewritten variables.	+	Note: Before version 1.4, the rewrite rule will also rewrite variables and XML tags, which will cause problems in some situations. Run [[pofilter]] as a quick method to fix up incorrect changes, or upgrade to version 1.4.

toolkit:running_the_tools_on_microsoft_windows

Mon, 27 Aug 2007 12:22:27 +0000

1186567913		current
Line 23:		Line 23:
	C:\Program Files\GnuWin32\bin\		C:\Program Files\GnuWin32\bin\

		+	===== Change Windows file to Unix file ======
		+
		+	Some programs in Windows will add CRLFs to the file which is considered rather poor practice for l10ns that require Unix files. To fix a text file, drag and drop it to the dos2unix.exe utility at Bastet.com:
		+
		+	[[http://www.bastet.com/]]

toolkit:sub2po

Mon, 22 Jun 2009 12:22:27 +0000

	current
Line 1:	Line 1:
	+	====== sub2po and po2sub ======
	+
	+	sub2po allows you to use the same principles of PO files with [[subtitles]]. In PO only items that change are marked fuzzy and only new items need to be translated, unchanged items remain unchanged for the translation.
	+
	+
	+	===== Usage =====
	+
	+	sub2po [options] <foo.srt> <foo.po>
	+	po2sub [options] [-t <foo.srt>] <XX.po> <foo-XX.srt>
	+
	+	Where:
	+	\| foo.srt \| is the input subtitle file \|
	+	\| foo.po \| is an empty PO file that may be translated \|
	+	\| XX.po \| is a PO file translated into the XX language \|
	+	\| foo-XX.srt \| is the foo.srt file translated into language XX \|
	+
	+	Options (sub2po):
	+
	+	\| --version \| show program's version number and exit \|
	+	\| -h, --help \| show this help message and exit \|
	+	\| --manpage \| output a manpage based on the help \|
	+	\| [[--progress=PROGRESS]] \| show progress as: dots, none, bar, names, verbose \|
	+	\| [[--errorlevel=ERRORLEVEL]] \| show errorlevel as: none, message, exception, traceback \|
	+	\| -iINPUT, --input=INPUT \| read from INPUT in .srt format \|
	+	\| -xEXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|
	+	\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in po, pot formats \|
	+	\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|
	+	\| -P, --pot \| output PO Templates (.pot) rather than PO files (.po) \|
	+	\| [[--duplicates=DUPLICATESTYLE]] \| what to do with duplicate strings (identical source text): merge, msgctxt (default) \|
	+
	+	Options (po2sub):
	+
	+	\| --version \| show program's version number and exit \|
	+	\| -h, --help \| show this help message and exit \|
	+	\| --manpage \| output a manpage based on the help \|
	+	\| [[--progress=PROGRESS]] \| show progress as: dots, none, bar, names, verbose \|
	+	\| [[--errorlevel=ERRORLEVEL]] \| show errorlevel as: none, message, exception, traceback \|
	+	\| -iINPUT, --input=INPUT \| read from INPUT in po, pot formats \|
	+	\| -xEXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|
	+	\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in srt format \|
	+	\| -tTEMPLATE, --template=TEMPLATE \| read from TEMPLATE in txt format \|
	+	\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|
	+	\| --fuzzy \| use translations marked fuzzy \|
	+	\| --nofuzzy \| don't use translations marked fuzzy (default) \|
	+
	+	==== Examples ====
	+
	+	To create the POT files is simple:
	+
	+	sub2po -P SUBTITLE_FILE subtitles.pot
	+
	+	A translator would copy the POT file to their own PO file and then create translations of the entries. If you wish to create a PO file and not a POT file then leave off the //-P// option.
	+
	+	To convert back:
	+
	+	po2sub -t SUBTITLE_FILE subtitles-XX.po subtitles-XX.srt
	+
	+
	+	==== Translating ====
	+
	+	Translate as normal. However, see the issues mentioned at [[subtitles]].
	+
	+	==== Bugs ====
	+	There might be some issues with encodings, since the srt files don't specify them. We assume files to be encoded in UTF-8, so a conversion should solve this easily. Note that most of the handling of the srt files come from gaupol.

toolkit:subtitles

Mon, 22 Jun 2009 11:07:47 +0000

1234466812		current
Line 1:		Line 1:
	====== Subtitles ======		====== Subtitles ======
		+
		+	The translation of subtitles are supported in the toolkit with the commands [[sub2po]] and po2sub.

	The following formats are supported for subtitles:		The following formats are supported for subtitles:

toolkit:support_for_toolkit_tmx

Mon, 29 Oct 2007 08:19:50 +0000

	current
Line 1:	Line 1:
	+
	+	===== Support for TMX =====
	+
	+	Although TMX is supposed to be an exchange standard, not all tools create or read standard TMX files, and consequently some tools may not be able to use the Toolkit's TMXes and vice versa.
	+
	+	Have a good Unicode editor handy so that you can fiddle with the encoding of the file in extreme cases. For MS Windows users, we suggest Babelpad.
	+
	+	=== How they were tested ===
	+
	+	I tested other tools by checking if they import Toolkit TMXes without complaint, and in some cases if I could get translation matches from it. I tested their TMXes with the Toolkit by doing a pocount on the TMX and doing a pot2po (with --tm=file.tmx) on a file with known matches.
	+
	+	==== Support for Toolkit TMXes ====
	+
	+	=== Cafetran 2007 ===
	+
	+	Seems fully compatible with Tranlate-toolkit, in both directions. Cafetran imports our TMX without complaints. A Cafetran user was able to read and use one of our TMXes, and we were able to test and use one of the Cafetran user's TMXes.
	+
	+	=== Wordfast 5 ===
	+
	+	Fully compatible with Translate-toolkit. Wordfast opens our TMXes directly and converts them to its own internal format. Wordfast can also export to TMX, which can be read by our tools. Remember, Wordfast's Unicode format is UTF16LE with BOM, so if you run into problems, try converting it by character encoding. Wordfast 3 and 4 should also work.
	+
	+	=== Trados 2007 (Workbench 8) ===
	+
	+	Possibly compatible with Translate-toolkit. To import using Trados, first create a Trados TM and then import the TMX into it. Trados did import our test TMX (22000 segments) but it lost about 30% of the segments in the process. Our tools can read TMXes exported from Trados.
	+
	+	=== OmegaT 1.6 ===
	+
	+	Fully compatible with Translate-toolkit. Simply place our TMXes in the /tm/ folder of your project. All of OmegaT's exported TMXes can be read by the Translate-toolkit -- although which one you use will depend on what your workflow is (i.e. with OmegaT's internal tags or without them).
	+
	+	==== No or little support for Toolkit TMXes ====
	+
	+	=== Aid Trans Professional 2.0 ===
	+
	+	Actually, this tool is still in beta and it kept crashing when I tested it, but I was able to discover one thing: the TMX DTD (called tmx14.dtd) must be in the same folder as the TMX file you're trying to import.
	+
	+	=== Transolution ===
	+
	+	I was unable to test this tool because I couldn't figure out how it works.
	+
	+	=== Across ===
	+
	+	This tool was too big for me to test (several hundreds of megabytes).
	+
	+	=== Deja Vu ===
	+
	+	I was unable to test this tool because I couldn't figure out how it works.
	+

toolkit:symb2po

Thu, 05 Feb 2009 09:10:56 +0000

1229507449		current
Line 3:		Line 3:
	Converts Symbian-style translation files to PO files and vice versa. The Symbian translation files currently have a strong Buddycloud flavour, but the tools will be made more general as the need arises.		Converts Symbian-style translation files to PO files and vice versa. The Symbian translation files currently have a strong Buddycloud flavour, but the tools will be made more general as the need arises.

-	<note>These tools currently only appear in the development version of the toolkit. You can get it by [[toolkit:installation\|checking out the code from Subverion]]</note>	+	<note>Appears in version 1.3 of the toolkit.</note>

	===== Usage =====		===== Usage =====

toolkit:tbx

Fri, 20 Mar 2009 15:50:36 +0000

1237564172		current
Line 103:		Line 103:
	<code xml>		<code xml>
	<termEntry id="4324 (8)">		<termEntry id="4324 (8)">
-	<note>tag1, tag2, tag3 (7) (Actually not clear what the best mapping to TBX is in this case.)	+	<note>tag1, tag2, tag3 (7) -
		+	(Actually not clear what the best mapping to TBX is in this case.)</note>
	<langSet xml:lang="en">		<langSet xml:lang="en">
	<tig>		<tig>

toolkit:text

Thu, 11 Oct 2007 12:29:00 +0000

1192105700		current
Line 4:		Line 4:

	In some cases you will need to adjust the source text for the conversion management to work well. This is because the text file format support considered units to be space separated blocks of text.		In some cases you will need to adjust the source text for the conversion management to work well. This is because the text file format support considered units to be space separated blocks of text.
		+

	===== Example =====		===== Example =====
Line 9:		Line 10:
	Heading		Heading
	=======		=======
		+
	Paragraph One		Paragraph One
		+
	Paragraph Two:		Paragraph Two:
	* First bullet		* First bullet

toolkit:tiki2po

Mon, 15 Dec 2008 18:26:47 +0000

	current
Line 1:	Line 1:
	+	====== tiki2po ======

	+	Converts [[http://tikiwiki.org\|TikiWiki]] language.php files to Gettext PO format.
	+
	+	===== Usage =====
	+
	+	tiki2po [options] <tiki> <po>
	+	po2tiki [options] <po> <tiki>
	+
	+	Where:
	+	\| <tiki> \| is a valid language.php file for TikiWiki \|
	+	\| <po> \| is a PO file \|
	+
	+	Options (tiki2po):
	+	\| --version \| show program's version number and exit \|
	+	\| -h, --help \| show this help message and exit \|
	+	\| --manpage \| output a manpage based on the help \|
	+	\| [[--progress=PROGRESS]] \| show progress as: dots, none, bar, names, verbose \|
	+	\| [[--errorlevel=ERRORLEVEL]] \| show errorlevel as: none, message, exception, traceback \|
	+	\| -i INPUT, --input=INPUT \| read from INPUT in php format \|
	+	\| -x EXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|
	+	\| -o OUTPUT, --output=OUTPUT \| write to OUTPUT in po, pot formats \|
	+	\| --include-unused \| When converting, include strings in the "unused" section? \|
	+
	+	Options (po2tiki):
	+	\| --version \| show program's version number and exit \|
	+	\| -h, --help \| show this help message and exit \|
	+	\| --manpage \| output a manpage based on the help \|
	+	\| [[--progress=PROGRESS]] \| show progress as: dots, none, bar, names, verbose \|
	+	\| [[--errorlevel=ERRORLEVEL]] \| show errorlevel as: none, message, exception, traceback \|
	+	\| -i INPUT, --input=INPUT \| read from INPUT in po, pot formats \|
	+	\| -x EXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|
	+	\| -o OUTPUT, --output=OUTPUT \| write to OUTPUT in php format \|
	+
	+	===== Examples =====
	+
	+	These examples demonstrate the use of tiki2po:
	+
	+	tiki2po language.php language.po
	+
	+	Convert the tiki language.php file to .po
	+
	+	po2tiki language.po language.php
	+
	+	Convert a .po file to a tiki language.php file
	+
	+
	+	===== Notes =====
	+
	+	* Templates are not currently supported.
	+
	+	===== Bugs =====
	+
	+	None known

toolkit:tmserver

Thu, 15 Jan 2009 15:07:00 +0000

	current
Line 1:	Line 1:
	+	====== tmserver ======
	+	tmserver is a Translation Memory service that can be queried via HTTP using a simple REST like URL/http and data is exchanged between server and client encoded in JSON
	+
	+	===== Usage =====
	+	tmserver.py --bind=HOSTNAME --port=PORT [--tmdb=TMDBFILE] [--import-translation-file=TMFILE [--import-source-lang=SOURCE_LANG] [--import-target-lang=TARGET_LANG]]
	+
	+	TMDBFILE is the sqlite database file containing [[tmdb]] translation memory data, if not specified a new temporary database is created
	+
	+	TMFILE is a translation file (po, xliff, etc.) that should be imported into the database (mostly useful when no tmdb file is specified).
	+
	+	Options:
	+	\| -h, --help \| show this help message and exit \|
	+	\| -d TMDBFILE, --tmdb=TMDBFILE \| translation memory database \|
	+	\| -f TMFILES, --import-translation-file=TMFILE \| translation file to import into the database \|
	+	\| -t TARGET_LANG, --import-target-lang=TARGET_LANG \| target language of translation files \|
	+	\| -s SOURCE_LANG, --import-source-lang=SOURCE_LANG \| source language of translation files \|
	+	\| -b BIND, --bind=HOSTNAME \| adress to bind server to \|
	+	\| -p PORT, --port=PORT \| port to listen on \|
	+
	+	===== Testing =====
	+	easiest way to run the server for testing is to pass it a large translation file (maybe generated by [[pocompendium]]) to create a tmdb database on the fly.
	+
	+	tmserver -b localhost -p 8080 -f compendium.po -s en_US -t ar
	+
	+	The server can be queried using a webbrowser. the url would be http://HOST:PORT/tmserver/SOURCE_LANG/TARGET_LANG/unit/STRING
	+
	+	So to see suggestions for "open file" try the url http://localhost:8080/tmserver/en_US/ar/unit/open+file
	+
	+	===== API =====
	+	===== Example Client =====

toolkit:tmx

Sat, 28 Jul 2007 20:02:53 +0000

1138788346		current
Line 3:		Line 3:

	===== Standard conformance =====		===== Standard conformance =====
		+
		+	FIXME: I think with base class and string escaping we now do strip markup in as much as we have relatively standard escaping (DB)
		+
	Summary: TMX version 1.4 conformance to Level 1, except that no markup is stripped.		Summary: TMX version 1.4 conformance to Level 1, except that no markup is stripped.
	* All required header fields are supplied.		* All required header fields are supplied.
	* The adminlang field in the header is always English.		* The adminlang field in the header is always English.
-	* Non of the optional header fields are supplied.	+	* None of the optional header fields are supplied.
	* We assume that only two languages are used (source and single target language).		* We assume that only two languages are used (source and single target language).
	* No special consideration for segmentation.		* No special consideration for segmentation.
	* Currently text is treated as plain text, in other words no markup like HTML inside messages are stripped or interpreted as it should be for complete Level 1 conformance.		* Currently text is treated as plain text, in other words no markup like HTML inside messages are stripped or interpreted as it should be for complete Level 1 conformance.

toolkit:ts

Fri, 12 Jun 2009 09:42:27 +0000

1244799651		current
Line 25:		Line 25:
	* byte: within various text areas		* byte: within various text areas
	* translation: obsolete (currently handled with comments in conversion to PO. But should be able to convert Obsolete PO back into obsolete TS. This might mean moving this format properly onto the base class).		* translation: obsolete (currently handled with comments in conversion to PO. But should be able to convert Obsolete PO back into obsolete TS. This might mean moving this format properly onto the base class).
		+	* lengthvariants
		+	* *comment: various new comment fields
		+	* old*: ability to store previous source and comments

	===== Validate =====		===== Validate =====

toolkit:ts2po

Wed, 16 Jan 2008 09:23:07 +0000

1199865798		current
Line 25:		Line 25:
	\| -xEXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|		\| -xEXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|
	\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in po, pot formats \|		\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in po, pot formats \|
-	\| [[--psyco=PSYCO\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|	+	\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|
	\| -P, --pot \| output PO Templates (.pot) rather than PO files (.po) \|		\| -P, --pot \| output PO Templates (.pot) rather than PO files (.po) \|

Line 38:		Line 38:
	\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in ts format \|		\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in ts format \|
	\| -tTEMPLATE, --template=TEMPLATE \| read from TEMPLATE in ts format \|		\| -tTEMPLATE, --template=TEMPLATE \| read from TEMPLATE in ts format \|
-	\| [[--psyco=PSYCO\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|	+	\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|

	===== Examples =====		===== Examples =====

toolkit:txt2po

Mon, 21 Jan 2008 08:28:10 +0000

1200475387		current
Line 123:		Line 123:

	First we retrieve the file in raw dokuwiki format, then we create a POT file for editing. We created a French translation and using po2txt plus the original file as a template we output fr.txt which is a French version of the original txt2po.txt. This file can now be uploaded to the wiki server.		First we retrieve the file in raw dokuwiki format, then we create a POT file for editing. We created a French translation and using po2txt plus the original file as a template we output fr.txt which is a French version of the original txt2po.txt. This file can now be uploaded to the wiki server.
		+

	==== MediaWiki ====		==== MediaWiki ====

-	To retrieve the raw media wiki syntax add '?action=raw' to you wiki URL. The following retrieves the Translate Toolkit page from Wikipedia in raw MediaWiki format [[http://en.wikipedia.org/wiki/Translate_Toolkit?action=raw]]	+	To retrieve the raw media wiki syntax add '?action=raw' to you wiki URL. The following retrieves the Translate Toolkit page from Wikipedia in raw MediaWiki format [[http://en.wikipedia.org/wiki/Translate_Toolkit?action=raw]] or [[http://en.wikipedia.org/w/index.php?title=Pootle&action=raw]].

	to process follow the instructions above but substituting the MediaWiki retrieval method.		to process follow the instructions above but substituting the MediaWiki retrieval method.

toolkit:using_csv2po

Fri, 27 Jul 2007 14:52:12 +0000

1185547849		current
Line 1:		Line 1:
	====== Using csv2po ======		====== Using csv2po ======

-	[[toolkit:csv2po]] allows you to create CSV files from PO files. This allows you to	+	[[csv2po]] allows you to create CSV files from PO files. This allows you to
	send translation work to translators who do not or cannot use PO Editors but who		send translation work to translators who do not or cannot use PO Editors but who
	can use a Spreadsheet.		can use a Spreadsheet.
Line 7:		Line 7:
	===== Quickstart =====		===== Quickstart =====

-	- [[toolkit:pofilter]] --fuzzy --review -t untranslated <po-dir> <po-filtered-dir> (this step is optional)	+	- [[pofilter]] --fuzzy --review -t untranslated <po-dir> <po-filtered-dir> (this step is optional)
	- divide into sections		- divide into sections
-	- [[toolkit:csv2po\|po2csv]] <po-dir\|po-filtered-dir> <csv-out>	+	- [[csv2po\|po2csv]] <po-dir\|po-filtered-dir> <csv-out>
	- edit in Excel or OpenOffice.org Calc		- edit in Excel or OpenOffice.org Calc
-	- [[toolkit:csv2po]] --charset=windows-1250 -t templates <csv-in> <po-in> (you must work against a template directory, the charset option corrects problems with characters sets)	+	- [[csv2po]] --charset=windows-1250 -t templates <csv-in> <po-in> (you must work against a template directory, the charset option corrects problems with characters sets)
-	- [[toolkit:phase]] - to do basic checks sort out encoding issues	+	- [[phase]] - to do basic checks sort out encoding issues
-	- [[toolkit:pomerge]] --mergeblank=no -t <po-dir> <po-in> <po-dir>	+	- [[pomerge]] --mergeblank=no -t <po-dir> <po-in> <po-dir>
	- cvs diff -u > x.diff --- check the changes		- cvs diff -u > x.diff --- check the changes
	- cvs ci --- commit changes		- cvs ci --- commit changes
Line 58:		Line 58:
	(we use zip because most people are Windows users)		(we use zip because most people are Windows users)

-	==== Creating a wordcount ====	+	==== Creating a word count ====

	Professional translators work on source word counts. So we create a word count		Professional translators work on source word counts. So we create a word count
Line 104:		Line 104:
	the csv2po command without templates as this allows you to preserve the original file layout.		the csv2po command without templates as this allows you to preserve the original file layout.
	Only run it without -t if you are dealing with a partial part of the PO that you will		Only run it without -t if you are dealing with a partial part of the PO that you will
-	merge back using a [[toolkit:pomerge]].	+	merge back using a [[pomerge]].

	Note (1): running csv2po using the input PO files as templates give spurious		Note (1): running csv2po using the input PO files as templates give spurious

toolkit:using_oo2po

Fri, 27 Jul 2007 15:03:11 +0000

1185548556		current
Line 7:		Line 7:

	- [[ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT\|Download the latest POT and GSI files]]		- [[ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT\|Download the latest POT and GSI files]]
-	- [[toolkit:oo2po]] -P <gsi> <new-pots>	+	- [[oo2po]] -P <gsi> <new-pots>

	===== Detailed Description =====		===== Detailed Description =====
Line 18:		Line 18:
	* [[ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT\|Download the latest POT and GSI files]]		* [[ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT\|Download the latest POT and GSI files]]

-	However, you will need this file if you need to use some of the other features of [[toolkit:oo2po]] such as changing the source language from English.	+	However, you will need this file if you need to use some of the other features of [[oo2po]] such as changing the source language from English.

	==== Produce the POT files using oo2po ====		==== Produce the POT files using oo2po ====

toolkit:using_pofilter

Sat, 05 Jan 2008 18:05:00 +0000

1238081044		current
Line 7:		Line 7:

	===== Quickstart =====		===== Quickstart =====
-		+	//Use any preferred text editor wherever ''vim'' is used.//
-	- pofilter -l (select a filter)	+	- Select filter(s): ''pofilter -l''
-	- pofilter -i existing_files/ -o errors/ [-t specific tests] [--excludefilter don't perform specific tests]	+	- Run filter(s): ''pofilter -i existing_files/ -o errors/ [-t specific tests] [--excludefilter don't perform specific tests]''
-	- *vim errors/.po (delete** items you don't want changed, set fuzzy if needed, delete if not needed)	+	- Delete items you don't want changed, set fuzzy if needed, delete if not needed: ''vim errors/*.po''
-	- pomerge -i errors/ -o existing_files/ -t existing_files/ (will overwrite existing files)	+	- Merge changes back: ''pomerge -i errors/ -o existing_files/ -t existing_files/'' (will overwrite existing files)
-	- cvs diff -u existing_files/ > x.diff	+	- Create a patch for the changes: ''cvs diff -u existing_files/ > x.diff''
-	- vim x.diff (check to see that the updates are what you want)	+	- Check to see that the updates are what you want: ''vim x.diff''
-	- cvs ci existing_files/	+	- Commit changes: ''cvs ci existing_files/''

	===== Detailed Description =====		===== Detailed Description =====

toolkit:wiki

Thu, 11 Oct 2007 14:29:37 +0000

1192106394		current
Line 13:		Line 13:
	* [[http://wiki.splitbrain.org/wiki:dokuwiki\|docuwiki]] - heading, bullet, numbered list		* [[http://wiki.splitbrain.org/wiki:dokuwiki\|docuwiki]] - heading, bullet, numbered list
	* [[http://www.mediawiki.org/wiki/MediaWiki\|MediaWiki]] - heading, bullet, numbered list		* [[http://www.mediawiki.org/wiki/MediaWiki\|MediaWiki]] - heading, bullet, numbered list
		+

	===== Possible uses =====		===== Possible uses =====
Line 19:		Line 20:

	With further enhancement the tool could probably be capable of converting from one wiki syntax to another, but that is of course not its main aim		With further enhancement the tool could probably be capable of converting from one wiki syntax to another, but that is of course not its main aim
		+
		+	===== Additional notes on MediaWiki =====
		+
		+	Media wiki can also export in XML format, see http://en.wikipedia.org/wiki/Special:Export and http://www.mediawiki.org/wiki/Manual:Parameters_to_Special:Export this however exports in XML so not directly usable by txt2po.
		+
		+	For importing please see http://en.wikipedia.org/wiki/Help:Import this is disabled on most wikis so not directly usable currently.

toolkit:wml

Fri, 27 Jun 2008 10:53:09 +0000

1214482846		current
Line 1:		Line 1:
	====== Wireless Markup Language ======		====== Wireless Markup Language ======
-	This page documents the support for WML and is used for planning our work on it. For more information about WML, see ....	+	This page documents the support for [[wp>Wireless Markup Language\|WML]] and is used for planning our work on it. For more information about WML, see ....

	This is implemented as a generic XML document type that is handled similarly to the way the [[developers:projects:ODF]] project handles ODF documents.		This is implemented as a generic XML document type that is handled similarly to the way the [[developers:projects:ODF]] project handles ODF documents.

toolkit:wordfast

Fri, 13 Mar 2009 10:46:47 +0000

1218031760		current
Line 1:		Line 1:
	====== Wordfast Translation Memory ======		====== Wordfast Translation Memory ======
-
-	(Only in v1.1)

	The Wordfast format, as used by the [[wp>Wordfast]] translation tool, is a simple tab delimited file.		The Wordfast format, as used by the [[wp>Wordfast]] translation tool, is a simple tab delimited file.

toolkit:xliff

Thu, 26 Mar 2009 09:31:45 +0000

1214493211		current
Line 39:		Line 39:
	===== XLIFF and other tools =====		===== XLIFF and other tools =====

-	Here is a small report on XLIFF and MS Windows tools:	+	Here is a small report on the [[guide:tools:XLIFF support by MS Windows programs]].
-		+
-	http://translate.sourceforge.net/wiki/guide/tools/xliff_support_by_ms_windows_programs	+

toolkit:xliff2oo

Wed, 09 Jan 2008 19:34:23 +0000

1199907142		current
Line 1:		Line 1:
-	~~REDIRECT>toolkit:po2oo~~	+	~~REDIRECT>toolkit:oo2po~~

toolkit:xliff2po

Thu, 05 Feb 2009 14:39:28 +0000

1200475388		current
Line 2:		Line 2:

	Converts XLIFF localization files to Gettext PO files. XLIFF is the XML Localization Interchange File Format		Converts XLIFF localization files to Gettext PO files. XLIFF is the XML Localization Interchange File Format
-	developed by [[http://lisa.org/\|LISA]] (The Localization Industry Standards Authority) to allow translation	+	developed by [[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff\|OASIS]] (Organization for the Advancement of Structured Information Standards) to allow translation
	work to be standardised no matter what the source format and to allow the work to be freely moved from tool to		work to be standardised no matter what the source format and to allow the work to be freely moved from tool to
	tool.		tool.

1199556500		current
Line 4:		Line 4:
	\| & \| [[guide:KDE desktop]], [[guide:Mozilla]] (when using [[toolkit:moz2po]]) \|		\| & \| [[guide:KDE desktop]], [[guide:Mozilla]] (when using [[toolkit:moz2po]]) \|
	\| _ \| [[guide:GNOME desktop]] \|		\| _ \| [[guide:GNOME desktop]] \|
-	\| ~ \| [[:OpenOffice.org]] \|	+	\| ~ \| [[guide:OpenOffice.org]] \|

1259405926		current
Line 74:		Line 74:
	* [[wp>LaTeX]] - see [[http://plastex.sourceforge.net/plastex/index.html\|plasTeX]], a Python framework for processing LaTeX documents		* [[wp>LaTeX]] - see [[http://plastex.sourceforge.net/plastex/index.html\|plasTeX]], a Python framework for processing LaTeX documents
	* [[http://dag.wieers.com/home-made/unoconv/\|unoconv]] - Python bindings to OpenOffice.org UNO which could allow manipulation of all formats understood by OpenOffice.org.		* [[http://dag.wieers.com/home-made/unoconv/\|unoconv]] - Python bindings to OpenOffice.org UNO which could allow manipulation of all formats understood by OpenOffice.org.
-	* Trados TTX ([[http://www.tracom.de/04/EN/techdoccenter/download/TRADOS_TTX-DTD.zip\|Reverse Engineered DTD]], [[http://blogs.sun.com/timf/entry/beds_mattresses_and_open_standards\|other discussion]])	+	* Trados:
		+	* TTX ([[http://www.tracom.de/04/EN/techdoccenter/download/TRADOS_TTX-DTD.zip\|Reverse Engineered DTD]], [[http://blogs.sun.com/timf/entry/beds_mattresses_and_open_standards\|other discussion]])
		+	* Multiterm XML [[http://syntax.biz.pl/multiterm.html\|TSV to MiltiTerm conversion script]]
	* Tcl: .msg files. [[http://www.google.com/codesearch?hl=en&q=show:XvsRBDCljVk:M2kzUbm70Ts:D5EHICz0aaQ&sa=N&ct=rd&cs_p=http://www.scilab.org/download/4.0/scilab-4.0-src.tar.gz&cs_f=scilab-4.0/tcl/scipadsources/msg_files/AddingTranslations.txt\|Good documentation]]		* Tcl: .msg files. [[http://www.google.com/codesearch?hl=en&q=show:XvsRBDCljVk:M2kzUbm70Ts:D5EHICz0aaQ&sa=N&ct=rd&cs_p=http://www.scilab.org/download/4.0/scilab-4.0-src.tar.gz&cs_f=scilab-4.0/tcl/scipadsources/msg_files/AddingTranslations.txt\|Good documentation]]
	* Installers:		* Installers:

1200475378		current
Line 38:		Line 38:
	\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|		\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation, modes: none, full, profile \|
	\| -wWRAP, --wrap=WRAP \| set number of columns to wrap html at \|		\| -wWRAP, --wrap=WRAP \| set number of columns to wrap html at \|
		+	\| --notidy \| don't use tidy to clean up HTML, even if installed (new in version 1.2.1) \|
	\| --fuzzy \| use translations marked fuzzy \|		\| --fuzzy \| use translations marked fuzzy \|
	\| --nofuzzy \| don't use translations marked fuzzy (default) \|		\| --nofuzzy \| don't use translations marked fuzzy (default) \|

1150281865		current
Line 6:		Line 6:
	Other cases in which you can expect inconsistencies:		Other cases in which you can expect inconsistencies:

-	* Multiple translators are invovled	+	* Multiple translators are involved
	* Translations are very old		* Translations are very old
-	* You preped this set of translations with translations from multiple sources	+	* You prepared this set of translations with translations from multiple sources
	* You changed terminology at some stage in the translation		* You changed terminology at some stage in the translation
	* You did not do a formal glossary development stage		* You did not do a formal glossary development stage
Line 14:		Line 14:
	===== What we won't be able to achieve =====		===== What we won't be able to achieve =====

-	We cannot find gramatical errors and we won't be able to find all cases of words, etc	+	We cannot find grammatical errors and we won't be able to find all cases of words, etc

	===== Scenario =====		===== Scenario =====
Line 23:		Line 23:
	- Terminology is well defined but not well used by the old translators		- Terminology is well defined but not well used by the old translators

-	We'll look at the translations first from the English, or source text, point of view. Then we will look at it from the Afrikaans point of view. The first will pick up where whe have translated the same English word differently in Afrikaans ie an inconsistency. While the second will determine if we use the same English word for different English words, possibly this will confuse a user.	+	We'll look at the translations first from the English, or source text, point of view. Then we will look at it from the Afrikaans point of view. The first will pick up where we have translated the same English word differently in Afrikaans ie an inconsistency. While the second will determine if we use the same English word for different English words, possibly this will confuse a user.

	==== Step 1: Extracting conflicting target text translations ====		==== Step 1: Extracting conflicting target text translations ====
Line 43:		Line 43:
	etc...		etc...

-	These are normal PO files which you can edit in any PO editor or text editor. If we look at the first file ''change.po'' we can see that the source text //Change// was translated as //Verander// and //Wysig//. The translators job is noe to correct these PO files, ignoring instances where the diffeerence is in fact corret.	+	These are normal PO files which you can edit in any PO editor or text editor. If we look at the first file ''change.po'' we can see that the source text //Change// was translated as //Verander// and //Wysig//. The translators job is noe to correct these PO files, ignoring instances where the difference is in fact correct.

-	Once all fixes have been made we can merge our changes back into the origianl files.	+	Once all fixes have been made we can merge our changes back into the original files.

-	==== Step 2: Merging our corrections back into the oroginal files ====	+	==== Step 2: Merging our corrections back into the original files ====

-	Our files in //af-conflicts// are in a flat structure. We need to structure them into the heirachy of the existing pofiles.	+	Our files in //af-conflicts// are in a flat structure. We need to structure them into the hierarchy of the existing PO files.

	porestructure af-conflicts af-restructured		porestructure af-conflicts af-restructured
Line 69:		Line 69:
	poconflicts -v -I --accelerator="&" af af-conflicts-invert		poconflicts -v -I --accelerator="&" af af-conflicts-invert

-	We use the same command line as in Step 1 but add //-v// to allow us to invert the match. We are also now outputing to //af-conflicts-invert// to make things clear.	+	We use the same command line as in Step 1 but add //-v// to allow us to invert the match. We are also now outputting to //af-conflicts-invert// to make things clear.

	This time the PO files that are created have Afrikaans names		This time the PO files that are created have Afrikaans names

1225810053		current
Line 86:		Line 86:
	po2moz -lzu-ZA -t en-US.xpi zu zu-ZA.xpi		po2moz -lzu-ZA -t en-US.xpi zu zu-ZA.xpi

-	Create a Zulu language (//-lzu-ZA//) XPI called //zu-ZA.xpi// from translations found in //zu// using //en-US.xpi// as a template. We use a template to ensure that our DTD and .properties files appear exactly as those in en-US	+	Create a Zulu language (''-lzu-ZA'') XPI called ''zu-ZA.xpi'' from translations found in ''zu'' using ''en-US.xpi'' as a template. We use a template to ensure that our DTD and .properties files appear exactly as those in en-US

	po2moz -t l10n/en-US po/xh l10n/xh		po2moz -t l10n/en-US po/xh l10n/xh

-	Create Mozilla files using the templates files in //l10n/en-US// (see above for how to create them) with PO translations in //po/xh// and ouput then	+	Create Mozilla files using the templates files in ''l10n/en-US'' (see above for how to create them) with PO translations in ''po/xh'' and ouput them to ''l10n/xh''. The files now in ''l10n/xh'' are ready for submission to Mozilla and can be used to build a language pack or translated version of Mozilla.
-	to //l10n/xh//. The files now in //l10n/xh// are ready for submission to Mozilla and can be used to build a language pack or translated version of Mozilla.	+


Line 101:		Line 100:
	Localisation of XHTML is not yet perfect, you might want to work with the files directly.		Localisation of XHTML is not yet perfect, you might want to work with the files directly.

-	Bug [[bug>129]] tracks the outstanding features	+	Bug [[bug>129]] tracks the outstanding features which would allow complete localisation of Mozilla including; all help, start pages, rdf files, etc. It also tracks some bugs.
-	which would allow complete localisation of Mozilla including; all help, start pages, rdf files, etc.	+
-	It also tracks some bugs.	+

-	Accesskeys don't yet work in .properties files and in several cases where the Mozilla dtd files don't follow the normal conventions, for example in security/manager/chrome/pippki/pref-ssl.dtd.po. You might also want to check the files mentioned in this bug [[mozbug>329444]] where mistakes in the DTD-definitions cause problems in the matching of accelerators with the text.	+	Accesskeys don't yet work in .properties files and in several cases where the Mozilla .dtd files don't follow the normal conventions, for example in ''security/manager/chrome/pippki/pref-ssl.dtd.po''. You might also want to check the files mentioned in this bug [[mozbug>329444]] where mistakes in the DTD-definitions cause problems in the matching of accelerators with the text.

	You might want to give special attention to the following files since it contains customisations that are not really translations.		You might want to give special attention to the following files since it contains customisations that are not really translations.
Line 113:		Line 110:
	Also, all width, height and size specifications need to be edited with feedback from testing the translated interfaces.		Also, all width, height and size specifications need to be edited with feedback from testing the translated interfaces.

-	There are some constructed strings in the Mozilla code which we can't do much about. Take good care to read the localisation notes. For an example, see mail/chrome/messenger/downloadheaders.dtd.po. In that specific file, the localisation note from the DTD file is lost, so take good care of those.	+	There are some constructed strings in the Mozilla code which we can't do much about. Take good care to read the localisation notes. For an example, see ''mail/chrome/messenger/downloadheaders.dtd.po''. In that specific file, the localisation note from the DTD file is lost, so take good care of those.

-	The file extension of the original Mozilla file is required to tell the Toolkit how to do the conversion. Therefore, a file like foo.dtd must be named foo.dtd.po in order to po2moz to recognise it as a DTD file.	+	The file extension of the original Mozilla file is required to tell the Toolkit how to do the conversion. Therefore, a file like foo.dtd must be named foo.dtd.po in order to ''po2moz'' to recognise it as a DTD file.

1242050283		current
Line 1:		Line 1:
	====== pomerge ======		====== pomerge ======

-	Pomerge will merge corrected PO/XLIFF files (or snippets) into your existing PO/XLIFF files. Usually you would extract	+	Pomerge will merge corrected PO, XLIFF, or TMX files (or snippets) into your existing PO, XLIFF, TMX files. Usually you would extract
-	errors using [[pofilter]], make corrections to these PO (or XLIFF) snippets then merge them back using pomerge. You	+	errors using [[pofilter]], make corrections to these PO (or XLIFF, TMX) snippets then merge them back using pomerge. You could also use [[pogrep]] to extract a number of messages matching a certain string, make corrections then merge the correction back using pomerge.
-	could also use [[pogrep]] to extract a number of messages matching a certain string, make corrections then merge	+
-	the correction back using pomerge.	+

-	It is probably best to run pomerge against files stored in some kind of version control system so that	+	It is probably best to run pomerge against files stored in some kind of version control system so that you can monitor what changes were made.
-	you can monitor what changes were made.	+

-	Pomerge will also attempt to make as small a change as possible to the text, making it easier to	+	Pomerge will also attempt to make as small a change as possible to the text, making it easier to see the changes using your version control system.
-	see the changes using your version control system.	+


Line 20:		Line 16:
	Where:		Where:

-	\| <template> \| is a set of reference PO/XLIFF files, either the originals or a set of POT files \|	+	\| <template> \| is a set of reference PO, XLIFF, TMX files, either the originals or a set of POT files \|
	\| <input> \| contains the corrected files that are to override content in <output> \|		\| <input> \| contains the corrected files that are to override content in <output> \|
	\| <output> \| contains the files whose content will be overridden by <input>. This can be the same directory as <template> \|		\| <output> \| contains the files whose content will be overridden by <input>. This can be the same directory as <template> \|
Line 31:		Line 27:
	\| [[--progress=PROGRESS]] \| show progress as: dots, none, bar, names, verbose \|		\| [[--progress=PROGRESS]] \| show progress as: dots, none, bar, names, verbose \|
	\| [[--errorlevel=ERRORLEVEL]] \| show errorlevel as: none, message, exception, traceback \|		\| [[--errorlevel=ERRORLEVEL]] \| show errorlevel as: none, message, exception, traceback \|
-	\| -iINPUT, --input=INPUT \| read from INPUT in po, pot and xlf formats \|	+	\| -iINPUT, --input=INPUT \| read from INPUT in po, pot, xlf, tmx formats \|
	\| -xEXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|		\| -xEXCLUDE, --exclude=EXCLUDE \| exclude names matching EXCLUDE from input paths \|
-	\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in po, pot and xlf formats \|	+	\| -oOUTPUT, --output=OUTPUT \| write to OUTPUT in po, pot, xlf, tmx formats \|
-	\| -tTEMPLATE, --template=TEMPLATE \| read from TEMPLATE in po, pot and xlf formats \|	+	\| -tTEMPLATE, --template=TEMPLATE \| read from TEMPLATE in po, pot, xlf, tmx formats \|
	\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation (set mode) \|		\| [[psyco_mode\|--psyco=MODE]] \| use psyco to speed up the operation (set mode) \|
	\| --mergeblanks=MERGEBLANKS \| whether to overwrite existing translations with blank translations (yes/no). Default is yes. \|		\| --mergeblanks=MERGEBLANKS \| whether to overwrite existing translations with blank translations (yes/no). Default is yes. \|