Common English to Russian Translation Errors. Part 9. Basics

May 23rd, 2017, Roman Mironov

This article continues the series of posts about errors that translators working in the English to Russian language combination make. This time, the focus is on basic errors that may sound obvious to you, but you wоuld be surprised how many people make them.


Because English is less strict about the dash than Russian, you can encounter a variety of dashes within the same text. Examples:

Original Mark
John is a loner—lives by himself and rarely goes out. Em dash
John is a loner – lives by himself and rarely goes out. En dash
John is a loner – lives by himself and rarely goes out. Hyphen

However, as a professional translator, you cannot just follow the author’s lead. Your first task is to to use the dash consistently. The second task is to use the em dash—this is what Russian punctuation rules require. The en dash is more or less acceptable. But make sure not to use the hyphen—it is totally wrong.

Original Translation Correct or not?
John is a loner—lives by himself and rarely goes out. Джон — настоящий отшельник, живет один и редко выходит в люди. Correct
John is a loner – lives by himself and rarely goes out. Джон – настоящий отшельник, живет один и редко выходит в люди. Less correct, but not that bad
John is a loner – lives by himself and rarely goes out. Джон – настоящий отшельник, живет один и редко выходит в люди. Incorrect

Remember to put a non-breaking space before the dash to ensure that it does not go to the next line.

Original Translation Incorrect
Previous sentence… John is a loner—lives by himself and rarely goes out. Джон — настоящий отшельник, живет один и редко выходит в люди. Джон
— настоящий отшельник, живет один и редко выходит в люди.

Measurement units

English texts often do not use a space between numbers and measurement units. When translating into Russian, however, you need to add a space before the measurement unit, even if it is just a percent sign. And always remember to translate the measurement unit:

Original Correct Incorrect
The free disk space is 100GB. Свободное место на диске составляет 100 ГБ. Свободное место на диске составляет 100GB.
The free disk space is 30%. Свободное место на диске составляет 30 %. Свободное место на диске составляет 30%.

Note that a non-breaking space is required before the measurement unit to avoid the number appear on one line and the measurement unit on the next:

Original Correct Incorrect
The free disk space is 30%. Свободное место на диске составляет 30 %. Свободное место на диске составляет 30

Omitting or translating “you” or “your”

Translation of “you” can be tricky. Firstly, as a rule of thumb, it does not belong in Russian technical documents. You must always find a way to make text work without it. Example:

Original Correct Incorrect
Wait 30 seconds to turn your device back on. Подождите 30 секунд, прежде чем включать устройство. Подождите 30 секунд, прежде чем включать ваше устройство.

Omitting “you” in the translation is usually as easy as deleting it, as in the example above. Sometimes it is more challenging, but that does not mean it is okay to keep it. With certain types of text, however, omitting “you” does not work, because it is important to distinguish between two items:

Original Correct Incorrect
Compare the mask to your device. See your device manual if the values do not match. Сравните маску с устройством. См. руководство пользователя вашего устройства, если значения не совпадают. (“вашего устройства” clearly refers to the “device,” thus distinguishing it from the “mask,” which is also a device.) Сравните маску с устройством. См. руководство пользователя устройства, если значения не совпадают. (Strictly speaking, it is not clear which of the two devices—the mask or the “device”—the word “устройства” refers to.)

Omitting “you” is also impractical when authors address the reader directly. Obvious examples include questionnaires where the point is to ask questions about the respondent—“you”—or marketing copy, which is less formal than technical texts.

Original Correct
Revitalize your body and mind in spacious rooms with unique interiors. Вас ждут просторные номера с уникальной обстановкой, отдых в которых поможет восстановить силы.
How many hours do you watch TV per week on average? Сколько часов в неделю Вы в среднем смотрите телевизор?

Thirdly, “вы” should normally be lower-case. The upper-case “Вы” is only required when addressing a specific person formally: in letters, e-mails, etc. Otherwise, the lower-case “вы” is in order.

Original Correct Incorrect
I am contacting you with a request regarding the new initiative. Хочу обратиться к Вам с просьбой по поводу нового проекта. Хочу обратиться к вам с просьбой по поводу нового проекта. (Actually, lower-case “вам” is okay, it is simply less common.)
A direct subordinate is angry with you about a perceived slight on a critical conference call. Прямой подчиненный злится на вас, считая, что вы неуважительно отнеслись к нему в ходе важного конференц-вызова. Прямой подчиненный злится на Вас, считая, что Вы неуважительно отнеслись к нему в ходе важного конференц-вызова.

Note, though, that questionnaires are an exception to this rule: even though you are referring to respondents in general, you still need to use the upper-case “Вы.”

Original Correct Incorrect
Please estimate how much you enjoyed staying in our hotel. Оцените, насколько Вам понравился отдых в нашем отеле. Оцените, насколько вам понравился отдых в нашем отеле.

For more articles in this series, click the link below.

Video: Boosting Your Productivity with a Project Template in OmegaT – Edited

May 11th, 2017, Roman Mironov

This video explains creating new projects in OmegaT based on a project template instead of doing it from scratch.

Using a template

Instead of creating each new project within OmegaT, you keep a template which you copy to a target folder to create a project. Suppose you have a project template stored on a network drive:

Project template
Copy to your projects folder to create a project
Y:\Auxiliary files\OmegaT project template\.ini
Y:\Auxiliary files\OmegaT project template\dictionary
Y:\Auxiliary files\OmegaT project template\glossary
Y:\Auxiliary files\OmegaT project template\omegat
Y:\Auxiliary files\OmegaT project template\source
Y:\Auxiliary files\OmegaT project template\target
Y:\Auxiliary files\OmegaT project template\tm
Y:\Auxiliary files\OmegaT project template\omegat.project
Y:\Projects\Project 014\.ini
Y:\Projects\Project 014\dictionary
Y:\Projects\Project 014\glossary
Y:\Projects\Project 014\omegat
Y:\Projects\Project 014\source
Y:\Projects\Project 014\target
Y:\Projects\Project 014\tm
Y:\Projects\Project 014\omegat.project

This template includes settings, files, and folders that you would otherwise have to configure or copy into the new project manually. Let’s look at how helpful it is to avoid this manual work.

Keeping file filters and segmentation project-specific

The main reason for creating projects with a project template is using project-specific filters.xml and segmentation.conf files for each project automatically.

File What it is for
filters.xml Settings for file filters
segmentation.conf Segmentation rules

If you create a new project through OmegaT, it uses the default filters.xml and segmentation.conf stored on your computer (under the user settings folder, such as C:\Users\Your name\AppData\Roaming\OmegaT under Windows). If you open the same project on a different computer, it might not have the same tags or segmentation, because the default settings stored on that computer are different. By relying on a project template that already includes filters.xml and segmentation.conf, you ensure that OmegaT will use these project-specific settings regardless of the computer you are at.

Storing these project-specific settings in a template makes it possible to optimize them continually. For example, if you create a powerful segmentation rule that you want to re-use in the future, you add it to this project template (by simply opening it as a regular project and then adding the rule). Next time you create a project by copying this template, this rule will be be in your project-specific settings. The project template thus serves as a storage for accumulating preferred filter and segmentation settings, whereas otherwise, you are likely to bury those new settings within individual projects or at different computers.

Building your custom spelling dictionary

You can store your custom spell checker dictionary (learned_words.txt) in the OmegaT project template as well. This allows re-using the dictionary in each new project, which saves you time by not having to add the same words to the custom dictionary again and again. Remember, though, that building this custom dictionary over time requires collecting new words from individual projects into it manually—OmegaT cannot do it for you.

Ability to add custom folders and files to each project automatically

New projects created by OmegaT have a default folder structure. If you want to add anything to this structure, you do this manually. However, a project template spares you this manual work. By simply adding custom files and folders to this template, you make them available in each new project automatically. Examples include:

Configuring project settings

Within your project template, you can also configure project settings in the omegat.project file to use those settings in each new project automatically, without manual configuration. Examples include:

I encourage you to give this project template idea a try. If you need help with it or have feedback, get back to me in the comments.

If this article was of value to you, please let others know about this blog by posting a link to it on your site or social media.

The Ultimate Shortcut to Translating Russian into English with Optimal Quality

February 3rd, 2016, Roman Mironov

 Jason Taellious,
Looking for a translation agency to translate Russian into English? This article explains why it is important to have your translation done by a native speaker, budget permitting.

Why a native speaker?

Translation is best done by native speakers of the target language (the one being translated into), because it requires excellent command of the language that only people who learned it as native speakers have. Learning a second language later in life rarely results in excellent command.

That said, when it comes to translating from Russian into English, your translation team must include native speakers of English. Now, the problem is that there is a huge supply of RU-EN translators in Russia, native speakers of Russian, producing low-quality work at bargain-basement rates, which makes it difficult to find the proverbial diamond in the rough in this market. The problem is exacerbated by the fact that clients sometimes succeed in buying good EN-RU translations at low rates and assume they can do the same for RU-EN, never realizing that good RU-EN translation costs are much higher because of a different supply and demand ratio—there are many fewer skilled translators in this combination.

As a result, the market for RU-EN translations is segmented into at least three categories, with huge price and quality gaps between them.

Three quality categories

  1. The first category is native speakers of English who are professional translators. Being in the best position to translate into their native language and equipped with professional training, they deliver top-notch work.
  2. The second category is non-native speakers of English who are professional translators. They produce average translations that appear to follow English grammar and punctuation rules, but use language patterns typical of Russian, sounding weird to native English speakers. Such word-for-word translations are called “Runglish.” Here is an example:
    Russian Runglish English
    Мы уделяем особое внимание нашим услугам в области устного перевода. We pay particular attention to our services in the area of oral translation. Our particular focus is interpretation services.
  3. The third category is non-native speakers of English who are hobby translators. As if literal translations were not bad enough, these folks also inject their work with mistranslations, bad grammar, faulty punctuation, and spelling errors. Often lacking essential knowledge of the English language, they fail to adhere even to basic rules, such as distinguishing between BE and AE spelling.


What do you make of these categories? Most importantly, you need to understand your quality expectations before you buy. And by all means, consider these expectations, rather than making your choice based on budget alone:

    1. Just like medical or legal services, important translation is a service that does not lend itself to economy. You need a professional native RU-EN speaker for mission-critical content where nothing but top quality is acceptable. For instance, it makes no sense to save on translating marketing copy, because you will inevitably end up with texts that fail to sell or, worse, make people ridicule you. Here is an example of a great marketing translation from Russian into English: Bitrix24.
    2. For less important materials, such as documents submitted only to fulfill a legal requirement or internal company materials, a professional non-native RU-EN translator might be sufficient. If you believe that average quality is fine for a particular piece of text, there is nothing wrong with buying this kind of translation.
    3. Going with the cheapest hobby RU-EN translators is never a good idea. Although you might enjoy the low costs, you will end up wasting your time and money or even damaging your reputation. You may think that you are saving money, but in the final analysis, you are losing it. Think of it this way: you can spend an entire day doing something that a professional could have done in just one hour—you are not really saving money by doing it yourself, but wasting time you could have spent way more productively.

How to ensure you get a native speaker to translate Russian into English

You can take certain steps to have your translation done by native speakers:

  1. Insist on a native speaker when you talk to a translation agency’s salesperson. That does not mean you will get one, but increases the odds.
  2. Request a sample from an agency to evaluate quality before you buy.
  3. Try engaging a translator who is a native speaker directly.

Another way to safeguard yourself is to outsource translating from Russian to English to folks who know these subtle differences and have your best interests at heart, as we do. Contact Velior for a free quote today so that we can recommend you a quality level that meets your needs.

Video: Translating Trados Files in OmegaT? It’s Never Been Easier!

December 27th, 2015, Roman Mironov

Are you tasked with translating SDLXLIFF files from an agency client, but want to use OmegaT to do the translation? This may happen when you do not own a SDL Trados Studio license or you, like some of our readers, have an aversion to this program. Here is the good news: OmegaT makes such task easy with the use of the XLIFF filter included in the Okapi plugin. In fact, this filter has been around for a few years, but it is only with the M26 release that it can save translated SDLXLIFFs properly, without breaking them.

How to use the Okapi XLIFF filter

Choosing XLIFF filter provided by Okapi plugin in OmegaT

  1. Put SDLXLIFF files into the source folder of your OmegaT project.
  2. Open the project, then open project properties and go to File Filters. Make sure the XLIFF files (Okapi) filter is checked, while the XLIFF (native) filter is unchecked. OmegaT will highlight the current filter for your convenience.
  3. In the project properties, uncheck Enable Sentence-level segmenting. By disabling segmentation, you keep the original segmentation of SDLXLIFF files and also enable OmegaT to insert any 100% matches automatically.
  4. Translate the text.
  5. Create the translated files.


Although this is absolutely the easiest way to translate SDLXLIFF files in OmegaT, I cannot promise it is the safest one. I did test it extensively and found no problems so far. However, I stongly recommend a roundtrip. Before diving deep in translation, you translate a few segments, save the “translated” file, and open it in SDL Trados Studio to make sure everything is fine.

It is also a good idea to open translated files in Studio after completing translation. Obviously, to do this kind of check, you need to own a Studio license. If you do not have one, at least have a colleague who has such a license and can check files for you in important projects.


You may also want to use this route with files that have a lot of 100% matches, because there is no easy way to handle such files with the native XLIFF filter.


What is still slightly disappointing about this filter is that tags it displays have incremental numbers, which can undesirably turn non-unique segments (i.e., repetitions) into unique ones.
Tags by the Okapi plugin filter vs. tags by the native XLIFF filter

If this blog post helped you, you can help it in return—share a link to it on your site or social media profile. You can also watch other OmegaT videos we posted.

Video: Don’t Translate in Studio If You Don’t Want to

December 18th, 2015, Roman Mironov

This video explains the basics of translating SDL Trados Studio files in OmegaT to give you a general idea of the process:

Two filters

OmegaT has two XLIFF filters: the native one and the one from the Okapi plugin. The native filter requires that the text to be translated is placed between the “target” tags within the file or, put simply, source is copied into target. This is the filter that I am going to work with.

Native OmegaT and Okapi File Filters for XLIFF

Preparing the SDLXLIFF file for translation in OmegaT

  1. Open the SDLXLIFF file in Studio.
  2. Use the Copy All Sources to Target command to insert the original text into the right column. This creates the “source equals target” format expected by OmegaT. For pre-translated segments, you will need to use the Clear Target Segment command first, or else Studio will not populate those segments with the original text.
  3. Save and close the file.

Translating the file in OmegaT

  1. Open the project in OmegaT and make sure the native XLIFF filter is used. The text for translation will appear in the Editor pane.
  2. Translate the text.
  3. Create the translated file.

Checking the translated file

  1. Open the translated file in Studio and watch for any errors during opening.
  2. Run QA Checker.
  3. Save the target file in Studio to make sure the SDLXLIFF was not corrupted while translating with OmegaT.

What I showed is a very basic process. There are quite a few nuances and ways to automate the process, including the ability to forgo using Studio.

If this blog post helped you in some way, please share a link to it on your site or social media. Watch other OmegaT videos posted on this blog.

Video: How to Save Time While Avoiding Losing TMs and Glossaries with a Centralized Location for TMs and Glossaries in OmegaT

September 6th, 2015, Roman Mironov

This video explains yet another way to be more productive with OmegaT.

Centralized location concept

When you create a new project, OmegaT puts the “tm” and “glossary” subfolders in the project folder. If you have any additional TMs for this project, you copy them into the “tm” subfolder, and the same for the glossaries. With long-term projects (returning clients), you end up copying all previous project TMs and glossaries into these subfolders whenever you create a new project. This is inefficient and—like any manual process—prone to human error, such as forgetting to copy some of your files.

To avoid this problem, you can store and access TMs and glossaries for clients in a centralized manner. The setup looks like this:


Your clients’ TMs and glossaries go into the “tm” and “glossary” subfolders within this centralized location. When you set up a project, you point OmegaT to this folder for the TMs and glossaries, thus making it use the centralized location instead of the local folders.

The next time you create a project for this client, all you need to do is this:

  1. Copy the TM and the glossary from the last project into the centralized location. This will make sure your centralized location has all files from previous projects. This is still a manual process, but it is much easier and smarter than copying files between local project subfolders.
  2. Point the new project to the centralized location for TMs and glossaries.

Final tips

  1. If you use OmegaT on different devices, it is a good idea to put this centralized location on a network share accessible from all these devices.
  2. To avoid configuring paths to the centralized location manually for each new project, you can simply copy the project configuration file (omegat.project) from the last project to the new one, provided the old one has correct paths.

In conclusion

Relying on a centralized location to store TMs and glossaries is an important step to keeping your valuable translation assets under control. Not only does it bring organization to TMs and glossaries, but it also saves time and prevents you from using outdated files or losing important files.

If this article was of value to you, please help keep this blog going by posting a link to it on your site or social media.

Common English to Russian Translation Errors. Part 8. “Function” and “Functional”

April 17th, 2015, Roman Mironov

This is the next article in the series about frequent challenges that Russian translators face. It explains nuances of translating the term “function” in the context of business administration.

Meaning and challenge

Function is a traditional way of organizing people into broad groups within an organization, based on their most general role. Common functions include operations, human resources, marketing, and accounting.

The challenge with the Russian translation of “function” is two-fold:

Problem Original Incorrect or clumsy
Literal translation of “function” does not work. The entire decision-making process can stall, usually at one of four bottlenecks: function versus function Вследствие этого весь процесс принятия решений может застопориться, обычно из-за одной из четырех проблем: конфликт между функциями
There is no short and sweet Russian equivalent that would fit all contexts, which often forces translators to use longer, descriptive word combinations. Sometimes, the words chosen by translators are not fully equivalent to the original meaning. Colleagues feel that people help across functions. Сотрудники считают, что люди в организации готовы помогать друг другу независимо от функциональной области, в которой они работают.

Possible translations of “function” and “functional”

Option Original Translation
Функциональная область (you can also add “деятельности”) For example, after senior managers at a major U.S. retailer used this method to sort out a particularly thorny set of corporate decisions, they promptly built the process into their own functional organizations. Например, после того как высшие руководители крупного американского ритейлера успешно применили метод для ряда особенно проблематичных корпоративных решений, они поспешили наладить аналогичный процесс в собственных функциональных областях.
Функциональное подразделение But fluid decision making across functional teams remains a constant challenge, even for companies known for doing it well, like Toyota and Dell. Однако совместное принятие решений несколькими функциональными подразделениями по-прежнему затруднено, даже в компаниях, известных своими успехами в этой области, таких как Toyota и Dell.
Подразделение (отдел). Be careful because it may appear narrower than “function” and clash with translations of “division” or “department.” Different functions have different incentives and goals, which are often in conflict. У разных подразделений (отделов) разные стимулы и цели, которые часто противоречат друг другу.

Regardless of the option chosen, it might be a good idea to explain what is exactly meant the first time the term is used.


“Cross-functional,” meaning “bringing together people from different functions,” takes the translation challenge to the next level. Translators find themselves between a rock and a hard place—a literal translation that makes readers scratch their heads or a long, descriptive translation that makes the text difficult to read.

Option Original Translation
Literal translation Each table group will form a cross-functional team tasked with proposing a new logo for a division of our global company. Группа за каждым столом формирует межфункциональную команду, перед которой поставлена задача разработать новый логотип для подразделения нашей глобальной компании.
Long, descriptive translation Cross-functional decisions too often result in ineffective compromise solutions, which frequently need to be revisited because the right people were not involved at the outset. Решения, принятые группой людей из разных функциональных областей организации, слишком часто оборачиваются неэффективным компромиссом и требуют пересмотра из-за того, что изначально к принятию решения не были привлечены нужные люди.

The choice depends on context. If you choose “межфункциональный,” make sure to provide an explanation the first time the term is used.

Incorrect translations

Once again, it is important to avoid the simplistic translations provided as examples below:

Original Correct Incorrect
For instance, a team that thinks it’s more efficient to make a decision without consulting other functions may wind up missing out on relevant input. Например, группа сотрудников может посчитать, что примет более эффективное решение, не консультируясь с представителями других функциональных областей, и в итоге может упустить из виду существенную информацию Например, один отдел может посчитать, что примет более эффективное решение, не консультируясь с другими функциями, и в итоге может упустить из виду существенную информацию
Different functions have different incentives and goals, which often create conflicts in departments. У разных функциональных областей организации разные стимулы и цели, которые часто создают конфликты на уровне отделов. У разных отделов разные стимулы и цели, которые часто создают конфликты на уровне отделов. (Too narrow and also clashes with translation of “departments.”)

More materials about terminology and other errors in Russian translations.

Video: How to Disconnect Alternative Translations from File Names (OmegaT 3.1.3 Review)

March 26th, 2015, Roman Mironov

Version 3.1.3 brings 16 enhancements, but this video focuses on just four most important ones.

Enhancement in the area of alternative translations

Previously, each alternative translation was rigidly attached to a specific file name. OmegaT would only insert alternative translations when the file name in the translation memory matched the actual name of the translated file. If you forgot about this and change the file name, OmegaT would not insert the alternative translation.

Now you can disable this behavior by unchecking Ignore file context when identifying segments with alternative translations under File Filters. OmegaT will save alternative translations without file names and will insert them in any file as long as the context of the segment is the same, of course.

Although this improvement does not sound exciting, everyone who ran into the issue with alternative translations after renaming files will appreciate it.

project_save.tmx created automatically in team projects

In the past, you had to create the project_save.tmx file in a repository for each team project. Otherwise, you would get an error about the project_save.tmx file that did not exist. Now OmegaT is supposed to create this file automatically.

Navigating to selected fuzzy matches

If you want to jump to the segment that displays in the Fuzzy Matches pane, you can do so by right-clicking it and selecting Go To Source Segment. OmegaT now also makes it possible to do the same through the Go To menu. Simply select the fuzzy match and click Source of Selected Match.

File names displaying for search results

OmegaT now conveniently displays file names for each search result. All you need to do is enable the file names checkbox in the Text Search window.

If this blog helped you in some way, please share a link to this post on your site or through social media.


Video: Better QA and Access to EU Terminology in OmegaT (OmegaT 3.1.2 Review)

March 7th, 2015, Roman Mironov

I know this is a review of an old version, but better late than never!

Join me for another video review of OmegaT—this time it is my pleasure to review most of enhancements introduced in version 3.1.2.

Notes from orphan segments and external TMXs display in search.

Previously, OmegaT could find segments with notes from TMXs placed in the tm subfolder of the project, but it did not display the actual text of notes. Now, it displays this text right below the target part, preceded by the equal sign. And it does the same for orphan segments.

Aggregation of search results

Similarly to the Fuzzy Matches pane, the Text Search window now displays several identical results as one and also shows the number of other results that are not displayed. This makes it much easier to use.

Alternative progress bar

You can now click the progress bar in the lower right corner to switch to the alternative one that shows the percentage of translated text and the number of words left for the current file and the entire project.

Sortable errors in QA output

The main QA script now displays the errors sorted by error type by default, making it easier to check errors efficiently.

Spelling errors included in QA output

Instead of running both the QA script and the spellcheck script when you finalize the project, you can now run just the QA script, because it will include spelling errors as well.

Stripping tags only in selection

Kos Ivantsov improved the “Strip tags” script by making it delete tags in the selected text only, provided some target text is selected.

Connector to TaaS

OmegaT now includes the ability to connect to the EU termbase project. You can download the glossaries (collections) for the project’s language combination to the glossary subfolder of the project or access the termbase in real-time. While public collections are freely available, access to private ones requires an API key that you can get on the API key page.

Enhanced auto-completer

In addition to inserting suggestions by hitting Enter, you can do the same by double-clicking.

OmegaT detects the type of repository automatically in team projects.

No need to select between Git or SVN anymore.

Two labels in the Text Search window renamed for clarity

Number of matching segments and Display all matching segments instead of Number of results and Display all results, respectively.

Word bug fix

In the past, OmegaT failed to include the text placed before leading tags in target files. This bug is fixed in the latest version, allowing you to rearrange the text with regard to leading tags as necessary.

If this article and video were of value to you, please support this blog by posting a link to it on your site or social media (the sharing buttons are below this post).


Video: Less Dreadful Scripting in OmegaT 3.1.0

October 10th, 2014, Roman Mironov

Version 3.1.0 of OmegaT has seen massive improvements in the area of scripts. This video explains the most important enhancements.

Saving window position and size in preferences

OmegaT now keeps the Scripting window position and size in the preferences file, so that every time you open this window, you do not have to resize or move it all over again.

New location for the Run button

The Run button now displays in the lower left corner of the Scripting window, which makes it easier to access. Remember also that you can press it using the Alt+R hotkey.

User-friendly script names

The scripts now support user-friendly names that display in the script list instead of the file names. Most standard scripts already have names configured. To add names to other scripts, you can do the following:

Add a line to the beginning of a script. /* :name=QA – Check Rules     :description=The rules are based on the Checkmate Quality check
Сreate a file that has the same name as the script, but properties extension. In this file, you need to provide values for name and description. name=Convert XLIFF to TMX
description=Converts translated XLIFFs into translation memories

Script localization

You can also create a file script_name_[language].properties which will have the localized name and description for that language. For example, this localization file includes the name and description that will display in the Japanese version of OmegaT.

File name Contents Localized name and description for the Japanese language

Real-time monitoring

OmegaT now monitors the scripts folder for changes in real time. If you make any changes to any script, the script list updates automatically without having to press F5.

To make sure you do not miss future videos about the latest functions added to OmegaT, subscribe to our YouTube channel about OmegaT.

If this blog post was of help to you, please share a link to it on your site or social media.

  • RSS

    Subscribe by E-mail

  • © 2005-2015 Velior

    Contact Us


    +7 (962) 155-89-07