• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 1641 views
  • Users 0 members are here
Options
Related

Issues while auto-translating dates into Dutch

David Lopez

Dear all,

I was trying to auto-translate dates into Dutch, and I came across some issues.

Thus, in the source, EN-GB, I had, for instance these dates: 

  • 20/11/2015
  • 15/12/28

I had already similar dates "translated" in my TM. Actually, in these cases, the auto-translation would be the very same as per the source, that is:

EN-GB: 20/11/2015
NL-NL: 20/11/2015

EN-GB: 15/12/28
NL-NL: 15/12/28

Whenever I try to auto-translate dates, I go to Language Pairs>English (United Kingdom)->Dutch, and I select the right format for long and short dates. This is used to work fine in Trados 2007.

However, now in Studio 2017, also in Studio 2014 (I haven't tried in Studio 2015, but probably it is the same), I can choose dd/MM/yy, but the figures on the right side state the auto-translation will be 27-04-17. For that one, we already have dd-MM-yy.

 

Besides, this also means we have the very same option appearing twice instead of the one I would need: 27/04/2017. 

Is this a bug that could be fixed (so as to know if it is possible to flag this)?

I know there would be several workarounds such as filtering in the Review Pane, by using SDLXLIFF Toolkit (this one might be risky), or by using regex, but just imagine you are working on huge files and you have to speed it up, since you want to make it straight-forward. That's the reason in the end why you have the option dd/MM/yy even though it does not work as it should.

Do you think I am doing something wrong? Why do we have so many limitations while auto-translating dates? I know Studio uses the Region and Language settings, but it would be great to count on more flexibility. 

Thanks a lot for your time!

 

Kind regards,

David
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi David,

    This looks like a bug to me. You actually have two problems to deal with:

    1. The format being substituted is wrong
    2. Your source contains two formats for the year and Studio is very prescriptive in "normalizing" them

    I will log this, and in the meantime your best bet is going to be regex search & replace in the end.

    I would have suggested you use the Regex AutoSuggest provider as this would do a great job of dealing with these, but unfortunately we broke its ability to work with numbers when we launched Studio 2017. This problem has been fixed in CU5 that is due imminently, so once you update you can use that to better effect. In the meantime the best solution I can come up with is regex search & replace.

    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

Reply
  • 0
    Hi David,

    This looks like a bug to me. You actually have two problems to deal with:

    1. The format being substituted is wrong
    2. Your source contains two formats for the year and Studio is very prescriptive in "normalizing" them

    I will log this, and in the meantime your best bet is going to be regex search & replace in the end.

    I would have suggested you use the Regex AutoSuggest provider as this would do a great job of dealing with these, but unfortunately we broke its ability to work with numbers when we launched Studio 2017. This problem has been fixed in CU5 that is due imminently, so once you update you can use that to better effect. In the meantime the best solution I can come up with is regex search & replace.

    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

Children