Problem in localising a simple decimal number (DE --> GB)

Hi experts,

I am using SDL Trados Studio 2017 with the latest update.

While translating/ localizing a simple decimal number in a sentence, e.g.

               Source text: "Die Zahl lautet 7,7 %"

               Target text: "The number is 7.7 %"

SDL is reporting an error: "Number is missing in target segment or is not properly localized".

What am I doing wrong?

So far as I can see, it is a just a conversion from German notation (,) to English notation (.) of a decimal number.

At other places in the same file, the DE --> GB decimal number localization seems to be no problem.

It must be something very simple but I cannot find it. Can someone give me a tip, please?

 

Thanks and best regards

Shyam Gupta  

Parents Reply Children
  • Hi Paul,

    Thanks for your suggestion, I checked that immediately and found that the settings in my case are exactly tha same as shown in your screenshot, but the error message is still there.

    So, one possible reason could be that the "spacing option" selected is not the correct one.
    But how to find which option could be the right one. Use "hit and trial method" for the six options? And what would it be for the next text or project?

    There is probably some logic behind making the right selection, but unfortunately I don't know it.
    Would be thankful for any advice from your side.

    Best regards
    Shyam
  • Hi ,

    There shouldn’t be an error message at all! But if you share your sdlxliff and tell me what you expect on the target including type of space between the number and the unit then I can test it.

    Thank you

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Hello

    Thank you for sending me your file.  The problem is this:

    Note that the number is not correctly recognised as “3,6 %”.  It’s seen by Studio as “3” and “6 %”, so two separate numbers.  This is because the default decimal separator for de(CH) in windows is a period and not a comma.  This is where Annemieke is 100% correct since the number verifier plugin is able to set this up the way you would prefer and not be reliant on your operating system which is where Studio takes its settings from.

    You might be able to change the default in your windows language settings, but I tried this and was not able to make it work.  But this could be related to my own setup.  Maybe worth trying though.

    Alternatively your options are these:

    1. Define custom regex rules and then you can make it work, in this case I set the rule to have no space in target between the number and the percentage symbol.  So turn off number recognition and rely on your own rules:


    2. Or use the number verifier, and turn off the default Studio checks.  Frankly I think a combination of the number verifier and custom QA rules is the way to go with QA in Studio because number/date recognition is simply not good enough because of its rigid adherence to Microsoft windows.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Hi Paul,
    Thanks a lot for testing my file.

    I will, of course, try the Windows language settings approach at least once to see what efforts are required or is it possible at all. But to be frank I don't want to meddle with Windows settings .
    After all it is not often that I work with DE(CH) files.

    But of course, I will use (i.e. after I have learned how to use it) the number verifier app from now on. Thanks a lot again for your very fast response.

    Best regards
    Shyam