Reece Dunn wrote:
John Maddock wrote:
Hi all,
The line ending code for quickbook appears to be broken again: when
building under cygwin if the quickbook files have \r\n endings then
I'm getting garbage inserted at the end of various block-level
elements. Stripping the \r's from the quickbook files fixes the
problem, but it's a far from ideal solution.
Isn't there an end-of-line parser (eol_p?) that's supposed to handle
line ending issues to cope with the various possibilities (Linux, Mac
and Windows)? If so:
1. Is quickbook using it?
2. If it is, then why is it broken?
3. If not, then why isn't it?
Well... Yes there is. 1. yep; 2. it isn't; 3. should it be broken? ;-)
I think that quickbook parses the line-endings nicely. The problem is
that it currently outputs mixed line-endings. One place where I noticed
this problem is inside code blocks: EOLs in code blocks come out as they
come in, while in other places most get replaced with a single '\n'.
A workaround is to convert qbk source files to use exclusively '\n' line
endings... but of course the proper place to fix this once and for all
is in quickbook.
I'll have a go at it later, if no one beats me to it.
Regards,
João Abecasis
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Boost-docs mailing list
[email protected]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
