[jira] Commented: (XALANC-471) file permissions wrong in 1.9 xalan-c source distribution....

[ http://issues.apache.org/jira/browse/XALANC-471?page=comments#action_62617 ] Steve Glaser commented on XALANC-471: - I don't understand. Your resolution comments says to use switch to CVS or to Version 1.9 but the complaint is _about_ version 1.9.

[jira] Resolved: (XALANJ-2098) ToHTMLStream: no space between PUBLIC and SYSTEM identifiers if both present

[ http://issues.apache.org/jira/browse/XALANJ-2098?page=history ] Brian Minchau resolved XALANJ-2098: --- Resolution: Duplicate Probably a duplicate of an earlier bug. Resolving as duplicate, but it is already fixed in CVS. > ToHTMLStream: no space

[jira] Created: (XALANC-480) XML1.1 and Namespaces for XML1.1 support

XML1.1 and Namespaces for XML1.1 support - Key: XALANC-480 URL: http://issues.apache.org/jira/browse/XALANC-480 Project: XalanC Type: New Feature Components: XalanC Versions: CurrentCVS Environment: all Report

[jira] Resolved: (XALANC-471) file permissions wrong in 1.9 xalan-c source distribution....

[ http://issues.apache.org/jira/browse/XALANC-471?page=history ] Dmitry Hayes resolved XALANC-471: - Resolution: Won't Fix Please try the latest CVS or the XalanC1.9. Thanks! > file permissions wrong in 1.9 xalan-c source distribution >

[jira] Created: (XALANC-479) Remove test cases from Windows project files

Remove test cases from Windows project files Key: XALANC-479 URL: http://issues.apache.org/jira/browse/XALANC-479 Project: XalanC Type: Improvement Components: XalanC Versions: 1.10 Environment: Windows Re

[jira] Updated: (XALANC-479) Remove test cases from Windows project files

[ http://issues.apache.org/jira/browse/XALANC-479?page=history ] Matt Hoyt updated XALANC-479: - Attachment: patch.txt Please review > Remove test cases from Windows project files > > > Key: XALANC-479 >

[jira] Commented: (XALANJ-2098) ToHTMLStream: no space between PUBLIC and SYSTEM identifiers if both present

[ http://issues.apache.org/jira/browse/XALANJ-2098?page=comments#action_62575 ] Sergey Ushakov commented on XALANJ-2098: Yes, that is exactly what I meant. I can confirm that the current code in the CVS is ok. I'll look better in the CVS next

[jira] Commented: (XALANC-474) Segmentation Fault (core dumped) on Solaris using Xalan

[ http://issues.apache.org/jira/browse/XALANC-474?page=comments#action_62569 ] Dmitry Hayes commented on XALANC-474: - I can't reproduce it with the latest CVS too. Can you please get the latest CVS version (we have the source only) and rebuild it ?

[jira] Commented: (XALANJ-2098) ToHTMLStream: no space between PUBLIC and SYSTEM identifiers if both present

[ http://issues.apache.org/jira/browse/XALANJ-2098?page=comments#action_62561 ] Brian Minchau commented on XALANJ-2098: --- Sergey, the current code in CVS in ToHTMLStream.startDocumentInternal(), is more or less this: writer.write("'); I think th

[VOTE] for XalanC committers : Bi-weekly call

Hello XalanC committers! I'd suggest to schedule a biweekly teleconference call for discussing our current matters and better coordination on every second Tuesday , 4 PM EST Here is my +1 Thanks! Dmitry Hayes

Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3 Sources to Apache]]

Hello All, Sometimes back i wrote an article on JAXP 1.3 which explains the new concepts and important features introduced in JAXP 1.3 Especially the new - Schema Validation Framework - Object model neutral XPath APIs - XML Schema Datatypes etc. Advantages of New Schema Validation Framework and h

xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3 Sources to Apache]

Hello All, xml-commons has been upgraded to JAXP 1.3 APIs. If anyone could try and confirm that would be great. - Neeraj Neeraj Bajaj wrote: I tagged xml-commons module yesterday with tag name '*before-jaxp13-upgradation*'. I plan to do the following but i will wait till tomorrow so as to give c

[EMAIL PROTECTED]: Project xalan (in module xml-xalan) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xalan has an issue affecting its community integration. This issue affects 317 pr

[EMAIL PROTECTED]: Project xsltc (in module xml-xalan) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xsltc has an issue affecting its community integration. This issue affects 1 proj