Discussion bug XALANJ-1906

[Robert van Loenhout <r....@greenvalley.nl>]

Hi,

I would like to discuss bug XALANJ-1906  [xhtml output] Empty element 
form for non EMPTY declared elements.

Currently the XHTML output for non EMPTY elements without content is 
invalid.

I was wondering if someone is trying to resolve it.
Why is the priority set to minor? Isn't the fact that XHTML output is 
not possible a major issue?

If nobody is trying to resolve it should I try to resolve it by myself?
And if so should I fix it based on 2.6.0 or on the HEAD?

Any ideas about when a new version of XalanJ will be released?

Kind regards,
Robert


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org

Re: Discussion bug XALANJ-1906

[Henry Zongaro <zo...@ca.ibm.com>]

Hi, Robert.

Robert van Loenhout <r....@greenvalley.nl> wrote on 2005-02-22 
05:57:22 AM:
> I would like to discuss bug XALANJ-1906  [xhtml output] Empty element 
> form for non EMPTY declared elements.
> 
> Currently the XHTML output for non EMPTY elements without content is 
> invalid.
> 
> I was wondering if someone is trying to resolve it.
> Why is the priority set to minor? Isn't the fact that XHTML output is 
> not possible a major issue?

The priority was set by the original reporter of the problem.  I guess 
Marco didn't feel it was a particularly important problem.

> If nobody is trying to resolve it should I try to resolve it by myself?

You should always feel free to at work on any problem that interests you. 
I don't know that anyone is actively working on that particular problem.

The extent of the support for XHTML serialization is really very limited - 
elements that are empty are emitted with a space before the closing "/>" 
characters.  Support for XHTML is not something that is required (or 
specified) by XSLT 1.0 or by JAXP, so not much effort ever went into 
providing a full-featured implementation of XHTML serialization.

> And if so should I fix it based on 2.6.0 or on the HEAD?

It's preferable if patches are based on the head of the MAIN branch.  I 
suggest you take a look at 
org.apache.xml.serializer.ToHTMLStream.m_elementFlags for an idea of how 
you might handle this problem.

> Any ideas about when a new version of XalanJ will be released?

There was some discussion of a Xalan-J 2.7.0 release that would include 
support for the transform and XPath APIs of JAXP 1.3, but that stalled 
when Sun ran into some legal snags with releasing its reference 
implementation of JAXP 1.3.  I'm not sure where the legal discussions 
between Sun and Apache sit today.

Thanks,

Henry
------------------------------------------------------------------
Henry Zongaro      Xalan development
IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
mailto:zongaro@ca.ibm.com



---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org