Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 83659 invoked from network); 9 Sep 2008 09:03:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Sep 2008 09:03:26 -0000 Received: (qmail 60505 invoked by uid 500); 9 Sep 2008 09:03:23 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 60461 invoked by uid 500); 9 Sep 2008 09:03:23 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 60450 invoked by uid 99); 9 Sep 2008 09:03:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Sep 2008 02:03:23 -0700 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of sjurnm@mac.com does not designate 195.197.172.116 as permitted sender) Received: from [195.197.172.116] (HELO gw02.mail.saunalahti.fi) (195.197.172.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Sep 2008 09:02:24 +0000 Received: from a88-112-40-119.elisa-laajakaista.fi (a88-112-40-119.elisa-laajakaista.fi [88.112.40.119]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 7D8EA1398E5 for ; Tue, 9 Sep 2008 12:02:53 +0300 (EEST) Message-Id: <42A281E5-140D-48B4-B364-4DA49289DF28@mac.com> From: Sjur Moshagen To: Forrest Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v928.1) Subject: FOPNGSerializer and user-configurable fonts - fonts not found Date: Tue, 9 Sep 2008 12:02:52 +0300 X-Mailer: Apple Mail (2.928.1) X-Virus-Checked: Checked by ClamAV on apache.org Hello all, The work I've done lately isn't completely successful, but I'm not able to find the source of the problem. Success story first: It is now possible to specify the font family being used (hm, I have a feeling I have said this a couple of times...). This was tested by just switching around the generic families serif, sans-serif and monospace, and it works fine. Conclusion: the changes I made are working as intended. BUT: now I wanted to use this to specify the correct font family for a site of ours, but the fonts are not found. Instead I get error messages like: WARN - Font 'Lucida Grande,normal,700' not found. Substituting with 'any,normal,700'. WARN - Font 'Junicode,italic,400' not found. Substituting with 'any,italic,400'. WARN - Font 'Junicode,normal,400' not found. Substituting with 'any,normal,400'. I admit that this is really a FOP question, and not really a Forrest issue. Then on the other hand, FOP 0.94 (which we are using) and the font-finding features have been around for some time now, and should work, or problems should be known, and workarounds should be available in e-mail list archives, wikis, FAQs etc. I have found nothing, which makes me wonder whether there is a problem in the interaction between Forrest and FOP. The font configuration file is correctly found (otherwise the error message would have been completely different), and I have updated the configuration file to what is described on the FOP pages[1] (I actually copied the file from the FOP svn repository, as described on [2], the structure of the file has changed quite a bit since our previous FOP version), still no luck. I have tried with system-installed fonst (on MacOS X), and fonts available only to Forrest/FOP (in the $PROJECT_HOME/src/documentation/ resources/fonts/ folder). Nothing works. If I specify one of the base-14 fonts (Times, Helvetica, Courier, symbols and dingbats), I get no error messages, but characters outside ANSI 1252 are displayed as #, even though the fonts on my system actually do contain the requested glyphs. Somehow this seems to be related to the FOP 0.94 upgrade a while ago, as this used to work for me and my colleagues. Any help would be greatly appreciated. Best regards, Sjur [1] http://xmlgraphics.apache.org/fop/0.94/fonts.html [2] http://xmlgraphics.apache.org/fop/0.94/configuration.html