Tikal - Extraction Commands - Revision history

Kuro2 at 21:51, 12 April 2021

2021-04-12T21:51:39Z

← Older revision		Revision as of 17:51, 12 April 2021
Line 190:		Line 190:
	\| <code>-overtrg</code> \|\| Copy the leveraged translation into the target, even if is already an existing target content.		\| <code>-overtrg</code> \|\| Copy the leveraged translation into the target, even if is already an existing target content.
	\|- valign="top"		\|- valign="top"
	\| <code>-bpt</code> \|\| Use the <code><bpt>/<ept>/<ph></code> notation instead of the <code><g>/<x></code> notation in <code>&~~lat~~-trans></code> elements.		\| <code>-bpt</code> \|\| Use the <code><bpt>/<ept>/<ph></code> notation instead of the <code><g>/<x></code> notation in <code><alt-trans></code> elements.
	\|- valign="top"		\|- valign="top"
	\|nowrap="nowrap"\|<code>-from mosesFile</code> \|\| The path of the Moses InlineText file from which to leverage the text. If this option is not set, the file to leverage from is the same as the input file with the language code of the target appended as an extension. <b>Warning:</b> You must not use this option if you are processing several files at the same time.		\|nowrap="nowrap"\|<code>-from mosesFile</code> \|\| The path of the Moses InlineText file from which to leverage the text. If this option is not set, the file to leverage from is the same as the input file with the language code of the target appended as an extension. <b>Warning:</b> You must not use this option if you are processing several files at the same time.

Kuro2: Removing mentions of -x1, -x2, and skeleton file as they are obsolete.

2021-04-09T18:00:19Z

Removing mentions of -x1, -x2, and skeleton file as they are obsolete.

← Older revision		Revision as of 14:00, 9 April 2021
Line 15:		Line 15:
	-x [options] inputFile [inputFile2...]		-x [options] inputFile [inputFile2...]

	~~Note: <code>-x2</code> is the same as <code>-x</code> while <code>-x1</code> extract without generating a skeleton file (and is meant to be merged using <code>-m2</code>).~~
	Where the options are:		Where the options are:

Line 74:		Line 74:
	==Merge Files==		==Merge Files==

	This command merges back into their original format one or more XLIFF documents that were created using the [[#Extract Files\|Extract Files command]]. If you have extracted with <code>-x</code> or <code>-x2</code> you must have the skeleton files in the same directories as their corresponding XLIFF documents. If you have extracted with <code>-x1</code> you must have the original files in the same directories as their corresponding XLIFF documents.		This command merges back into their original format one or more XLIFF documents that were created using the [[#Extract Files\|Extract Files command]].

	{{NoteBox\|If you are merging with the original files (<code>-x1</code>), the original files must be exactly the same as when they were extracted to XLIFF, and the same encoding and filter configuration must be used. Any difference may result in a different extraction and could cause merging errors.}}

	The XLIFF document names must be the name of the original files with an additional <code>.xlf</code> extension. The new documents are created in the directories where the XLIFF documents are, with a <code>.out</code> extension pre-pended to the original extension. For example, if your original file is <code>myFile.html</code>, the XLIFF document should be <code>myFile.html.xlf</code>, and the merged file will be <code>myFile.out.html</code>.		The XLIFF document names must be the name of the original files with an additional <code>.xlf</code> extension. The new documents are created in the directories where the XLIFF documents are, with a <code>.out</code> extension pre-pended to the original extension. For example, if your original file is <code>myFile.html</code>, the XLIFF document should be <code>myFile.html.xlf</code>, and the merged file will be <code>myFile.out.html</code>.
Line 84:		Line 83:
	-m [options] xliffFile [xliffFile2...]		-m [options] xliffFile [xliffFile2...]

	~~Note: <code>-m2</code> is the same as <code>-m</code> and use a skeleton file for the merge, while <code>-m1</code> uses the original document for the merge.~~

	Where the options are:		Where the options are:

Okapifra: /* Extract Files */

2017-08-13T10:43:12Z

Extract Files

← Older revision		Revision as of 06:43, 13 August 2017
Line 34:		Line 34:
	\| <code>-od outputDirectory</code> \|\| The directory where to place the output.		\| <code>-od outputDirectory</code> \|\| The directory where to place the output.
	\|- valign="top"		\|- valign="top"
	\|nowrap="nowrap"\| <code>-pen tmDirectory\|<br/>-tt hostname[:port]\|<br/>-gs configFile\|<br/>-mm [key]\|<br/>-gg configFile\|<br/>-apertium [configFile]\|<br/>-ms configFile\|<br/>-tda configFile</code>		\|nowrap="nowrap"\| <code>-pen tmDirectory\|<br/>-tt [hostname[:port]]\|<br/>-gs configFile\|<br/>-mm [key]\|<br/>-gg configFile\|<br/>-apertium [configFile]\|<br/>-ms configFile\|<br/>-tda configFile\|<br/>-lingo24 configFile\|<br/>-mmt url context\|<br/>-bi bilingualFile</code>
	\| A translation resource connector to use to translate the document: <code>-pen</code> for the [[Pensieve TM Connector]], <code>-tt</code> for the [[Translate Toolkit TM Connector]], <code>-gs</code> for the [[GlobalSight TM Connector]], <code>-mm</code> for [[MyMemory TM Connector]], <code>-gg</code> for the [[Google MT v2 Connector]], <code>-apertium</code> for the [[Apertium MT Connector]], <code>-ms</code> for the [[Microsoft Translator Connector]], ~~and~~ <code>-tda</code> for the [[TDA Translation Repository Connector]].		\| A translation resource connector to use to translate the document: <code>-pen</code> for the [[Pensieve TM Connector]], <code>-tt</code> for the [[Translate Toolkit TM Connector]], <code>-gs</code> for the [[GlobalSight TM Connector]], <code>-mm</code> for [[MyMemory TM Connector]], <code>-gg</code> for the [[Google MT v2 Connector]], <code>-apertium</code> for the [[Apertium MT Connector]], <code>-ms</code> for the [[Microsoft Translator Connector]], <code>-tda</code> for the [[TDA Translation Repository Connector]], <code>-lingo24</code> for the [[Lingo24 Premium MT Connector]], <code>-mmt</code> for the [[ModernMT API Connector]] and <code>-bi</code> for the [[Bilingual File Connector]].

	The leveraging occurs after segmentation, if you have ~~specify~~ segmentation rules.		The leveraging occurs after segmentation, if you have specified segmentation rules.

	Note that some Internet-based resource may be slow and result in lengthy processing time. Be also aware that some translation resources may not always provide a good handling of inline codes.		Note that some Internet-based resource may be slow and result in lengthy processing time. Be also aware that some translation resources may not always provide a good handling of inline codes.

Okapifra: /* Leverage Files from Moses */

2017-03-12T15:32:08Z

Leverage Files from Moses

← Older revision		Revision as of 11:32, 12 March 2017
Line 194:		Line 194:
	\| <code>-bpt</code> \|\| Use the <code><bpt>/<ept>/<ph></code> notation instead of the <code><g>/<x></code> notation in <code>&lat-trans></code> elements.		\| <code>-bpt</code> \|\| Use the <code><bpt>/<ept>/<ph></code> notation instead of the <code><g>/<x></code> notation in <code>&lat-trans></code> elements.
	\|- valign="top"		\|- valign="top"
	\|nowrap="nowrap"\|<code>-from mosesFile</code> \|\| The path of the Moses InlineText file from which to leverage the text. If this option is not set, the file to leverage from is the same as the input file with the language code of the target appended as an extension.		\|nowrap="nowrap"\|<code>-from mosesFile</code> \|\| The path of the Moses InlineText file from which to leverage the text. If this option is not set, the file to leverage from is the same as the input file with the language code of the target appended as an extension. <b>Warning:</b> You must not use this option if you are processing several files at the same time.
	\|- valign="top"		\|- valign="top"
	\|nowrap="nowrap"\|<code>-to outputFile</code> \|\| The path of the output file to generate. If this option is not set, the output is the same as the input with <code>.out</code> prepended to the file extension.		\|nowrap="nowrap"\|<code>-to outputFile</code> \|\| The path of the output file to generate. If this option is not set, the output is the same as the input with <code>.out</code> prepended to the file extension. <b>Warning:</b> You must not use this option if you are processing several files at the same time.
	\|- valign="top"		\|- valign="top"
	\|nowrap="nowrap"\|<code>-seg [srxFile]</code> \|\| The segmentation rules to utilize. To specify the default rules that come with the installation, use <code>-seg</code> without filename. The default rules are in <code>config/defaultSegmentation.srx</code> in your Okapi main directory.		\|nowrap="nowrap"\|<code>-seg [srxFile]</code> \|\| The segmentation rules to utilize. To specify the default rules that come with the installation, use <code>-seg</code> without filename. The default rules are in <code>config/defaultSegmentation.srx</code> in your Okapi main directory.

Okapifra: /* Extract Files to Moses */

2017-03-12T15:31:21Z

Extract Files to Moses

← Older revision		Revision as of 11:31, 12 March 2017
Line 141:		Line 141:
	\| <code>-2</code> \|\| Extract two files: one for the source, one for the target. The target file has as many lines as the source file as lines. If there is an existing target segment, the target segment is extracted, otherwise an empty line is used for the missing target.		\| <code>-2</code> \|\| Extract two files: one for the source, one for the target. The target file has as many lines as the source file as lines. If there is an existing target segment, the target segment is extracted, otherwise an empty line is used for the missing target.
	\|- valign="top"		\|- valign="top"
	\|nowrap="nowrap"\|<code>-to srcOutputFile</code> \|\| The path of the Moses source file to generate. The last part of the path is the template filename to use, the code of the source language is added automatically. <b>Warning:</b> You must not use this option if you are processing several files at the same time~~. If you do so, the output will contain only the result of the last input file~~.		\|nowrap="nowrap"\|<code>-to srcOutputFile</code> \|\| The path of the Moses source file to generate. The last part of the path is the template filename to use, the code of the source language is added automatically. <b>Warning:</b> You must not use this option if you are processing several files at the same time.
	\|- valign="top"		\|- valign="top"
	\|nowrap="nowrap"\| <code>-seg [srxFile]</code> \|\| The segmentation rules to utilize. To specify the default rules that come with the installation, use <code>-seg</code> without filename. The default rules are in <code>config/defaultSegmentation.srx</code> in your Okapi main directory.		\|nowrap="nowrap"\| <code>-seg [srxFile]</code> \|\| The segmentation rules to utilize. To specify the default rules that come with the installation, use <code>-seg</code> without filename. The default rules are in <code>config/defaultSegmentation.srx</code> in your Okapi main directory.

Okapifra: /* Extract Files to Moses */

2017-03-12T14:15:00Z

Extract Files to Moses

← Older revision		Revision as of 10:15, 12 March 2017
Line 141:		Line 141:
	\| <code>-2</code> \|\| Extract two files: one for the source, one for the target. The target file has as many lines as the source file as lines. If there is an existing target segment, the target segment is extracted, otherwise an empty line is used for the missing target.		\| <code>-2</code> \|\| Extract two files: one for the source, one for the target. The target file has as many lines as the source file as lines. If there is an existing target segment, the target segment is extracted, otherwise an empty line is used for the missing target.
	\|- valign="top"		\|- valign="top"
	\|nowrap="nowrap"\|<code>-to srcOutputFile</code> \|\| The path of the Moses source file to generate. The last part of the path is the template filename to use, the code of the source language is added automatically.		\|nowrap="nowrap"\|<code>-to srcOutputFile</code> \|\| The path of the Moses source file to generate. The last part of the path is the template filename to use, the code of the source language is added automatically. <b>Warning:</b> You must not use this option if you are processing several files at the same time. If you do so, the output will contain only the result of the last input file.
	\|- valign="top"		\|- valign="top"
	\|nowrap="nowrap"\| <code>-seg [srxFile]</code> \|\| The segmentation rules to utilize. To specify the default rules that come with the installation, use <code>-seg</code> without filename. The default rules are in <code>config/defaultSegmentation.srx</code> in your Okapi main directory.		\|nowrap="nowrap"\| <code>-seg [srxFile]</code> \|\| The segmentation rules to utilize. To specify the default rules that come with the installation, use <code>-seg</code> without filename. The default rules are in <code>config/defaultSegmentation.srx</code> in your Okapi main directory.

Ysavourel: 1 revision imported

2016-06-04T23:12:50Z

1 revision imported

← Older revision	Revision as of 19:12, 4 June 2016
(No difference)

Ysavourel: /* Merge Files */

2014-05-09T20:36:48Z

Merge Files

New page

{{Tikal Common Menu}}
__TOC__
==Extract Files==

This command extracts the translatable content of one or more given files into an [[XLIFF|XLIFF document]]. You can then use any XLIFF-aware translation tool to translate the document (See "[[How to Translate XLIFF Documents]]" for more information). When the translation is done, you can use the [[#Merge Files|Merge Files command]] to create a new translated file in its original format.

The XLIFF documents created are placed in the same directories as the original files, and have the same name with an additional .xlf extension.

By default, some extensions are mapped to a specific filter configuration (for example: <code>.docx</code> to <code>okf_openxml</code>, <code>.odt</code> to <code>okf_openoffice</code>, <code>.po</code> to <code>okf_po</code>, etc.). But you can define your own configuration and specify it as well using the <code>-fc</code> option. To get a list of all available filter configurations use the [[Tikal - Miscellaneous Commands#List Filter Configurations|List Filter Configurations command]]. For more details the filters available and their configurations, see each [[Filters|filter's documentation]].

You can use the <code>-seg</code> option to specify that the extracted text should be segmented. Use <code>-seg</code> without file name to use the default segmentation rules, use "<code>-seg myRules.srx</code>" to specify your own rules. The rules file must be in SRX format. The segments are marked up according the XLIFF 1.2 specifications.

The syntax of this command is:

-x [options] inputFile [inputFile2...]

Note: <code>-x2</code> is the same as <code>-x</code> while <code>-x1</code> extract without generating a skeleton file (and is meant to be merged using <code>-m2</code>).
Where the options are:

{| border="1" cellpadding="5" cellspacing="0"
|- valign="top"
| <code>-fc configId</code> || The identifier of the filter configuration to use for the extraction.
|- valign="top"
| <code>-ie encoding</code> || The encoding name of the input files. this is used only if the filter cannot detect the encoding from the input file itself.
|- valign="top"
| <code>-sl srcLang</code> || The code of the source language of the input files. [[Tikal - Usage#Source and Target Languages|See more details...]]
|- valign="top"
| <code>-tl trgLang</code> || The code of the target language for the output (also used in the input if the input documents are multilingual). [[Tikal - Usage#Source and Target Languages|See more details...]]
|- valign="top"
| <code>-seg [srxFile]</code> || The segmentation rules to utilize. To specify the default rules that come with the installation, use <code>-seg</code> without filename. The default rules are in <code>config/defaultSegmentation.srx</code> in your Okapi main directory.
|- valign="top"
| <code>-rd rootDirectory</code> || The root directory (by default the user's home directory).
|- valign="top"
| <code>-od outputDirectory</code> || The directory where to place the output.
|- valign="top"
|nowrap="nowrap"| <code>-pen tmDirectory| -tt hostname[:port]| -gs configFile| -mm [key]| -gg configFile| -apertium [configFile]| -ms configFile| -tda configFile</code>
| A translation resource connector to use to translate the document: <code>-pen</code> for the [[Pensieve TM Connector]], <code>-tt</code> for the [[Translate Toolkit TM Connector]], <code>-gs</code> for the [[GlobalSight TM Connector]], <code>-mm</code> for [[MyMemory TM Connector]], <code>-gg</code> for the [[Google MT v2 Connector]], <code>-apertium</code> for the [[Apertium MT Connector]], <code>-ms</code> for the [[Microsoft Translator Connector]], and <code>-tda</code> for the [[TDA Translation Repository Connector]].

The leveraging occurs after segmentation, if you have specify segmentation rules.

Note that some Internet-based resource may be slow and result in lengthy processing time. Be also aware that some translation resources may not always provide a good handling of inline codes.
|- valign="top"
| <code>-opt threshold</code> || TM query option: The threshold is a number between 0 and 100. If this option is not set the default is 95. Note that this option may be limited for some search engines because of the way they are configured.
|- valign="top"
| <code>-maketmx [tmxFile]</code> || Generates a TMX document with all the entries leveraged. You can specify the name of the document, if you do not it will be named <code>pretrans.tmx</code>.
|- valign="top"
| <code>-nocopy</code> || Ensures that the generated XLIFF files do not have a copy of the source text in the target entries if the original target does not exists.
|- valign="top"
| <code>-noalttrans</code> || Ensures that the generated XLIFF files do not have added <code><alt-trans></code> elements.
|- valign="top"
| <code>-codeattrs</code> || Enables the output of extended attributes <code>ctype</code> and <code>equiv-text</code> for inline codes.
|- valign="top"
| <code>-safe</code> || Shows a warning before overwriting output files.
|}

For example:

tikal -x *.docx *.html

Extracts all <code>.docx</code> and .html files in the current directory into corresponding <code>.docx.xlf</code> and <code>.html.xlf</code> XLIFF documents. The source language here is the default, which is the current language of the system. The target language by default is <code>fr</code>. No segmentation is done.

tikal -x -sl EN tl DE -fc okf_regex-srt -ie iso-8859-1 findingNemo.srt

Extracts the sub-title file <code>findingNemo.srt</code> into a <code>findingNemo.srt.xlf</code> XLIFF document. The encoding <code>iso-8859-</code>1 is used to process the input file. The filter used is the [[Regex Filter]] with the predefined configuration for SRT documents. The source language is English (<code>EN</code>) and the target language is German (<code>DE</code>). No segmentation is done.

tikal -x *.docx -seg -tl BR

Extracts all <code>.docx</code> files in the current directory into corresponding <code>.docx.xlf</code> XLIFF documents. The source language here is the default, which is the current language of the system. The target language is Breton (<code>BR</code>). The extracted text units will be segmented according the rules defined in the default SRX segmentation rules file (located in the <code>config</code> sub-directory in your Okapi main directory).

tikal -x *.odt -od toTrans -tl ZU

Extracts all <code>.odt</code> files in the current directory into corresponding <code>.odt.xlf</code> XLIFF documents into the <code>toTrans</code> sub-directory of the current directory. The source language here is the default, which is the current language of the system. The target language is Breton (<code>ZU</code>). The extracted text units will be segmented according the rules defined in the default SRX segmentation rules file (located in the <code>config</code> sub-directory in your Okapi main directory).

==Merge Files==

This command merges back into their original format one or more XLIFF documents that were created using the [[#Extract Files|Extract Files command]]. If you have extracted with <code>-x</code> or <code>-x2</code> you must have the skeleton files in the same directories as their corresponding XLIFF documents. If you have extracted with <code>-x1</code> you must have the original files in the same directories as their corresponding XLIFF documents.

{{NoteBox|If you are merging with the original files (<code>-x1</code>), the original files must be exactly the same as when they were extracted to XLIFF, and the same encoding and filter configuration must be used. Any difference may result in a different extraction and could cause merging errors.}}

The XLIFF document names must be the name of the original files with an additional <code>.xlf</code> extension. The new documents are created in the directories where the XLIFF documents are, with a <code>.out</code> extension pre-pended to the original extension. For example, if your original file is <code>myFile.html</code>, the XLIFF document should be <code>myFile.html.xlf</code>, and the merged file will be <code>myFile.out.html</code>.

The syntax of this command is:

-m [options] xliffFile [xliffFile2...]

Note: <code>-m2</code> is the same as <code>-m</code> and use a skeleton file for the merge, while <code>-m1</code> uses the original document for the merge.

Where the options are:

{| border="1" cellpadding="5" cellspacing="0"
|- valign="top"
|nowrap="nowrap"| <code>-fc configId</code> || The identifier of the filter configuration to use for the re-extraction of the original file.
|- valign="top"
| <code>-ie encoding</code> || The encoding name of the original files. This is used only if the filter cannot detect the encoding from the input file itself.
|- valign="top"
| <code>-oe encoding</code> || The encoding name of the file to generate. The same encoding as the input file will be used if this option is not specified.
|- valign="top"
| <code>-sl srcLang</code> || The code of the source language. [[Tikal - Usage#Source and Target Languages|See more details...]]
|- valign="top"
| <code>-tl trgLang</code> || The code of the target language. [[Tikal - Usage#Source and Target Languages|See more details...]]
|- valign="top"
| <code>-sd sourceDirectory</code> || The directory where to find the source file of the XLIFF document.
|- valign="top"
| <code>-od outputDirectory</code> || The directory where to place the output.
|}

For example:

tikal -m *.xlf -sl EN -tl DE

Merges all XLIFF documents in the directory. The skeleton files should be in the same directory as well. The source language is English and the target language is German.

tikal -m toTrans/*.xlf -sl EN -tl ZU -sd . -od xlated

Merges all XLIFF documents in the <code>toTrans</code> sub-directory of the current directory. The skeleton files are in the current directory. The merged files are placed in the <code>xlated</code> sub-directory of the current directory. The source language is English and the target language is Zulu.

==Extract Files to Moses==

This command extracts the translatable content of one or more given files into a [[Moses Text Filter|text format usable by Moses]]. You can then perform various tasks on this document.

The Moses files created are placed in the same directories as the original files, and have the same name with an additional extension that is the code of the source locale.

If the option <code>-2</code> is set, the target output has the same name as the source output, but with an extension that is the code of the target locale, except if the source file ends with an extension that it the code of the source locale. In that case, the target file takes the name of the source file with the last extension replaced by the code of the target language. For example, if the English source output is <code>out.txt</code>, the target output for French is <code>out.txt.fr</code>. If the English source output is <code>out.en</code>, the target output for French is <code>out.fr</code>.

The syntax of this command is:

-xm [options] inputFile

Where the options are:

{| border="1" cellpadding="5" cellspacing="0"
|- valign="top"
| <code>-fc configId</code> || The identifier of the filter configuration to use for the extraction.
|- valign="top"
| <code>-ie encoding</code> || The encoding name of the input files. This is used only if the filter cannot detect the encoding from the input file itself.
|- valign="top"
| <code>-sl srcLang</code> || The code of the source language of the input files. [[Tikal - Usage#Source and Target Languages|See more details...]]
|- valign="top"
| <code>-tl trgLang</code> || The code of the target language (used in the input if the input documents are multilingual). [[Tikal - Usage#Source and Target Languages|See more details...]]
|- valign="top"
| <code>-2</code> || Extract two files: one for the source, one for the target. The target file has as many lines as the source file as lines. If there is an existing target segment, the target segment is extracted, otherwise an empty line is used for the missing target.
|- valign="top"
|nowrap="nowrap"|<code>-to srcOutputFile</code> || The path of the Moses source file to generate. The last part of the path is the template filename to use, the code of the source language is added automatically.
|- valign="top"
|nowrap="nowrap"| <code>-seg [srxFile]</code> || The segmentation rules to utilize. To specify the default rules that come with the installation, use <code>-seg</code> without filename. The default rules are in <code>config/defaultSegmentation.srx</code> in your Okapi main directory.
|- valign="top"
| <code>-rd rootDirectory</code> || The root directory (by default the user's home directory).
|}

For example:

tikal -xm myFile.html

Extracts the HTML file <code>myFile.html</code> in the current directory into corresponding <code>myFile.html.en</code> Moses document, assuming the default source language is English.

tikal -xm myFile.xlf -2 -sl en-us -tl af

Extracts the content of the XLIFF document <code>myFile.xlf</code> into two Moses InlineText files. The first one named <code>myFile.xlf.en-us</code> for the source, the second called <code>myFile.xlf.af</code> for the target.

tikal -xm myFile.xlf -2 -to out.txt -sl en -tl zu

Extracts the content of the XLIFF document <code>myFile.xlf</code> into two Moses InlineText files. The first one named <code>out.txt.en</code> for the source, the second called <code>out.txt.zu</code> for the target.

==Leverage Files from Moses==

This command takes an input file, and leverages the translation found in its corresponding Moses InlineText files. The initial InlineText file should be created with the [[#Extract Files to Moses|Extract Files to Moses command]].

The filter configuration, input encoding and segmentation parameters must be the same in this command as they were in the extraction command. This is to ensure the entries between the input file and the corresponding Moses file match one-to-one.

The new documents are created in the directories where the input documents are, with a <code>.out</code> extension pre-pended to the original extension. For example, if your original file is <code>myFile.xlf</code>, and your target language is Zulu, the Moses InlineText document should be (by default) <code>myFile.xlf.zu</code>, and the leveraged result file will be <code>myFile.out.xlf</code>.

The syntax of this command is:

-lm [options] inputFile

Where the options are:

{| border="1" cellpadding="5" cellspacing="0"
|- valign="top"
| <code>-fc configId</code> || The identifier of the filter configuration to use for the extraction.
|- valign="top"
| <code>-ie encoding</code> || The encoding name of the input files. This is used only if the filter cannot detect the encoding from the input file itself.
|- valign="top"
| <code>-oe encoding</code> || The encoding name of the file to generate. The same encoding as the input file will be used if this option is not specified.
|- valign="top"
| <code>-sl srcLang</code> || The code of the source language of the input files. [[Tikal - Usage#Source and Target Languages|See more details...]]
|- valign="top"
| <code>-tl trgLang</code> || The code of the target language. [[Tikal - Usage#Source and Target Languages|See more details...]]
|- valign="top"
| <code>-totrg</code> || Copy the leveraged translation into the target, except if there is already an existing target content.
|- valign="top"
| <code>-overtrg</code> || Copy the leveraged translation into the target, even if is already an existing target content.
|- valign="top"
| <code>-bpt</code> || Use the <code><bpt>/<ept>/<ph></code> notation instead of the <code><g>/<x></code> notation in <code>&lat-trans></code> elements.
|- valign="top"
|nowrap="nowrap"|<code>-from mosesFile</code> || The path of the Moses InlineText file from which to leverage the text. If this option is not set, the file to leverage from is the same as the input file with the language code of the target appended as an extension.
|- valign="top"
|nowrap="nowrap"|<code>-to outputFile</code> || The path of the output file to generate. If this option is not set, the output is the same as the input with <code>.out</code> prepended to the file extension.
|- valign="top"
|nowrap="nowrap"|<code>-seg [srxFile]</code> || The segmentation rules to utilize. To specify the default rules that come with the installation, use <code>-seg</code> without filename. The default rules are in <code>config/defaultSegmentation.srx</code> in your Okapi main directory.
|- valign="top"
|nowrap="nowrap"|<code>-rd rootDirectory</code> || The root directory (by default the user's home directory).
|- valign="top"
| <code>-noalttrans</code> || Ensures that the generated XLIFF files do not have added <code><alt-trans></code> elements.
|}

For example:

tikal -lm myFile.html -tl zh

Puts in the input file <code>myFile.html</code> from the corresponding <code>myFile.html.zh</code> Moses InlineText document. The source language is the default for the platform, while the target is Chinese (zh). The output file is <code>myFile.out.html</code>.

tikal -lm myFile.xlf -sl en -tl ja -from trans.txt -totrg

Leverages the XLIFF file named <code>myFile.xlf</code> in the current directory using the Moses InlineText document named <code>trans.txt</code>. The source language is English and the target is Japanese. The output file is <code>myFile.out.xlf</code>. The Moses translation is copied into the <code><target></code> elements only if the element is empty or non-existing in the source document. The <code><alt-trans></code> elements are added for all segments.

[[Category:Tikal]] [[Category:Filters]] [[Category:XLIFF]]