On 17 Feb 2016, at 19:56, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
I read the whole Article, seems like a tricky, to not say hard, subject.
Yes. The Unicode specs are big and complex. Step one is to read & understand them, at least well enough to find your way. Doing some implementation is not too hard, but getting 100% scores on the very extensive test suites was/is quite hard.
The article is very detailed and well written though.
Thx.
What is the rationale behind embracing such a challenging feature like supporting Unicode?
Unicode is the de facto standard for internationalisation of computer software. Any serious platform has to tackle (big parts of) Unicode.
Regards!
Esteban A. Maringolo
2016-02-17 15:24 GMT-03:00 Max Leske <maxleske@gmail.com>:
Good stuff guys!
On 17 Feb 2016, at 10:16, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Hi,
In Pharo we can deal with and represent any Unicode character and string, but there are still some important pieces of functionality missing.
The goal of the Pharo Unicode project is to gradually improve and expand Unicode support in Pharo. We started in December last year to lay the foundation and are now ready to go public with what we built.
The first delivery is an implementation of Unicode Normalization, together with an implementation of the Unicode Character Database.
Please read the following article for more information (the appendix explains how to get the code).
An Implementation of Unicode Normalisation
Streaming NFC, NFD, NFKC & NFKD, normalization QC and normalization preserving concatenation.
https://medium.com/concerning-pharo/an-implementation-of-unicode-normalizati...
The development branch also contains a work in progress implementation of Unicode Collation.
Much work remains to be done and contributions are more than welcome.
Sven & Henrik