[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xalan-c-users
Subject:    Re: Does Xalan care about Xerces compile settings?
From:       David Bertoni <dbertoni () apache ! org>
Date:       2011-04-09 18:34:43
Message-ID: 4DA0A6C3.3000405 () apache ! org
[Download RAW message or body]

On 4/6/2011 4:03 PM, Garyl Erickson wrote:
> 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?
The message loader is separate and is not dependent on the Xerces-C 
settings. Note that the ICU message load is broken with newer versions 
of the ICU. Luckily, there is no advantage to using the ICU message 
loader over the in-memory message loader.

The transcoder setting is a bit of a misnomer, and really needs to be 
cleaned up. In fact, this really controls whether or not Xalan-C uses 
the ICU to enable certain functionality, such the Unicode collation 
algorithm, and support for the number-format function.

For transcoding, Xalan-C always uses whatever transcoding service you've 
built into Xerces-C.

Dave
[prev in list] [next in list] [prev in thread] [next in thread]