Menu
▾
▴
#794 Word: specific tag processing not working when extension in uppercase
This bug report is a follow-up to [#634]
I am not completely sure how this new report is related to the workaround created in the last report.
File: text missing.docx
Source:
<t0/>X’s<t1/> Privacy Statement<t2/>
Target:
translation <t0/>X<t1/><t2/>
Microsoft Word:
X (i.e. the word “translation” is missing)
File: formatting incorrectly applied.docx
Source:
<t0/>X’s<t1/> Information Security Policies<t2/>
Target:
translation <t0/>X<t1/><t2/>
Microsoft Word:
Formatting is applied to the word “translation” as well, rather than just to X. It would be great to have some way not to avoid that.
Download the project: https://yadi.sk/d/w6ZgK5nwoJ25b
Related
The issue is indeed related to the previous workaround. For the formatting partially applied, we cannot do anything about it (within the current way we work with .docx). The only correct solution is to not put anything before the first tag or, even safer, would be not allowing unchecking Remove leading tag for .docx documents (but that wouldn't be obvious to do programmatically).
For the missing translation, that's another issue. The extension was ".DOCX", and we were only testing ".docx" (as I wasn't expecting extensions in uppercase). This will be fixed. I changed the title accordingly.
Didier
Fixed in SVN (3.5 and /trunk).
Didier
Closed in the released version 3.6 of OmegaT.