Non-system Fonts Don't Seem to be Supported

[schmidtw]

It appears that the non-system font directory that can be passed in from maven-jdocbook-plugin gets silently ignored, providing no way to use a non-system font directory path.

src/main/java/org/jboss/jdocbook/render/fop/FopConfigHelper.java:

// did not work for me :(
//          if ( environment.getFontDirectories() != null ) {
//              for ( File fontDirectory : environment.getFontDirectories() ) {
//                  DefaultConfiguration fontDirectoryElement = new DefaultConfiguration( "directory" );
//                  fontDirectoryElement.setValue( fontDirectory.getAbsolutePath() );
//                  fontsConfig.addChild( fontDirectoryElement );
//              }
//          }

[sebersole]

What does work?

[schmidtw]

I'm sorry, I don't understand your question. The problem I was trying to solve was as follows:

A user/author checks out the document maven project. When she builds the document, the correct fonts are not being used (which are part of the project pom.xml file), but instead system fonts are being substituted.

[sebersole]

And I am asking you what is the fix to make it do what you want? None of
us are really "DocBook people". Mostly we are Hibernate developers and we
mostly get this.to work for our cases. You have a much better chance of
this getting resolved if you tell us how.

[email protected]
http://hibernate.org
On Dec 7, 2011 1:24 PM, "schmidtw" <
[email protected]>
wrote:

I'm sorry, I don't understand your question. The problem I was trying to
solve was as follows:

A user/author checks out the document maven project. When she builds the
document, the correct fonts are not being used (which are part of the
project pom.xml file), but instead system fonts are being substituted.

---

Reply to this email directly or view it on GitHub:
#7 (comment)

[sebersole]

I do remember there being a "FOP font cache". You might want to look at deleting that cache file and then rerunning your build.