Translate Toolkit & Pootle guide:tools

guide:tools:comparison

Fri, 03 Oct 2008 07:26:54 +0000

1222968736		current
Line 1:		Line 1:
	\| ^ [[virtaal:index\|Virtaal]] ^ [[http://www.poedit.net\|poEdit]] ^ [[http://kbabel.kde.org\|KBabel]] ^ [[http://gtranslator.sourceforge.net\|GTrans- lator]] ^ [[http://translate.sourceforge.net/wiki/locfactoryeditor\|Loc Factory Editor]] ^ Emacs PO mode ^ Tran- solution ^ [[http://www.omegat.org\|OmegaT]] ^ [[http://www.wordfast.net\|Wordfast]] ^		\| ^ [[virtaal:index\|Virtaal]] ^ [[http://www.poedit.net\|poEdit]] ^ [[http://kbabel.kde.org\|KBabel]] ^ [[http://gtranslator.sourceforge.net\|GTrans- lator]] ^ [[http://translate.sourceforge.net/wiki/locfactoryeditor\|Loc Factory Editor]] ^ Emacs PO mode ^ Tran- solution ^ [[http://www.omegat.org\|OmegaT]] ^ [[http://www.wordfast.net\|Wordfast]] ^
-	^ FOSS \| Y \| Y \| Y \| Y \| N \| Y \| Y \| Y \| N \|	+	^ FOSS \| Y \| Y \| Y \| Y \| N \| Y \| Y \| Y \| N \|
	^ //Platform// ^^^^^^^^^^		^ //Platform// ^^^^^^^^^^
-	^ Windows \| Y \| Y \| Y \| N \| N \| Y \| Y \| Y \| Y \|	+	^ Windows \| Y \| Y \| Y \| N \| N \| Y \| Y \| Y \| Y \|
-	^ Linux \| Y \| Y \| Y \| Y \| N \| Y \| Y \| Y \| N \|	+	^ Linux \| Y \| Y \| Y \| Y \| N \| Y \| Y \| Y \| N \|
-	^ MacOS X \| :?: \| N \| N \| N \| Y \| Y \| :?: \| Y \| Y \|	+	^ MacOS X \| :?: \| N \| N \| N \| Y \| Y \| :?: \| Y \| Y \|
	^ //Supported formats// ^^^^^^^^^^		^ //Supported formats// ^^^^^^^^^^
-	^ PO \| Y \| Y \| Y \| Y \| Y \| Y \| N \| :?: \| :?: \|	+	^ PO \| Y \| Y \| Y \| Y \| Y \| Y \| N \| :?: \| :?: \|
-	^ XLIFF \| Y \| N \| N \| N \| Y \| N \| Y \| N \| :?: \|	+	^ XLIFF \| Y \| N \| N \| N \| Y \| N \| Y \| N \| :?: \|
		+	^ TBX \| Y \| N \| N \| N \| :?: \| N \| N \| :?: \| :?: \|
		+	^ Qt Linguist (.ts) \| Y \| N \| N \| N \| N \| N \| N \| N \| :?: \|
		+	^ Qt Phrasebook (.qph) \| Y \| N \| N \| N \| N \| N \| N \| N \| :?: \|
	^ //Translation memory// ^^^^^^^^^^		^ //Translation memory// ^^^^^^^^^^
-	^ TMX \| :?: \| N \| Y \| :?: \| Y \| N \| :?: \| Y \| Y \|	+	^ TMX \| Y \| N \| Y \| :?: \| Y \| N \| :?: \| Y \| Y \|
		+	^ WordFast TM (.txt) \| Y \| N \| N \| N \| N \| N \| N \| N \| Y \|

guide:tools:glossary

Mon, 29 Oct 2007 14:36:17 +0000

1121974219		current
Line 1:		Line 1:
	====== Glossary Tools ======		====== Glossary Tools ======

-	For a quality translation it is important to develop a good glossary of terms. In this section we list	+	For a quality translation it is important to develop a good glossary of terms. In this section we list the various tools that can help you create and manage such a glossary.
-	the various tools that can help you create and manage such a glossary.	+
		+	===== Glossary management =====
		+
		+	To create a glossary of terms (words and phrases), you can either create it as you go along during a pilot project, or you can extract terms from the source text and compile them into a glossary.
		+
		+	The advantage of creating it during a pilot project is that the term list is created in context, but the disadvantage is that it is a slower method and it yields less terms (although most terms are useful). The advantages of automatic term extraction are that it is fast and yields potentially more relevant terms. The disadvantage is that terms are not viewed in context, and you have to initially search through many unimportant or useless terms.
		+
		+	The disadvantages of either method can be overcome, though.
		+
		+	==== Bulk term extractors ====
		+
		+	=== Bilingual term extractors ===
		+
		+	Since some texts are available in bitext format (which can be a TM or a PO file or similar), it would be possible through smart guessing to figure out which source words fit which target words. These tools are generally called "word aligners" in the computational linguistics industry, and sadly most "free" tools are free for academic purposes only. Word aligners have great potential because bitexts are usually translated by humans, and so the terms are likely to be accurate.
		+
		+	A good compromise may be to do monolingual term extraction on a TM -- I know of no such tools, however.
		+
		+	=== Monolingual term extractors ===
		+
		+	Monolingual term extractors usually look for words or phrases that occur more than X number of times in the text, or for words that occur in the text but do not occur in a dictionary or established term list. Such an extraction usually contains a large percentage of useless terms unless steps are taken to remove irrelevant repetitions from the result.
		+
		+	== ExtPhr32 by Tim Craven ==
		+
		+	Tim Craven's ExtPhr32 for MS Windows is not GPL but it is freeware for all purposes. It is very fast. Unfortunately it converts all terms to uppercase. You can also use a stoplist. You can choose how many occurances of a term must be the minimum, and you can choose the minimum number of words in a term. The output can be exported to two column plaintext (the second column contains a count).
		+
		+	== PlusTools from Wordfast ==
		+
		+	PlusTools is a macro that runs within MS Word on MS Windows. It is not GPL but it is freeware for all purposes. It is slow but potentially useful for smaller texts because it can exclude words that occur in MS Word's spellchecker and/or thesaurus, or words that have less than X synonymns in the thesaurus. You can also exclude certain words (similar to a stoplist, but you can add any words to it), words beginning with a certain set of characters, and words that are smaller than X number of characters.
		+
		+	== Other tools ==
		+
		+	* http://uplug.sourceforge.net/
		+
		+	GPL collection of corpus tools.
		+
		+	* SDL MultiTerm 7 Extract Freelance
		+
		+	Extracts terms from Trados compliant bitexts. Pricetag: EUR 525.00 per single user licence.
		+
		+	==== Concordancers ====
		+
		+	A concordancer is a tool that displays a word in context. An excellent, easy to use concordancer, is Corpsis (previously Tenka Text). Or, if you're willing to pay some money, try Mike Scott's Wordsmith tools. Corpsis can display multiwords phrases using wildcards.
		+
		+	http://corpsis.sourceforge.net/
		+
		+	==== Glossary editors ====
		+
		+	Whichever way you look at it, a glossary is a database, and most comprehensive glossaries can be edited in a database editor tool. For simple, three-column glossaries, a spreadsheet program may be all that's necessary, though.
		+
		+	(todo)
		+
		+	==== Glossary viewers ====
		+
		+	There are quite a few glossary viewers, but they often require that you convert your glossary to their weird format. Examples are StarDict, Jalingo, jDictionary and Pododict. If you're willing to pay for a non-free product, AnyLexic is an excellent glossary tool that supports simple formats too.
		+
		+	(todo)

	===== Web based creation and management tools =====		===== Web based creation and management tools =====

guide:tools:list

Sat, 02 May 2009 16:00:30 +0000

1241271567		current
Line 13:		Line 13:
	* [[guide:LocFactoryEditor]] (XLIFF and PO editor for Mac OSX)		* [[guide:LocFactoryEditor]] (XLIFF and PO editor for Mac OSX)

-	===== Xliff editors =====	+	===== XLIFF editors =====

	* [[http://userbase.kde.org/Lokalize\|Lokalize]]		* [[http://userbase.kde.org/Lokalize\|Lokalize]]
Line 19:		Line 19:
	* Heartsome		* Heartsome
	* [[guide:locfactoryeditor\|LocFactoryEditor]] (Mac OSX)		* [[guide:locfactoryeditor\|LocFactoryEditor]] (Mac OSX)
		+	* [[virtaal:index\|Virtaal]]

	===== XLIFF converters =====		===== XLIFF converters =====

guide:tools:online

Fri, 23 Dec 2005 10:27:17 +0000

1197440582		current
Line 11:		Line 11:
	===== Web-based Tools =====		===== Web-based Tools =====

-	* [[:pootle:index\|Pootle]] - A PO file based translation and translation project management system. Actively being developed and used by the Translate.org.za project as part of the [[:toolkit:index\|Translate Toolkit]]. There is also an active [[http://pootle.wordforge.org\|translation portal]] for those who cannot host there own copy of Pootle. Pootle is released under the GPL.	+	* [[:pootle:index\|Pootle]] - A PO file based translation and translation project management system. Actively being developed and used by the Translate.org.za project as part of the [[:toolkit:index\|Translate Toolkit]]. There is also an active [[http://pootle.locamotion.org\|translation portal]] for those who cannot host there own copy of Pootle. Pootle is released under the GPL.
	* [[http://i18n.kde.org/tools/kartouche/\|Kartouche]] - Developed for the Welsh localisation team. See also Omnivore their online compendium tool. See the Welsh team's [[http://www.kyfieithu.co.uk/\|live site]].		* [[http://i18n.kde.org/tools/kartouche/\|Kartouche]] - Developed for the Welsh localisation team. See also Omnivore their online compendium tool. See the Welsh team's [[http://www.kyfieithu.co.uk/\|live site]].
	* [[http://info.linspire.com/irma/\|IRMA]] - Developed by Linspire aiming to make things as simple as possible for translatiors. Michael Robertson of Linspire talks about his [[http://www.michaelrobertson.com/archive.php?minute_id=147\|first date with IRMA]]. This is not free software.		* [[http://info.linspire.com/irma/\|IRMA]] - Developed by Linspire aiming to make things as simple as possible for translatiors. Michael Robertson of Linspire talks about his [[http://www.michaelrobertson.com/archive.php?minute_id=147\|first date with IRMA]]. This is not free software.

guide:tools:spreadsheet

Thu, 12 Feb 2009 16:42:41 +0000

guide:tools:trans_editors

Fri, 03 Oct 2008 09:17:04 +0000

1222969366		current
Line 23:		Line 23:
	You may be able to use a text editor to edit PO files, since they are text:		You may be able to use a text editor to edit PO files, since they are text:

-	* vi --- You can use the vi editor. Make sure you install the updated PO syntax highlighter available here: [[http://www.vim.org/scripts/script.php?script_id=913]]	+	* vi --- You can use the vi editor. It includes syntax highlighting, but you might want to check if there is a [[http://www.vim.org/scripts/script.php?script_id=913\|newer version]]
	* emacs --- The Emacs editor has a PO mode for editing PO files.		* emacs --- The Emacs editor has a PO mode for editing PO files.

guide:tools:xliff_support_by_ms_windows_programs

Thu, 04 Oct 2007 08:02:26 +0000

1191436038		current
Line 22:		Line 22:
	* The file must be sourcecopied (you can do that using msgen)		* The file must be sourcecopied (you can do that using msgen)
	* To translate, simply open the XLIFF file in TagEditor.		* To translate, simply open the XLIFF file in TagEditor.
		+


Line 30:		Line 31:
	* The file must be sourcecopied (you can do that using msgen)		* The file must be sourcecopied (you can do that using msgen)
	* The file extension must be XLF		* The file extension must be XLF
		+	* OmegaT saves XML files with LF even if the source file is CRLF.

	The version I tested, didn't ignore the notes tags, but I'm told that that bug has been dealt with in the next version of OmegaT.		The version I tested, didn't ignore the notes tags, but I'm told that that bug has been dealt with in the next version of OmegaT.

-	* All of the same applies to the semifork, OmegaT2-20070928, except that it saves the file with LF instead of the system default CRLF.	+	* All of the same applies to the semifork, OmegaT2-20070928.

	==== SDLX (build 7014) ====		==== SDLX (build 7014) ====

1222968736		current
Line 1:		Line 1:
	\| ^ [[virtaal:index\|Virtaal]] ^ [[http://www.poedit.net\|poEdit]] ^ [[http://kbabel.kde.org\|KBabel]] ^ [[http://gtranslator.sourceforge.net\|GTrans- lator]] ^ [[http://translate.sourceforge.net/wiki/locfactoryeditor\|Loc Factory Editor]] ^ Emacs PO mode ^ Tran- solution ^ [[http://www.omegat.org\|OmegaT]] ^ [[http://www.wordfast.net\|Wordfast]] ^		\| ^ [[virtaal:index\|Virtaal]] ^ [[http://www.poedit.net\|poEdit]] ^ [[http://kbabel.kde.org\|KBabel]] ^ [[http://gtranslator.sourceforge.net\|GTrans- lator]] ^ [[http://translate.sourceforge.net/wiki/locfactoryeditor\|Loc Factory Editor]] ^ Emacs PO mode ^ Tran- solution ^ [[http://www.omegat.org\|OmegaT]] ^ [[http://www.wordfast.net\|Wordfast]] ^
-	^ FOSS \| Y \| Y \| Y \| Y \| N \| Y \| Y \| Y \| N \|	+	^ FOSS \| Y \| Y \| Y \| Y \| N \| Y \| Y \| Y \| N \|
	^ //Platform// ^^^^^^^^^^		^ //Platform// ^^^^^^^^^^
-	^ Windows \| Y \| Y \| Y \| N \| N \| Y \| Y \| Y \| Y \|	+	^ Windows \| Y \| Y \| Y \| N \| N \| Y \| Y \| Y \| Y \|
-	^ Linux \| Y \| Y \| Y \| Y \| N \| Y \| Y \| Y \| N \|	+	^ Linux \| Y \| Y \| Y \| Y \| N \| Y \| Y \| Y \| N \|
-	^ MacOS X \| :?: \| N \| N \| N \| Y \| Y \| :?: \| Y \| Y \|	+	^ MacOS X \| :?: \| N \| N \| N \| Y \| Y \| :?: \| Y \| Y \|
	^ //Supported formats// ^^^^^^^^^^		^ //Supported formats// ^^^^^^^^^^
-	^ PO \| Y \| Y \| Y \| Y \| Y \| Y \| N \| :?: \| :?: \|	+	^ PO \| Y \| Y \| Y \| Y \| Y \| Y \| N \| :?: \| :?: \|
-	^ XLIFF \| Y \| N \| N \| N \| Y \| N \| Y \| N \| :?: \|	+	^ XLIFF \| Y \| N \| N \| N \| Y \| N \| Y \| N \| :?: \|
		+	^ TBX \| Y \| N \| N \| N \| :?: \| N \| N \| :?: \| :?: \|
		+	^ Qt Linguist (.ts) \| Y \| N \| N \| N \| N \| N \| N \| N \| :?: \|
		+	^ Qt Phrasebook (.qph) \| Y \| N \| N \| N \| N \| N \| N \| N \| :?: \|
	^ //Translation memory// ^^^^^^^^^^		^ //Translation memory// ^^^^^^^^^^
-	^ TMX \| :?: \| N \| Y \| :?: \| Y \| N \| :?: \| Y \| Y \|	+	^ TMX \| Y \| N \| Y \| :?: \| Y \| N \| :?: \| Y \| Y \|
		+	^ WordFast TM (.txt) \| Y \| N \| N \| N \| N \| N \| N \| N \| Y \|

1186064734		current
Line 1:		Line 1:
	====== Using CSV and your Spreadsheet to edit translations ======		====== Using CSV and your Spreadsheet to edit translations ======

-	A CSV (Comma Seperated Value) file is one in which each field or cell is seperated by a comma (or	+	A CSV (Comma Separated Value) file is one in which each field or cell is separated by a comma (or
-	another character) and each record or line is seperated by a newline.	+	another character) and each record or line is separated by a newline.

	When using CSV files generated by [[toolkit:po2csv]] you will find the data as follows:		When using CSV files generated by [[toolkit:po2csv]] you will find the data as follows:
Line 37:		Line 37:
	===== Getting the most from your spreadsheet =====		===== Getting the most from your spreadsheet =====

-	Initialy the first column will stretch across the page as it contains a large	+	Initially the first column will stretch across the page as it contains a large
	amount of data, but you cannot see or work with this data. Therefore do the		amount of data, but you cannot see or work with this data. Therefore do the
	following:		following:

	- Adjust the column widths - 5" works well as you can then see both the original and translation clearly.		- Adjust the column widths - 5" works well as you can then see both the original and translation clearly.
-	- Adjust the cell formating for the first column to allow the insertion of automatic line breaks (this will cause the data to wrap within the column and make it all readable) this also allows for automatic hyphenation which will then hyphenate long words. The result of this step is that you can now read all data in column one as the rows will become larger to accomodate this information.	+	- Adjust the cell formating for the first column to allow the insertion of automatic line breaks (this will cause the data to wrap within the column and make it all readable) this also allows for automatic hyphenation which will then hyphenate long words. The result of this step is that you can now read all data in column one as the rows will become larger to accommodate this information.
	- You can repeat this process for other columns but then messages will wrap differently to how they appear in the translation. Do this only if you really don't have space or otherwise look at text shrinking options.		- You can repeat this process for other columns but then messages will wrap differently to how they appear in the translation. Do this only if you really don't have space or otherwise look at text shrinking options.

-	Each Spreadsheet application will achive the above in a slightly different	+	Each Spreadsheet application will achieve the above in a slightly different
	way. Here are specific instructions.		way. Here are specific instructions.