--- Xavier Hanin <[EMAIL PROTECTED]> wrote:

> On 5/31/07, Matt Benson <[EMAIL PROTECTED]>
> wrote:
> >
> > Guys, can I interject a dumb question and ask why
> > Xooki must use LF endings?
> 
> 
> The question is not dumb, xooki is :-)
> The problem is that when you use xooki to edit a
> page, xooki writes the
> page. And when it writes the page, it uses '\n' for
> eol whatever the
> platform is. Thus you end up with LF whatever your
> platform, so using
> eol-style 'native' does not work with xooki.
> 
> But fixing this in xooki shouldn't be too long, so
> if it's a problem to use
> LF as eol-style for these pages, I'll try to fix
> xooki.

My understanding of the svn property is that it will
store the files however it sees fit and on checkout
will give them to the user in his native EOL.  IOW,
there is no conflict.  Xooki can do whatever it wants
to your templates, you can check them in (with
eol-style set) and everybody will be happy.  This
presumes that Xooki can handle as input any eol thrown
at it.  I noticed the \r?\n regex in use in Xooki.js
so the only problem situation I can foresee ATM is if
Xooki were used on a platform with \r as its default
separator as the regex doesn't handle this, but (1)
that should be easily fixable, and (2) there are
probably very few people developing Ivy (or any other
sf package using Xooki for its documentation ;) ) on
such a platform.

WDYT?

-Matt

> 
> Xavier
> 
> -Matt
> >
> >
> >
> >
> >
> >
>
____________________________________________________________________________________
> > Get the Yahoo! toolbar and be alerted to new email
> wherever you're
> > surfing.
> >
>
http://new.toolbar.yahoo.com/toolbar/features/mail/index.php
> >
> 
> 
> 
> -- 
> Xavier Hanin - Independent Java Consultant
> Manage your dependencies with Ivy!
> http://incubator.apache.org/ivy/
> 



       
____________________________________________________________________________________
Sick sense of humor? Visit Yahoo! TV's 
Comedy with an Edge to see what's on, when. 
http://tv.yahoo.com/collections/222

Reply via email to