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:
tre: Indeed LT can perform differently well in different languages. And: How did you use it? There are several ways to implement it.
I didn't know that there are several ways to implement it; I will have a new look at it tomorrow. I just opened the resource as offered by CT and tried the non-premium version with a well written, rather long Italian sentence, and it "found" three or four places that needed improvement such as article repetition, which the so-so Office proofing tool correctly didn't spot. Therefore, for what I saw today, it's checking mechamism seemed a bit too simplistic to me. But, again, I will be more precise tomorrow.
> > always renders...
>Well, then you must be right.
This is not the point. It seems there is a lack of experience with CheckMate to see how useful it can be in combination with LT, only using its API and a LT server instance (also a question of privacy and NDAs - using the web interface vs. using a local server instance). Why then isn't this possible with CT?
Indeed LT can perform differently well in different languages. And: How did you use it? There are several ways to implement it.
Out of curiosity, I tried LT and—at least in may target language (Italian)—I found it to be an impressive way to slow down the translation process given the number of false errors it outputs. A junior high school student would do a better work, me think.
> always renders...
Well, then you must be right.
> I am pretty sure
I would be quite unsure when guessing user habits. As you see every day, they can be quite different.
> would produce lots of false QA grammar errors
Well, CheckMate, another, but external resource, always renders a reasonable and rather correct number of errors with LT enabled (they are limited to grammar, not spelling). I cannot reproduce this statement.
> Perhaps some day, there will be a full QA for LT, that can be performed in the project review stage.
LanguageTool is especially useful when you check target segments now and then (e.g when in doubt). I am pretty sure that checking each and every segment (as in the full QA run) would produce lots of false QA grammar errors - especially in technical translations, which would render it rather counterproductive in such an integration.
>The Translate and Transfer buttons for querying and transferring MT web results work for this QA web resource as well.
IMHO, this button label is no longer valid here. There is no 'translation' taking part. It's the transfer of target segment to the checker. So perhaps 'Transfer' would be a more generic label?
(I'm aware that there's already a Transfer button in the MT panes. If that's misleading, perhaps change to 'Transfer back'? or another wording. Insert MT suggestion? Transfer MT suggestion.
On a side note: I'll probably not use this on the fly implementation of LT. When I'm translating, I want to move forward quickly. No time to check 4 or 5 different panes for any QA info.
I realise that this is a matter of personal preference.
Perhaps some day, there will be a full QA for LT, that can be performed in the project review stage.
Thanks. I've set it to Dutch (Nederlands) now*). LT's description is wrong: Dutch 'gedetecteerd' (actually it hasn't been detected/identified: it has been manually set):
There is no way for you to limit the display to LT's white field? Ignoring all distracting info.
*) I've set the Dutch language here:
> How do you set the target language for LanguageTool?
LanguageTool web resource detects the language automatically - see auto-detect option in its interface. If not, please just select your target language there.
> the right-hand ALT key disables all ALT+arrow keyboard shortcuts.
Until Java developers improve this ALT shortcut, please use the left-hand ALT key on your Mac if you make use of ALT+arrow word navigation.
How do you set the target language for LanguageTool?
For all Mac users: note that this build does not solve the issue where using the right-hand ALT key disables all ALT+arrow keyboard shortcuts.
The update 2019010501 of CafeTran 2019 Forerunner is available with the following:
- added LanguageTool as a Web resource (see it the menu Resources > Web). The Translate and Transfer buttons for querying and transferring MT web results work for this QA web resource as well.
- added support for Java 12 (to be released in March). The early access (ea) of this new Java version fixes an issue on MacOS Mojave with the insertion of accented characters via Mac pop-up characters window. If you insert the accented characters through this method on your Mac, you need to update CafeTan by downloading and installing again to have this issue fixed. Otherwise, there is no need to reinstall the program, which works with the current Java 11.
Please download and apply the update file as described in the first announcement post to this thread.
Happy New Year!
Aha, just meant the CafeTran theme I'm using (GTK look and feel with the Bright Theme and no background grid/transparency).