Difference between revisions of "Apertium OmegaT Native"

From Apertium
Jump to navigation Jump to search
m
(Corrected installation path to a working location that won't break the signature of the signed app.)
Line 9: Line 9:
 
* '''Copy''' the file to the OmegT plugins folder, which
 
* '''Copy''' the file to the OmegT plugins folder, which
 
** on '''Windows''' is here: <code>C:\Program Files (x86)\OmegaT\plugins</code>
 
** on '''Windows''' is here: <code>C:\Program Files (x86)\OmegaT\plugins</code>
** on '''macOS''' is here: <code>/Applications/OmegaT.app/Contents/Java/plugins</code>
+
** on '''macOS''' is here: <code>~/Library/Preferences/OmegaT/plugins</code> (create the dir if it's not there)
   
 
== Using OmegaT with Apertium ==
 
== Using OmegaT with Apertium ==

Revision as of 12:07, 13 March 2017

Tested on OmegaT 4.1.0 on Windows and macOS with latest Java 8.

Install OmegaT

Install the Apertium plug-in (Needed for machine translation)

  • Download this file: apertium-omegat-native.jar (the same file for Windows and Mac)
  • Copy the file to the OmegT plugins folder, which
    • on Windows is here: C:\Program Files (x86)\OmegaT\plugins
    • on macOS is here: ~/Library/Preferences/OmegaT/plugins (create the dir if it's not there)

Using OmegaT with Apertium

  1. From the Options menu, select Apertium Native (nightly).... From the popup, click Install on the language pair you want to install.
  2. From the Options menu, select Machine Translate, and enable Apertium Native (nightly).
  3. Then make a translation project (= a folder for your files) via the Project > New menu.
  4. At this point, you should be adviced to read the OmegaT documentation (yes, it helps)

Source

Known Bugs

  • Windows: apertium-transfer has issues with UTF-8 streams. Will be fixed. Fixed as of Apertium r74180.
  • Mac: The Install Language Pairs window under Options > Apertium Native (Nightly) is too small, * the rightmost boxes on each line are not visible. On Windows, the size is right.
  • Mac: Different types of formatting marks show up as <f0/>, <t1/> and similar tags, and the give rise to Error: Input is empty - nothing to parse! in the MT window .This happens when the original has e.g. hyperlinks or non-ascii letters.