Bob Stayton | 8 Jun 01:05 2011

Re: [oXygen-user] R: Additional XSLTstylesheet in docbooktransformation

An anomaly in DocBook profiling came up on the Oxygen users mailing list, but it is 
actually a DocBook XSL issue, so I'm posting the problem and solution to the 
docbook-apps mailing list as well.

From: "Sorin Ristache" <sorin <at>>
To: <oXygen-user <at>>
> We did not use profile-docbook.xsl because it does not apply all the
> profiling attribute values always correctly for complex DocBook
> documents. We tested that version of profiling stylesheet on a complex
> document and it allowed in the output some subsections which did not
> have the profiling attribute value set as the profiling parameter of the
> transformation. The profile.xsl stylesheet did not have this problem so
> we used that in the Oxygen scenarios.

With Sorin's help, I tracked down the source of this problem, because it did not seem 
right to me that the profile-docbook.xsl stylesheet would produce a different profile 
from the profile.xsl stylesheet.  It turns out to be an issue with customization of 
the DocBook HTML chunking stylesheet while profiling, and does not seem to be 
documented anywhere, so I'm posting the solution here for the record.

Because DocBook's chunking stylesheet relies on XSL import precedence to separate the 
chunking functions from the formatting functions, a customization of the chunking 
stylesheet requires a particular setup that imports and includes various DocBook XSL 
modules in a certain order.  That process is described here:

To customize the chunking stylesheet for single-pass profiling, my book says to import 
"profile-docbook.xsl" instead of "docbook.xsl". But that is not sufficient for chunked 
(Continue reading)

Michael Smith | 3 Nov 11:33 2010

Selecting/Creating oXygen editor windows


I have recently been developing a standalone oXygen 12.0 workspace 
plugin that produces an XML document containing oXygen's track-change 
processing instructions. Currently this plugin can write its results 
either to an existing editor or to a file. In the latter case the file 
is opened in an oXygen editor once it has been written. In the former 
case, the editor is correctly updated but not selected as the current 
editor. Is there a way of selecting this output editor as the current 
editor from within the plugin?

I would also like to allow the user to send the output to a "new" 
freshly constructed editor window with an appropriate "untitled #number" 
name, where the action of "saving" the document would prompt the user 
for the location to save the file in. There may be cases where the user 
just wants to view the result, rather than save it to a file. We 
generally know the type of document that is being generated (e.g. DITA, 
DocBook, general XML) so could supply this to the oXygen editor creation 
API, if this is helpful. Any pointers on how this - or something similar 
- could be achieved would be welcome.

I am new to the oXygen plugin development and this mailing list; and 
have done my best to search both the API and archive for answers to the 
issues I have just raised.  I apologise in advance for missing previous 
answers to these questions.

Nigel Whitaker | 29 Oct 16:22 2010

Plugin access to frameworks and catalogs


We're developing a workspace plugin which reads form either existing 
editors or on-disk files.

We're using all the catalogs in the standard 12.0 release using this 
rather brute-force approach:

   <configProperty name="cat_dita" 
value="${install.dir}/../../../frameworks/dita/catalog.xml" />
   <configProperty name="cat_docbook" 
value="${install.dir}/../../../frameworks/docbook/catalog.xml" />
   <configProperty name="cat_xmlspec" 
value="${install.dir}/../../../frameworks/xmlspec/catalog.xml" />

   <configProperty name="xml.catalog.files"  
value="${cat_dita};${cat_docbook};...${cat_xmlspec}" />

However, we dont know about any user defined frameworks.   Is there a 
way of knowing the framework associations of editors/files so that we 
could use the specific catalog file (also reducing the possibility of 
conflicts between the catalogs).  Alternatively access to a URI/Entity 
resolver appropriate for the type of file which we could use when 
parsing (xerces) may be useful.  

We know about XMLUtilAccess and its resolvePathThroughCatalogs method, 
but we'd like something we can use with the resolver/xerces directly.  
We've also seen some references to a 'grammarCache' object but are 
unsure how to use it.
(Continue reading)

Roger | 27 Oct 00:00 2010

What does Apple's deprecation of Java mean for oXygen?

Dear oXygen Users,

Apple recently announced that future versions of Mac OS X may no longer
include a Java runtime:


Any idea what that will mean for the future of Java-based apps like oXygen?

Will a Mac version of oXygen bring its own JRE, or will we need to download
one from somewhere else to run oXygen?

I know it's a long way off, but just curious what this announcement will mean...

Ted Kuster | 26 Oct 20:40 2010

Can't uninstall/reinstall Eclipse plugin

I need to reinstall Oxygen Author 12, in Eclipse 3.5.2 on Ubuntu 10.4. I 
have completely cleaned any traces of Oxygen from my Eclipse 
installation --a file search reveals no files with any form of the 
string "oxygen" anywhere in the file system. I have restarted Eclipse 
with the -clean option. No Oxygen-related options or settings are 
available anywhere in the Eclipse UI. However, when I try to use Help > 
Install New Software to install Oxygen, Eclipse refuses on the grounds 
that Oxygen is already installed. What am I doing wrong?

Ted Kuster
Shannon | 23 Oct 00:24 2010

GUI change request

Hi, please consider giving the user the option to hide the Text/Grid/Author controls to increase
available space to the editor. I often use a tiny screen on a notebook and have configured a minimal
layout--no toolbars or panels whatsoever--; since I never change the view, I'd like to get rid of those
buttons too. Thanks,
Shannon | 22 Oct 17:20 2010

Error: Invalid authority


I searched the site and mailing list archive for this error with no results.

In the XML Databases perspective, the Data Source Explorer panel returns, "Error: Invalid authority"
when I attempt to explore by expanding any one of the Connections, after briefly showing,
"Pending…"--these are the same Connections that execute successfully in every other perspective for
transforming, querying, and debugging.

The Database Source is type MarkLogic. Running Oxygen 11.2 on OS X 10.6.4.

Please let me know if you need more information, or what I am doing wrong, thanks,
Reaves, Timothy | 15 Oct 14:32 2010

Re: Trouble validating SVG document

Thanks for all the info; I now understand what is going on.

On Fri, Oct 15, 2010 at 7:31 AM, Chris Lilley <chris@...> wrote:

> On Friday, October 15, 2010, 11:03:26 AM, Radu wrote:
> RC> Hi Tim,
> RC> W3C describes the content of a <svg> document in a schema-independent
> way.
> RC>  From what I know there are also XML Schemas which can be used to
> RC> validate SVG files.
> Yes.
> Going forward, W3C plans to use RelaxNG to define the SVG grammar (and to
> recommend NVDL for portioning out a multi-namespace document such that the
> SVG parts are validated to the SVG RNG).
> RC> Indeed the usual way to validate a SVG file is by using the DTDs but
> RC> as a grammar specification is not namespace aware and understands
> RC> constructs like "xmlns:x" as usual attributes.
> Yes.
> It should not, but DTDs predate namespaces and are not aware of namespace
> declarations.
> RC> Radu Coravu
(Continue reading)

Radu Coravu | 15 Oct 11:03 2010

Re: Trouble validating SVG document

Hi Tim,

W3C describes the content of a <svg> document in a schema-independent way.
 From what I know there are also XML Schemas which can be used to 
validate SVG files.
Indeed the usual way to validate a SVG file is by using the DTDs but DTD 
as a grammar specification is not namespace aware and understands 
constructs like "xmlns:x" as usual attributes.


Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger

On 10/14/2010 6:00 PM, Reaves, Timothy wrote:
> I'm confused then.  From
> they reference to follow what is outlined
> .
> "
> An example namespace declaration, which associates the namespace prefix
> *edi* with the namespace name ||:
> <x xmlns:edi=''>
>    <!-- the"edi"  prefix is bound to
>         for the"x"  element and contents -->
> </x>
(Continue reading)

Reaves, Timothy | 14 Oct 15:50 2010

Trouble validating SVG document

I have an SVG document where the openeing SVG element is:
<svg  version="1.0" xmlns:x="&ns_extend;" xmlns:i="&ns_ai;"
xmlns:graph="&ns_graphs;" xmlns="&ns_svg;" xmlns:xlink="&ns_xlink;"
     width="497.611" height="591.554" viewBox="0 0 497.611 591.554"
     style="overflow:visible;enable-background:new 0 0 497.611 591.554;"

Validation fails on each of the xmlns attributes.  This should be valid.
The errors look like:
SystemID: /home/bv6679/Development/images/HSVG/99571_97YA_17.svg
Engine name: Xerces
Severity: error
Description: Attribute "xmlns:x" must be declared for element type "svg".
Start location: 29:21
End location: 29:42

Any ideas?
Yves Barbion | 13 Oct 11:00 2010

The entity "nbsp" was referenced, but not declared

Hi group

I know this topic has been discussed before, so I'm sorry to bother you with
this again.

I've got non-breaking spaces in my topics (&nbsp) and when I generate XHTML
output with oXygen XML Author, my build fails and I get the message:

"The entity "nbsp" was referenced, but not declared."

I get a "build successful" with oXygen XML Editor though, so I must have
fixed it there in some way, but I cannot remember how anymore. I also
searched the archives, but to no avail.

Can someone please refresh my memory?



Yves Barbion