RE: xalan 1.5 build problem on tru64

Hi! Yes, I used Xalan 1.3 (with Xerces 1.6) on tru64 without any problem. Thanx, I will try to make an error free link. mean >-Original Message- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Thursday, May 29, 2003 6:12 PM >To: [EMAIL PROTECTED] >Subject: Re: xalan 1.5 bui

cvs commit: xml-xalan/java/src/org/apache/xml/serializer ToHTMLStream.java ToXMLStream.java ToStream.java ToTextStream.java

minchau 2003/05/30 00:08:43 Modified:java/src/org/apache/xml/serializer ToHTMLStream.java ToXMLStream.java ToStream.java ToTextStream.java Log: Minor changes to m_writer.write(). Changing write("x") to write('x'). Changing write('a'); write('b'); to write

cvs commit: xml-xalan/c/src configure Makefile.in

dbertoni2003/05/29 17:27:25 Modified:c/srcconfigure Makefile.in Log: zOS updates. Revision ChangesPath 1.10 +1 -1 xml-xalan/c/src/configure Index: configure === RCS file: /home/cvs/xml-

cvs commit: xml-xalan/c/src/XSLT NamespacesHandler.hpp

dbertoni2003/05/29 17:26:34 Modified:c/src/XSLT NamespacesHandler.hpp Log: Added missing export. Revision ChangesPath 1.19 +1 -1 xml-xalan/c/src/XSLT/NamespacesHandler.hpp Index: NamespacesHandler.hpp ==

cvs commit: xml-xalan/c/src/PlatformSupport DOMStringHelper.cpp DOMStringHelper.hpp

dbertoni2003/05/29 17:26:10 Modified:c/src/PlatformSupport DOMStringHelper.cpp DOMStringHelper.hpp Log: Changes for new zOS compiler. Revision ChangesPath 1.86 +7 -8 xml-xalan/c/src/PlatformSupport/DOMStringHelper.cpp Index: DOMStrin

cvs commit: xml-xalan/c/src/Include VCPPDefinitions.hpp

dbertoni2003/05/29 17:25:26 Modified:c/src/Include VCPPDefinitions.hpp Log: Moved export keyword for better compatibility with zOS compiler. Revision ChangesPath 1.23 +2 -2 xml-xalan/c/src/Include/VCPPDefinitions.hpp Index: VCPPDefinitions.hpp ===

cvs commit: xml-xalan/c/src/Include OS390Definitions.hpp

dbertoni2003/05/29 17:24:59 Modified:c/src/Include OS390Definitions.hpp Log: Changes for new zOS compiler. Revision ChangesPath 1.15 +5 -34 xml-xalan/c/src/Include/OS390Definitions.hpp Index: OS390Definitions.hpp ===

Re: U_ICU_NAMESPACE

Hi David, This was a case where I was compiling Xalan 1.4 with ICU 2.2 on zOS 1.4 ( supposedly an improved update on zOS from the problematic OS390 v2r10 compiler). For some reason I wasn't seeing that macro get defined so I'm about convinced now that something went wrong with the ICU buil

Re: U_ICU_NAMESPACE

Hi Suzanne, Dmitry is correct -- that macro is defined by the ICU. What version of the ICU are you using? We only test ICU 2.2 with that version of Xalan, and all versions of ICU since 2.0 have defined that macro. Dave

Re: U_ICU_NAMESPACE

Hi Dmitry, In ICUBridgeCollationCompareFunctorImpl.hpp there is a place where U_ICU_NAMESPACE is checked before setting up a typdef for 'Collator'. I think what happened here is that this U_ICU_NAMESPACE is maybe supposed to be exported out of an ICU library and somehow my ICU library

Re: xalan 1.5 build problem on tru64

Hi, We don't officially support Tru64, but we build on the platform regularly, and I believe you can ignore those warnings. There are some issues with the standard library shipped with the Tru64 compiler, and I was never able to get it to work with the Xalan code, nor could I get rid of these

Re: U_ICU_NAMESPACE

Hi Suzanne! May be I don't understand the question, but I don't see any connection between U_ICU_NAMESPACE (ICU definition) and XALAN_NO_NAMESPACES define I mean that U_ICU_NAMESPACE is still included and still exists, but it's simply isn't used (like other namespace definitions) Hope I've answ

cvs commit: xml-xalan/java/xdocs/sources/xalan history.xml

ilene 2003/05/29 07:27:12 Modified:java/xdocs/sources/xalan history.xml Log: Updated history file from Christine Li ([EMAIL PROTECTED]) Revision ChangesPath 1.36 +27 -0 xml-xalan/java/xdocs/sources/xalan/history.xml Index: history.xml ===