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
  • Former Member
    Former Member in reply to Philippe Riondel

    This is indeed very weird that the typical $XXX.XX is not recognized. Anyway, you did find the right setting for auto-propagation ! Slight smile

    Now regarding Studio, what annoys me most with SDL is that they do release new features, but they rarely fix old features that have never worked properly or take user suggestions into account. They are selling enticing new features, but some basic features you paid for years ago still don't work.

    And although the development goes on, some aspects are getting very old:

    -The interface is based on the Office 2007 ribbon model. It has almost not changed since then. There are way too many small UI elements, and buttons close to each other. I have a 29" screen and Trados still feels "stuffed". It also lacks customization options, notably regarding windows/modules. If you try to move modules around, you will quickly see you can indeed arrange them as you like, most of them will just be unusable if you move them away from their original corner.

    -The second major problem is the software itself. It is slow and buggy. Whatever task you run with Trados, your hardware will always be underused. And it is quite frustrating to wait for basic tasks when the CPU, the RAM and the disk usage never exceed 10% of your overall resources.

  • in reply to Former Member

    I tried this app years ago. Unfortunately, it doesn't solve this particular problem.

  • in reply to Former Member

    I use a couple of those apps, but I did not try that one yet.

    While Studio may seem un "ageing" software, I would not say they neglect its development. The release notes of SR2 show there were many improvements and fixes done.


    I just regret many suggestions from users are not implemented. That Community section seems to be overseen by SDL team. I made a proposal a long time ago to improve the comment box (rich text format, a magnifier or a function to enlarge fonts, any way, something to make it more legible), and I got some support for it from other users, but that comment box is still a pity, and I suppose many other potentially useful proposals are ignored. It's a pity

  • 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

  • in reply to Philippe Riondel

    Please discard that post, that was not finalized. 

    @SDL: is it possible to edit/remove our own posts?