I can’t speak to the do-Xerces-settings-have-to-be-the-same-as-Xalan settings question, but as far as Xalan goes, the transcoder option does not have to be the same as the message loader. We are using ICU as transcoder which works fine, but ICU as message-loader did totally not work, so we ended up just using the default for message-loading.
From: Garyl Erickson [mailto:garyl.erick...@flec.tv] Sent: Thursday, April 07, 2011 1:04 AM To: xalan-c-users@xml.apache.org Subject: Does Xalan care about Xerces compile settings? Does Xalan care about any of the five Xerces settings that are settable during, and reported by, the configure step, which are: File Manager: POSIX | ... Mutex Manager: Windows | ... Transcoder: gnuiconv | iconv | icu | macosunicodeconverter | windows NetAccessor: curl | socket | cfurl | winsock | none Message Loader: inmemory | icu | iconv I.e., does the Xalan runConfigure -t setting have to match a Xerces configure --enable-transcoder-* setting or does the Xalan runConfigure -m setting have to match a Xerces configure setting? Also, do any of these Xerces settings have to match each other, i.e., if iconv is used for transcoder, does it also have to be used for message loader? Thanks ________________________________ 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.
