Re: [Boost-docs] [BoostDocs] Parasit characters generated when C++codeis included directly

Subject: Re: [Boost-docs] [BoostDocs] Parasit characters generated when C++codeis included directly
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2008-04-15 20:35:31

----- Original Message ----- 
From: "John Maddock" <john_at_[hidden]>
To: "Discussion of Boost Documentation" <boost-docs_at_[hidden]>
Sent: Tuesday, April 15, 2008 5:22 PM
Subject: Re: [Boost-docs] [BoostDocs] Parasit characters generated when 
C++codeis included directly

> vicente.botet wrote:
>> Hello,
>>
>> I'm using  quickbook and I have some little problems when including
>> directly C++ code
>>
>> For example, the following quickbook extract:
>> "
>> The Boost (C++0x) mutexes have associated a category which  form a
>> subtyping hierarchy:
>> ExclusiveLock <- SharableLock <- UpgradableLock
>>
>>    exclusive_lock_tag <- sharable_lock_tag <- upgradable_lock_tag
>>
>> Substitutability applies both to the degree of syntactic support and
>> to the locking semantics
>> "
>>
>> generates
>>
>> "
>> <p>
>>        The Boost (C++0x) mutexes have associated a category which
>> form a subtyping
>>        hierarchy: ExclusiveLock &lt;- SharableLock &lt;-
>>      UpgradableLock </p>
>> <pre class="programlisting">
>>    <span class="identifier">exclusive_lock_tag</span> <span
>> class="special">&lt;-</span> <span
>> class="identifier">sharable_lock_tag</span> <span
>> class="special">&lt;-</span> <span
>> class="identifier">upgradable_lock_tag</span>
>>
>> <span class="identifier">i</span></pre>
>> <p>
>>        Substitutability applies both to the degree of syntactic
>> support and to the
>>        locking semantics
>>      </p>
>> "
>>
>> Note the <span class="identifier">i</span> at the end of the
>> "programlisting".
>> The contents of this last span varies from one generation to another.
>> Some time one character other more.
>>
>> Have some one already found similar problems?
>>
>> I use 1.35.0 on cygwin.
>
> Hmmm, did you build quickbook with cygwin?  It could be some issue with
> Windows vs Unix line ending styles, I've seen similar issues in the past,
> but not for a long while thankfully.  Can you try using a regular Win32
> build of quickbook (either with Mingw or VC++ and see if that fixes 
> things?
>
> Likewise, it might be best to use the native Win32 versions of xsltproc 
> etc.
>
> HTH, John.

Thanks John,

I have do a dos2unix for all the .qbk files and now it works well.

Is there a simple way to automate this on the Jamfile?

Best

_____________________
Vicente Juan Botet Escriba