CafeTran
How can we help you today?
REQ Regex tagger
Your assumption is correct with the exception that CT will treat them as 100% Assembly results that can be skipped via the option in the Action > Skip menu. You can also define a few patterns in a segment to control the assembling function better. For example:
German: {1} Willkommen bei {2}
Dutch: {1} Dutch translation {2}
The latest addition to Fuzzy match auto-correction can repair fuzzy matches with non-translatable fragments. Based on your above example, if you add Maier GmbH and Müller AG to your non-translatable list, CafeTran will try to fix the TM Fuzzy matches automatically.
>The latest addition to Fuzzy match auto-correction can repair fuzzy matches with non-translatable fragments. Based on your above example, if you add Maier GmbH and Müller AG to your non-translatable list, CafeTran will try to fix the TM Fuzzy matches automatically.
Thanks Igor, but the reg ex tagger is still an added value ;).
The non-translatables solution also supports regular expressions. They work like in glossaries - introduce a regular expression with the pipe "|".
I have been looking for a way to mark up text strings in XLIFF files in such a way that they are treated as tags by CafeTran. I found a comment thing in the XLIFF spec and wrapped the numbers in a test document with these comment things:
Then I loaded the XLIFF in CafeTran and to my very pleasant surprise, the text that I wanted to mask (hide) was indeed represented by a tag:
Of course, CafeTran didn't like this hacking, so the number propagation was awful. But I don't blame the tool for that.
Eternally happy I was when I noticed that I could export the file. Obviously, the comment things didn't disturb anything:
This gives the citizen hope.
Using this comment thing it's also possible to mask strings with formatting:
Hello Igor,
Can you already tell me, when the regular expressions tagger will be available? Today I have to translate this SDLXLIFF:
It would be very nice if I could hide the fields from the segments.
Have a nice day!
Hans
Hiding the fields might be dangerous. If the client decided to include and display the fields in the source segments, they may provide the valuable context. In this example, it looks like CafeTran would need to 'fix' the segmentation done in another tool. The question is why they are there and why the fields have not been hidden behind one of the xliff tags.
>The question is why they are there and why the fields have not been hidden behind one of the xliff tags.
Lazy/unexperienced PM that created an SDLXLIFF from a simple XLSX containing software strings.
Not to mention the huge improvement of the TM: it would only contain the real text, just like this will appear in the citations in the manual later. No fuzzy rate reducing and distracting field codes in the TM!
Losing hours and hours in an attempt to install a plug-in in Studio 2017 that should allow me to tag the fields. Not very happy today :(
http://www.proz.com/forum/sdl_trados_support/311552-how_to_exclude_string_from_segment.html
If only all CAT tools could be as simple as CafeTran :)
I may code into CafeTran faster than you will find the solution. Just joking. :)
Tagged in Studio:
Representation in CafeTran, just the way I want:
alwayslockyourbike
Igor Kmitowski
>I think hiding selected phrases behind the tags is a bit exotic request seemingly based on the principle "other tools have it so CT should have it too". However, I find it interesting and probably will be added as an option to non-translatables which could be hidden this way. I can't tell you when as it is not the top priority although I can't wait to start coding it. :)
Any progress here?
HL