Bug #6063: Incorrect attribute indentation - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #6063

closed

Incorrect attribute indentation

Added by Michael Kay 11 months ago. Updated 8 months ago.

Status:

Closed

Priority:

Normal

Assignee:

Michael Kay

Category:

Serialization

Sprint/Milestone:

Start date:

2023-06-05

Due date:

% Done:

100%

Estimated time:

Legacy ID:

Applies to branch:

11, 12, trunk

Fix Committed on Branch:

11, 12, trunk

Fixed in Maintenance Release:

12.3, 11.6

Platforms:

.NET, Java

Description

The number of spaces output before an indented attribute is one too many. We are seeing, for example

<isee:ISEE-Event xmlns="http://www.example.com/schemas/ex/5.00"
__________________xmlns:isee="http://www.w3.org/2001/XMLSchema-instance/isee"
__________________xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
__________________schemaVersion="5.00">

with 18 spaces rather than 17 on lines 2, 3, and 4.

Problem was raised on StackOverflow, see https://stackoverflow.com/questions/76405207/saxon-he-9-x-11-x-12-x-indentation-differences-depending-on-operating-system/76408103#76408103

and subsequent discussion.

Actions

Copy link

Updated by Michael Kay 11 months ago

Description updated (diff)

Actions

Copy link

Updated by Michael Kay 11 months ago

Status changed from New to Resolved
Fix Committed on Branch 11, 12, trunk added

Actions

Copy link

Updated by Michael Kay 11 months ago

Changed XMLIndenter.startElement() from

             if (len > getLineLength()) {
                int indent = (level - 1) * getIndentation() + 3;
                emitter.setIndentForNextAttribute(indent);
            }

            if (len > getLineLength()) {
                int indent = (level - 1) * getIndentation() + 2;
                emitter.setIndentForNextAttribute(indent);
            }

Actions

Copy link

Updated by Michael Kay 11 months ago

Note, I have not investigated the suggestion that this varies by operating system. It seems too implausible; it seems highly likely that the user was running different Saxon versions on the different platforms.

Actions

Copy link