Bug 24707 - give feedback for invalid font sizes
Summary: give feedback for invalid font sizes
Status: CLOSED WORKSFORME
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: pdf (show other bugs)
Version: trunk
Hardware: All other
: P3 enhancement
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-14 10:49 UTC by Kai Schröder
Modified: 2007-11-20 02:34 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Schröder 2003-11-14 10:49:55 UTC 
Because I can't type right, I produce a xsl:fo file within a font-size="0pt"
argument for a fo:block element. This make no sence, but FOP doesn't output any
warning or error message like "illegal font size". The result was a broken PDF
file (an unrecognized token 'NaN' was found). This is not really a bug, but IMHO
it would be a nice feature to have such warning/error message.
Comment 1 Glen Mazza 2003-11-16 21:28:06 UTC 
Of course, absolutely--for our next version I expect us to have a thorough 
warning & error feedback system with easy-to-understand messages of "oddities" 
found while processing the FO stream.  (I don't think we can get to this for 
0.20.x though.)

I'll keep this bug open for the *specific* issue you're mentioning (font-size 
warning), hopefully we'll take care of this along with several others in the 
next release.

Thanks,
Glen
Comment 2 Pascal Sancho 2007-11-20 00:59:27 UTC 
IMHO, this is the correct behaviour.
as a work around, 
font-size="0pt" (and font-height="0pt", witch default to 120% * {font-height})
is used to avoid vertical margins to an image alone in a fo:block. 
This bug should be resolved as INVALID

WDYT?
Comment 3 Vincent Hennebert 2007-11-20 02:32:30 UTC 
Agreed, and anyway the PDF produced by FOP 0.94 is now valid.

Vincent