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

I do not know whether we need a status "autopropagated", but it would be nice to be able to filter them out (those segments with a red "p"), and especially, to have the first segment (aka "first segment that gets repeated later on") already marked.

Ah! Last but not least (and again...) Is it logical for you not having statuses autopropagated along with repetitions?
Yes, actually I'm very happy with the last update, using checked status for "Translated" makes the deal, but it has to be improved as for now we just lose other features. I think the big issue is considering "edited" segments as actual translations. If we remove this non real status calling it "Draft/edited/not confirmed/whatever" and name the "Checked" status as the real "translated" status could do the trick. We have now "Approved" that could be used in conjunction with the new "Rejected" status by proofreaders/project managers, so no need for a real "Checked" status. Does it make sense?

To say it a bit calmer and clearer:

With the last update we have 4 segment states (Translated, Checked, Approved, Rejected) after translating, but only one (Empty) before and while translating.

tre x10k! Dude I've just learnt two things from the post you pointed out that I either don't like/worry me a lot (like I'm seriously considering quit CT), a) "Virtual pretranslation"? I mean, lossing this thing between sessions is like the less convenient behaviour I've ever seen, it may work for short projects, but what about longer project? Should I redo it over and over? 臘‍♂️ b) more than 5 months to get Segment Statuses just "to keep it simple"? Dude, I can't imagine how other folks are translating but, if a segment is considered as "Translated" just when typing on it (and not edited), definitely this is not my tool, I need to draft, to go back to certain segments to make changes and so on, we could solve this using notes, but still one more manual step, NO WAY... Something else, one could thing this happens due to the use of non native projects (from Trados, for example) but actually this problem related to segment statuses is crossproject and, at the same time, from a commercial point of view, Trados is the king in terms of presence (I hate it too, right) but sometimes we just can't avoid working with their formats.

The reason for all this is that we do not have any properly differentiated status, at least a status "Edited", but in the best of cases also "Pretranslated" and "MT'ed" (with CT recognizing if a segment was simply populated with a MT short cut, without confirming, and if it was pretranslated by a MT-generated TM).

See here five months ago (and Michael Beijer already asked for the same thing). Only very few tools have such a limited numbers of statuses, and if I remember correctly, it is about "to make CT not too complicated" (as if we were too stupid to differentiate a bunch of statuses). On the other hand side, this makes CT rather error-prone. You simply cannot differentiate segment statuses.

Maybe this should be posted here:

With the recent changes, we can consider 

- Empty segment = Untranslated

- Translated segment = Draft/Edited

- Checked segment = Translated/Confirmed

- Approved segment = Signed off

It would be interesting having the statuses autopropagated, as lots of us (I'm sure) would work "confirming" (aka "checking") segments on the go, this way we wouldn't need to go to repetitions already checked (translated) because they're already confirmed.

The same applies for statistics. If we work "checking" on the go, but we have machine translation propagated for edition, we get the "translated statistic" but not the "checked", which actually are the real translations, SO, could Checked segments/words/characters AND Unchecked segments/words/characters be added to the statistics view?


My statistics board became useless :(

Scenario: translating a SDLXLIFF file, with "Translated" (Checked in CT/Confirmed in memoQ 100%/101%/102%), pretranslation from 80% but not "Translated", just "Edited" (which maps the "Translated" status from CT side) and pretranslation from MT, also not confirmed (which also maps the "Translated" status from CT side). As non-"Translated" pretranslation from Trados is consider a "Translated" status in CT, the statistics don't show your real progress.



Auto-completion (prompter) should not retain phrases with a mispelled word. It won't accept a phrase beginning in such a mispelled word, but it does so in the case of typos following a correctly spelled word.

Igor, would it be possible to add an option "do not recognise misspelled words at all".



> Added "Rejected" status for proofreaders. It also maps to the similar status in sdlxliff and mqxliff files.CafeTran "Approved" status maps the similar status in in sdlxliff files and mqxliff files now.CafeTran "Checked" status maps to the Translated status in sdlxliff files and the Confirmed status in mqxliff files now.

Dude, the solution to my WHOLE problem translating trados files was just as simple as reverse Approved and Checked statuses just the way you did, HUGE THANKS Igor, this is really convenient for people not working with CT native projects.

Just to make it perfect, we should have "Checked status autopropagation", i.e. autopropagation of the Checked status througout repetitions (with an option to enable/disable autopropagation of individual segments, as we already have for segments).


> Options to turn off the automatic case adjustment and overwriting during auto-completion - see the new Prompter tab in Preferences.

This is a very good thing. Thanks!

The new build (2018103001) of CafeTran Forerunner 2019 is available for download. It adds the following:

  • Options to turn off the automatic case adjustment and overwriting during auto-completion - see the new Prompter tab in Preferences.
  • Added "Rejected" status for proofreaders. It also maps to the similar status in sdlxliff and mqxliff files.
  • CafeTran "Approved" status maps the similar status in in sdlxliff files and mqxliff files now.
  • CafeTran "Checked" status maps to the Translated status in sdlxliff files and the Confirmed status in mqxliff files now.

Please complete your unfinished projects before updating. You can repeat the update as described in the first (announcement) post. Thank you!

3 people like this

After the latest update of CT (this edition), it seems that Autocmpletion has been case-sensitive and also overwriting the immedially following character.

1. Case-sensitive
Example: If the glossary has a term "ABC Company," when I type "AB," the inserted term is:

2. Overwritnig (or possibly a space appended)
Example (same as above): When I type "AB" immediately before another word (e.g. "will"), the result is:

Is there any way I can avoid these?

1 person likes this

Many thanks for the bunch of changes, which seem all to work properly.

It looks like you interrupt the selection of the file and change the focus. Please complete the action (file selection) before switching to other things. Otherwise, CTE (or rather Java in this case) brings back the parent dialog into the main focus, which is the Preferences panel).

Thanks for bringing the Import and Export of Preferences back.

On my Mac, the file selector disappears behind the Preferences dialogue box. It's a little difficult to click the Save button, since the file selector constantly jumps to the background.

Login to post a comment