-
Bug
-
Resolution: Fixed
-
None
-
High
-
Add new TMX processor and config with regex to filter problematic TUs from TMX on import
-
Emptyshow more show less
Problem
The content protection did spoil some segments on TMX import. It did import the content inside of <bpt></bpt> or <ph></ph> tags as normal text content for the segments. This happened my a mismatching Regex. It did not happen as it looks like for <ept></ept> tags.
Solution
We automatically delete those segments with a change in translate5 code, that is only available on the affected instances while the next content conversion of TMs is running.
We should delete (not newly import) segments, that contain the regex
- type="\d+" category="\d+"
- or the stringĀ
extstyle="yes" - or the stringĀ
extstyle="no"
Instead we save those segments in a tmx file in the log directory.