Also many languages such as Hebrew Arabic and more does not have upper/lower case thingy (Arabic have for most but not all chars 3 types of appearing one at the beginning of the word/next to a non combined char), one in the middle of the chars (combined on both sides) and one for the end, if it does not combine after that char like end of a word or char just not part of the combined chars.
So it's not simple to Math it, unlike ASCII regarding regular latin chars. Ido On Tue, Aug 26, 2008 at 12:05 PM, Daniël Mantione <[EMAIL PROTECTED]> wrote: > > > Op Tue, 26 Aug 2008, schreef Graeme Geldenhuys: > >> On Tue, Aug 26, 2008 at 9:19 AM, Graeme Geldenhuys >> <[EMAIL PROTECTED]> wrote: >>> >>> project. Maybe we could use something there - it's written in Object >>> Pascal as well? The LPTK project used a BSD license. >> >> I had a quick look at the LPTK project source... So I gather this >> implementations is totally rubbish? First of all, a Unicode char is >> defined as a word (2 bytes), so that means it's only UCS2 compliant >> and not full Unicode UTF-16 (which is what we want). > > For uppercasing/lowercasing it is correct to define a Unicode char as 2 > bytes. > >> Plus, it uses no >> lookup tables as far as I can see - frankly, I don't understand the >> code at all. :-) > > The code is simple: If the char is in [#0..#255], it does a normal upcase, > otherwise it sets the least significant bit to zero. Seems not correct to > me. > > Daniël > _______________________________________________ > fpc-devel maillist - fpc-devel@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-devel > > -- http://ik.homelinux.org/
_______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
