Enable "prefer=public" in Author component
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 28
- Joined: Wed May 26, 2010 7:05 pm
Enable "prefer=public" in Author component
Hello,
In the options of Oxygen XML Editor desktop,in XML/XML catalogs, there is an option to specify whether the resolution of the DOCTYPE declarations should favor system or public identifiers.
With the same default dita framework loaded, with this option set to "system", a topic with the declaration cannot be validated because Xerces fails to find the DTD (it looks in the same directory as the opened file):
<!DOCTYPE dita PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
However, it works if the option is set to "public".
In the Author component, I think I get a similar behaviour as when the option is set to "system". My topics, standard and specialized, don't validate if I don't include the full path of the DTD in the SYSTEM part of the declaration.
I have deployed the same custom DITA framework, with my specialized DTDs, the standard ones, and their catalogs, in Oxygen XML Editor desktop, and I get the same results as with the standard framework: with the "prefer" option set to public, both standard and specialized topics are valid. If set to system, they aren't.
Question: assuming this "prefer" option is the reason why the PUBLIC IDs of the topics don't resolve in the Author component, how can I set it? I have looked for it in the options export I have made from the Oxygen Editor desktop, I didn't find it.
Thanks!
NB: I have set @prefer=public on all my custom XML catalogs, declaring all mappings two times: as <uri> and as <public>.
In the options of Oxygen XML Editor desktop,in XML/XML catalogs, there is an option to specify whether the resolution of the DOCTYPE declarations should favor system or public identifiers.
With the same default dita framework loaded, with this option set to "system", a topic with the declaration cannot be validated because Xerces fails to find the DTD (it looks in the same directory as the opened file):
<!DOCTYPE dita PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
However, it works if the option is set to "public".
In the Author component, I think I get a similar behaviour as when the option is set to "system". My topics, standard and specialized, don't validate if I don't include the full path of the DTD in the SYSTEM part of the declaration.
I have deployed the same custom DITA framework, with my specialized DTDs, the standard ones, and their catalogs, in Oxygen XML Editor desktop, and I get the same results as with the standard framework: with the "prefer" option set to public, both standard and specialized topics are valid. If set to system, they aren't.
Question: assuming this "prefer" option is the reason why the PUBLIC IDs of the topics don't resolve in the Author component, how can I set it? I have looked for it in the options export I have made from the Oxygen Editor desktop, I didn't find it.
Thanks!
NB: I have set @prefer=public on all my custom XML catalogs, declaring all mappings two times: as <uri> and as <public>.
Colin Maudry
Enterprise documentation analyst and Open Data specialist
Rennes, France
Tweets at @CMaudry
Enterprise documentation analyst and Open Data specialist
Rennes, France
Tweets at @CMaudry
-
- Posts: 9449
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Enable "prefer=public" in Author component
Hi Colin,
By default (without any additional changes on your side) the applet uses the same default options as the standalone application. So this means the applet also prefers public IDs by default.
In my opinion in your case the applet does not find a mapping in the XML catalogs for that specific public ID.
The applet comes with a "frameworks.zip.jar" resource which should contain a zipped version of your custom framework. Could you double check that the resource contains the proper custom XML catalogs, DTDs and modifications as the framework you use in the standalone installation?
Just to make sure the applet does not cache some older document type configuration, could you also follow steps (3) and (4) in this procedure?
http://www.oxygenxml.com/doc/ug-oxygen/ ... oting.html
Regards,
Radu
By default (without any additional changes on your side) the applet uses the same default options as the standalone application. So this means the applet also prefers public IDs by default.
In my opinion in your case the applet does not find a mapping in the XML catalogs for that specific public ID.
The applet comes with a "frameworks.zip.jar" resource which should contain a zipped version of your custom framework. Could you double check that the resource contains the proper custom XML catalogs, DTDs and modifications as the framework you use in the standalone installation?
Just to make sure the applet does not cache some older document type configuration, could you also follow steps (3) and (4) in this procedure?
http://www.oxygenxml.com/doc/ug-oxygen/ ... oting.html
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
-
- Posts: 28
- Joined: Wed May 26, 2010 7:05 pm
Re: Enable "prefer=public" in Author component
Hi Radu,
Thanks for replying quickly.
I have run 'javaws -uninstall' in Windows command prompt to clear the Java Web cache, and it works now. My changes were not taken into account.
Thanks!
Thanks for replying quickly.
I have run 'javaws -uninstall' in Windows command prompt to clear the Java Web cache, and it works now. My changes were not taken into account.
Thanks!
Colin Maudry
Enterprise documentation analyst and Open Data specialist
Rennes, France
Tweets at @CMaudry
Enterprise documentation analyst and Open Data specialist
Rennes, France
Tweets at @CMaudry
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service