DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44343>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=44343

           Summary: font-size in percentage error
           Product: Fop
           Version: 0.94
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: pdf
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


Error occurs in the combination of <fo:inline> of font-size="smaller"/"bigger" 
within <fo:block> of font-size in percentage. The error is "getBaselength 
called without context".
  
  <fo:block font-style="normal" font-size="80%" role="html:div"
    <fo:inline baseline-shift="super" font-size="smaller" 
role="html:sup">th</fo:inline>of each month. 
  </fo:block>

=====Original Post on fop-users mailing list===========
On Feb 1, 2008, at 18:36, Li, Hao wrote:

> You are right. The sample I posted actually works. I apologize not 
> recognizing the real problem. It is tricky and only occurs in the 
> combination of <fo:inline> of font-size="smaller"/"bigger" within 
> <fo:block> of font-size in percentage:

OK, now I see it too.

I'll run it through the debugger, but already think I know what is going on. 
The property resolution mechanism tries to resolve to smaller/larger font-
sizes too early. Percentages are resolved (mostly
anyway) during the layout-stage, where FOP tries to already resolve 
the "smaller" keyword long before that.

I haven't tried yet, but using em's could also lead to trouble in combination 
with percentages, as in:

<fo:block>
   <fo:block font-size="80%">
     <fo:inline font-size="8em">


Will keep you posted.

Cheers

Andreas

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to