# data[].attributes.body
26.03

Source text requieres translation for which I will use OmegaT version 5.4.4.

# data[].attributes.headline
I have already translated this text once but I was not happy with the outcome and how time consuming it was without using OmegaT.

# data[].attributes.subject
I have already translated this text once but I was not happy with the outcome and how time consuming it was without using OmegaT.

# data[].attributes.body
26.03 creating project

# data[].attributes.body
adding spellchecker

# data[].attributes.body
a plain visual of the project

# data[].attributes.body
Creating glossary

# data[].attributes.body
Changing font and colours

# data[].attributes.body
aligning texts

# data[].attributes.body
machine translation

# data[].attributes.body
After creating the project and before translating and checking I wanted to install plugins. After adding the plugin to the folder and restarting the aplication the plugin did not work.

# data[].attributes.body
I have decided that unpacking this plugin is risky due to suspicious amounts of files and in addition they took a lot of space for such a plugin so I'm looking for a better one.

# data[].attributes.body
I have succesfully added a new machine translator "Autshumato Translate". The issue is that it has limited language pairs where polish is not an option but now I learned how to install plugins.

# data[].attributes.body
Learn how to add plugins and revise the steps that were done during the course

# data[].attributes.body
target text

# data[].attributes.body
During this project I have learned how to add plugins thanks to a youtube video https://www.youtube.com/watch?v=eLwRhI6ywH4&t=2s on how to install them.

# data[].attributes.attachment_link.title
Increasing Ease of Use in OmegaT with FolderMenu Plugin

# data[].attributes.body
Moreover the plugin "Autshumato Translate" came with instruction that I have followed.

# data[].attributes.body
Many plugins require different versions or OmegaT or Java, a lot of them are with API key requirements especially those that enable machine translation.

# data[].attributes.body
However that link provided to be very helpful, because thanks to it I also saw all the intructions on how to add plugins

# data[].attributes.attachment_link.readable_text
Use to access this dialog (the OmegaT menu on macOS).

Use the search field at the top of the preferences list to look for specific items.

Preferences set in this dialog are saved to the default configuration folder and apply to all translation projects unless you have specified a different configuration folder.

Note

It is possible to have OmegaT use a different configuration folder to define project-specific configurations. See the Command line launch section for details. If you specify such a configuration folder, all modifications made in this dialog will be stored there.

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.

Access Configuration Folder

Opens the local folder where OmegaT configuration files are stored.

Note

The location depends on the operating system and launch options. See the Configuration Folder appendix for details.

Automatically fetch translations

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 in the current segment. You then have to press that combination again to insert the suggestion.

Untranslated segments only

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.

Note

Most providers require some kind of registration before using their services. Make sure you have the proper credentials before using this function.

Preferences here define how the contents of the dictionary folder are displayed in the Dictionaries pane.

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.

Select the font and font size used to display the text in the main window panes.

You can assign different colours for the various parts of the user interface.

Scripts can be used to set predefined themes. OmegaT is bundled with a script called Switch Colour Theme that provides a default dark theme. See the window for details.

This dialog lists the file filters available to projects that do not use local file filters.

The contents of this preference are identical to the contents of the local file filters dialog. See the File Filters appendix for details.

Note

If local file filters are used, modifying global file filters will have no effect on the project.

See the Segmentation appendix for a general explanation of segmentation (global or local, paragraph or sentence, etc.)

Warning

This dialog only accesses the global segmentation rules. If you have set local rules in the Project Properties dialog, modifications here will not be taken into account.

Only the rules associated to language patterns that correspond to the source language of your project are applied. See the project properties.

When you click on a language pattern in the top half of the dialog, a list of associated rules will be displayed in the bottom half of the dialog.

All segmentation rule sets for a matching language pattern are active and are applied in order. Rules for specific language regions should be higher than default ones.

To create a new rule set:

The existing rules always provide a good starting point.

The auto-completion menu is available in the pane. See the Auto-completion menu section for details.

Click on Glossary to configure the auto-completer glossary view.

Click on Autotext to configure the Autotext options, and to add or remove entries.

Click on Character Table to set the Character table auto-completer options.

Click on Enable history completion or Enable history prediction to set history based completions.

Note

Absolutely none of your data (history, etc.) is sent to an external server by OmegaT for processing. All prediction/completion results are computed locally.

If the Show Relevant Suggestions Automatically option is checked, typing the first letter of a translated glossary entry, or < for a tag, automatically launches the auto-completer.

OmegaT has a built-in spellchecker but requires you to install spellchecking dictionaries based on your target languages.

Warning

OmegaT will use the language dictionary that has the same name as the target language code set in the project property. An dictionary will not spellcheck target segments. If necessary, modify the name of the dictionary or change your project's language settings.

Spellcheck the translation

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 or to . See spellchecker files for details.

Spellchecking dictionaries location

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.

URL of downloadable spellchecking dictionaries

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.

Warning

This action requires an internet connection

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.

External searches are either web searches or local commands that take the string selected in the Editor as a parameter. The web searches are opened in the default browser and the commands are equivalent to items launched on the command line.

Allow local external search commands

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.

Warning

Restart OmegaT to apply this change.

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 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.

Example 22. URL search example

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

This opens a search for the {target} term on DuckDuckGo with a number of search parameters.

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

Example 23. Command example

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

This opens the dictionary application that implements the dict protocol on your machine looking for the {target} term.

When entering an empty segment:

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

Leave the segment empty

You can enter your translation right away.

Insert the best fuzzy match

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.

The name you enter here will be attached to all the segments you translate.

Repository Credentials

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.

Minimal threshold to show a fuzzy match

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

Note

Each of the three types of matching percentages presented in the Fuzzy Matches pane are taken into account to determine whether a match is displayed. Potential matches are rejected if all three percentages are below the threshold.

Select how tags of non-OmegaT TMXs should be displayed

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/>).

Include matches from other languages

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.

Match display template

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.

Table 4. Match template variables

Percentage calculated with the Stemming, no tags and no numbers option.

${noStemScore}

Percentage calculated with the No tags and no numbers option.

${adjustedScore}

Percentage calculated with the Full text, including tags and numbers option.

Project data saving interval

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:

Global post-processing commands

OmegaT can automatically run commands after you use or . 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.

Allow local post-processing commands

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.

Note

Local commands are run before global commands.

If you use an authenticated proxy server to access the Internet, enter your credentials here.

Define or reset the master password used to protect login credentials as well as access keys for machine translation services.

Before resetting the master password, always make a backup of that information, because it will be deleted and will have to be re-entered.

Displays the list of all the installed plugins.

Plugins are by default installed in the configuration folder, but can also be installed in the plugins/ folder under the application folder.

Additional plugins can be found on the OmegaT development site.

# data[].attributes.attachment_link.description
Use to access this dialog (the OmegaT menu on macOS).

# data[].attributes.body
A few days ago I have also posted a question on reddit but as an answer I got a link to a manual

# data[].attributes.headline
30.05  After working with many translation tools such as Memoq, OmegaT and PhraseTMS, I've decided to try to find some more tools but they had to be in the brower simiraly to Phrase in order to see the differences. I will be trying new translation tools without using any tutorials.

# data[].attributes.subject
30.05  After working with many translation tools such as Memoq, OmegaT and PhraseTMS, I've decided to try to find some more tools but they had to be in the brower simiraly to Phrase in order to see the differences. I will be trying new translation tools without using any tutorials.

# data[].attributes.body
The next tool I'd like to see is Doc3, a tool that can be used for free (with limitations).

# data[].attributes.body
The first thing to notice is that in free version you can use only local glossaries and TM.

# data[].attributes.body
The layout is very user friendly, including various information about your project status, however these constant ad sabout ''pro'' version can be pretty annoying.

# data[].attributes.body
First thing to notice is that to confirm the segment you can't use ctrl+enter, it simply doesn't work. You need to press button submit. What I do like is when a tag is in the text it will appear under the segments, you can add it by pressing it.

# data[].attributes.body
Another useful option is that under the burron ''segments'' you can filter all your segment and see these specific that you're looking for.

# data[].attributes.body
Conclusion:

After some work with Doc3 I can tell that this is a good tool but is has some downsides, lack of alignment tool is definetly on that list. This tool can be used as a multiple person project platform simiraly to Phrase, but it doesn't log you out after 2 weeks of free trial. This tool is very useful for quick and easy translations, more advanced texts could be too time consuming.

# data[].attributes.body
The next tool I wanted to see is Matecat. The first thing I noticed after creating a project was ''split'' button, even before translating so that is definetly new.

# data[].attributes.body
Now instead of 1 long translation I have 2 smaller ones, but I'll merge them back together.

# data[].attributes.body
The general layout is confusing at the beggining, there are no segment numbers which gives the idea why to use the ''split'' button before translating.

# data[].attributes.body
I had a very hard time to determine which is my acutal translation segment and where are machine translation suggestions. The text is immiedietly pre translated, which both good and bad in my opinion.

# data[].attributes.body
Based on Doc3 experience I was very happy to see the aligment tool

# data[].attributes.body
The alignment tool is not respoding.

# data[].attributes.body
I think this tool could be useful for someone who translates only simpler texts because of the instant pre translation, but any bigger or more advanced text could cause the translator to lose himself in this grey coloring. But contrary to Doc3, ctrl+enter works!

# data[].attributes.body
In the following sections I present a project consisting of translating a text using OmegaT and then follow it with practice on how to install plugins.

# data[].attributes.body
After working with quite a few translation tools (I tried also CafeTran Espresso tool but it was just horrible to look at that i gave up, too weird) I notcied that tools that are in the browser are much more limited than software ones. I sitll have much to learn especially when it comes to coding, sometimes the app can just fall apart and it can be omitted by altering the code.