Hi jfeise,

Is this specific to a skin?
I am pretty sure all hardcoded line endings are "\n" in the B2evolution package. However soft line endings (those made by the editor used) may well be CR/LF (depending on the developer ;) but I don't know a case where that could matter.
If you are complaining about the 'ugly' sourcecode generated especially in the sidebars, that's a known problem.

Good luck

Afwas wrote:

Hi jfeise,

Is this specific to a skin?
I am pretty sure all hardcoded line endings are "\n" in the B2evolution package. However soft line endings (those made by the editor used) may well be CR/LF (depending on the developer ;) but I don't know a case where that could matter.

As far as I know, it applies to all files. I didn't see rendering anywhere, not on the admin pages, and not on the blog.
I wasn't aware that it matters, either, but the Firefox error console told me that the browser ignored the CSS because it was not sent as text/css MIME type. This may also have been some weird caching by Apache. I restarted Apache. In any case, it had baffled me the whole day yesterday, until I got the idea to check the Firefox error console. And as soon as I changed the line endings, and only in one file, skins/evopress/style.css, the problem went away. This was also certainly not caching in the browser, since I tried it with a fresh Firefox on a Solaris machine, and had the same issue there.

If you are complaining about the 'ugly' sourcecode generated especially in the sidebars, that's a known problem.

I can live with that, as long as it is valid HTML.