![]() ![]() ![]() I have created a new file from scratch that has the same content and the same formatting as the document where the issue happens, and the formatting looks good in the target document. I'm not sure I understand all of it, but based on that and also based on other observations I explain below, I tend to think that the problem is not in the filter but in the source document (but it could be both). I appreciate your possible programmatic solution, which seems to be a generic fix (for any language pair). Konovalyenko Thank you so much for having looked into this.Similar, the w:i or w:b run properties have to be added if the translated content contains non-complex script characters and there are only the w:iCs or w:bCs run properties specified. The w:iCs or w:bCs run properties have to be added if the translated run content contains complex script characters and there are only the w:i or w:b run properties specified. The merge has to be performed with the following clarification of the document markup.Also, the w:i and w:b run properties have to be removed if the original content does have the complex script characters only. The w:iCs or w:bCs run properties have to be removed if the original content does not have the complex script characters ( ). The extraction has to be performed with the following clarification of the document markup.The aggressive cleanup option has to be made non-applicable to the w:iCs and w:bCs run properties.I am afraid, there is no workaround for this case at the moment (other than fixing the document structure manually).Ī possible programmatic solution, I can imagine now, might consist of the following steps: That is why the italics formatting is not applied. Again, as we have just revealed, the Arabic content appeared to be the complex script one. Please notice that the w:i formatting is applied to all non-complex script characters only. Please observe the round-tripped document diff below:Īs for the first case with “italics removed”, below are the differences of the corresponding part: If this option is set to true, the mentioned w:bCs, w:iCs as well as w:spacing, w:szCs and w:w run properties will be removed on processing the document. īelow is the corresponding place in differences:Ī possible solution would be using the bPreferenceAggressiveCleanup OpenXML filter parameter. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |