How can I check the correct usage of decimal separators (German>English)?

Hi Trados Community,

I had a project translated from German to English and I noticed that one number (e.g. 1,5) was not localized in the translation (so it was 1,5 as well). However, the quality check did not show an error message. I made a test with thousand separators (e.g. for "1.000") where I also wrote the unlocalized version in the English segment (1.000 instead of 1,000) and in this case the quality check showed an error message.

I saw that you can use regex or the Number Verifier app from the AppStore. However, is there a simple solution to check decimal separators in Trados without additional applications? Am I missing some settings in Trados?

My version: Trados 2017 (but also tested with Trados 2019)

Thank you in advance.

Sara

  • Have you made sure, that the QA settings have been applied WITHIN your project (ie via Project settings) and NOT via File -> Options?

    In general checking numbers is a bit problematical, as 2.10 may be number as well a chapter and 10.02.20 may be a date and a part number. So the program needs to deal with such differently, but has no decision points to chose whether 2.10 is number or chapter...

    _________________________________________________________

    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.

  • Thank you for your reply.

    Yes, the QA settings within the project settings should be correct:

    Trados Studio project settings window showing QA Checker 3.0 with error messages for 'Zahlen prufen', 'Zeitangaben prufen', 'Datumsangaben prufen', and 'Ma einheiten prufen'.

    I just thought that it would be helpful to have this kind of check. Chapter numbers are often included as fields and there is a separate setting for dates. So there would maybe not be too many false positives.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 8:09 PM (GMT 0) on 28 Feb 2024]
  • Number verification is a bit of a thorny area, partly because, as Jerzy pointed out, it is not always possible for Studio to know that a number signifies. (E.g. "This is version 3.0 of the software" should not be translated into "Dies ist Version 3,0 dieser Software", but "A value of 3.0 or above is cause for concern." should be translated into "Ein Messwert von 3,0 oder größer ist Grund zur Besognis." - how will Studio know when the period should be replaced with a comma?)

    I noticed that one number (e.g. 1,5) was not localized in the translation (so it was 1,5 as well).

    Consider using the Number Verifier. It is not an additional application but a plug-in that runs with the normal Verify operaton.

    Regex is very customizable, very useful - if you know how to create them.

    Some people find the options provided by Studio insufficient and resort to either custom programming (custom plugins) or tools like XBench. For the problem you mentioned above, Number Verifier is sufficent.

    Daniel