Xalan-C 1.11 - Question on ICU builds

[sh...@e-z.net]

When building the Xalan-C 1.11 sources in SVN repository for ICU support,
should we also link with the Xerces-C 3.1.1 parser library that is
compiled with ICU support?

I would appreciate your discussion!

Sincerely,
Steven J. Hathaway



---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org

Re: Xalan-C 1.11 - Question on ICU builds

[sh...@e-z.net]

> On 12/5/2011 5:46 PM, shathawa@e-z.net wrote:
>> When building the Xalan-C 1.11 sources in SVN repository for ICU
>> support,
>> should we also link with the Xerces-C 3.1.1 parser library that is
>> compiled with ICU support?
> We should simply remove the old AllInOneWithICU project files. Here's
> how the ICU integration works with Xalan:
>
> AllInOneWithICU -- uses the ICU for message loading, collation and
> support for the format-number() function.
>
> AllInOne -- uses the ICU for collation and support for the
> format-number() function when one of the ".. with ICU" configurations is
> selected.
>
> Someone would need to re-write how we use the ICU for message loading as
> the way we were doing it was deprecated and is no longer supported. I
> don't think this is very worthwhile since the only advantage to the ICU
> message loading over any of the others is that it allows multiple
> languages in a single resource file. I can't imagine a practical use
> case where Xalan operates in multiple languages in a single invocation,
> so it seems like ICU message loading is overkill.
>
> Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xalan-dev-help@xml.apache.org
>
>
Thanks Dave,

Examining the Windows build structure for XalanC-1.11, the
AllInOneWithICU project (XalanICU.sln Solution) seems to be broken!

The AllInOne project (Xalan.sln Solution) has limited support for ICU,
but I have been unable at this time to do any testing.  I don't
currently have a platform that uses IBM-ICU libraries.

I am wondering how well the Xerces_C (parser) with ICU integrates
into the Xalan-C (XSLT) platform.

Your comments are appreciated.

Sincerely,
Steven J. Hathaway
- Xalan Documentation Project



---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org

Re: Xalan-C 1.11 - Question on ICU builds

[David Bertoni <db...@apache.org>]

On 12/5/2011 5:46 PM, shathawa@e-z.net wrote:
> When building the Xalan-C 1.11 sources in SVN repository for ICU support,
> should we also link with the Xerces-C 3.1.1 parser library that is
> compiled with ICU support?
We should simply remove the old AllInOneWithICU project files. Here's 
how the ICU integration works with Xalan:

AllInOneWithICU -- uses the ICU for message loading, collation and 
support for the format-number() function.

AllInOne -- uses the ICU for collation and support for the 
format-number() function when one of the ".. with ICU" configurations is 
selected.

Someone would need to re-write how we use the ICU for message loading as 
the way we were doing it was deprecated and is no longer supported. I 
don't think this is very worthwhile since the only advantage to the ICU 
message loading over any of the others is that it allows multiple 
languages in a single resource file. I can't imagine a practical use 
case where Xalan operates in multiple languages in a single invocation, 
so it seems like ICU message loading is overkill.

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org

RE: Xalan-C 1.11 - Question on ICU builds

[sh...@e-z.net]

Martin,

In previous Xalan-C 1.10 with ICU support, there was no ICU integrated
into Xerces-C.

I am wondering if any users have experience compiling and using the current
Xalan-C 1.11 with ICU.  I would like their insights for the documentation
project.

Thanks,
Steven J. Hathaway

> Steven asked the following a while back:
>>When building the Xalan-C 1.11 sources in SVN repository for ICU support,
>> should we also link with the Xerces-C 3.1.1 parser library that is
>> compiled with ICU support?
>
> I'm not quite sure what Steven meant to ask.  If you're going to use an
> "ICU using" Xalan then it seems to me that you should also be using an
> "ICU using" Xerces.
>
> OTOH, if the question is: should the use of possibly unnecessary
> dependencies on ICU be encouraged, I think that we should not do that.
>
> David Bertoni also said something a while back about how ICU transcoding
> is done, IIRC he wrote that Xalan/Xerces doesn't use much of ICU,
> but I can't find that post anymore :(
>
> Sincerely,
> Martin
>
>
> 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
> MailAdmin@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.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xalan-dev-help@xml.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org

RE: Xalan-C 1.11 - Question on ICU builds

[Martin Elzen <Ma...@usoft.com>]

Steven asked the following a while back:
>When building the Xalan-C 1.11 sources in SVN repository for ICU support, should we also link with the Xerces-C 3.1.1 parser library that is compiled with ICU support?

I'm not quite sure what Steven meant to ask.  If you're going to use an "ICU using" Xalan then it seems to me that you should also be using an "ICU using" Xerces.

OTOH, if the question is: should the use of possibly unnecessary dependencies on ICU be encouraged, I think that we should not do that.

David Bertoni also said something a while back about how ICU transcoding is done, IIRC he wrote that Xalan/Xerces doesn't use much of ICU,
but I can't find that post anymore :(

Sincerely,
Martin


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 MailAdmin@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.

---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org