Hi Colin,

If you can come up with a small set of examples which illustrate what you
are seeing, especially any differences between Xalan-C and xsltproc, that
would be great.  You can post them to the list, or create a bugzilla
report.

Thanks!

Dave



|---------+--------------------------->
|         |           Colin Paul Adams|
|         |           <[EMAIL PROTECTED]|
|         |           mon.co.uk>      |
|         |                           |
|         |           06/26/2003 11:17|
|         |           AM              |
|---------+--------------------------->
  
>---------------------------------------------------------------------------------------------------------------|
  |                                                                             
                                  |
  |        To:      xalan-c-users@xml.apache.org                                
                                  |
  |        cc:      (bcc: David N Bertoni/Cambridge/IBM)                        
                                  |
  |        Subject: Re: spurious (?) xmlns="" added by transform                
                                  |
  
>---------------------------------------------------------------------------------------------------------------|



>>>>> "david" == david n bertoni <[EMAIL PROTECTED]> writes:

    david> Hi Colin,

    >> >>>>> "david" == david n bertoni <[EMAIL PROTECTED]>
    >> writes:
    >>
    david> Hi Colin,
    >>
    >>  It was a combination of the two - I just don't understand why
    >> it happens so sporadically.

    david> When you say "sporadically," do you mean it's a bug, or
    david> that you don't understand when a namespace declaration of
    david> the form xmlns="" is necessary?  I don't want to ignore
    david> what might be a bug in Xalan.

The latter.
I still cannot understand why some elements needed it, and some did
not.

Also, xsltproc gave different results (after I made some changes, xslt
also added xmlns="" is some cases, but not the same set of cases.

    >> Anyway, I fixed it by declaring the default namespace on the
    >> zsl:transform element.

    david> Fixed it in all cases, or in just this one?

Well, the whole transform now works as I expect it to.
--
Colin Paul Adams
Preston Lancashire


Reply via email to