Idea Delivered

Processing of embedded content is improved so users can simply specify patterns for text to be converted to inline tags

Transfer the "Non-Translatable texts" option from the DOC filter to the new DOCX filter

Is this a bug?

In the old Trados Studio import filter for DOC files, it was possible to define specific text to be excluded from translation. This function was called "Non-Translatable texts". We used this function to exclude text between "{" and "}" - containing non-translatable field names and meta data.
This worked good and was an essential part of our workflow to translate report templates for users of our microscopy and imaging software.

As the DOC format is outdated, and DOCX is the new standard format, we did not expect that this "Non-Translatable texts" function would be missing in the new DOCX import filter. It seemed like a bug to us.
It would be very helpful to have this function transferred to the new DOCX import filter.

We are trying to establish a new stable, robust workflow without this function for the translation of our DOCX files. But this is causing several problems, why we already had to log 3 support cases (00306623, 00309563, 00309576).
The task to translate our DOCX files is a recurring task for many files and many languages. We think that other customers also would appreciate to have this efficient and well-working "Non-Translatable texts" function back again.

Peter Stallknecht

  • Dear Daniel, thank you very much for your proposal. I will forward this idea to my colleague who checks the possibility of a new workflow, and to the responsible developer who provides the word files. I understand that this ideas implies pre-processing and post-processing of the files, and that it is essentially the same idea as suggested in our support case 00306623:

    "We can propose a workaround however but you need to edit the source document. The Word Filter supports non-translatable styles, you can tell Studio to not extract text with a certain style."

    In this support case, my colleague answered:

    "We have talked with our software developer and decided that we could not apply your suggestion for our workflow.

    The main reason is, as I wrote before, we can not do all modification of the many files."

    So, I'm not too optimistic that this will help us, but nevertheless, of, course, I will forward this to my colleagues and especially ask them, if they already used a regex search for their tests of new possible workflows.

    For vacation reasons, an answer may take a while.

    Thank you and best regards, Peter

  • Hi , would an option be to do a regex search in Word files and apply a non-translatable character style to these strings? The previous functionality was meant for the (now very old) Robohelp files and similar file types, and we don't often hear about this kind of requirement anymore. Would be good to see if such preprocessing could work for you? Thanks, Daniel