This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4420 - Get XML::LibXML to output error countext beyond 80 characters, or output
Summary: Get XML::LibXML to output error countext beyond 80 characters, or output
Status: RESOLVED DUPLICATE of bug 6329
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: HEAD
Hardware: All All
: P2 enhancement
Target Milestone: 1.0
Assignee: Olivier Thereaux
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-29 06:05 UTC by Olivier Thereaux
Modified: 2009-02-02 23:20 UTC (History)
0 users

See Also:


Attachments

Description Olivier Thereaux 2007-03-29 06:05:21 UTC
libxml2 (and thus XML::LibXML) has a hardcoded limit of 80 columns (old skool!) for its xml parsing errors, hence making it almost impossible to know the exact context of the error. 

e.g:
http://www.opensource.apple.com/darwinsource/WWDC2003/libxml2-3/libxml2/error.c
    /* search backwards for beginning-of-line maximum 80 characters */

I have a (sad) workaround in the validator for that issue, but ideally, libxml would fix it by either:
* having an option to output the whole list
* having an option (similar to $parser->line_numbers(1)) to output the column number too

The latter would be best, but either would do.

Recording this as a bug in the validator, so that we don't let the workaround sit forever.
Comment 1 Olivier Thereaux 2007-04-04 04:35:27 UTC
As correctly pointed out by DV in http://bugzilla.gnome.org/show_bug.cgi?id=424017 the libxml2 API does allow for context info to be properly reported with parsing errors. Will take that to the implementors of the perl binding.
Comment 2 Olivier Thereaux 2009-02-02 23:20:42 UTC
With the advent of structured errors, and provided the bug explained in Bug 6329 gets fixed in XML::LibXML 1.70, this bug becomes moot.

*** This bug has been marked as a duplicate of bug 6329 ***