On Mon, 5 Dec 2005 10:53 pm, Luca Furini wrote: > First of all, thanks for your comments: I really tend to forget in a > short time all the details concerning white space! > > Manuel Mall wrote: > > Glyphs are only allowed to be merged if they carry the same / > > matching set of property values. Personally I would not be > > concerned if we therefore limit that logic to within a LM. While it > > is possible that someone could write something like > > <fo:block><fo:inline>a</fo:inline><fo:inline>̈</fo:inline> > > and the a and ̈ could be combined into an &x00e4; IMO this > > is a pretty degenerated case. > > Seems reasonable: so, we can delete glyph substitution from the list > of things we must consider in this phase. > > But, now I think of it, we must consider kerning too, so the list > does not get any thinner! > I wonder if the same argument does apply to kerning as well? The moment you change font-size, text-decoration, background-color, alignment and the like, which is what fo:inline is mainly for, you create a barrier with respect kerning. Or to put it differently, I believe kerning applies only to "like" characters, same as glyph merging.
Of course kerning needs to be considered as part of hyphenation as it may cause some minor width corrections if the hyphen is inserted between two characters who have a non zero kerning pair value. And vice versa if a soft hyphen is removed. But that is a different issue. Side note: Does XSL-FO provide any user control over kerning? I couldn't identify a property an author could use to switch kerning on/off for a particular section of text. Isn't something like that needed for high quality type setting? <snip/> Manuel
