Thank you very much! I've just applied the updated patch you sent me
off-list. I had some problems applying it since some of the lines were
broken. It would be best to attach the patch as a file next time.

On 07.06.2005 17:48:18 Hock Szabolcs wrote:
> Hi! 
> 
> I have the same problem  with text-transform1.xml and
> text-transform2.xml.
> The SAXParser splits the text into two parts and the FOText converts the
> second part's first character to uppercase.
> It is possible because the SAX specification allows it.
> "Note too that there is no promise that the output will be sent as a
> single call. As is always true in SAX, one logical string may be split
>  across multiple blocks of memory and hence delivered as several
> successive events."
> 
> the generated xml fragment for text-transform1.xml
> <block bap="0 0 0 0" bpd="14400" bpda="14400" ipd="360000"
> ipda="360000">
>       <lineArea bap="0 0 0 0" bpd="14400" bpda="14400" ipd="0">
>               <text color="#000000" font-family="F1" font-size="12000"
> vpos="10266">capitalize: </text>
>               <text color="#000000" font-family="F1" font-size="12000"
> vpos="10266">This T</text>
>               <text color="#000000" font-family="F1" font-size="12000"
> vpos="10266">Ext Is Capitalized.</text>
>       </lineArea>
> </block>
> 
> I managed to solve this problem by concatenating these parts and convert
> them when addChildNode or endOfNode call occur.
> The tests now passed, the generated xml:
> <block bap="0 0 0 0" bpd="14400" bpda="14400" ipd="360000"
> ipda="360000">
>       <lineArea bap="0 0 0 0" bpd="14400" bpda="14400" ipd="0">
>               <text color="#000000" font-family="F1" font-size="12000"
> vpos="10266">capitalize: </text>
>               <text color="#000000" font-family="F1" font-size="12000"
> vpos="10266">This Text Is Capitalized.</text>
>       </lineArea>
> </block>



Jeremias Maerki

Reply via email to