DO NOT REPLY [Bug 31000] - xml data is lost through transformation of Xalan-J2 xslt.Process key() function

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

DO NOT REPLY [Bug 31000] - xml data is lost through transformation of Xalan-J2 xslt.Process key() function

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

DO NOT REPLY [Bug 31000] - xml data is lost through transformation of Xalan-J2 xslt.Process key() function

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

DO NOT REPLY [Bug 31000] New: - xml data is lost through transformation of Xalan-J2 xslt.Process key() function

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

DO NOT REPLY [Bug 30999] - for-each bug on union of elements returned by key()

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

DO NOT REPLY [Bug 30999] New: - for-each bug on union of elements returned by key()

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

Re: [VOTE]: motion to transform Xalan into a top-level Apache project.

+1 to items 1,2,3,5,6 below (binding, PMC member). Yay Xalan! -1 to item 4 below. I would be very uncomfortable with only 2 people on a PMC; in my mind, an absolute minimum would be 5 existing and reasonably active committers. Also, I doubt the board will accept a PMC that small. Work with S

DO NOT REPLY [Bug 30750] - Minor spelling problems in XalanMsg_en_US.xlf

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

AIX 4.3.3 + gcc 3.3.4: punt!

Hi everyone, I told everyone I'd let them know what was needed to do to build xerces + Xalan on AIX using gcc instead of xlc/xlC. I was able to get xerces to build, and link with our existing programs. I needed to manually add an empty entry point. (All AIX shared libraries need this). Do do

Re: [VOTE]: motion to transform Xalan into a top-level Apache project.

+1 (with some thoughts below) Brian Minchau wrote: Hello, I'm formally calling for a vote on this proposition which is to transform Xalan from a sub-project of the Apache top-level XML project into a top-level Apache project of its own. 1. The top-level Xalan project will contain the existing Xal

Re: [VOTE]: motion to transform Xalan into a top-level Apache project.

+1 Regards, Arun. Brian Minchau wrote: Hello, I'm formally calling for a vote on this proposition which is to transform Xalan from a sub-project of the Apache top-level XML project into a top-level Apache project of its own. 1. The top-level Xalan project will contain the existing Xalan-J and X