Wrong date format in TM system fields

We are experiencing some odd behaviour of Studio 2021 when saving translations to a TM. On dates where -considering the plain numbers only- day and month are impossible to tell apart unless you know the date format, e.g. days 1-12 in June, Studio is saving translation units with some system fields in the wrong date format. So now we have TUs for different clients in several TMs and probably all working languages that were created in the future. For the moment this does not seem to be a big deal. However, there is a reason the data is gathered. So, we cannot predict when this might become a real problem.

Is this the first time someone reports this kind of behaviour? Does someone know what the cause may be?

Thanks in advance for looking into this. Here are some screenshots, first of the SDLXLIFF and then of the TM info within Studio. Opening the SDLTM with an SQLite Browser led to the same findings.

Screenshot of SDLXLIFF file in Trados Studio showing translation units with incorrect 'created' and 'last modified' dates in the future, such as 06082021 instead of 08062021.

Screenshot of Trados Studio TM info panel displaying a translation memory entry with mismatched 'created' and 'last used' dates, indicating a potential date format error.



Generated Image Alt-Text
[edited by: Trados AI at 1:25 PM (GMT 0) on 29 Feb 2024]
emoji
Parents Reply Children
  • Hi ,

    Thanks a lot for your hint. This will most probably be the cause. However, I just performed a test as follows: I created a project once with Studio 2021, once with Studio 2019 on the same system with Region settings set to M/d/yyyy.

    With both versions creation_date, change_date, last_used_date and insert_date are all entered with the same format: yyyy-M-d.

    Then I did the same on another system with Region settings set to M.d.yyyy. Here, Studio 2019 performs as expected and writes into the TM the same format as on the other system: yyyy-M-d. Studio 2021 however writes the insert_date with format yyyy-M-d but creation_date, change_date and last_used_date with format yyyy-d-M.

    To my perception this is a bug. Do you have other suggestions on how to solve this?