GET A FREE CONSULTATION OR SAMPLE TO GET YOUR PROJECT GOING.

Yes, I want my consultaion

Getting Started with OmegaT in No Time

A common user feedback about  OmegaT is that it’s difficult to set up properly when you’re just getting started. Indeed, the out-of-the box version doesn’t include all the features you’ll need if you’re going to use it professionally—you’ll need to download and add them one at a time from different web pages. Also, OmegaT provides many settings, and it’s no wonder that a user who is new to the program may have a hard time configuring them for top performance.

An easy way to avoid the hassle of setting up and configuring OmegaT is to get someone else’s version, which already includes all necessary features and settings. One option is to use our version that to get started with OmegaT quickly. It is based on our five years of working with the program on a day-to-day basis. By using our version, you can save at least two hours you’d otherwise spend on tuning OmegaT for peak performance yourself. Please note that this version is for Windows.

What’s included

We maintain the latest version, i.e., as soon as a new version of any feature is made available, we include it in our version.

Settings

We include all settings we find optimal with our version of OmegaT. This can make things easier for a user new to OmegaT, because understanding which settings are best for you can take weeks or months. To avoid the additional step of copying the settings manually after downloading, we keep them in the config subfolder of the program folder, rather than the default folder, c:/Users/username/AppData/Roaming/OmegaT  (you can open it easily by searching for %APPDATA%). As soon as you download the program, you can immediately run it with all proper settings.

Configuration file

We also include a customized configuration file, OmegaT.l4J.ini, which is where OmegaT gets its configuration when you run OmegaT.exe. Using this file allows to configure a few important settings:

  • Location of config subfolder (As mentioned above, it’s located directly in the program folder, rather than in Roaming.)
  • RAM size available to the program
  • User interface language (English)

Java Runtime Environment

Java is required to run OmegaT. Uur version uses the 64-bit JRE located in the jre subfolder. If you are using 32-bit Windows, do not download our version.

RAM Size

If you have 4 GB RAM or less, you need to reduce the amount of RAM available to OmegaT. Open the OmegaT.l4J.ini in the root folder and make a change similar to the one listed below:

RAM Suggested setting
4 GB or less -Xmx3000M

Generally, you do not want to assign too much RAM to OmegaT, because there might be not enough RAM left for running other software. So it is always a balancing act—feel free to experiment.

How to download and run our version

  1. Download OmegaT using this link: https://yadi.sk/d/kgpeoPT43YR6tH.
  2. Extract the ZIP archive to C:\OmegaT\. (This is important, because the paths of the spelling dictionaries (C:\OmegaT\dictionaries) and scripts (C:\OmegaT\scripts) depend on this folder. If you use a different folder for OmegaT , change these paths for these features to work.)
  3. Run OmegaT.exe.

Summary

If you are new to OmegaT, the task of setting up the program with all necessary components and optimal configuration can be a challenge. By downloading and using our version, which includes everything you need to get started, you can save at least a couple of hours and also avoid working with suboptimal configuration. We will also be happy to provide you with basic OmegaT support if you post a comment here or drop us an email at info@velior.ru.

16 comments

  • I added a few very useful scripts provided by Masao Kasuya and Yu Tang in OmegaT’s Yahoo Group. These scripts allow you to:
    open a project folder
    open a tm folder
    open a project glosary
    open project_save.tmx
    You can find these scripts in the Tools menu.

  • Having a tool that automatically translates between a variety of different languages is fantastic. Also having a blog such as this that helps with a quick and easy setup means everyone can benefit from this tool.

  • Tom says:

    Roman,
    Your already set-up version of omegaT available at
    http://www.velior.ru/blog/en/2012/09/24/free-translation-program-omegat-fully-configured-and-ready-to-use/
    was very helpful, particularly the plugins, when I used it on my PC. However, recently I moved to an imac. Do you have a similar already set-up version that I can download to my imac? I hope so.
    Thank you.
    Regards,
    Tom

    • Roman Mironov says:

      Hello Tom,

      Thank you very much for commenting and kind words. No, I don’t have a Mac version available. In theory, the OmegaT files for different platforms are pretty much the same, so our version should require very little adjustment for using on Mac.

      Best regards,
      Roman

  • Susan Welsh says:

    Using your download, I was having strange problems with a new German-English glossary. I had made it from a PDF, saving it as text directly from Adobe Reader, then as .utf8, and fixing up the tab format in Notepad2 (i.e., putting tabs between source and target terms, instead of returns). OmegaT could not read it. Upon closer inspection (view => white spaces) , it seems the “tabs” I put in manually were not actually tabs, but double spaces. I fixed those. It still didn’t work, although my old glossaries work.
    Then I downloaded OmegaT 3.0.7 (with the Java fix) from sourceforge, and now it is working. I copied your plugins and scripting folders into it.
    This is all very baffling, but there you have it.
    By the way, it would be useful if your download link specified the OmegaT build number.

    Best regards,
    Susan

    Susan

    • Hello Susan,
      Thank you for your bug report. I cannot reproduce it, though. I downloaded our version and then added your file as a glossary to a project, as well as renamed this file to “glossary.utf8” and put it into the source subfolder. Both the source file and the glossary worked as expected. Right now, I am not sure whether the problem is coming from. As to the build number, I will work on it.
      Best regards,
      Roman

  • Constantine says:

    Hello Roman,
    first of all, I would like to congratulate and thank you on your great and very useful blog.
    I have read almost all your postings since I discovered your Blog and I am very grateful for the information I found here.
    I have one request though. Could you please post a package with all your settings for a Linux setup?
    I downloaded the above package and tried it in a Windows environment but I am curious to see how YOU would (or already have made) make the setup on a Linux system.
    Of course I tried to imitate the windows setup on my Linux desktop, but I am not 100% sure I didn’t miss or oversee something. I hate the feeling of not being absolute sure I have a(n) (almost) perfect working system 😉
    I am eagerly looking forward hearing from you,

    Best Regards
    Constantine

    • Hello Constantine,

      Thank you very much for reading.

      Since I do not use OmegaT under Linux, I cannot offer a Linux-specific version. Anyway, this is how I would proceed in your case:

      1. Download and run the generic version of OmegaT (http://sourceforge.net/projects/omegat/files/OmegaT%20-%20Latest/OmegaT%203.0.8%20update%205/OmegaT_3.0.8_05_Beta_Linux.tar.bz2/download).

      2. Replace the contents of default configuration folder (in your user folder) with the contents of the configuration folder from our version (called “config”). You may even want to experiment and (1) copy the file OmegaT.l4J.ini and the “config” folder from our version to the installation folder of OmegaT and run the program to see whether OmegaT uses OmegaT.l4J.ini under Linux as it does under Windows. If it does, OmegaT will use our settings from the “config” folder.

      Please let me know if this helps.

      Best wishes,
      Roman

  • Constantine says:

    Hello Roman,

    thank you very much for your immediate response.
    I already was experimenting with the latest version of OmegaT.
    The “OmegaT.l4J.ini” is not the file that carries your settings, it is “omegat.prefs”.
    So, I just copied all your directories and files to their respective place under “/opt/omegat” (the default directory of the Linux installer) and then I used your “omegat.prefs” replacing the Windows directories with the correct Linux directories.
    Later today I am going to make a test run to see if everything works like within your Windows package.
    One bug (if I may call it so) that I noticed after starting OmegaT, is that when I check a menu-item, it is not readable anymore.
    Obviously, after checking a menu-item, the font color is being inverted to white. So I have to look for the place where I can change this behavior. Or better said where I can control the font colors.
    Once again, thank you for everything Roman, I know I already became a fan of your blog and I will keep visiting it frequently.

    Best Regards
    Constantine

  • Michéle says:

    Hi,
    I downloaded your version of OmegaT because I had problems installing the plugins. All seems to work fine, but can you please tell me how to get rid of the strange linen-like background? Is there any way to configure this or at least a workaround? I actually liked the grey background of the original one, but I wouldn’t mind if it’s just white.

    Anyway, thanks for provoding your version

    • Hi Michéle,

      Thank you for your interest in our version. To remove the linen-like background, you need to delete the subfolder
      config\plugins\Moenizer\

      This is a plugin written by Yu Tang that uses a JPG file as a background in OmegaT. Some people find the original white background too hard on the eyes, hence the desire to use something more neutral.

      Best wishes,
      Roman

  • Maribel says:

    Hi Roman,

    I was working on a previous version of Omega T, then I downloaded the newest version and today I just added your link with the download. I was working fine on my project until I tried to access the translated document. I keep getting a message saying that it cannot open the document because the program found a problem with its contents. I am in panic since I cannot have access to the translated version. Could you please help me to figure out what is going on and more importantly, to fix it? Thanks in advance and best regards,

    Maribel

    • Roman Mironov says:

      Hi Maribel,

      Sounds like you deleted one or more tags. Make sure to run tag validation before creating translated documents. (We also check tags in Verifika to be on the safe side.)

      Best wishes,
      Roman

Add comment


About the Author

Roman Mironov
Roman Mironov
CEO & Founder

As the founder of Velior, Roman has had the privilege of being able to turn his passion for languages into a business. He has over 15 years of experience in the translation industry. Roman has helped dozens of clients increase sales by making their products appealing for speakers of other languages.