Preferences

The default key to validate and leave a segment is Enter .

This option sets the segment validation key to Tab instead.

This option is useful with some Chinese, Japanese or Korean character input systems.

The program will ask for confirmation before closing.

Opens the local folder where OmegaT configuration files are stored.

Enable this option to automatically fetch machine translations from the providers you have enabled and configured. If you leave this option disabled, machine translations are only fetched when you use Edit Replace with Machine Translation C + M in the current segment. You then have to press that combination again to insert the suggestion.

Check this box to send only untranslated segments to the machine translation services.

In the list of machine translation available in OmegaT, check the Enabled box for each provider you want to access. Use the Configure button to manage your authentication credentials for that provider.

Uncheck this option if the context description shown for each glossary entry is unnecessary or too long.

When a glossary term is a compound word, the term will match even if the words appear separately in the source text.

OmegaT will use the associated tokenizer to find matches.

When you use

to insert the source content in the target segment, words with a glossary entry will automatically be replaced by their translation.

Matches with very different case are not displayed.

Select a layout for the glossaries pane contents. Additional layouts can be added as plugins.

If a glossary item has multiple definitions, they will be displayed on the same line.

While the option is disabled, use Edit Search Dictionaries A + S + D to search for matches of the selection or of all the terms in the segment source.

When the option is enabled, OmegaT automatically searches in all the dictionaries for matches of the terms it identified in the segment, as it enters the segment.

OmegaT will use the associated tokenizer to find matches.

Some dictionary drivers provided as plugins do not support this feature.

Select a theme for the OmegaT user interface.

Additional themes can be added as plugins. The themes also provide predefined set of default colours.

Not all natively provided Java themes are compatible with OmegaT operation.

Restores the OmegaT window panes to their default arrangement.

Use this feature when you are unable to restore the desired arrangement after undocking, moving, or hiding one or more panes. You can use it when panes do not appear as expected after an OmegaT upgrade.

Enable after installing a spellchecking dictionary. OmegaT will underline spelling mistakes with red wavy-lines.

Use the editor context menu to correct the mistake, to Ignore All or to Add to Dictionary. See spellchecker files for details.

The folder where OmegaT will install and search for spelling dictionaries. It is generally in the Configuration Folder folder.

The list of dictionaries that are present in the above folder.

If none are displayed it either means that you have not yet installed a spelling dictionary, or that your project uses a specific configuration folder that does not contain yet a spelling dictionary.

The default URL where OmegaT will look for dictionaries to install.

You can also download dictionaries from other locations, or copy dictionaries installed locally.

Displays the list of available dictionaries from the above URL.

Select the dictionaries that you want to install and click Install. Depending on your internet connection it may take a while before the dictionary is installed.

Select the location of the language checker.

Using a different language checker on your local machine than the one supplied with OmegaT allows you to customize the verification rules.

Select the rules depending on whether they are relevant to the type of text you are translating.

Local external search commands are saved in the filters.xml file. Only activate this option if you trust the source of that file.

This option enables you to change the order of the commands in the Editor pane context menu. Values around 100 display commands at the top, and values around 900 display them at the bottom.

Each set represents a group of web searches or local commands that are launched simultaneously.

A set must be given a name. The name will be displayed at the bottom of the Tools menu.

If you check Show in Editor context menu, the set name will also be displayed in the context menu if a string is selected.

URL searches as well as commands must contain the string {target} to be accepted. The {target} placeholder will be replaced by the string that was selected in the Editor.

URLs are opened with the default web browser, one per tab.

https://duckduckgo.com/?q=%22{target}%22+site%3A.fr+-linguee

Commands are opened on the command line. The Delimiterdefines the delimiter between command parameters. The default delimiter is |.

/usr/bin/open|dict://{target}

Use this option temporarily for parts of the translation that do not require much transformation.

You can enter your translation right away.

OmegaT inserts the translation with the highest match percentage above the value you set in this dialog.

The prefix identifies translations inserted as fuzzy matches. You can also register the prefix in the Flagged text preference to include it in the tag issues checking process and make sure you do not forget it in your translation.

When a fuzzy match is inserted, OmegaT tries to replace the numbers in the fuzzy match with the numbers in the source text.

[[2001年]]、ドイツの永住権を取得。

[[2003年]]、ドイツの永住権を取得。
[[2003]], elle acquiert la nationalité allemande.

[[2001]], elle acquiert la nationalité allemande.

A translation that is identical to the source text is not recognized as a translation by default. OmegaT will erase it and will count the segment as not translated.

Use this option to force OmegaT to register such entries and count them as translated.

When OmegaT enters a segment,

both located in the scripting folder.

The files are overwritten when OmegaT enters a new segment.

The Extract Text Content script does something similar but for the whole project at once. See the Scripting window.

Go To Next Untranslated Segment C + U also stops at segments with alternative translations.

Tags should generally not be modified, but that is possible when this option is enabled.

OmegaT runs an issues check on the segment as you leave it. The option is equivalent to using Tools Check Issues... C + S + V .

Translation memories located in tm/auto and tm/enforce can auto-populate the project memory. Segments that receive automated translation at that time can be marked in the Editor pane by using View . Highlight Auto-Populated Segments .

See the Reuse TMs how-to for details.

When machine translation is enabled, OmegaT registers the name of the engine that was used to populate a given segment.

The editor initially loads and displays 2,000 segments, and progressively loads more as you scroll up or down. Change this number according to your machine performance.

Use View Display Paragraph Delimitations to identify segments that belong to the same paragraph.

Check printf variables in file formats other than the PO format. The PO filter already handles variables marked with %.

You can select

Check Java MessageFormat placeholders in file formats other than the Java Bundles format. The Java Bundles filter already handles placeholders marked with {#} where # is a number.

Tags in a different order than the source will not appear in the list of tag issues. See the Tools Check Issues... C + S + V menu for details.

If you try to create the translated files, OmegaT will display the issues dialog until no issues are found. See the Tools Check Issues... C + S + V menu for details.

Unlike OmegaT tags, flagged text and custom tags are by default counted in the statistics. See the Tools Statistics menu for details.

Use regular expressions to define custom tags. To define a list of tags, group each tag between parentheses and separate the groups with | (equivalent to "OR" in regular expressions).

For example, use \d+ to treat all numbers as tags, enabling you to check that numbers have not been accidentally changed in the translation.

Similarly, use </?[^>]+> to make sure that HTML (or similar) tags entered into the source text are preserved without modification in the translation.

Use parentheses and | to have OmegaT consider the two tags: (\d+)|(</?[^>]+>) .

See the Regular expressions appendix for details.

Text in the target segment matching this expression is marked in red and identified as an extraneous tag for issue checking purposes. See the Tools Check Issues... C + S + V menu for details.

List of projects for which login details have been stored in OmegaT. Remove a project from this list if you want OmegaT to ask you for its credentials the next time you access it.

By default, stemming is used to determine the closest matches displayed in the Fuzzy Matches panel.

To obtain more literal matches closer to 100%, select the Full text, including tags and numbers option.

OmegaT displays the five best fuzzy matches above 30% by default. You can change that threshold here.

Determine how to handle tags in TMX files generated by other tools.

You can choose whether to display them and whether to use standard XML notation for standalone tags (e.g. <i/>).

Segments that have matches in different target languages can also be displayed in the Fuzzy Matches pane. You can apply a penalty to such matches.

Change how fuzzy matches are displayed, through the use of pre-configured variables:

The default is:

${id}. ${fuzzyFlag}${sourceText} ${targetText}
<${score}/${noStemScore}/${adjustedScore}%
${filePath}>

Here is a possible alternative:

⥤ ${id}. <${score}/${noStemScore}/${adjustedScore}%> ${fuzzyFlag} ${fileNameOnly}
[NEW]▷ ${diff}
			
[OLD]◀ ${diffReversed}
◀ ${targetText}

The template variables are also available from a drop-down menu and can be inserted with a button.

By default, only the current segment is displayed in bold face.

If source segments are displayed in normal face, you can use this option to display only the current source segment in bold.

Use View Highlight Repeated Segments to mark the second and subsequent copy of a repeated segments. Use this option to also mark the first copy of the segment.

OmegaT tags are protected text that represents format-specific tags in the source document. When hovering on an OmegaT tag, OmegaT displays a tooltip that contains the original content of the tag. If that content was originally enclosed in paired tags, the paired tags can be removed from the tooltip for better readability.

Segment modification information is displayed over the segment. the default setting shows who last modified the translation and when:

Translation last modified by suzume on Oct 6, 2022 at 2:18:27 PM
[[チューリッヒ大学]]大学院博士課程修了。
[[Université de Zurich]] Elle finit sa thèse de doctorat.<segment 0178>

Use View Display Modification Info to display segment modification information.

Use the template variables to adapt this template to your needs.

Use the template variables to adapt this template to your needs.

Allows the user to select the interval between automatic project data saves. See the Automatic backups section for details.

Change the default interval (3 minutes) depending on the characteristics of the project:

OmegaT can automatically run commands after you use Project Create Translated Files C + D or Project Create Current Translated File C + S + D . You can define such commands here.

Commands specified here are available to all the projects that use the same configuration folder. They are saved in the omegat.prefs file.

The template variables list gives you access to various project data and system variables. See the Template Variables section for details.

You can also define local post-processing commands available only to a given project. Such commands are defined in the Local post-processing commands window.

Local post-processing commands are saved in the omegat.project file. Only activate this option if you trust the source of that file.