Saxon

While trying to identify the line number and line position/column number of attribute nodes, I find that both SaxonCS and Saxon.NET seem to just assign the line position/column number of the start element the attribute belongs to, not the attribute's line position/column number itself.

The .NET XmlReader seems to output a more precise line position/column number for attribute nodes, however, so perhaps Saxon can be improved.

Here is some sample code using SaxonCS and .NET 6 and XmlReader:

using Saxon.Api;
using System.Xml;

var processor = new Processor();

var docBuilder = processor.NewDocumentBuilder();

docBuilder.LineNumbering = true;

docBuilder.BaseUri = new Uri("urn:from-string");

const string mixedContent = @"<text>This is <b id=""b1"" style=""font-weight: bold;"">mixed</b> content: <!-- test -->Can XPath tools select a text node?</text>";

var xdmDoc = docBuilder.Build(new StringReader(mixedContent));

foreach (XdmNode node in processor.NewXPathCompiler().Evaluate("//@*", xdmDoc))
{
    Console.WriteLine($"Node {node}; line: {node.LineNumber}; column: {node.ColumnNumber}");
}

using (var xr = XmlReader.Create(new StringReader(mixedContent)))
{
    while (xr.Read())
    {
        //Console.WriteLine($"Node {xr.NodeType}; Value: {xr.Value}; Line: {((IXmlLineInfo)xr).LineNumber}; Column: {((IXmlLineInfo)xr).LinePosition}");
        if (xr.HasAttributes)
        {
            xr.MoveToFirstAttribute();
            do
            {
                Console.WriteLine($"Node {xr.NodeType}; Value: {xr.Value}; Line: {((IXmlLineInfo)xr).LineNumber}; Column: {((IXmlLineInfo)xr).LinePosition}");
            }
            while (xr.MoveToNextAttribute());
        }
    }
}

Output I get is e.g.

Node id="b1"; line: 1; column: 16
Node style="font-weight: bold;"; line: 1; column: 16
Node Attribute; Value: b1; Line: 1; Column: 18
Node Attribute; Value: font-weight: bold;; Line: 1; Column: 26

So for both attribute nodes (id and style) Saxon reports 16 (which is the b element's column) for the column/line position while the reader has the right 18 and 26.

Known flaw/shortcoming?

Any settings to get better results?