Thread poster: bungholio
So I have an extensive project that contains the following German to be translated to English:
These are ordinal numbers, so the respective translations would be:
1st preset speed
2nd preset speed
1st skip frequency
2nd skip frequency
(not my translations, which still need to be checked for correctness)
Because these are ordinal numbers, I figured I would create a Segmentation Rule to deal with these to prevent me from having to merge all these units. The problem is, it won't work!
What's peculiar is that it DOES work if the word after the ordinal number is lowercase, e.g. 1. cat. Then I simply go into the segmentation rules, add "cat" (no RegEx) in the "After break" field (full stop rule). Voila, I see "1. cat" in my editor. This ALSO doesn't work with uppercase, i.e. doing the same thing yet adding "Cat" (instead of "cat").
It seems, therefore, that there is a problem with Trados in how it handles uppercase words after a break character. I've tested this with a brand new memory, thinking that maybe some existing segmentation rules were interfering, but the result is the same: lowercase gets "merged" but uppercase doesn't.
Does anybody have any help for me?
Thanks in advance!
| Never mind, I'm an idiot || Nov 27, 2013 |
Forgot completely about the ordinal follower list, Doh!
To report site rules violations or get help, contact a site moderator:
You can also contact site staff by submitting a support request »
|Anycount & Translation Office 3000|
|Translation Office 3000|
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info »
|For clarity and excellence|
WordFinder is the leading dictionary service that gives you the words you want anywhere, anytime.
Access 260+ dictionaries from the world's leading dictionary publishers in virtually any device.
Find the right word anywhere, anytime - online or offline.
More info »