[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Unwanted namespace prefix _0

Subject: Re: Unwanted namespace prefix _0
From: Martin Holmes <mholmes@xxxxxxx>
Date: Mon, 23 Dec 2013 14:08:39 -0800
 Re: Unwanted namespace prefix _0
On 13-12-23 01:53 PM, Graydon wrote:
On Mon, Dec 23, 2013 at 01:43:35PM -0800, Martin Holmes scripsit:
As I posted above, test files are here:


I get the same result with Saxon _in_Oxygen_ whether I provide a
prefix for the Examples namespace in the root stylesheet element or
not; and whether or not I exclude it with exclude-result-prefixes. I
do _not_ get the prefixes in the output if I run the transformation
at the command line with Saxon. So the problem has something to do
with the Oxygen context, but I can't figure out what it is.

Note that if I run your stylesheet with oXygen and change the data so the input has a prefix of "eg" for the examples namespace, I don't get that _0 prefix.

Me too -- I get eg: prefixes for all the elements in the example. But that's not ideal; our encoders need to be able to copy-paste blocks of code from their TEI files into <egXML> elements, where they move into the Examples namespace, without having to laboriously prefix all their element names.

What oXygen and saxon versions are you using?  might also be a relevant
question.  (15.1 and PE, in my case.)

Oxygen 15.1; Command-line Saxon is Saxon-HE; Saxon in Oxygen is


-- Graydon

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.