Plutext

Hi Jason,

Is there a fix for the below issue. If so can you please provide the version of jar with those changes.

Need to check/uncheck the check box using 2010 docx template and currently getting below error .

[ERROR] : unexpected element (uri:"http://schemas.microsoft.com/office/word/2010/wordml", local:"checkbox"). Expected elements are
- continuing (with possible element/attribute loss)

Thank you for the support.

Regards,
Isaac

Nightly builds from July 10 support 2010 checkbox. The most recent is currently http://www.docx4java.org/docx4j/docx4j- ... 130721.zip but I will probably publish another today.

Hi Jason,

Is it possible to provide the 2010 Check Box content control fix with 2.8.1 release jar ?

Thank you for the support and help.

Regards,
Isaac

Hello Issac

It would be possible, but not straightforward.

Better if possible to use a nightly build, or wait for 3.0

cheers .. Jason

Thank you for the support and cool stuff.

May I know when is 3.0 release ?

Planning to include this in next sprint and if you can provide patch on 2.8.1 that will be really helpful.

Regards,
Isaac

ikola wrote:May I know when is 3.0 release ?

Hi Isaac, hopefully within the next month or so. We've been a bit relaxed about releasing it, since the 2.8.1 point releases have taken most of the pressure off.

ikola wrote:Planning to include this in next sprint and if you can provide patch on 2.8.1 that will be really helpful.

I don't think it makes much sense to backport this key 3.0 feature to 2.8.1, given that it touches a lot of files and 3.0 is close. Sorry about that.

Hi Jason,

Is checking/uncheking a checkbox included in 3.0 beta version?

If yes, how to do that ?

Hi, yes it is.

The XML will look something like:



w14:checkbox is represented by org.docx4j.w14.CTSdtCheckbox

Assuming you have SdtPr sdtPr, you'll find it in here (probably wrapped in JAXBElement):

Below is my document:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <w:document xmlns:ve="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships" xmlns:m="http://schemas.openxmlformats.org/officeDocument/2006/math" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:wp="http://schemas.openxmlformats.org/drawingml/2006/wordprocessingDrawing" xmlns:w10="urn:schemas-microsoft-com:office:word" xmlns:w="http://schemas.openxmlformats.org/wordprocessingml/2006/main" xmlns:wne="http://schemas.microsoft.com/office/word/2006/wordml">
- <w:body>
- <w:p w:rsidR="00A7711F" w:rsidRDefault="00190296">
- <w:r w:rsidRPr="00907425">
- <w:rPr>
<w:b />
</w:rPr>
- <w:fldChar w:fldCharType="begin">
- <w:ffData>
<w:name w:val="" />
<w:enabled />
<w:calcOnExit w:val="0" />
- <w:checkBox>
<w:size w:val="18" />
<w:default w:val="0" />
<w:checked w:val="0" />
</w:checkBox>
</w:ffData>
</w:fldChar>
</w:r>
- <w:r w:rsidRPr="00907425">
+ <w:rPr>
<w:b />
</w:rPr>
<w:instrText xml:space="preserve">FORMCHECKBOX</w:instrText>
</w:r>
- <w:r>
- <w:rPr>
<w:b />
</w:rPr>
</w:r>
+ <w:r>
- <w:rPr>
<w:b />
</w:rPr>
<w:fldChar w:fldCharType="separate" />
</w:r>
- <w:r w:rsidRPr="00907425">
- <w:rPr>
<w:b />
</w:rPr>
<w:fldChar w:fldCharType="end" />
</w:r>
- <w:r>
- <w:rPr>
<w:b />
</w:rPr>
<w:t xml:space="preserve">My name is kshitiz</w:t>
</w:r>
</w:p>
- <w:sectPr w:rsidR="00A7711F" w:rsidSect="00764431">
<w:pgSz w:w="12240" w:h="15840" />
<w:pgMar w:top="1440" w:right="1440" w:bottom="1440" w:left="1440" w:header="720" w:footer="720" w:gutter="0" />
<w:cols w:space="720" />
<w:docGrid w:linePitch="360" />
</w:sectPr>
</w:body>
</w:document>

What to do for this structure?

That's a legacy FORMCHECKBOX - a completely different beast.

To see how it is represented in docx4j, you can upload your docx to the webapp (linked in menu above).

docx4j's higher level code for manipulating fields is in https://github.com/plutext/docx4j/tree/ ... del/fields

FieldRef contains:



and there is a corresponding setter.

If you want to try using this, you'll probably need to study the source code.

Bear in mind that the spec provides for simple and complex fields. The strategy in that package is to convert simple fields to complex ones, so it can focus on manipulating complex fields only.

What shall be passed in fldCharBegin?

public FieldRef(FldChar fldCharBegin) {
this.fldCharBegin = fldCharBegin;
}

as FieldRef constructor needs an argument of type fieldRef