Martin, How to get SVN version of XALAN. I do not have userID/passwd for SVN, do I need that?
Please let me know how to get the SVN version of XALAN, I already have xerces 3.1. Dinesh On Tue, Oct 11, 2011 at 5:17 AM, Martin Elzen <martin.el...@usoft.com>wrote: > A cursory look at http://xml.apache.org/xalan-c/download.html seems to > indicate that there are no prebuilt binaries of Xalan 1.10 available for any > other Visual C version than VC6. If memory serves, **officially** the > latest ‘compatible’ combinations of ICU, Xerces and Xalan are respectively > 3.4, 2.7 and 1.10 . Which you’ll probably all have to build yourself. > Which I really don’t recommend trying. Are you absolutely sure you can’t > make do with Xerces 3.1.1 and the SVN version of Xalan (and without ICU)? > If you can use Xerces 3.1.1 there **are** pre-built binaries available > from VC 7.1 up to and including VC 10… (see > http://xerces.apache.org/xerces-c/download.cgi)**** > > ** ** > > Martin **** > > ** ** > > *From:* Dinesh Behl [mailto:dinesh.b...@gmail.com] > *Sent:* Tuesday, October 11, 2011 1:23 AM > *To:* xalan-dev@xml.apache.org > *Subject:* Needed Xalan 1.10 C++ libraries**** > > ** ** > > ......built on VC 9. How can I get it? Also please let me know the > compatible Xerces version.**** > > **** > > Please advice.**** > > **** > > Thanks in advance.**** > > **** > > Dinesh**** > > ------------------------------ > The information contained in this communication is intended solely for the > use of the individual or entity to whom it is addressed and others > authorized to receive it. It may contain confidential or legally privileged > information. If you are not the intended recipient you are hereby notified > that any disclosure, copying, distribution or taking any action in reliance > on the contents of this information is strictly prohibited and may be > unlawful. If you have received this communication in error, please notify us > immediately by forwarding this email to mailad...@usoft.com and then > delete it from your system. > > USoft is neither liable for the proper and complete transmission of the > information contained in this communication nor for any delay in its > receipt. >
