CafeTran Espresso 2018 Akua Update 10 is available for download. The update can be performed via Drag and Drop as follows:
1. Run CafeTran.
2. Download 20180612_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 20180612-update.zip file anywhere in CafeTran's initial screen - the Dashboard.
Alternatively, you can install 20180612_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.
The update 10 brings some new Quality Assurance (QA) features:
Settings for the new QA checks are available in Preferences (Edit > Preferences > QA tab).
In the next update, would it be possible to please indicate what non-translatable fragment is missing when doing QA tests? For the moment the message only states a general "Missing non-translatable fragment". Thanks!!!
Would it be possible in forthcoming builds to change the designation of the Irish language to 'Irish (ga)' or 'Irish - Ireland (ga-IE)'. The current designation of 'Gaelic - Ireland (gd-IE) is incorrect and seems to cause conflict with MT engines which use the correct designation.
You can create new (or already populated) .txt files for non-translatables and store them in /cafetran/resources/placeables
These can then be selected for use in Preferences > General > Non-translatable fragments.
However, there is a simpler way that I recommend if you intend to use a different list every time:
- Keep using the standard non-translatable.txt file for storing any non-translatables that may apply universally, and create a project-specific glossary for storing your non-translatables (and running QA).
Indeed, when you create a new glossary, after you choose its filename and location, you can tick the checkbox "Non-translatable fragments only".
The result? Anything you add there will be counted as a non-translatable.
L: much the same as you now have for ProjectTM and ProjectTerms?
No, I don't want that. Besides, Igor did answer you. You are at risk of being severely [moderated]inged.
The issue with double percentage symbol for context matches in the Matchboard is fixed in the latest build (2018062001) . Please download and install the new build of the update 10 as described in the announcement post above. Thank you.
Thanks Wojciech. It does not bother me too much, I was just curious.
The double percentage sign is probably an accidental result of the shortening of the information column implemented recently. I have the same issue on my computer. With information shortened and 101% matches, CT continues to display the column the way it did before the new implementation (i.e. such column is currently broader than in the case of other matches, which is inconsistent).
Hopefully, it will be repaired.
Is the 101%% Context (with doubled %%) intended, or a typo?
> Then I noticed "non-translatables.txt" is a single list
Instead of the single list, you can use specific non-translatable lists for your languages. Just create a new glossary of non-translatables and select "Non-translatable fragments only" option in the Resource information panel.
Forget it. I can call up any relevant Service in the CafeTran menu or using CheatSheet.
Don't know if that works for KeyBoard Maestro, but they have their own menu item.
IK: ...the Windows context menu
Does that mean Window users can call up the Windows context menu rather than the CafeTran context menu like:
I've been asking that for ages for macOS, even calling it "Kmitowski highjacking." On a Mac, Mac shortcuts work, but not the the context menu, like:
Luisa: Thoughts on this?
But of course.
So the QA becomes useless because it hits a lot of "false positives"
That's one of the reasons I don't use that list. I add "real" untranslatables to my Big Papa (general TM for Fragments), while I add project-specific untranslatables to my ProjectTM (that has the highest priority, and that can be re-used, of course).
"gate" may be added to the Big Papa in the "normal" meaning, whereas your "gate" should be added to your radiology ProjectTM. That should not only fix your QA problem, it's also indispensable for [insert] Auto-Assemble. More on my use of resources.
By the way, I think you shouldn't have posted your message under "Updates, but rather in "Questions"
Hi Igor. Thanks for this version.
Small issue: now I get a lot of "false positives". Then I noticed "non-translatables.txt" is a single list, transversal to all projects! I think that's not a good idea: in some projects, words can be non-translatable brand names, for instance, and totally "normal", translatable words in other projects. So the QA becomes useless because it hits a lot of "false positives".
I'll give you an example: "gate" - this was a non-translatable word for a radiology project I was working on, but is a "normal" translatable word in any other context.
Thoughts on this? Thanks.
Really loving my fantastic (i.e. standard) keyboard on my new laptop! Having a Windows context menu key (aka "Menu key" or "Application key") is super-useful in CT … for quickly correcting typos or prioritizing terms in Glossaries.
re my new laptop, which is 100% silent as it is fanless, i.e. without any moving parts, have a look at my (very long) review over @ https://www.proz.com/forum/hardware/325813-okay_finally_bought_myself_a_fanless_100_silent_laptop_4_work_venom_blackbook_zero_14_review.html (I highly recommend going the fanless route, to anyone who doesn't like noise!)(yes, I know, Hans, Macs are already silent ;-))