Merge branch 'UnePierre-fix-comparator-constness'

version 1.5.3

version 1.5.2

NEWS: version 1.5.1

update v1.5.0

fix bug capture of requirements from odt documents

Failing use case was a document with:

<text:p text:style-name="P46">
    [
    <text:span text:style-name="T26">REQ-</text:span>
    Aes-Prt
    <text:span text:style-name="T26">-</text:span>
    001]
</text:p>

The fomer use of "xmlNodeListGetRawString" made a concatenation of all
the text contents under the <p>, but without the text within the
<text:span> parts, as follows:

    [
=> xmlNodeListGetRawString returns [Aes-Prt001]
    <text:span text:style-name="T26">REQ-</text:span>
=> xmlNodeListGetRawString returns REQ-
    Aes-Prt
=> xmlNodeListGetRawString returns Aes-Prt001]
    <text:span text:style-name="T26">-</text:span>
=> xmlNodeListGetRawString returns -
    001]
=> xmlNodeListGetRawString returns 001]

The new code, using xmlNodeGetContent, picks each fragment correctly.
As before, reqflow makes the concatenation of the fragments itself.

display all errors in the html report