Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Repeating Section Content Control in Word 2013 #54

Closed
cknaap opened this issue Apr 8, 2013 · 3 comments
Closed

Add support for Repeating Section Content Control in Word 2013 #54

cknaap opened this issue Apr 8, 2013 · 3 comments

Comments

@cknaap
Copy link

cknaap commented Apr 8, 2013

Word 2013 introduces the Repeating Section Content Control. It would be very useful if Docx4j would evaluate and populate this control with the repeating data from the custom XML that is bound to it. I think this could be used instead of the OpenDoPE implementation of repeating data.

Please refer to RepeatingSectionContentControl.zip for an example document. It includes:

  • Order_ContentControls.docx: a very simple order report containing a single order number and the aforementioned Repeating Section Content Control for the OrderLine items.
  • OrderExample1.xml: the xml data that was loaded into the Word document.
  • Order.xsd: the schema for the xml data.

See the question on StackOverflow that resulted in this issue.

@plutext
Copy link
Owner

plutext commented Jul 11, 2013

As from now, GitHub master will retain this element (and other important Word 2010 & 2013 extensions), as will docx4j 3.0, when released.

docx4j's binding implementation won't process it though. Maybe that'll come in 3.1.

@cknaap
Copy link
Author

cknaap commented Jul 28, 2013

Thank you for the update. I'll keep watching this thread for updates on processing it.

@plutext
Copy link
Owner

plutext commented Dec 4, 2018

@plutext plutext closed this as completed Dec 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants