- From: Grosso, Paul <pgrosso@ptc.com>
- Date: Wed, 18 Jan 2006 15:07:42 -0500
- To: "Manuel Mall" <mm@arcus.com.au>, <xsl-editors@w3.org>
Thank you for your input here. Since this issue exists in XSL 1.0, and the SG is busy trying to get out a Candidate Recommendation for XSL 1.1, we plan to handle this as a potential erratum to XSL 1.0 (which, if requiring a change to the spec, will be rolled into the XSL 1.1 spec before it becomes a Recommendation). What that means in practice is that we won't let this issue hold up our plan to take XSL 1.1 to CR in the near future, but we will consider this issue as soon as possible thereafter. Paul Grosso for the XSL FO SG > -----Original Message----- > From: xsl-editors-request@w3.org > [mailto:xsl-editors-request@w3.org] On Behalf Of Manuel Mall > Sent: Friday, 2005 October 21 1:41 > To: xsl-editors@w3.org > Subject: Overconstraint alignment > > > Dear Editors, > > With respect to line areas there can be conflicting or overconstraint > alignment specifications. I couldn't find a reference to that > situation in > the specification. Example: > > <fo:block font-size="32pt">Big > <fo:inline font-size=".25em" > dominant-baseline="reset-size" > alignment-baseline="before-edge">top > <fo:inline font-size="2em">alpha > </fo:inline> > </fo:inline> > </fo:block> > > Here we want "top" at the before-edge of the line area but > the nested inline > "alpha" wants to be aligned at the alphabetic baseline of > "top". Because > "alpha" uses a bigger font than "top" these two conditions cannot be > satisfied simultaneously. It is unclear to me how this is to > be resolved. > > Thank you very much > > Manuel Mall >
Received on Wednesday, 18 January 2006 20:07:45 UTC