Manuel Mall wrote:
Side note: FOP doesn't quite do the same internally, i.e. a character
explicitly specified using <fo:character.../> is handled separately from
'plain text'. If someone would write a style sheet which does a
transform of every character into a <fo:character /> object and would
feed the output to FOP the formatting results would be lets say VERY
DISAPPOINTING. Actually something like: <fo:block
background-color="yellow">word1<fo:character character="
"/><fo:character character= " "/>word2<fo:character character="
"/>word3<fo:character character=" "/></fo:block> currently causes an
exception!
This is a problem of the whitespace-related code, but anyway the
CharacterLM always creates a sequence of element corresponding to a
non-space character, so the only feasible breaks recognized by the
algorithm would be the hyphenation points inside the words ...
I think that just as TextArea and Character both extend an
AbstractTextArea, TextLM and CharLM should have a common super class
holding the createElementsFor*() methods. It would not be necessary to add
a SpaceArea or a WordArea child to a Character area, anyway (but we could
decide to do it anyway just for analogy).
Regards
Luca
