BUG : The library doesn't see bold and italic In someone else's file

[isajkin]

The library doesn't se bold and italic. By default, an empty node implies the presence of the property (RTF, EXCEL). And you are constantly trying to create a knot and breaking this rule. Example : appendAndGetNode,appendAndGetAttribute,...

t4.zip

[aral-matrix]

Fixed in development branch: d25f089
You are welcome.

[isajkin]

Functions that should not return "false" and "":
vertAlign() ,setbold(),setitalic() .... Excel doesn't understand

[aral-matrix]

I fixed vertAlign, underline and scheme (and setUnderline) in f11bc09

I do not see how setting false for the boolean values of <b> (bold) and <i> (italic) should cause a problem - unless Microsoft is (again) intentionally breaking their own standard:

https://c-rex.net/samples/ooxml/e1/Part4/OOXML_P4_DOCX_b_topic_ID0ESF35.html#topic_ID0ESF35

https://c-rex.net/samples/ooxml/e1/Part4/OOXML_P4_DOCX_i_topic_ID0EYQE6.html#topic_ID0EYQE6

Both tags are defined as

<complexType name="CT_BooleanProperty">
	<attribute name="val" type="xsd:boolean" use="optional" default="true"/>
</complexType>

And for xsd:boolean, valid values are

true
false
1
0

https://www.datypic.com/sc/xsd/t-xsd_boolean.html

Are you sure having a bold setting as <b val="false"/> is not understood correctly by Excel?

[isajkin]

The function vertAlign() must not create a node.

[aral-matrix]

The function vertAlign() must not create a node.

why not? The philosophy I implemented for XLStyles (because it is not performance critical to have explicit values here) is: once a property is requested through the API, it is explicitly set.

https://c-rex.net/samples/ooxml/e1/Part4/OOXML_P4_DOCX_vertAlign_topic_ID0EJTU5.html#topic_ID0EJTU5

That's what the "baseline" value is for.

[aral-matrix]

patch merged into master today