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 »
|Manage your TMs and Terms ... and boost your translation business|
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
More info »
|SDL MultiTerm 2019|
|Guarantee a unified, consistent and high-quality translation with terminology software by the industry leaders.|
SDL MultiTerm 2019 allows translators to create one central location to store and manage multilingual terminology, and with SDL MultiTerm Extract 2019 you can automatically create term lists from your existing documentation to save time.
More info »