[Please note that some of the entries are very old.*]
Showing posts with label Java. Show all posts
Showing posts with label Java. Show all posts

Tuesday, 3 July 2012

CafeTran July Update

It's just about impossible to keep up with Igor's updates, and usually, I don't. I mention them in "Latest" (top right of this page), and that's it.

The July update requires  some more attention, I think.

In earlier versions, CafeTran's spell-checker - Hunspell - required running OpenOffice, LibreOffice, or NeoOffice for "check spelling while typing". Those office suites opened automatically when you started CT. No problem. The only restriction was, that you couldn't increase the RAM assigned to Java to more than 2 GB (unless you run the suite under a Linux distro, the only version in 64 bit so far). So in the case of very large TMs, you had to choose: Either use the spell-checker and limit the RAM to 2 GB, or increase the the RAM an do without spell checking while you type. This latest update changes that. Spell-checking now works independently from an office suite, so you can have your cake and eat it too.
Please pay attention to the following:
The path to install the dictionaries is a bit longer than you may think it is. You should install in the "resources" rather than the "Resources" folder.

Click to enlarge

Please check here if your dictionary is available. The list is quite long, and you would think most languages are covered, but Turkish turned out to be left out. Very strange, it's not exactly a minority language (see UPDATE below).

Other improvements:
  • Set priorities for multiple TMs, both for TMX files and tab delimited glossaries.
  • Save tags in the TM. Extremely useful. The tags in the TM won't interfere with matches in case the source segment does not contain tags. Wonderful.
  • Typing a tag number after a number. Minor problem solved.
  • Go to the last edited segment in a TTX project. Solved.
  • Add fields (like subject, client, etc.) to glossaries made possible (useless, I think, but if you are that way inclined, go ahead).
  • The language codes in TMs are no longer case sensitive. This makes life a lot easier when you import TMs.
  • Autocompletion (AutoWrite) hints for two words.


"Every disadvantage has its advantage", Johan Cruijff used to say. This renders quite a few blog entries completely and utterly useless (thank you, Igor…).

UPDATE: Igor already solved the "Turkish problem".
After renaming both files from tr to tr_TR, now spell check works, says Selcuk (and I'm strongly inclined to believe him). Turkish users can download Hunspell dictionaries here.



Tuesday, 5 June 2012

Large TMs


Big TMs can slow you down considerably. To speed up the process, you can do the following:
  • Check the language codes of the TM, and see to it that they are in the right format.
Click to enlarge
  • Increase the RAM assigned to Java in Edit | Options | Memory. The default is 1 GB. If you set it to 4 GB or more, Mac users (I don't know about Windows and Linux) will also have to change the preferences in the Java app. Go to your Application folder | Utilities, right-click Java Preferences, Show Package Contents, MacOS, Java Preferences, and set 64-bit as first choice. Drawback: Check spelling as you type won't work anymore, since the open office apps are still 32-bit (though there is a 64-bit version for Linux that may solve this for Linux users). Igor will implement a spell check solution that doesn't depend on the various open office suites this summer.
  • Set your TM to "Read Only". Drawback: No new segments will be added. You can solve this problem easily by using a ProjectTM that you merge with the Fat One after finishing your translation.
  • Switch to the "Pretranslation" mode from the default "Automatic" in Memory Setting in Project Info and check the Translation in Review box. When you start the translation, you will se a progress bar that indicates the background pretranslation. There's no need to wait till the pretranslation is ready, just start working. No procrastination allowed!
  • In the Project Info, change the Matching Type field from "Fuzzy and Subsegment" to "Fuzzy". Drawback (if there is one): The statistical function of subsegment matching won't work (but fuzzy and exact phrase matching still works).

It's probably a good idea to play with these solutions to find out which combination of the above works optimally for your big TM.