Brad Orfall 

Can I see the TM?  You can send it to pfilkin at sdl dotcom if it's acceptable?

The TM is 617 MB. It has ~122k entries in it from past projects. I tried exporting in studio 2021 as a TMX and then reimporting into 2021 as a new TM. There is no difference in the behavior using 2024. It seems that 2024 is detecting something in the TM that 2021 does not and generates an error. I can share the TM via dropbox or upload it to you.

The TM is 617 MB. It has ~122k entries in it from past projects. I tried exporting in studio 2021 as a TMX and then reimporting into 2021 as a new TM. There is no difference in the behavior using 2024. It seems that 2024 is detecting something in the TM that 2021 does not and generates an error. I can share the TM via dropbox or upload it to you.

Brad Orfall 

I have the TM, thank you.  I'm not seeing any problems with it though.  Can you confirm the path, the full path, to where it is stored?

The TM is stored in the default c:\Users\Brad Orfall\Documents\Trados 2024\Translation Memories folder.

I tried uninstalling Trados Studio 2024, and deleting the folders:

C:\Users\%USERNAME%\AppData\Roaming\Trados\Trados Studio\Studio18

C:\Users\%USERNAME%\AppData\Local\Trados\

I reinstalled the software with a fresh download from Trados' website, but the problem is still there. The file will not process using the TM. I can change to a different TM, and the file will process.

What I did so far:

1. Tried to process a Word file with just the contents "Test". File processed correctly.

2. Made four separate Word files with the contents of each page of the whole. Page 4 will not process.

3. Took the contents of page 4 and pasted as plain text into a new Word file. Maybe the Word file has some corruption in that area? -> No. Page 4 will not process.

3. Deleted portions of page 4 and tested repeatedly to see if I could locate the problem area.

4. Narrowed it down to one section that causes the file to not process.

5. Deleted each line of the problem section and found the text that causes the problem.

6. Checked a different file (there are multiple versions based on an underlying template). The same section in the other file causes the file to not process.

7. Checked a third file. The same section causes the file to not process.

It seems certain items that appear in the problem section of each of the three files are causing the file to not process. The items are different each time. It's a different string of characters that causes the errors. Somehow, when processing the file, it seems that searching the TM causes an error when certain text strings are present.

I tried each of these three files in Trados 2021, and they process correctly with the problem areas included.

I will e-mail the problem text to you, along with screen shots of the errors and my settings.

Brad Orfall 

Thanks for that.... really appreciate you do this.  I narrowed this down a bit further and can actually make up my own content that fails now.  For example, strings that consist of an alphanumeric code and a date range in the format "DD/MM/YYYY-DD/MM/YYYY" like this:

HU0826 12/03/2024-06/30/2025
GY0777 07/28/2025-11/30/2026
LM1323 07/01/2024-06/30/2025

If I just add one sentence like this it fails.  I'll share my test file with the support team for them to validate.

One thing you could do in the meantime is filter on sentences like this in the document with a little regex and lock the segments.  Then pre-translate.  This works fine.

Just putting a space before and after the hyphen in the date range makes the file process correctly.

It's not a "bug" it's an "unintended feature." :-)

Brad Orfall 

Oh dear... even I wouldn't go that far!!

Hi Brad Orfall , the error does indeed only occur when a regular hyphen is used between the dates in the source segment. There is no error when a non-breaking hyphen is used either. However, I noticed that the second date is not recognized in Studio 2022 either (although there is no error), so the problem is definitely related to hyphen followed by date. I logged the issue for Development, as CRQ-39227, so they can investigate further and implement a fix in a future Studio update.