[ 
https://issues.apache.org/jira/browse/XALANJ-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510519
 ] 

Eric Kolotyluk commented on XALANJ-2387:
----------------------------------------

Brian, I disagree.

In the case of pretty-printing you 'do' know the intent of what will be done 
with the generated XML - it will be read by a person who does not care if the 
newline generates a new node. If someone wants to preserve the syntatic 
correctness of the XML they they should not use pretty-printing.

I can see no other use for pretty printing than to make it easier for people to 
read.

- Eric Kolotyluk

> Pretty Print Serialization does not put newlines between all elements
> ---------------------------------------------------------------------
>
>                 Key: XALANJ-2387
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2387
>             Project: XalanJ2
>          Issue Type: Bug
>    Affects Versions: 2.7
>         Environment: Windows XP and Apple OS X
>            Reporter: Eric Kolotyluk
>            Priority: Trivial
>
> When pretty-printing is specified in LSSerializer newlines are not placed 
> between all elements. For example.
> <?xml version="1.0" encoding="UTF-8"?><User clientName="EKolotyluk_380" 
> clientPlatform="Windows XP (5.1)" 
> clientProtocolVersion="{DB4AEBDF-A4A9-4521-880B-02310D12723B}" 
> clientType="Admin" clientVersion="0.0.0.0" 
> cookie="-7dfe3a9b:11377ee20de:-7fdd" isoLanguageCode="en" 
> sendCompressed="true" type="checkProtocolVersion"/>
> the <User> element should start on a new line.
> While this is a Trivial problem, it is blocking me from transitioning my code 
> from the deprecated XMLSerializer to the official LSSeralizer.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to