• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 6203 views
  • Users 0 members are here
Options
Related

Auto-propagation of decimal comma

Alistair Binks

Hello,

 

I understand from previous forum answers that there is a solution for my problem, but I can't make it work.

EN decimal points should be decimal commas in HU, but I cannot set my project in a way to autopropagate numbers correctly:

Under the specific language pair > Auto-substitution, Numbers and measuremenst are selected as well, and as the blue line indicates, Studio recognizes the numbers. I have created my project with these settings, added the TM for the specific language pair (not All Language Pairs), but the behaviour does not change. My only solution when proofreading is to filter for number-only segments and confirm them in one go, so at least the already correct segments are not auto-propagated incorrectly.

 

Please advise what setting needs to be changed. Thanks!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Alistair Binks
    There is a much faster way to deal with number only segments than auto propagation.
    Use the Display filter, enter ^[\d\W]*$ there and press Enter.
    This will show only segments, containing non translatable items.
    You can now copy source to target and confirm all in one go.
    If a switch between dot and coma is necessary, run a search & replace operation for doing that.
    Of course the regex for filtering will need to be modified, if you have also dates in your document, but that is also quite simple.
    This way you can deal with many number only segments much faster than with the AP method. And much more reliable

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0 in reply to Jerzy Czopik
    Thanks! We also have our workarounds to solve this, QA software can also fix the commas relatively simply, it just seemed a pity that e.g. we have all the numbers correctly in the the translated files, would then ruin them all with autopropagation during proofreading, and would then correct them again during QA. I was wondering if some project setting was causing the phenomenon, but if not, we will proceed as we did so far.