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:
||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
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|
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:
- .ini folder with files used by OmegaT scripts written by Kos Ivantsov
- a folder for reference files
- a file for communicating queries to clients.
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:
- language combination (e.g., English to Russian translation)
- sentence or paragraph segmentation
- paths to dictionaries or glossaries
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.