[ https://jira.codehaus.org/browse/DOXIASITETOOLS-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359616#comment-359616 ]
Herve Boutemy commented on DOXIASITETOOLS-88: --------------------------------------------- bq. we aren't talking about fixing mixed line breaks but nomalization to the currently used platform, right? exactly: DOXIASITETOOLS-87 was about fixing mixed line endings your expanded description of what is expected is exactly what I summarised in the issue description, even if in real world, I don't expect a skin to have different line endings for each files the issue is just that a Unix end-user using a skin built on Windows will get Windows line endings for files taken from the skin and the opposite: a Windows end-user using a skin built on Unix will get Unix line-endingsg for files taken from the skin > normalize newlines of text resources copied from skin > ----------------------------------------------------- > > Key: DOXIASITETOOLS-88 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-88 > Project: Maven Doxia Sitetools > Issue Type: Bug > Components: Site renderer > Reporter: Herve Boutemy > Priority: Minor > > text resources from skin (*.css, *.js, ...) are copied in binary form > but since the skin jar is done on one machine and reused on multiple other > ones, not necessarily same platform, these files can have newlines > inconsistent with actual platform > Notice: I don't know if this is a severe problem, as severe as > DOXIASITETOOLS-87, where inconsistency happened inside text files -- This message was sent by Atlassian JIRA (v6.1.6#6162)