Hi Bruno Ciola

I recall seeing this behaviour but I didn't really figure out why it was happening except, for example, if there was a punctuation mark preventing the software from making the match properly. 

I and other users also have periodically seen the occurrence of identical duplicates being added to a TM when confirming or of existing units not being overwritten when corrected during translation but rather creating a new unit and leaving the incorrect one inn the TM. Someone in the technical department said that it was because their background hex values were different. It hasn't happened yet with Studio 2017...

Possibly the oddest TM behaviour I recall, I think it was with Studio 2014 or earlier, was this: No matter how many times I confirmed a certain frequently-used single-word source and target TU to the TM, I think it was 'Brenner <> Burner', it 'disappeared' and did not come up again in the Translation Results window or populate segments at the pretranslate stage of project setup. I remember that I exported the TM to tmx and opened it in Olifant and found numerous seemingly identical duplicate TUs with just 'Brenner <> Burner'. I never did find out why it was happening. I presumed at the time that it was a display issue.

Huge complex pieces of software that have been built, revised and rebuilt, 'new programming on top of old' (?) will have the odd glitch now and then...

Makes life more 'interesting' ;-))

All the best

Alison

Hi Bruno Ciola

I recall seeing this behaviour but I didn't really figure out why it was happening except, for example, if there was a punctuation mark preventing the software from making the match properly. 

I and other users also have periodically seen the occurrence of identical duplicates being added to a TM when confirming or of existing units not being overwritten when corrected during translation but rather creating a new unit and leaving the incorrect one inn the TM. Someone in the technical department said that it was because their background hex values were different. It hasn't happened yet with Studio 2017...

Possibly the oddest TM behaviour I recall, I think it was with Studio 2014 or earlier, was this: No matter how many times I confirmed a certain frequently-used single-word source and target TU to the TM, I think it was 'Brenner <> Burner', it 'disappeared' and did not come up again in the Translation Results window or populate segments at the pretranslate stage of project setup. I remember that I exported the TM to tmx and opened it in Olifant and found numerous seemingly identical duplicate TUs with just 'Brenner <> Burner'. I never did find out why it was happening. I presumed at the time that it was a display issue.

Huge complex pieces of software that have been built, revised and rebuilt, 'new programming on top of old' (?) will have the odd glitch now and then...

Makes life more 'interesting' ;-))

All the best

Alison