| Key: |
FOR-492
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Incomplete
|
| Priority: |
Blocker
|
| Assignee: |
Unassigned
|
| Reporter: |
Ross Gardler
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Environment:
|
|
|
Issue Links:
|
Blocker
|
|
|
|
This issue is blocked by:
|
|
|
XALANJ-656 <xsl:copy> introduces inappropriate line-end characters processing comments
|
|
|
|
|
|
|
|
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 LF endings whilst most other lines have CRLF 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?
|
|
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 LF endings whilst most other lines have CRLF 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?
|
Show » |
| No work has yet been logged on this issue.
|
|
Inconsistent Line Endings in generated sites
