harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Ellison <t.p.elli...@gmail.com>
Subject [classlib][niochar] charset providers
Date Thu, 10 Jul 2008 09:38:55 GMT
I've been playing with nio_char to see if I can easily reduce the 
footprint of a Harmony install, and make the charset data more modular.

At the moment, that module build into nio_char.jar (1.32Mb) and 
hycharset.dll (1.51Mb), and uses the ICU charset code in 
icu4j-charsets-3_8.jar (2.36Mb).

These are so big because a number of the charset encoders/decoders are 
data driven rather than algorithmic.

Q1: Why do we only specify the ICU providers in the services file? 
Seems like we are not even using the Harmony providers at all.

So I updated that file to prefer the Harmony providers.

The providers use heuristics about when it makes sense to go into the 
native code to do the encode/decode.  So I've simply added a flag to see 
if the natives are available, allowing me to remove the hycharset.dll 
and loose no functionality when space is at a premium.

Finally the Harmony charsets are split across standard and additional 
providers, but they are all accessed from the same provider.

Q2: What is the distinction used to classify some as standard and some 
as additional?  The spec requires only a small subset of charsets 
supported as standard [2].

For now I just split the packaging into Harmony's standard/additional 

So I've ended up with:
   nio_char.jar (155kb)
   nio_char_add.jar (1.23Mb) optional
   hycharset.dll (1.51Mb)  optional
   icu4j-charsets-3_8.jar (2.36Mb) optional

Like I say, I'd have to restructure Harmony's definition of standard 
charsets to comply with the spec since we have far more in there than 
the spec requires.

[2] http://java.sun.com/j2se/1.5.0/docs/api/java/nio/charset/Charset.html


View raw message