CafeTran Espresso 2019 Forerunner

It is time to start rolling out the Forerunner (aka Preview) version of CafeTran Espresso 2019. This update and the subsequent builds this year will make up the CTE 2019 version to be released in December/January.

The update can be performed via Drag and Drop as follows:

1. Run CafeTran.

2. Download file from here and place it on your desktop. Do not unzip or rename the file after downloading.

Note:   On Mac OSX system, Safari web browser may unzip the file automatically after downloading it. Before you download the update file, uncheck the  following Safari option:

Safari > Preferences > General > Open "safe" files after downloading.

3. Drag and Drop the downloaded file anywhere in CafeTran's initial screen - the Dashboard.

Alternatively, you can install file via the "Install Update" button in the Help > About panel instead of dragging and dropping.

Important! Please complete all your translation projects in your current CafeTran version before updating.

What's new in this update:

  • Autopilot. This may be a very handy feature during the Review or QA phase of translation. You can also use it when translating short, repetitive/similar phrases or numbers. It allows hands-free navigation with the set delay between the segments. The default delay of 2000 milliseconds (2 seconds) can be increased in Edit > Preferences > General tab. Activation/deactivation of the Autopilot is done via the Action menu. After that, you will notice the Autopilot button in the target segment editor. Click this button to turn on/off the Autopilot. Going to the next segment triggers off its functioning. To suspend it for a while (e.g for the correction of the current segment), press the Esc key or click the mouse on the target segment editor.
  • Automatic transfer of numbers being the full segments which end with the white space character.
  • Recognition of language variants in SDLTB termbases.
  • Support for subtitles (.itt and .srt file formats).
  • Added video resource preview for translation of subtitles.



3 people like this

Than we could go a bit further: adding voice capabilities so that CT reads out the text for you. 

Vocal reading is considered the best proofing method, and combined with the Autopilot would make CT stand out even more from the competition, besides transforming itself in the never-look-back CAT tool for me if only an improved project management system were adopted. 

I know Macs have a native reading capability which could perhaps be used directly with CT; Windows too has it although for Word only, while I know nothing about Linux. By the way, can CT work with Dragon Speaking?

1 person likes this

adding voice capabilities

IMHO quite difficult, perhaps to resolve via interfaces the three OSs offer (Linux?). Perhaps there is a Java solution for this.

But it is – from the point of view of voice quality – really usable?

Tre: But it is – from the point of view of voice quality – really usable?

In my opinion, it is. Word's synthesized voice is very good. I use regularly the Italian and the Japanese voices and despite some minor errors they help a lot finding small errors, which you may easily miss when only reading on screen or on paper.Voice quality doesn't need to be perfect.

Just more more point.

When restarting CT, the Autopilot should be deactivated by default (for heavy AP users – if any – this could perhaps be overruled by a point in the Preferences).

Love the "new" Autopilot functionality. However, it seems to be delayed for me by one segment (on Mac). When I activate it and move to the next segment, auto assembling and TM don't kick off and when the Autopilot moves to the next segment, auto assembling and TM show the results for the previous segment. 

Any idea how to solve this? :)

  • Faster internet connection
  • More RAM for CT

However this shows that Autopilot should perhaps only be used in certain scenarios (e.g. after all segments translated).

PS: This might be easier to handle if there was a state "edited" for segments as in many other tools … 

It doesn't have anything to do with my setup. Working on a MacBook Pro 15 (2017) with a 120 Mbit cable connection. CafeTran itself runs as smoothly as ever. It's not a random delay caused by a lack of speed, the functionalities kick in virtually instantly when the autopilot changes segments, it's just off by one segment.

> it's just off by one segment

Yes, this is confirmed and being fixed for the next build soon. Stay tuned. Thanks.

Perfect. Thanks for getting back to me so soon.

Another thing I have noticed, not just in this build: if you work with a bigger font (say. 25) in the segment editor, die two dots of capitalized Umlaute Ä, Ö, Ü stick to their position in the line even if the word itself is moved by adding/deleting parts of the sentence. Not a big deal but confusing at times :)

> Another thing...

Did you try changing the font via the View > Font menu? Is it on Mac, Linux or Windows?

Sorry for the lack of information. It is on Mac, I changed the font via VIew > Font and it seems to happen for me with all font sizes from 24 upwards in Helvetica.

In Java, some font types may be displayed correctly within some size range. If you need such big fonts, try Verdana, for example. 

The new build of CTE 2019 Forerunner is available for download. It features the following major changes:

  • added an option to set the variable delay for Autopilot. The default setting in Edit > Preferences is 1000 millisecond per 10 characters in the current segment. You can adjust it as preferable.
  • fixed a search off by one segment issue with Autopilot.
  • added the menu option to turn on/off automatic searching - useful with Autopilot during the review - see it the Action menu.
  • fixed an issue with the "Transpose selection to the right".

Please download and install this new build (2018091401) as described in the announcement post above. Thank you.

Just one thing on the Autopilot function. In files that include only-number translation units, for instance "12", CT stops longer than, for instance, single-word translation units such as "Coverage". 

Perhaps number-only segments should be excluded from the Autopilot, or the stopping time calculated as if numbers were characters?

Login to post a comment