September 2005 - oXygen-user - www.oxygenxml.com

Working with Catalogs
by Eliot Kimber 11 Oct '05

11 Oct '05

I'm trying to set up some new catalogs for DITA (I'm tasked with defining how DITA will use various forms of URL and public ID to handle version-specific and inspecific references). I'm trying to use oXygen 6.2 to develop and test my catalogs and I'm not having much luck, which is probably mostly user error but I think there may be some limitations in oXygen's catalog implementation and I'm trying to figure out which is which. Unfortunately, the online help for catalogs is not helpful in this case. I'm trying to do several things: 1. Set up entries that map namespace URIs to local URLs for the corresponding schema document 2. Set up entries that map one URL to another URL. 3. Set up entries that map public IDs to system IDs that are fully-qualified URLs that then map, via URI entries, to local files I'm running into several problems. In all cases, I have set the catalog options to not use the default catalogs and I only list one top-level catalog, which then uses <next-catalog> elements to point to subordinate catalogs that do the actual mapping, i.e.: <catalog> <nextCatalog catalog="dtd/catalog-dita-dtd.xml" /> </catalog> -------------------------------------------- Problem 1: HTTP URL not resolved via catalog I have a document with this DOCTYPE declaration: <!DOCTYPE topic SYSTEM "http://dita.oasis-open.org/DITA/version.1.0/topic.dtd"> In my catalog I have this entry: <uri name="http://dita.oasis-open.org/DITA/version.1.0/topic.dtd" uri="topic.dtd"/> I have verified that the file "topic.dtd" is where the catalog says it is (using "edit file at cursor within oXygen). When I validate the document, I get this error: "Description: F HttpException-dita.oasis-open.org (http://dita.oasis-open.org/DITA/version.1.0/topic.dtd)" This suggests that the validator is trying to resolve the URL and, upon failure to do so (the URL isn't currently resolvable), is not then trying to resolve it via the catalog, which it should be doing. Also, in this case, even if the URL was resolvable over the net, I would prefer to have it resolved via the catalog--I didn't see an option for controlling that behavior. ----------------------------------------------------- Problem 2: Non-HTTP URN gives malformed URL exception In another document I have this doctype declaration: <!DOCTYPE topic SYSTEM "urn:oasis:http://dita.oasis-open.org/DITA/topic.dtd"> When I try to validate I get this failure: "Description: F MalformedURLException-unknown protocol: urn" This suggests that oXygen is expecting the SYSTEM value to be an HTTP URL, which is not required by the XML spec (the SYSTEM value is a URI, not a URL). In this case, I would expect the validator to try to resolve the URN via the catalog (where it is mapped) and only if that fails then return "could not resolve URN" error, not a malformed URN exception. ------------------------------------------------------ Problem 3: Unclear response from catalog verbose trace It's also not clear what these catalog trace messages are telling me: Description: Public: null System: http://dita.oasis-open.org/DITA/version.1.0/topic.dtd = null In particular, what the final "null" is indicating--does that indicate that the file to which the URI is mapped couldn't be found? I couldn't find an explanation of this case in the online docs. Cheers, Eliot -- W. Eliot Kimber Professional Services Innodata Isogen 9390 Research Blvd, #410 Austin, TX 78759 (512) 372-8841 ekimber(a)innodata-isogen.com www.innodata-isogen.com

3 14

Duplicate entity declarations are warnings, not errors.
by Chris Lilley 29 Sep '05

29 Sep '05

Hello oXygen-user, I am concerned about an aspect of DTD validation in oXygen. Duplicate entity declarations are flagged as errors, and validation halts. from the XML spec, 4.2 Entity Declarations http://www.w3.org/TR/REC-xml/#sec-entity-decl >> If the same entity is declared more than once, the first declaration >> encountered is binding; at user option, an XML processor MAY issue a >> warning if entities are declared multiple times. Unless I missed a configuration option, the message is not at user option but is always on. Further, its given as an error rather than a warning. The obvious workaround to delete the dupes :-) may not apply if the DTD is read-only and on someone else's website. Besides, they might decline to fix it on the grounds that per the XML spec, its harmless and should not generate an error. Please at minimum make this a warning, not an error; ideally, make reporting of the warning configurable. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG

2 1

configuring a catalog
by lists＠userdox.com 26 Sep '05

26 Sep '05

Hi, I've run into a problem using my catalog with oXygen. The catalog works successfully when transforming my files from the command-line using saxon/xerces/fop etc, but it isn't working when I edit with oXygen. Version 6.0 running on Windows XP SP2 I have unchecked the Use default catalog option in the Preferences and added my own catalog to the list. I made sure I restarted oXygen before testing but still no luck. I have set my CLASSPATH to include the directory where the catalog and the properties files are located. Have I missed something obvious? Thanks for your help, Geoff. This is my catalog: <?xml version="1.0" encoding="UTF-8"?> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">  <group prefer="public" xml:base="file:///d:\doc_workarea\zzuncontrolled\docbook-dtd-4.3\"> <public publicId="-//OASIS//DTD DocBook XML V4.3//EN" uri="docbookx.dtd"/> <system systemID="http://doctools.its.utas.edu.au/docbook/dtd/docbookx.dtd" uri="docbookx.dtd"/>  <nextCatalog catalog="catalog.xml"/> </group>  <system systemID="http://doctools.its.utas.edu.au/custom/xinclude.mod" uri="file:///d:\doc_workarea\zzuncontrolled\xinclude.mod"/>  <rewriteURI uriStartString="http://doctools.its.utas.edu.au/docbook/xsl/" rewritePrefix="file:///d:/doc_workarea/zzuncontrolled/docbook-xsl-1.68.1/"/>  <rewriteURI uriStartString="http://doctools.its.utas.edu.au/custom/" rewritePrefix="file:///d:/doc_workarea/single-source/"/> </catalog> My CatalogManage.properties file is: catalogs=gmp-catalog.xml;zzuncontrolled/docbook-dtd-4.3/catalog.xml relative-catalogs=false static-catalog=yes catalog-class-name=org.apache.xml.resolver.Resolver verbosity=1 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

2 1

Re: [oXygen-user] Eclipse: Scenario edit in 6.2
by Sorin Ristache 26 Sep '05

26 Sep '05

Hello, You don't have to export the scenarios created in previous versions. They should be loaded automatically. Please add the -clean parameter to the command used to start Eclipse: C:\eclipse\eclipse.exe -clean If any error is logged in the error log please post the stacktrace or the error message. Also specify the build id of your installed Eclipse 3.1. Best regards, Sorin Hobson, Neville wrote: > Sorry, no I'm using Eclipse 3.1.0. > > Neville > > > > Neville Hobson > Senior Consultant > Mentor Graphics UK Ltd, > Rivergate, London Road, > Newbury, > Berks, RG 14 2QB Tel.: - direct: +44 1635 811473 > - main: +44 1635 811411 > - fax : +44 1635 810110 > > Web - http://www.mentor.com > "Create Customer Competitive Advantage Through Passionate Teamwork" > > > > > -----Original Message----- > From: oxygen-user-bounces(a)oxygenxml.com > [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Sorin Ristache > Sent: 23 September 2005 10:03 > To: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Eclipse: Scenario edit in 6.2 > > Hello, > > You loaded the <oXygen/> plugin in one of the 3.0.x Eclipse versions. > Any <oXygen/> plugin version supports the latest stable version of > Eclipse. For version 6.2 that is Eclipse 3.1. See the Download page: > > http://www.oxygenxml.com/download.html > > Please use Eclipse 3.1. Otherwise you have to stay with version 6.1. > > > Best regards, > Sorin > > > Hobson, Neville wrote: > >>Having just upgraded to the 6.2 plugin for Eclipse (from 6.1) I can no > > >>longer edit scenarios for transformations. The scenario list box is >>presented but the edit button has no effect. No errors or logs seem to > > >>be generated. There's no clue as to why it won't edit. >>Have reverted to 6.1 and it works okay. >>Should I have done something when I loaded 6.2 - exported the >>scenarios for instance? >>However, it seems to work okay in the native oXygen 6.2 GUI! >> >> >>*Neville Hobson >>Senior Consultant* >> *Mentor Graphics UK Ltd, >>*Rivergate, London Road, >>Newbury, >>Berks, RG 14 2QB Tel.: - direct: +44 1635 811473 >> - main: +44 1635 811411 >> - fax : +44 1635 810110 >> >>Web - http://www.mentor.com <http://www.mentor.com/> >>*"Create Customer Competitive Advantage Through Passionate Teamwork"* >> > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user

1 0

Starting with Specific VM
by Raymond 26 Sep '05

26 Sep '05

Reinstalled 6.2 on Windows platform; have both 1.4.2 and 1.5 jre. Oxygen defaults to 1.4.2 vm when starting. JAVA_HOME env var set to 1.5 jre path; still starts with 1.4.2 How does one configure oXygen to start with 1.5 ? Raymond

2 1

Eclipse: Scenario edit in 6.2
by Hobson, Neville 23 Sep '05

23 Sep '05

Having just upgraded to the 6.2 plugin for Eclipse (from 6.1) I can no longer edit scenarios for transformations. The scenario list box is presented but the edit button has no effect. No errors or logs seem to be generated. There's no clue as to why it won't edit. Have reverted to 6.1 and it works okay. Should I have done something when I loaded 6.2 - exported the scenarios for instance? However, it seems to work okay in the native oXygen 6.2 GUI! Neville Hobson Senior Consultant Mentor Graphics UK Ltd, Rivergate, London Road, Newbury, Berks, RG 14 2QB Tel.: - direct: +44 1635 811473 - main: +44 1635 811411 - fax : +44 1635 810110 Web - http://www.mentor.com <http://www.mentor.com/> "Create Customer Competitive Advantage Through Passionate Teamwork"

2 1

Eclipse Transformation Problems
by Raymond 20 Sep '05

20 Sep '05

docbook-dtd-4.5CR1, docbook-xsl-1.69.1, jdk-1.5.0_4, kubuntu-5.04, oXygen-6.1, saxon-6.5.4, eclipse-3.1 Installed the oXygen plugin for Eclipse and moved an xml project that correctly validates and transforms on standalone oXygen to Eclipse. Validates correctly but now generates the following transformation error: "Processing terminated by xsl:message at line 410" Traceback indicates it appears at the first xinclude statement (xincludes are enabled). Raymond

2 1

how to change fonts when transforming into pdf?
by Chip Wiegand 17 Sep '05

17 Sep '05

I am guessing there is some parameter I need to specify in my transformation stylesheet, but what is it? I see only body font family on http://docbook.sourceforge.net/release/xsl/current/doc/fo/index.html, nothing that would allow me to do italics and colors. What do I do to make a different color font and add emphasis or strong to individual words? Thanks, Chip Wiegand Computer Services Simrad, Inc 425-778-8821 425-771-7211 (FAX)

2 1

Bash Syntax Hightlignting Problem
by Raymond 13 Sep '05

13 Sep '05

oXygen-6.1 The following bash shell script fragment: /bin/cat <<-SCRIPT is legal but causes syntax highlighting to display literal color to the end of the script. How can I correct this? Raymond

2 2

Print Error
by Raymond 12 Sep '05

12 Sep '05

docbook-dtd-4.5CR1, docbook-xsl-1.69.1, jdk-1.5.0_4, kubuntu-5.04, oXygen-6.1, saxon-6.5.4 When attempting to print; receive the following dialog message: "No print service found" Raymond

2 1