CafeTran Espresso 2017 Harbinger - Release Candidate 1



CafeTran Espresso 2017 Harbinger aka Release Candidate is available for download. The update can be performed via the Drag & Drop procedure as follows:

1. Run CafeTran.

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

Note: On Mac OSX, the Safari web browser may unzip the file automatically after downloading. To prevent this, just use the right-click menu and choose the "Download Linked File" command.


3. Drag and drop the downloaded file into the Project Dashboard and restart the program.

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

What's new:

  • A glossary can contain non-translatable fragments only - see the option when you add a new glossary.
  • Auto-completion fragments from TMs and glosssaries are sorted by their quality now.
  • Unchecking the alphabetic sorting in the Matchboard lets CafeTran sort them in the mixed mode - first by quality followed by (multiple) matches for the same source. 
  • Trimming double-spaces when transferring matches to the target segment (e.g in the Machine Translation results). 

As 2017 is around the corner, we are near the release of CafeTran Espresso 2017 version being the summary of all the improvements and fixes done this year. The update is the first release candidate. If you notice any issues, please submit a support ticket and report. Thank you!

Enjoy your week,


2 people like this

Wow, thanks. great info... over Christmas I'm going to have to read the whole KB and learn how to use this CAT properly!


I've found a very very bad thing:


 In this example, the matched source term is "安全," which is the third entry in the glossary, but MatchBar shows the first entry "担保," which does not exist in the source. I've never seen this kind of inaccuracy in any other CAT tools. Please fix this.

Could this be because CT thinks you're looking for a segment number that's way higher than the number of segments in the project?

That's probably it. However, it should display "Segment number not found" message instead of the Export dialog. To be fixed in the Release Candidate 2.


I need to know a wider context and settings (e.g. prefix matching?) to understand your image. Can you submit a ticket with that glossary and the exported .ctp package attached to test it? Thanks!

Login to post a comment