DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30681>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30681

<xsl:namespace-alias stylesheet-prefix="foo" result-prefix="#default" />





------- Additional Comments From [EMAIL PROTECTED]  2004-08-28 04:39 -------
"However, I think you are trying to generate XHTML output that is XML, but 
which would be acceptable to a browser that reads HTML, and that the extra 
prefix in the output is messing that up.  Is that right?
- Brian Minchau"

Brian, That is exactly correct.  That is my whole desire behind filing this 
bug.  For what it's worth the MS .Net framework removes the prefix, so I can 
use that for my application, however I wanted something in java and something 
that is cross platform...

I recently filed the same bug to gnome/libxml2 and they made changes to remove 
the prefix.

I agree 100% with this statement:

"The xsl:namespace-alias 
element does have the attribute "result-prefix", but it has a meaning more 
like "result-uri-that-is-associated-with-this-prefix"."

Doesn't this statement mean if result-prefix is #default, then there should be 
no prefix for that namespace uri in the resulting document?

I don't follow this logic:

"I think the output of either:
   <html xmlns="http://http://www.w3.org/1999/xhtml";><head>...
or
   <html:html xmlns:html="http://http://www.w3.org/1999/xhtml";><html:head>...
are both all right. I there is flexibility in the XSLT 1.0 recommendation."

I think both are perfectly legitimate outputs, but the stylsheet that 
generated them must have been different.  I don't think
    <html:html xmlns:html="http://http://www.w3.org/1999/xhtml";><html:head>...
is valid output if the xslt contains
    <namespace-alias sytlesheet-prefix="html" result-prefix="#default"/>
(where the xslt document root contains
    xmlns:html="http://http://www.w3.org/1999/xhtml";)

Why profide a <namespace-alias .../> if it is ambiguous if it aliases the 
output prefix or not?  That's my logic anyway.

As for this statement:
"one of the problems here is that this element:
   <xsl:namespace-alias stylesheet-prefix="html" result-prefix="#default" />
is causing difficulty because there is no default namespace, and no URI 
associated with it."

I understand that this is something that absolutely would need to be 
addressed, but it doesn't apply to my example.  In the above it shouldn't 
matter if there is a default namespace or not.  The namespace-alias (at least 
in my thinking) says take the uri associated with "html" and make it the 
default namespace uri in the resulting document.  It would be an error if the 
html prefix wasn't defined in the stylesheet where that particular namespace-
alias element occurred, but in my examples I assume it is already defined.

Regards,
Galen

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to