On 21 May 2010 11:23, Richard Quadling <rquadl...@googlemail.com> wrote:
> On 21 May 2010 11:15, Richard Quadling <rquadl...@googlemail.com> wrote:
>> On 21 May 2010 10:08, Philip Olson <phi...@roshambo.org> wrote:
>>>>
>>>> The problem is not the tags per se. I can and have successfully
>>>> compiled all the manuals I've altered (en, es, fa, fr, ja, tr) from
>>>> the XML through to a Windows CHM (I'm on Windows after all).
>>>>
>>>> I'm not getting the warnings that you are seeing.
>>>
>>> For example, add <para>FOO</para> to strlen.xml outside of a refsect1 and
>>> you'll see the datetime xcinlude errors along with the real error. It's
>>> confusing, and annoying, but I'm unsure how to solve said annoyance.
>>>
>>> Regards,
>>> Philip
>>>
>> configure.php already suppresses xinclude errors when the errors are
>> being reported ( see print_xml_errors() ).
>>
>> It would seem that we also need to include the ability to suppress
>> xpointer errors.
>>
>> But sometimes the errors may be needed, so I think the option
>> --enable-xml-details should show the xinclude and the xpointer errors.
>>
>> Using ...
>>
>> if ($details || (!strpos($err->message, 'xi:include') &&
>> !strpos($err->message, 'element include') && False ===
>> strpos($err->message, 'XPointer evaluation failed:'))) {
>>
>> will now also suppress the XPointer errors, but show all the errors if
>> the --enable-xml-details option is enabled.
>>
>> Enough do you think?
>
> Nope. Seems that there are a LOT of errors which we suppress. Maybe
> something to work on there.
>
> So, going to just suppress the XPointer evaluation errors along with
> the other errors.
The warnings are being generated by the DOMDocument::xinclude() call,
not as part of the reporting that configure.php does when errors are
found which I've fixed when the xml is invalid.
It also seems that xinclude() is reporting warnings and not errors.
Errors would break the configure.
So, the only option I can see is to use ...
$dom->xinclude(LIBXML_NOWARNING);
on line 615 ($Id: configure.php 299572 2010-05-21 11:04:34Z rquadling $)
But I can't determine the efficacy of this without being able to
generate the fault in the first place. Also, it may suppress other
warnings which are not related to this issue.
The online editor is using libxml 2.7.5 compared to my 2.7.3 ( Anyone
help me upgrade my libxml please?)
Regards,
Richard.
--
-----
Richard Quadling
"Standing on the shoulders of some very clever giants!"
EE : http://www.experts-exchange.com/M_248814.html
EE4Free : http://www.experts-exchange.com/becomeAnExpert.jsp
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
ZOPA : http://uk.zopa.com/member/RQuadling
