If you are generating your fo file via a transform, maybe you could add to it to convert light, heavy and black to appropriate numeric values? Then the fo file would contain all legal values while maintaining the source's values as required by the designers and avoids making changes to FOP to support non standard font weight names.
Or perhaps it might be nice to add capability to add to the xconf file a section to describe a font weight 'name' and a translation to a suitable numeric value. From my recent playing with code that reads in the xconf file this shouldn't be too difficult. e.g. <font-weight-template name='heavy' weight='800'/> - not sure where in the xconf this should go without looking in more detail. (If this option is the one then I guess it would be nice to create a patch so that it can be considered for the trunk for others to use.) Thanks. -Mike On 03/06/11 11:10, Theresa Jayne Forster wrote: The problem is that the Designers specify it must be HEAVY not BOLD and they have no understanding of the numeric weights. The designers use light, normal, bold, heavy and black The current FOP only supports normal and bold. I guess I will need to make sure that the fop I use is modded to support the black and heavy as well as light. Kindest regards Theresa Forster Senior Software Developer From: Eric Douglas [mailto:edoug...@blockhouse.com] Sent: 02 June 2011 16:03 To: fop-users@xmlgraphics.apache.org<mailto:fop-users@xmlgraphics.apache.org> Subject: RE: Problems since upgrading, heavy is not a standard keyword. If you select the wrong value for the fonts you have loaded it should log a warning for font replacement. Keywords translate to specific numbers. You would want to use the numbers instead of the words to be sure it's always correct. They might think light is 200 but your light font has a weight of 100, or normal 300 / 400 etc. http://www.w3.org/TR/CSS2/fonts.html#font-boldness Standard keywords are normal (400) and bold (700), and lighter / bolder (relative to parent). ________________________________ From: Theresa Jayne Forster [mailto:ther...@inbrand.co.uk] Sent: Thursday, June 02, 2011 10:46 AM To: fop-users@xmlgraphics.apache.org<mailto:fop-users@xmlgraphics.apache.org> Subject: Problems since upgrading, Since upgrading the fop I use from 0.23 to 1.0 I am now getting problems One of which is that the font designations I used to use are now no longer possible, and was wondering why this has seemingly changed, and is there plans to support the method I am used to using? Before <fo:block font-family=”Frutiger” font-style=”normal” font-weight=”heavy”/> Now apparently I need to do weight as a number 700=bold etc Kindest regards Theresa Forster Senior Software Developer ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com> Version: 10.0.1375 / Virus Database: 1509/3662 - Release Date: 05/26/11 Michael Rubin Developer [http://thunderhead.com/email_signature/images/Thunderhead-logo.png] [http://thunderhead.com/email_signature/images/make-every-communication-count.png] [http://thunderhead.com/email_signature/images/triangles.png] T F M E W +44 20 8238 7400 +44 20 8238 7401 mru...@thunderhead.com<mailto:mru...@thunderhead.com> www.thunderhead.com<http://www.thunderhead.com> Thunderhead recognized in the Red Herring 2011 Top 100 Europe. Click here<http://www.herring100.com/RHE/2011/top100.html> to read more. [http://thunderhead.com/email_signature/images/linkedin.png]<http://www.linkedin.com/companies/25033/Thunderhead> [http://thunderhead.com/email_signature/images/twitter.png] <http://twitter.com/Thunderheadon> [http://thunderhead.com/email_signature/images/rss.png] <http://www.thunderhead.com/rss/rss.php> [http://thunderhead.com/email_signature/images/youtube.png] <http://www.youtube.com/user/ThunderheadOn> [http://thunderhead.com/email_signature/images/theblog.png] <http://thunderheadinnovate.wordpress.com/> [http://thunderhead.com/email_signature/images/werehiring.png] <http://thunderhead.com/about/careers.php> The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
