Open joaoe opened 5 years ago
I saved myself from this trouble by using instead a single cell table, with fixed dimensions and an inline image with layout set to behind text.
I see this here
When using this feature, make sure you don't use comments, footnotes, bookmarks, etc. This is because these elements have an id attribute, which must be unique. This library does not handle this, resulting in invalid documents.
Could it be the same issue ?
Hi, This is indeed related to text boxes, witch may have anchors, position, etc ; they are not managed by the merge_pages def. Note that the documentation you quoted refers to a version not released yet by @Bouke. However, this version (def merge_pages replaced by def merge_templates) will not managed either text boxes for the same reasons.
Hi.
Context
My template document has a text box. The original document was an invitation in which the text box was used to mark the margin to cut them into the right size and to also specify a background image.
Current behavior
Generating the merge files seems to go ok and the final document has all the expected text. However, MS Word 2016 complains when first opening it:
The document is generated using
MailMerge.merge_pages(...)
, e.g.:Expected Behavior
Hopefully that warning is not serious. Nonetheless, it should be investigated to see if the generated file is not broken or if we are getting lucky and Word manages to rebuild it.
Steps to Reproduce (for bugs)
testcase.docx
andtestcase.py
.python testcase.py
. Obviously this python instance should havedocx-mailmerge
installed.testcase_generated.docx
with Word 2016Environment
Thank you !