Bug 94641 - issues with vtags and xmlParseMemory
Summary: issues with vtags and xmlParseMemory
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Localization (show other bugs)
Version:
(earliest affected)
5.0.2.2 release
Hardware: Other Solaris
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-30 13:26 UTC by Richard PALO
Modified: 2016-10-10 11:13 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
grep "Warning :" screen.log.0 (69.36 KB, text/plain)
2016-01-22 08:15 UTC, Richard PALO
Details
for example, here is translations/source/is/svx/inc.po (icelandic) (11.65 KB, text/x-gettext-translation)
2016-01-22 08:17 UTC, Richard PALO
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Richard PALO 2015-09-30 13:26:51 UTC
As an isolated mention on the dev list a while back, I decided to add a debug output on error return from xmlParseMemory in helper.cxx to see the whole string that is failing in the call...

Here are a few lines:

Entity: line 1: parser error : Opening and ending tag mismatch: bookmark_value line 1 and root
okmark_value>Solver for Nonlinear Problems;Options&lt;/bookmark_value&gt;</root>
                                                                               ^
Entity: line 1: parser error : Premature end of data in tag root line 1
okmark_value>Solver for Nonlinear Problems;Options&lt;/bookmark_value&gt;</root>
                                                                               ^
DBG> <root><bookmark_value>Solver for Nonlinear Problems;Options&lt;/bookmark_value&gt;</root>
Entity: line 1: parser error : Opening and ending tag mismatch: emph line 1 and root
olations and only if those are equal, it measures their current solution.</root>
                                                                               ^
Entity: line 1: parser error : Premature end of data in tag root line 1
olations and only if those are equal, it measures their current solution.</root>
                                                                               ^
DBG> <root>If <emph>disabled&lt;/emph&gt; (default), the BCH Comparator is used. It compares two individuals by first looking at their constraint violations and only if those are equal, it measures their current solution.</root>
Entity: line 1: parser error : Opening and ending tag mismatch: emph line 1 and root
braries worst known solutions (in regard to their constraint violations).</root>
                                                                               ^
Entity: line 1: parser error : Premature end of data in tag root line 1
braries worst known solutions (in regard to their constraint violations).</root>
                                                                               ^
DBG> <root>If <emph>enabled&lt;/emph&gt;, the ACR Comparator is used. It compares two individuals dependent on the current iteration and measures their goodness with knowledge about the libraries worst known solutions (in regard to their constraint violations).</root>
Entity: line 1: parser error : Opening and ending tag mismatch: emph line 1 and root
t;/emph&gt;, the library is simply filled up with randomly chosen points.</root>
                                                                               ^
Entity: line 1: parser error : Premature end of data in tag root line 1
t;/emph&gt;, the library is simply filled up with randomly chosen points.</root>
                                                                               ^
DBG> <root>If <emph>enabled&lt;/emph&gt;, the library is simply filled up with randomly chosen points.</root>
Entity: line 1: parser error : Opening and ending tag mismatch: emph line 1 and root
es (as given by the user) are inserted in the library as reference point.</root>
                                                                               ^
Entity: line 1: parser error : Premature end of data in tag root line 1
es (as given by the user) are inserted in the library as reference point.</root>
                                                                               ^
DBG> <root>If <emph>disabled&lt;/emph&gt;, the currently present values (as given by the user) are inserted in the library as reference point.</root>
Entity: line 1: parser error : Opening and ending tag mismatch: emph line 1 and root
 known solution as well as the possibility, to stop or resume the solver.</root>
                                                                               ^
Entity: line 1: parser error : Premature end of data in tag root line 1
 known solution as well as the possibility, to stop or resume the solver.</root>
                                                                               ^
DBG> <root>If <emph>enabled&lt;/emph&gt;, an additional dialog is shown during the solving process which gives information about the current progress, the level of stagnation, the currently best known solution as well as the possibility, to stop or resume the solver.</root>


There seems to be various issues with the vtag processing.

Pour info, I'm using libxml2
>#define LIBXML_DOTTED_VERSION "2.9.2"
Comment 1 Buovjaga 2015-10-02 13:13:16 UTC
Please give more information on what you are doing + link to the mailing list post.

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
Comment 2 Richard PALO 2015-10-02 14:18:30 UTC
here is the forwarded header of the discussion:
-------- Message original --------
Sujet: Re: errors building wikisend.xhp
Date : Wed, 30 Sep 2015 16:57:48 +0200
De : Richard PALO <richard@netbsd.org>
Pour : libreoffice@lists.freedesktop.org
Groupes de discussion: gmane.comp.documentfoundation.libreoffice.devel
Références : <mkjgbr$r1u$1@ger.gmane.org>


you may need to have to configure with '--with-lang="ALL"'
to see any issue.
Comment 4 Robinson Tryon (qubit) 2016-01-17 18:49:00 UTC
(In reply to Richard PALO from comment #0)
> As an isolated mention on the dev list a while back, I decided to add a
> debug output on error return from xmlParseMemory in helper.cxx to see the
> whole string that is failing in the call...
> ...
> Entity: line 1: parser error : Opening and ending tag mismatch:

Hi Richard,
Thanks for doing some digging in the internals here. A few q's for you:
1) Do you have a document or particular repro steps to trigger this parse error?
2) Can you reproduce this problem with a 5.1 or master build?
3) Can you confirm this is a Solaris-only bug?

Thanks!

Status -> NEEDINFO
Comment 5 Richard PALO 2016-01-21 19:21:22 UTC
Having passed to 5.1.0 I haven't seen this yet again.
I kinda believe that it perhaps was related to a bison issue on the base
platform (omnios) which perhaps was missing i18n support.

Being on pkgsrc, I forced using pkgsrc for most of the utilities now
and I haven't seen it directly for a time.  I'm trying a
Comment 6 Richard PALO 2016-01-22 08:15:22 UTC
Created attachment 122141 [details]
grep "Warning :" screen.log.0

Not sure, but with 5.1.0.2 I see the attached warnings, seems to be in about the same area so I wonder if these are related or not, in which case I should file a new bug report.
Comment 7 Richard PALO 2016-01-22 08:17:38 UTC
Created attachment 122142 [details]
for example, here is translations/source/is/svx/inc.po  (icelandic)
Comment 8 Xisco Faulí 2016-09-11 21:40:45 UTC Comment hidden (obsolete)
Comment 9 Xisco Faulí 2016-10-10 11:13:05 UTC Comment hidden (obsolete)