RE : non rendered characters

[Nicolas Mazziotta <Ni...@ulg.ac.be>]

I don't know if I have to report it in bugzilla (or if someone else
will, since I don't know how to do it).

To me it's a severe bug, because no philologue would use FOP knowing
that some characters are not rendered... It is not possible to edit
texts the words of which have been tokenized.

Best regards.

N. Mazziotta


-----Message d'origine-----
De : Keiron Liddle [mailto:keiron@aftexsw.com] 
Envoyé : mercredi 17 avril 2002 14:43
À : fop-user@xml.apache.org
Objet : Re: non rendered characters


This problem is a result of the way the line is built. It has pending 
areas that need to be added to form a word due to different text
elements, 
this happens if you use inline or other xml elements. These areas are 
dropped at the end of the page.

So yes this is a bug.

On 2002.04.17 14:22 Nicolas Mazziotta wrote:
> Hello,
> 
> [I've posted sample.zip with this message; it demonstrates my problem,
> ftp://www.ulg.ac.be/merci/sample.zip]
> 
> I've noticed that text() of tags that occur at page-break as well as
the
> characters that preceed in the same word-unit (surrounded by
> whitespaces) are not rendered at all in PDF and AWT view.
> 
> Look at the beginning of page 15 in the pdf file: 'tensible' for
> 'extensible' [E<fo:inline>x</fo:inline>tensible]; notice that even
> though the first 'e' is not surrounded by any tag, it is not rendered
> either.
> 
> One more thing: if I process a 'simple.xml' file with occurrences like
> [E<r>x</r>tensible], the same happens, even if I dont write any
template
> for the 'r' element.
> 
> Thank you all for your answers.
> 
> N. Mazziotta
> 
>