OmegaT: Customizing Options for Okapi Filters


February 4th, 2014, Roman Mironov

The Okapi Filters plugin makes it possible for OmegaT to use the Okapi filters. This has two advantages:

  1. Some of the filters included in the plugin, such as XLF and TXML, are different from the native OmegaT filters and can therefore be used where the native ones are less effective.
  2. The plugin has filters for important file formats not supported by OmegaT natively, such as TTX and IDML.

Until recently, users could not configure the Okapi filters to use with OmegaT, although these did have configurable options. On November 10, Okapi developer Yves Savourel announced that customizing these options had been made possible. This post explains how to do this and provides an example.

Step-by-step procedure

  1. Download the latest version of the Okapi Filters plugin and put it into OmegaT’s plugins folder.
  2. Open Rainbow and select Tools => Filter Configurations.
  3. In the Folder field, select the folder to save your custom configuration.
  4. Select the desired filter, for example IDML (okf_idml).
  5. Click Create.
  6. Change the configuration’s name, for example to “copy-of-default-IDML.”
  7. Change the options as desired. For instance, enable the Create new text units on hard returns checkbox.
  8. Click OK. Rainbow will save the file to the selected folder under “copy-of-default-IDML.fprm”
  9. In OmegaT, open the File Filters settings (global or project-specific ones, depending on what you are using). I recommend using project-specific file filters; in this case, go to Project => Properties => File Filters.
  10. Select the appropriate filter. In our example, this is going to be InDesign IDML files (Okapi).
  11. Click Options.
  12. Enable the Use the following filter parameters file checkbox and select the file that you created.
  13. Click OK until you get back to the Editor, and reload the project. The new options will apply.
  14. If you need to change the options in your custom FPRM file, you need to do that from Rainbow again. After changing the custom file, you do not need to change anything in OmegaT, since the plugin will re-read the custom file upon the next reload.
  15. Note that all custom FPRM files need to be within the same folder.

Example: Customizing the IDML filter

By default, this filter does not segment text on hard returns, resulting in multiple occurrences of sentences packed into one segment. But the filter does allow configuring this option, although it is still in beta. Simply enable the checkbox in your custom file. Below is a comparison of two files segmented with this option disabled and enabled. The custom file (with this option enabled) results in many more segments, which is beneficial for translation.Comparison of Create new text units on hard returns enabled and disabled

Tags: ,

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

  • RSS

    Subscribe by E-mail

  • © 2005-2014 Velior

    Contact Us

    Phone

    +7 (962) 155-89-07
    +7 (4932) 23-87-23

    info@velior.ru
    velior@list.ru