Nadya, Are you sure that all website source files now have CRLFs?
Regards, 2007/3/13, Morozova, Nadezhda <[EMAIL PROTECTED]>:
Oops! The question seems persistent. Help needed :) I've changed the svn settings as required, and because I'm working on Windows, I now have the whole website checked out with CRLF line endings as should be. However, I've got problems when building the site locally: some lines from source files get LF endings out of the blue. Example: File xdocs/auth_cont_quest.xml (CR LF) gets parsed and docs/auth_cont_quest.html appears. Inside it, the header and footer get the required encoding (CR LF), and so do some other lines, like the <h1> heading. However, some lines get the LF end-of-life symbols, all inside <pre> tags. Has anyone experienced something like that? Do you have an idea why this can happen? I tend to blame it on the Velocity parser, but perhaps it's me doing something wrong. Cheers, Nadya >-----Original Message----- >From: Morozova, Nadezhda [mailto:[EMAIL PROTECTED] >Sent: Tuesday, March 13, 2007 3:28 PM >To: [email protected] >Subject: RE: [website] EOL formatting inconsistent > >Thanks. >Done, and this helps. Sorry for reiterating over the old stuff. > >Cheers, >Nadya > > >>-----Original Message----- >>From: Alexei Zakharov [mailto:[EMAIL PROTECTED] >>Sent: Monday, March 12, 2007 2:16 PM >>To: [email protected] >>Subject: Re: [website] EOL formatting inconsistent >> >>So if you are working on Windows then just set this property to >>"native" to all website files, then convert all EOLs in these files to >>"CR LF" and then commit. And everything should be fine :) >> >>Regards, >> >>2007/3/12, Alexey Petrenko <[EMAIL PROTECTED]>: >>> There was an agreement to set eol-style svn property to native and >>> this should fix your issue. >>> Search dev list for this discussion. >>> >>> SY, Alexey >>> >>> 2007/3/12, Morozova, Nadezhda <[EMAIL PROTECTED]>: >>> > Hi, >>> > What's the correct line-ending format for website materials? >>> > I remember we agreed earlier for source files that the UNIX >encoding >>> > (LF) should be used, not Windows (CR LF). Website files were a >mixture >>> > of these, with some files having inconsistent line endings. Is this >ok >>> > that I transferred all the files to UNIX encoding? If so, can we >agree >>> > that we follow the same format in future for consistency? >>> > >>> > Thanks, Nadya
-- Alexei Zakharov, Intel ESSD
