Jan Cerny wrote:
One new problem has arisen, concerning entities:
Documentation Environment including the DTD
When I import the documentation environment including the DTD, the value of a text entity is displayed within the editor as a normal text string (e.g "Coca Cola") and translatable. Is there a way to only display the entity (e.g "&ProductName;") instead and make it write-protected?
No (I'm talking from a user point of view).
When I generate the translated documents, they contain the DTD file content in the translated document (same problem as in the bug report I linked in my first post).
If the bug report is still open, that's because it is still valid.
Also, the output files again contain the "Coca Cola" value instead of the entity.
What you see in the Editor is what you will get in the target document.
Documentation Environment without DTD
If I only import XML files, entities are represented as blanks. This is also not ideal, because you miss them while translating. The output files also contain blanks where the entities should be.
Yes, that's not a very satisfying solution.
Is there a way around these problems?
I cannot think of any that doesn't involve pre- and post-processing the documents.
For instance, replace &my-entity; with #my-entity; in source documents, and do the reverse operation in target documents.
By doing so, you can have your "entities" identified as tags in OmegaT. In Options > Tag Validation, enter #.*?; as the regular expression for custom tags.