[protege-discussion] New bug(?) report HTML export: Saving Export Configuration fails

[Jennifer Vendetti]

Markus,

I just tested the HTML export functionality using the Protege 3.2.1 
release (which we recommend in favor of older Protege 3.2 beta builds).  
Both my Protege installation and the output path for the HTML files had 
spaces in the path.  Everything worked fine and I was not able to 
reproduce this error message.

 From the error message you posted, it seems that one of the files 
(HTMLExportConfigurations.xml) is missing from your installation.  This 
file is used by the HTML export plug-in and is installed when you 
install Protege.  Please check that it exists in the following directory:

<your-protege-install-dir>/plugins/edu.stanford.smi.protegex.standard_extensions/html_export

If the file is missing, please reinstall Protege and try the HTML export 
process again.

Jennifer

Markus Bohr wrote:
> Dear Protege Team,
>
> I noticed (Frame based Protege3.2b Built324) that saving the Export
> Configuration under a specific name currently fails if the Protege installation
> directory contains spaces in its path...
> This may also be the case for spaces occuring in the specified Output 
> Directory).
>
> The following error is issued:
> java.io.FileNotFoundException: file:\D:\Program%20Files\Protege_3.2_beta_324\plu
> gins\edu.stanford.smi.protegex.standard_extensions\html_export\HTMLExportConfigu
> rations.xml (The filename, directory name, or volume label syntax is incorrect)
>
> Best Regards,
> Markus Bohr.
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
>