You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Karl Wright (Commented) (JIRA)" <ji...@apache.org> on 2012/01/29 17:35:10 UTC

[jira] [Commented] (FOR-1233) Forrest's PDF plugin configuration documentation seems to be incorrect

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

Karl Wright commented on FOR-1233:
----------------------------------

I've discovered that it is the symbols-project-v10.ent file that is simply never read.  Replacing the PDF plugin's output.xmap with one the directly references the config.xml file seems to work, but the entity replacement does not take place (obviously) because there is no processed entity declaration.

                
> Forrest's PDF plugin configuration documentation seems to be incorrect
> ----------------------------------------------------------------------
>
>                 Key: FOR-1233
>                 URL: https://issues.apache.org/jira/browse/FOR-1233
>             Project: Forrest
>          Issue Type: Bug
>          Components: Documentation and website
>    Affects Versions: 0.10-dev
>            Reporter: Karl Wright
>
> When I follow the instructions at http://forrest.apache.org/pluginDocs/plugins_0_90/org.apache.forrest.plugin.output.pdf, they say to place a configuration file called config.xml at the location $PROJECT_HOME/src/documentation/resources/schema/symbols-project-v10.ent.  However, when I create this file and point it to a config.xml, as stated in the documentation, the config.xml is never parsed.  (I can determine this by making the xml badly formed, which I would hope would cause an error of some kind).  I have not gone into using strace to see where Forrest is actually looking but will try this soon.
> I am using the trunk version of Forrest at the moment.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira