Fw: Forrestbot + SVN = mixed line-endings in HTML

["Gav...." <br...@brightontown.com.au>]

erm, sent this 12 hours ago to user@ , never got there so posting it here.


----- Original Message ----- 
From: "Gav...." <br...@brightontown.com.au>
To: <us...@forrest.apache.org>
Sent: Friday, March 03, 2006 7:17 AM
Subject: Re: Forrestbot + SVN = mixed line-endings in HTML


> Just a passing comment that may not have relevence.
>
> In one of my user forums, someone who is much better at xslt than me
> stated not to
> use <xsl:copy> with xslt 1.0 .
>
> I have asked him why he thinks this, and pointed him to the XALANJ-656
> issue to
> see whether he thinks it relevent or not in this case.

Just adding, I think he may be talking about specific xsl:copy methods
introduced in 2.0, but it was interesting he recomended using
apply-templates instead of. Would using apply-templates in this case
be a viable alternative to try or not. Apologies for showing my ignorance
here, still haven't got my head round xsl yet.


>
> Gav...
>
> ----- Original Message ----- 
> From: "Ross Gardler" <rg...@apache.org>
> To: <us...@forrest.apache.org>
> Sent: Friday, March 03, 2006 12:58 AM
> Subject: Re: Forrestbot + SVN = mixed line-endings in HTML
>
>
>> X-SpamKiller-AcctId: 1
>> X-SpamKiller-MsgId: 1129546381.12724
>>
>> Web Maestro Clay wrote:
>>> We have a new problem using forrestbot. Part of this could be my own
>>> settings, but I am assured by Jeremias that this isn't completely the
>>> case. Please see below.
>>>
>>>> On 02.03.2006 00:12:42 Clay Leeds wrote:
>>>>
>>>>> On Mar 1, 2006, at 1:28 PM, Jeremias Maerki wrote:
>>>>>
>>>>>> Wonderful. Just what I need. Different platforms, different line
>>>>>> endings, no SVN properties set. And if I want to manually set  them,
>>>>>> SVN
>>>>>> complains about mixed line endings in HTML files. Clay, would you
>>>>>> mind
>>>>>> asking the Forrest people how they deal with that or how we're
>>>>>> supposed to deal
>>>>>> with this? I'm not very amused to process each file separately
>>>>>> until I have consistent line-endings and the right SVN properties
>>>>>> and the
>>>>>> next Forrest run might even take everything apart again. I liked  the
>>>>>> scp
>>>>>> approach better. Sigh.
>>>>>
>>>>>
>>>>> My bad... I don't have my SVN settings correct. I need to set my
>>>>> svn:eol-style property to 'native' & then this shouldn't be a
>>>>> problem. Sorry for the grief!
>>>>>
>>>>> I've made the change locally. I need to also do the same for my other
>>>>> projects.
>>>>
>>>>
>>>> Part of that may be due to your SVN settings, but I got mixed line
>>>> endings in HTML files generated by Forrest. I haven't checked, yet,
>>>> why
>>>> this happens but that probably doesn't happen because of your SVN
>>>> settings.
>>>>
>>>> Jeremias Maerki
>>>
>>>
>>> Please advise.
>>
>>
>> Can't be certain without more info about the specific problem. However, I
>> strongly suspect this is a symptom of
>> http://issues.apache.org/jira/browse/FOR-492
>>
>> This, in turn, is caused by
>> http://issues.apache.org/jira/browse/XALANJ-656
>>
>> I'd like to say "its not our fault", but this Xalan is open source, just
>> like Forrest, any one of us could fix the problem. Who will get the itch
>> first?
>>
>> Ross
>>
>> Ross
>

Re: Fw: Forrestbot + SVN = mixed line-endings in HTML

[Ross Gardler <rg...@apache.org>]

Gav.... wrote:
> erm, sent this 12 hours ago to user@ , never got there so posting it here.
> 
> 
> ----- Original Message ----- From: "Gav...." 
> <br...@brightontown.com.au>
> To: <us...@forrest.apache.org>
> Sent: Friday, March 03, 2006 7:17 AM
> Subject: Re: Forrestbot + SVN = mixed line-endings in HTML
> 
> 
>> Just a passing comment that may not have relevence.
>>
>> In one of my user forums, someone who is much better at xslt than me
>> stated not to
>> use <xsl:copy> with xslt 1.0 .
>>
>> I have asked him why he thinks this, and pointed him to the XALANJ-656
>> issue to
>> see whether he thinks it relevent or not in this case.
> 
> 
> Just adding, I think he may be talking about specific xsl:copy methods
> introduced in 2.0, but it was interesting he recomended using
> apply-templates instead of. Would using apply-templates in this case
> be a viable alternative to try or not. Apologies for showing my ignorance
> here, still haven't got my head round xsl yet.

Apply templates is not really an option. It can be done, of course, But 
creates a maintenance problem. One of the reasons for using an internal 
format that is as close as possible to XHTML is so that we don't have to 
   create templates for every single element in the transformation process.

Ross