Page tree

With Okapi Rainbow anyone can write custom file filters for special file formats.

For example for special XML dialects, special kind of txt-files - or to exclude for example all cells with red font color from an Excel file on import time.

When importing a zip import package into translate5, you optionally can add a bconf-file (batch configuration file) from Okapi Rainbow to it on the root level of the zip file. Then translate5 will use this bconf file for parsing your imported documents instead of the default one.

The batch configuration file is a bconf-file as exported from Okapi Rainbow. With Okapi Rainbow you can create your own custom file filters, for example for special kind of xml or txt-files.

For customizing a file filter, we recommend to start with the okapi_default_import.bconf, that you find in your translate5 installation at /application/modules/editor/Plugins/Okapi/data.

If you use the Okapi plugin for translate5, you can seamlessly use Okapi in the background to convert files on import time - and convert them back on export (without the user having to touch Okapi). Please see details on the translate5 file format page and on the translate5 Okapi Plug-in page.

Every translate5 user is invited to share her/his special filter creations below this page here. Just log in and create a sub-page to this page here.

  • No labels


  1. When I install okapi_default_import.bconf in Okapi Rainbow and export it, and reinstall it, the extensions-mapping.txt is changed, specifically .sdlxliff okf_xliff@translate5-sdl is lost. Any hint on this? 

  2. wordsmith yes. Unfortunately Okapi Rainbow defines its extension handling based on the files you have in your Okapi Rainbow file list.

    For every file extension mapping that you want to have in your exported bconf you have to have a file with this file extension in your file list and point this file to the corresponding Okapi setting you want to use for this file extention.

    Unfortunately manupulating bconf files in Rainbow is not trivial - and this only because the usability of Rainbow is very bad. Technically everything you need is there.

    The generation of bconf files directly in translate5 is currently in development.