We're having issues with auto-substitution in Studio 2017. Here's an example:
We have 3 TMS for a customer:
All 3 have identical Recognize settings, Penalty settings, and Auto-substitution settings.
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.
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:
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,
Thank you for your response. Yes, my apologies, I didn't realize the quality on the images was so bad. Here they are again, let me know if they're more legible now when you click to expand them:
The TM settings:
The auto-substitution examples:
The other ESP example:
I am experiencing the same. It was not like this before:
Maybe a bug came in with 2019 SR1? I would love to hear from SDL about this.
Paul, any news on this issue? I de-installed the Number Verifier Add-on, but that did not help, so I re-installed it. Daniel
EDIT: This is really a problem for us, so I kept working on it. I am now pretty sure that is has to do with what characters are adjacent to the number. If the character is not considered a separator, the number is not replaced properly or something like that? The substitution behavior changes when I enter characters into "Alphanumeric custom separators".
Hi Daniel Hug Madeleine Barois
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.
This is an example when you set Number, Measurements and Alphanumeric when files are opened in the editor. Auto-substitution doesn't work.
This is an example after closing files and reopening them. Auto-substitution works.
The same applies for Acronyms.
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.
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.
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,