How can we help you today?

Discussions CafeTran Forums CafeTran News

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
230 CommentsSorted by Oldest First

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.



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.

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.

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?
Ah! Last but not least (and again...) Is it logical for you not having statuses autopropagated along with repetitions?

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.

Oh yes, indeed! I forgot those: "autopropagated", "MT'ed" and "pretranslated", the latter along with its matching %. I don't know how hard would be coding this, but I remember when collaborating with OmegaT, the Devs used to say the statuses were impossible (then) because they where just not supported by TMX file (the one used by OmegaT instead of xliff). Also, correct me if I'm wrong, does this little red "P" stay between sessions when working with non native projects?

Could there be some more finetuning for the new upper/lower case AC feature.


When typing MAss (second letter uppercase by mistake), AC completes to MAssACHUSETTS.


Could there please be an AC to Massachusetts or MASSACHUSETTS only (assuming that a mix a upper/lower case is not very probable and only accepting it when already present in TM/target segments/TB)?

IMHO "autocompletion in the middle of words" is one of the best features added in the last monhs.


However it still has some really important flaws.

  • When used with composite words (yeah, German!) it deletes the rest of the following word. This is not always desired (e.g. when changing undercapacity to overcapacity (having marked the first five letters "under"), AC proposes "over" first and then deletes the rest of the word ("capacity").
  • Same with following commas or closing parenthesis. They are simply overwritten/deleted. This is even worse.
  • Same with following words (sometimes), this should not happen at all. The last two cases can perhaps be seen in conjunction with the first one – CT does not recognize spaces, commas or parenthesis as word limits. 
Or do I need to make a certain setting to stop this overwrite mode?

1 person likes this

> Or do I need to make a certain setting to stop this overwrite mode?


Sure, please turn it off in Preferences > Prompter tab.


1 person likes this

> Sure, please turn it off in Preferences > Prompter tab.


Uh, I did not have the last edition installed. Perhaps this should be deactivated by default. 


Or at least consider commas, full stops and parenthesis as not part of a word, to avoid their deletion (this would perhaps also be a plus for all these frog legs eaters that do not have composite words). 

>> Sure, please turn it off in Preferences > Prompter tab.

>Uh, I did not have the last edition installed. Perhaps this should be deactivated by default. 


I agree. The current default behaviour has annoyed me too, this week. 


image




The new update (2018110201) of CafeTran 2019 Forerunner has been made available for download with the following changes:

  • Statistics for checked, rejected and approved segments.
  • Removing the two-word (typed) phrase from the Prompter if one of the words is a spelling mistake.
  • Some improvements to Ms Excel filter.
  • Added the "es" language code (neutral - without a country variant) for Spanish spoken in the US.
  • Keeping the punctuation character when replacing a word during auto-completion.
  • Option to propagate the current segment status during auto-propagation.


As there are changes to the Ms Excel filter, please complete any unfinished Ms Excel projects before updating.


Thank you,

Igor

2 people like this

Just out of curiosity. What changes are there to the MS Excel filter? Sometimes it did not work for me, when I wanted to do “Bilingual Excel”.

Chances are that this has been fixed indeed. Sent da master such a file this week. Will Test after coffee. do widzenia
Login to post a comment
More topics in CafeTran News
See all 136 topics