David Bertoni wrote:
>
> ra wrote:
>>
>> David Bertoni wrote:
>>> ra wrote:
>>>> How to force xalan to not closing tags, I mean I've for example tag
>>>> and after transformation it's changed to , it's not desired behaviour
>>>> for
>>>> me
>>> Well, it looks like something along the way has stripped the sample
>>> markup
>>> from your post, so I'm going to have to guess what you're asking for.
>>>
>>> Xalan-J's XML serialization method can only generate well-formed markup,
>>> so
>>> you cannot generate unclosed tags, without resorting to hacks like
>>> disable-output-escaping.
>>>
>>> You'll have to post-process the serialized XML to remove whatever
>>> closing
>>> tags you don't want.
>>>
>>> Dave
>>>
>>>
>>
>>
>> Here is a sample, it should be visible
>> <xx></xx> is change to <xx/>
>> I belive both samples are well-formed but only first one is accepted for
>> example if instead of xx we put a (like anchor link)
> OK, so you meant an empty tag, not an unclosed tag. The two forms are
> considered identical in XML, so there's no way to tell the serializer to
> use one or the other. It sounds like you really need to generate XHTML
> for
> a broken browser, and that's tricky to do without a custom output method.
>
> Dave
>
>
Thanks, I try to use xhtml I hope without negative impact for the content
that already exists
BTW according to the specification empty a tag is not allowed and behaviour
of the browser is undetermined. And really IE and Firefox don't manage with
empty tag. Firebug shows that Firfox opens a tag, insert some content,
generates hundreds of links
Regards,
Arek
--
View this message in context:
http://www.nabble.com/closed-tags-tp14421214p14433776.html
Sent from the Xalan - J - Users mailing list archive at Nabble.com.
