Joel,
Making a dependency on a library is not a trivial thing. You have not
given me a task that you currently cannot implement without making the
SWORD library ALWAYS need icu.
Your praise of the functionality of icu is rightly due, and I say 'use
it'. But we will not force
On October 1, 2002 00:46, Troy A. Griffitts wrote:
> My position on ICU:
>
> We use it in the engine. It is never exposed in the engine and is
> always optional.
>
> For example, we have a utf8_toupper function in the api that does it's
> best to change a utf8 string to uppercase. If the api is
This would make sword unusable on Handhelds for non-Roman languages. There
must be a better way.
I don't know too much about ICU. Is it possible only to extract the
functionality you want, say, by static linking? For example, would the
toupper functionality really blow up the api so bad that i
My position on ICU:
We use it in the engine. It is never exposed in the engine and is
always optional.
For example, we have a utf8_toupper function in the api that does it's
best to change a utf8 string to uppercase. If the api is configured to
use icu, it does a much better job for non-rom
I agree with Joel. ICU dependancy is the price we have to pay for clean
Unicode support. We also will need it for the locale handling (toupper).
Martin
Am Dienstag, 1. Oktober 2002 00:40 schrieb Joel Mawhorter:
> Hi all,
>
> I'm writting to get reactions to the idea of making sword dependent o
Hi all,
I'm writting to get reactions to the idea of making sword dependent on ICU.
Currently we only have optional dependencies on ICU (at least for
transliteration but I'm not sure what else). I would like to suggest making
ICU required for sword. The reason I would like to see this happen i
