MATLAB: Error while trying to publish on PDF format

pdfpublish

Hi all,
I have just installed 2011a and I am trying to publish some code on pdf. Even though html works smoothly, the pdf choice lead to the following error…
??? Java exception occurred:
java.io.FileNotFoundException: C:\Program Files\MATLAB\R2011a\toolbox\matlab\codetools\private\fop_config.xml (The
system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(Unknown Source)
at java.io.FileInputStream.<init>(Unknown Source)
at sun.net.www.protocol.file.FileURLConnection.connect(Unknown Source)
at sun.net.www.protocol.file.FileURLConnection.getInputStream(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at
org.apache.avalon.framework.configuration.DefaultConfigurationBuilder.build(DefaultConfigurationBuilder.java:254)
at
org.apache.avalon.framework.configuration.DefaultConfigurationBuilder.build(DefaultConfigurationBuilder.java:237)
at org.apache.fop.apps.FopFactoryConfigurator.setUserConfig(FopFactoryConfigurator.java:263)
at org.apache.fop.apps.FopFactory.setUserConfig(FopFactory.java:666)
Error in ==> publish>fopInitialize at 550
fopFactory.setUserConfig(file2urn(...
Error in ==> publish>publishToPdf at 501
[fopDriver, fopOutputStream] = fopInitialize(outputAbsoluteFilename);
Error in ==> publish at 193
publishToPdf(dom,options,outputAbsoluteFilename)
Error in ==> mdbpublish at 55
outputPath = publish(file, options);
??? Error using ==> open at 69
NAME must contain a single string.
any ideas?
Thanks, Nick

Best Answer

Sorry for the trouble, Nick. This is a known issue. The workaround is here:
Related Question