Idea Delivered

This has been delivered with Studio 2021 where you can customize number, date, time, currency and measurement formats, including using non-breaking spaces as appropriate.

Better currency and percentage symbols management, with support of unbreakable space

Hi,

SDL Trados Studio is able to automatically change the currency number formats, just as in the screenshot below, that is converting $2,000 into 2°000$:

Yet, at least in Canadian French, the right format should be 2°000°$, with an unbreakable space before the dollar symbol, this way:

I did not find any parameter to change it in Studio, including in the last 2017 version. That is those changes have to be done manually, which can be a big waste of time in financial documents.


Also, when I have a series of monetary figures, like below, the unbreakable space in the unconfirmed subsequent figures (if they have an unbreakable space previously inserted) is removed by Studio when I confirm the first one:

  >>> 

Lastly, and likey a consequence of it, when I run a QA Check (F8), SDL trados find an error when $22,30 (or any other fiure) is translated into 22,30°$, but not if it is traslated inot 22,30$:

 

By the way, QA check sees an error as soon as a figure (it being an amount, a percentage or a date) is written in the translated segment with an unbreakable space. E.g., 21°octobre, 3,57°% or 1°200°$, respectively for october 21st, 3.57% or $1,200. Unlike the issues previously described, which are more of a missing function, the latter one lokks more like a bug, since Studio does not recognize figures which, basically, are the same.

I hope you will be able to fix in a next SR those issues all and every French translators undergo since Studio 2009.

 

Thank you

Philippe Riondel
Parents
  • Former Member
    Former Member

    Hi Philippe and Michael,

    The problems only seem to appear when the currency is on the left side of the number in the target segment (and on the left in source).

    Obviously, my tests are far from comprehensive, but as you can see on the screenshots below , I have no problem when the currency is moved after the number (which is the normal position in French…), whatever the number format in the source. The auto-propagation even works as instructed (I tried with nbsp and no space).

    I am pretty sure there are some hidden/conflicting settings.

    By the way, the QA checks for numbers are activated in all screenshots below (I tried invalid numbers as well to make sure).

    @Philippe  :  I will try and look for this option in 2019 tonight.

    Pass, target currency on the right

    I am a bit tired and it's likely I'm not seeing some details in your examples. Anyway, this needs multiple thorough tests.

  • in reply to Former Member

    I made some experiments, and I was able to confirm the issue in QA is indeed related to the left-hand sided $ symbol:

    I used a series of LHS dollar amounts, RHS dollars amounts and percentages. Here is the translation initial result :

    One can see the QA only sees errors when and oly when the $ symbol is on the left,.

    That suggests the NB space is not the issue for QA, but that Studio does not see the yet typical English $XXX.XX format as a number (since the number is considered as added in French)!



    As per the NB space before any unit symbol, I was able to confirm, like Matthieu and Georgy wrote it above, that the automatic insertion of a NB space before the symbol can be forced when using the relevant pair of languages section (in my case, EnCA -> FrCA) for TMs, rather than the All Language Pairs section:






    It works well except for the QA issue. 

    But let's admit SDL team could have found more obvious a way to select that option.

    Regards

Comment
  • in reply to Former Member

    I made some experiments, and I was able to confirm the issue in QA is indeed related to the left-hand sided $ symbol:

    I used a series of LHS dollar amounts, RHS dollars amounts and percentages. Here is the translation initial result :

    One can see the QA only sees errors when and oly when the $ symbol is on the left,.

    That suggests the NB space is not the issue for QA, but that Studio does not see the yet typical English $XXX.XX format as a number (since the number is considered as added in French)!



    As per the NB space before any unit symbol, I was able to confirm, like Matthieu and Georgy wrote it above, that the automatic insertion of a NB space before the symbol can be forced when using the relevant pair of languages section (in my case, EnCA -> FrCA) for TMs, rather than the All Language Pairs section:






    It works well except for the QA issue. 

    But let's admit SDL team could have found more obvious a way to select that option.

    Regards

Children
  • in reply to Philippe Riondel

    However, what I do no understand is why the features in the yellow rectangle below are not available when you prepare a project, while you can access and use them once the project is ready. You have then to re-open the Settings windows and choose the right options, to re-pretranslate the files. That is double work.

    Hello, SDL Team?