Re: [Boost-docs] [quickbook] Problem with [pre element

Subject: Re: [Boost-docs] [quickbook] Problem with [pre element
From: John Maddock (boost.regex_at_[hidden])
Date: 2012-04-12 17:09:00

>> Which doesn't honour the spaces in front of the first "1", but does for 
>> all
>> the others - I've checked BTW that the problem is present in the docbook, 
>> so
>> I assume this is a quickbook issue?
>
> Yes, it has always done that. Looking at the source I fixed it for 1.6
> but didn't for older versions to maintain backwards compatibility.
> I've done that quite a lot because I've found that seemingly sensible
> changes can break things. I should get round to finishing of 1.6, it's
> pretty much ready. I think I just need people to have a look at the
> changes and try them out to see if there's anything they object to or
> want changed.
>
> As a workaround, you can trick quickbook by putting something that
> doesn't cause any output after the pre tag (other than a comment),
> such as an empty template:
>
> [template empty]
> [pre [empty]
>     1
> ]

OK that works, thanks.

BTW this looks like a plain bug to me - stripping newlines after [pre seems 
fair enough, but I can't think of a legitimate use case for stripping all 
whitespace, but, <shrug> I guess ;-)

Thanks, John.