Download Omegat
Hiko Meckler
If the error is java.lang.NoSuchMethodError: org.omegat.filters2.FilterContext.getProjectProperties()Lorg/omegat/core/data/ProjectProperties; then you are using an older version of this plugin with a newer version of OmegaT (see #Requirements). Update your plugin.
Like any other OmegaT project (multi-user or local), it consists of an `omegat.project` file containing the project settings, an `omegat/` folder containing, among other things, the translation memory in `TMX` format, which is shared for reading and writing, and a `glossary/` folder containing, among other things, the glossary in `TSV` format (encoded in `UTF-8`), which is also shared for reading and writing.
It will now display the list of files in the project. Note that the source files within the project are not hosted on the corresponding file management repository site, but rather in a separate repository which is set up in the `omegat.project` file described above:
To understand the use of translation memories in OmegaT, it is important to talk about them. First, OmegaT creates one translation memory per project by default. The user never needs to create a memory and associate it with a project. An OmegaT project is a translation memory, which is at the heart of the project. It is fueled by the translator's work and, in multi-user mode, by the synchronized translations of other project members. As mentioned above, it is also located in the `omegat/` folder:
An OmegaT project is a files' hierarchy in which there is, at the same level of `omegat/`, `source/`, `glossary/`, a `tm/` folder which aims at receiving reference memories (generally in `TMX`, but also in other bilingual formats supported by OmegaT: `XLIFF`, `PO`, etc.).
The fault is with the omegat shell script which tries to find out java version. The script is supposed to start the program only if it finds an openjdk or a sun java implementation on the machine. For this, it tries to look at the path where java is installed using below line:
From the link: The solution is easy: in /usr/bin/omegat, the bash script tests java version and checks if it's openjdk or sun. Replace 'sun' by 'oracle' and it works. The author of the question has Oracle Java, not openjdk-6-jdk or openjdk-7-jdk, installed so this solution should also work for him.
Remember that under the project directory (GuideTrans in our case) you have several sub-directories that you can access: dictionary, glossary, source and target and translation memory. There is also several .tmx files (translation memory files) under the omegat directory. Again, do not hesitate to read the OmegaT documentation to go further with this helpful tool.
Download apertium-omegat.jar from [1] and copy it to the plugins/ directory of your OmegaT installation. The folder in question is the folder that contains the OmegaT.jar file, for the Mac version this is e.g. the /Applications/OmegaT_3/OmegaT.app/Contents/MacOS/Java/ directory.
Caution! Up to version 2.6.1, only the /omegat/project-save.tmx file, the one that contains the translated elements, is versioned (synchronized). Starting from version 2.6.1_2, the project glossary is also versioned, usually/glossary/glossary.txt`. That means that any changes to other files in the project, such as changes to segmentation or source files, are not automatically detected by OmegaT. However, since the whole project is uploaded on the SVN server, you can always do the checkout and manually synchronize using an SVN client (provided that OmegaT is not active during these operations, in order to avoid conflicts).
760c119bf3