Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: 
 <22163275.1115392117432.JavaMail.jettyjira@strider.outerthought.net>
Date: Fri, 6 May 2005 10:08:37 -0500 (CDT)
From: issues@cocoondev.org
To: dev@forrest.apache.org
Subject: [JIRA] Updated: (FOR-492) Inconsistent Line Endings in generated
 sites
In-Reply-To: 
 <31801971.1115391877415.JavaMail.jettyjira@strider.outerthought.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

The following issue has been updated:

    Updater: Ross Gardler (mailto:ross@saafe.org)
       Date: Fri, 6 May 2005 10:07 AM
    Changes:
             summary changed from Inconsitent Line Endings in generated sites to Inconsistent Line Endings in generated sites
             description changed from Sites generated by Forrest have inconsitent line endings when created on a Windows platform. 

I did a little testing, here's what I have discovered so far:
 
- any file that is processed by XSLT has the line endings problem
- on investigating one such file (index.html) I discovered that the  generated comments from site2xhtml.xsl (such as breadtrail comment) have 
 CRLF endings whilst most other lines have LF endings.
 
I'm running on Windows, and get the same results whether I run under 
CYGWIN or DOS.
 
To reproduce cd into any plugin directory, do "ant docs" and check out 
the generated docs in build/site.

This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default.

Is there a way to tell the XSLT transformer what line endings to use?
 to Sites generated by Forrest have inconsistent line endings when created on a Windows platform. 

I did a little testing, here's what I have discovered so far:
 
- any file that is processed by XSLT has the line endings problem
- on investigating one such file (index.html) I discovered that the  generated comments from site2xhtml.xsl (such as breadtrail comment) have  CRLF endings whilst most other lines have LF endings.
 
I'm running on Windows, and get the same results whether I run under 
CYGWIN or DOS.
 
To reproduce run "forrest site" in any site and check out the generated docs in build/site.

This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default.

Is there a way to tell the XSLT transformer what line endings to use?

             Fix Version changed to 0.8
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.cocoondev.org//browse/FOR-492?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-492

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-492
    Summary: Inconsistent Line Endings in generated sites
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Forrest
 Components: 
             Core operations
   Fix Fors:
             0.8
   Versions:
             0.7-dev

   Assignee: 
   Reporter: Ross Gardler

    Created: Fri, 6 May 2005 10:04 AM
    Updated: Fri, 6 May 2005 10:07 AM
Environment: Windows (with or without CYGWIN)

Description:
Sites generated by Forrest have inconsistent line endings when created on a Windows platform. 

I did a little testing, here's what I have discovered so far:
 
- any file that is processed by XSLT has the line endings problem
- on investigating one such file (index.html) I discovered that the  generated comments from site2xhtml.xsl (such as breadtrail comment) have  CRLF endings whilst most other lines have LF endings.
 
I'm running on Windows, and get the same results whether I run under 
CYGWIN or DOS.
 
To reproduce run "forrest site" in any site and check out the generated docs in build/site.

This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default.

Is there a way to tell the XSLT transformer what line endings to use?


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira