Test with attached example file
and pre-translations of
and lookup in condordance search, what is actually returned by the service and re-export of the TMX proof the following
Short-comings compared to what is defined in the TMX 1.4b standard:
bpt, ept, ph, it tags
Code encapsulated by these tags is removed on import. Attributes are preserved.
This means an imported segment that looks like this
returns like this
As tests with the supplied example data shows, sub tags are not handled and supported, because they are only allowed within a bpt, ept, ph, it and ut tag - and the content of those tags is ignored by the service.
ut and hi tags
In an exported tmx they return the same, was they have been imported, including code that may be contained and attributes.
Yet in a fuzzy search or concordance search they are not returned as tags. This means, the service does not treat them as tags.
They are NOT supported by the translate5-tm-service as of now.