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 20190105_update.zip 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 20190105-update.zip file anywhere in CafeTran's initial screen - the Dashboard.


Alternatively, you can install 20190105_update.zip 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.


Enjoy!

Igor


3 people like this

Yep. The 'bilingual import' has been fixed. Greatz!


image


>Option to propagate the current segment status during auto-propagation.


Someone will be happy here ;).


image



2 people like this

Hello,


I have just completed a project with the latest CafeTran version and I have noticed a few things that could be improved:


1. TM matches highlighted in the source segment editor seem to also highlight parts of words that contain the TM match.


So for example, if you ad "or" or "and" as a fragment, any word with these letters will have these highlighted, such as as "more" or "understand".


Is there a way to avoid this? Is it related to the latest prompter (auto-complete) improvements?


Screenshot: 


image

So, in the above example, I have "or" as a TM fragment. I don't know if this also happens with Glossaries.


2. In the target segment, even small words are cut to the other line sometimes. This makes it difficult to read.


Example:


image


Here, the word is "simplement", the t appears in the next line. This happens for small words such as "qui" Which appears as:

qu

i


This may also be related to the prompter update, and suggestions in the middle of a word.


3. Finally, there has been an issue with an Excel file export which lost paragraph marks within one cell, where I have used the split feature, but I prefer to open a ticket for this as I need to attach the project files.


Jean


1 person likes this

>  In the target segment, even small words are cut to the other line sometimes. This makes it difficult to read.


As I can't reproduce it, please submit a ticket indicating the segment number with this issue. It may be due to squeezing the editor too much.

I don't know if this also happens with Glossaries.


It does.

I'm sure I've read this somewhere, but I can't find where and I think it's an issue.


When translating from French into Spanish, the French "élision" is considered as a whole word, so termbases don't recognize it as a word (nor the QA). Example:

L’élément - L’élision - L’invention and so on are not recognized even if I record "élement", "élision", "invention". I usually use this (') as an apostrophe for French, but my project manager sends me the documents with this (’) instead (I guess it's due to Abbyy FineReader, as we work with PDFs converted into .docx files).

Read here and there (the whole thing, not only the first pages).


Short from here

The user needs to remove the curly apostrophe from the "Do not match" list in Edit > Preferences > Memory tab to have it matched. This should also work for straight ones.


1 person likes this

And just one last thing to fine tune Statuses, when a segment is "Checked", why not to "Uncheck" the segment if we type something on it after we "checked" it? This could avoid, for example, typing by mistake a checked segment and actually consider it as checked and not edited.

OFFTOPIC: isn't it AMAZING we, the users/translators, are shaping the software on the go because the developer is just here, listening all the time? This is priceless.


1 person likes this

>OFFTOPIC: isn't it AMAZING we, the users/translators, are shaping the software on the go because the developer is just here, listening all the time? This is priceless.


A) I don't think that this is off topico.


2. Yep, that's what amazed us too, years ago :).


III/. Spread the word.

Igor: Added the "es" language code (neutral - without a country variant) for Spanish spoken in the US.


Would it be possible to let the user choose whether to add the country variant to the language code upon file export? I always find myself deleting it.


Thank you

A solution is to use multiple-file projects, even for one file. The exported folder bears the language code, the contain files do not.

JeanA solution is to use multiple-file projects, even for one file. The exported folder bears the language code, the contain files do not.


This is an even better solution, thank you. I didn't know it exist at all. I'll try it out.

Hi again Jean, 


I followed your suggestion, but the file in the exported folder still has the country code. Does your CTE behave differently?

Try using Project > Export all documents, instead of "Export current document".

Login to post a comment