On Tue, Feb 22, 2011 at 3:33 AM, Daniel Herring dherr...@tentpost.comwrote:
As for the database, you can always split it into separately loadable
chunks and throw an error if a chunk is not available when needed.
It seems that I did not explain myself properly. There have been several
threads
On 2/22/11 3:14 AM, Juan Jose Garcia-Ripoll wrote:
I am not going to move ECL from its current single-word (16 or 32 bit)
encoding right now. It would be too much of a hassle. I am just
offering the possibility of having a compromise for devices and
platforms that do not care much about the
On Sat, 19 Feb 2011, Juan Jose Garcia-Ripoll wrote:
Would you find it useful to have an ECL that only supports character codes 0
- 65535? That would make it probably easier to embed the part of the Unicode
database associated to it ( 65535 bytes) and have a standalone executable.
On Sat, 19 Feb 2011 23:43:33 +
Juan Jose Garcia-Ripoll juanjose.garciarip...@googlemail.com wrote:
Would you find it useful to have an ECL that only supports character codes 0
- 65535? That would make it probably easier to embed the part of the Unicode
database associated to it ( 65535
