forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <>
Subject [jira] Commented: (FOR-492) Inconsistent Line Endings in generated sites
Date Wed, 19 Apr 2006 08:26:17 GMT
    [ ] 

Gavin commented on FOR-492:

As far as I can see, all lines on Windows from a generated .html file all end with CRLF.
Also I see no difference in the way comments are treated as previously mentioned.

Example code from an index.html file.

Oops, sorry cant paste code - the ^M gets converted to a CRLF !!, I'll attach a file instead.

This Wikipedia explains the difference between the 3 main OS versions and their handling.
I blame it on CP/M myself :)

> Inconsistent Line Endings in generated sites
> --------------------------------------------
>          Key: FOR-492
>          URL:
>      Project: Forrest
>         Type: Bug

>   Components: Core operations
>     Versions: 0.7
>  Environment: Windows (with or without CYGWIN)
>     Reporter: Ross Gardler
>     Priority: Blocker
>      Fix For: 0.8-dev

> 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 
> 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?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message