[ 
https://issues.apache.org/jira/browse/FOR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628564#action_12628564
 ] 

Sjur N. Moshagen commented on FOR-132:
--------------------------------------

Since r 691220 the pdf plug-in has been updated to be fully configurable by the 
user to solve exactly this issue. Updated documentation is found within the 
plug-in.

So far tested is changing the generic font families (replacing serif with 
sans-serif), but the plugin will now also correctly find and use a FOP/PDF 
config file as specified by the user in 
$PROJECT_HOME/src/documentation/resources/schema/symbols-project-v10.ent

I have not yet fully tested whether changing the actual font family works with 
this new setup, but since the pdf config file is found, the work is done as far 
as Forrest is concerned. In another project where we use Forrest for 
documentation, we have been using this successfully for a while to get pdf 
files with all glyphs in place (see discussion earlier in this bug about the 
Sámi (Saami) characters coming out as # - we have had this solved for quite 
some time by editing the pdf plug-in; with this latest commit you don't need to 
edit the plug-in anymore, just your project settings files).

Please give feedback as to whether this works for you (and remember to 
re-deploy the pdf plug-in before you restart Forrest, otherwise the plug-in 
used code will still be the old one).



> Allow Custom Fonts for PDF files
> --------------------------------
>
>                 Key: FOR-132
>                 URL: https://issues.apache.org/jira/browse/FOR-132
>             Project: Forrest
>          Issue Type: Bug
>          Components: Plugin: output.pdf
>         Environment: win2003, latest forrest
>            Reporter: baikkyung
>         Attachments: polish_national_chars.sxw
>
>
> When you transform a document with other characters than latin to PDF, in 
> spite of the unicode(UTF-8) of the original file all characters get broken 
> and isn't readable. please, does anyone have a simple solution for this?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.