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</bookmark_value></root> ^ Entity: line 1: parser error : Premature end of data in tag root line 1 okmark_value>Solver for Nonlinear Problems;Options</bookmark_value></root> ^ DBG> <root><bookmark_value>Solver for Nonlinear Problems;Options</bookmark_value></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</emph> (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</emph>, 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>, 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>, the library is simply filled up with randomly chosen points.</root> ^ DBG> <root>If <emph>enabled</emph>, 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</emph>, 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</emph>, 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"
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.
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.
http://lists.freedesktop.org/archives/libreoffice/2015-September/070405.html
(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
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
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.
Created attachment 122142 [details] for example, here is translations/source/is/svx/inc.po (icelandic)
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Sun, 11 Sep 2016 21:43:24 +0200
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20161010