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=39560.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
in FOP 0.92 beta spaces in font names are deleted and then it doesn't match
with the original font names (like 'Agfa Rotis Sans Serif', it is handled as
AgfaRotisSansSerif). If you change the configuration file 'userconfig.xml using
font names without spaces it doesn't match with the Windows
Some background on my latest change. I found out that certain TrueType
fonts were off vertically inside their line area. It turned out it has
to do with different interpretations of the ascender and descender
values which are part of font metrics and which FOP uses to determine
the baseline
I recently found that FOP currently does not properly parse the
font-family property as specified in the XSL spec [1]. However, it says
that you can quote the font names. Maybe that helps you already.
I don't think anyone has paid much attention to the font family names in
use. It's also
Cliff's answer:
Yes -- as you suspect, this license fits the definition of Category A,
since it doesn't place restrictions on independent works that use it
or the licensing of larger works, nor does it have any reciprocity
provisions. It looks like X.Net with some Artistic tendencies.
So
On Tuesday 16 May 2006 19:58, Jeremias Maerki wrote:
Some background on my latest change. I found out that certain
TrueType fonts were off vertically inside their line area. It turned
out it has to do with different interpretations of the ascender and
descender values which are part of font
