• State Suggested Answer
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 3735 views
  • Users 0 members are here
Options
Related

Numbers and alphanumeric strings not being auto-substituted consistently

Madeleine Barois

 Hello,

 

We're having issues with auto-substitution in Studio 2017. Here's an example:

 

We have 3 TMS for a customer:

  • DEU-ESP
  • DEU-RUS
  • DEU-ENG

 

All 3 have identical Recognize settings, Penalty settings, and Auto-substitution settings.

 

 Trados Studio Recognize settings with checkboxes for Dates, Acronyms, Alphanumeric strings, Times, Variables, Numbers, and Measurements.

Penalty settings in Trados Studio with values set to 0 for Missing formatting, Different formatting, Multiple translations, Auto-localization, Text replacement, and Alignment penalties.

 Auto-substitution settings in Trados Studio with checkboxes for Dates, Numbers, Variables, Times, Measurements, and Acronyms.

 

All 3 have been re-indexed and had their fuzzy index statistics recomputed.

 

The TUs that compose these TMs are from translations of identical DEU source files.

 

Now we have a new project, for which the source file is the same for translation into ESP, RUS and ENG.

 

However, when we attach the TMs, it seems that the auto-substitution function only works sometimes.

 

ENG:

Segment comparison in Trados Studio showing '1,5 mm2' correctly auto-substituted to '2,5 mm2' for English translation.

RUS:

Segment comparison in Trados Studio showing '1,5 mm2' incorrectly auto-substituted to '2,5 mm2' for Russian translation.

ESP:

Segment comparison in Trados Studio showing '1,5 mm2' correctly auto-substituted to '2,5 mm2' for Spanish translation.

 

When we looked up this ESP segment in the ESP-DEU TM, the measurement cited in the segment was "1,5 mm2" and not "2,5 mm2", so it seems like the auto-substitution was indeed successful in this case - only for ESP.

 

However, for ESP there are other examples of auto-substitution of measurements/alphanumerics not being auto-substituted properly, ex:

 

Segment comparison in Trados Studio showing inconsistent auto-substitution with '1,5 mm2' for English and '2,5 mm2' for Spanish.

 

Are there language-specific variables that we're unaware of that might affect the behavior of the auto-substitution function (and, by extension the analysis results)?

 

Thanks in advance for your help,

 

Madeleine

Generated Image Alt-Text
[edited by: Trados AI at 3:24 PM (GMT 0) on 28 Feb 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Daniel Hug

    Hi   

    Auto-substitution works only when Auto-substitution settings are set before opening files. Changes made when project files are opened in the editor are not applied and substitution doesn't work.

    Trados Studio Project Settings window showing Auto-substitution options for Numbers, Variables, Measurements, and Alphanumeric strings checked.

    This is an example when you set Number, Measurements and Alphanumeric when files are opened in the editor. Auto-substitution doesn't work.

    Trados Studio editor window with a list of cable types, showing no auto-substitution applied to numbers and measurements in the source and target columns.

    This is an example after closing files and reopening them. Auto-substitution works.

    Trados Studio editor window with a list of cable types, showing auto-substitution applied to numbers and measurements in the source and target columns after reopening the files.

    The same applies for Acronyms.

     

    Best regards,

    DArek
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 3:25 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Dariusz Adamczak

    Dear all,

     

    thanks a lot for your feedback! I'm afraid none of the suggestions will work for us at the moment. We've applied the same auto-substitution settings to all languages we work with for this client and they are all loaded when creating a new project.

    I found that in more recent projects the auto-substitution feature worked perfectly for all languages except Russian and Greek.

    Here's one example where it didn't work for Russian:

    In segment 309 "2,4" from the TM should have been replaced by "1" and therefore automatically been turned into a 100% match.

    Trados Studio segment 309 showing '2,4' not replaced by '1' in Russian TM, resulting in less than 100% match.

    Trados Studio segment 502 showing successful auto-substitution of '2,4' with '1' in Spanish TM, resulting in 100% match.

    In the Spanish file, the auto-substitution feature worked flawlessly, replacing "2,4" from the TM with "1" in seg. 502. Both the Russian and the Spanish TM are the basically the same and subject to the same TM settings.

    Trados Studio segment comparison highlighting the lack of auto-substitution for '2,4' in Russian TM.

    Trados Studio segment comparison showing successful auto-substitution for '2,4' in Spanish TM.

    As we're experiencing the same problems with Greek, my initial thought was that the problem is somehow connected to Greek and Russian using a different alphabet/code compared to the other languages we work with for this client. But considering that this problem also occurred in our English files in the past, this might not quite be it...

     

    Studio version: Trados Studio 2017 SR1 - 14.1.10014.38031

    I will keep investigating, but I would appreciate a keen eye to have a look it!

     

    Thanks in advance and best,

    Julian
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 3:26 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Julian Hamm

    In the meantime I found out that my problem with auto-substitution was most likely caused by the project TM not working properly. After fixing that, everything is working perfectly.
    In my case, the batch job "update project TMs" would exit with an error.
    Daniel