I'm trying to create a workflow to be able to hide invariant and nuisance strings in both native CafeTran Espresso 2019 and third-party projects.
In CafeTran Espresso 2019's native MS-Word projects you have maximum flexibility to hide what you don't want to see (duh).
However, in InDesign, FrameMaker etc. projects, you don't have this feature.
And in third-party projects it's neither possible. Hence the need of a way to get this disturbing info out of your project.
NOTE: This solution is only attractive for projects that don't contain (many) tags.
So: propagation is only limited to very similar non-translatables. This could be improved. Note that I didn't define the strings as non-translatables. But I don't think this will fix propagation.
The work around via MS-Word hides all invariant info. Propagation is optimal.
About how to import the table as a TM:
This is how tags are represented in CafeTran Espresso 2019's native project's bilingual documents:
Let me investigate whether something similar can be simulated for Studio projects.
>Let me investigate whether something similar can be simulated for Studio projects.
Well, of course you can always create the bilingual table in Studio, when you have access to this tool, and translate the table in CafeTran Espresso 2019.
Here you see an animation showing two TMs: one created from a native CafeTran Espresso 2019 project and one from a Studio project from the same text:
Just as expected: the TM looks the same, including the storage of the location of the tags.
This brings me to the following idea:
If tags in bilinguals for Studio projects are represented as either a pipe or one hidden project, this will have many advantages:
Of course the workflow has to be adapted to CafeTran Espresso 2019. For instance, the font attribute 'hidden' has to be used instead of a T4WIN style. I'll come back on this ...
Tortoise Tagger will probably be overkill for the relatively simple task of tagging bilingual export documents.