On 13/06/12 18:06, Carsten Haitzler (The Rasterman) wrote: > its not the freetype font glyph index - its the codepoint - unicode. call it > whatever u like - it has to be an int. read temrinology's code. it does this > and it works just fine.. between fonts.
Ok, codepoint, and unicode, that's Eina_Unicode, it's *always* at least 32 bit which is perfect for what you need. That's what we use for unicode codepoints all across the EFL (when it's code I laid my eyes upon). > >> said, it won't work between fonts, so you have to store the unicode >> value... And if you store the unicode value, why not use Eina_Unicode >> which was made just for that? > > 16bits is not enough on windows. at least that's what vincent claims. and > there > is no need or DESIRE to abstract this. size matters. we need 32bits of space. > efl works on the notion that int == 32bits. make it an int. It's always 32bit. There are many reasons to abstract that: 1. I did it ages ago and it's already used in many places of the EFL. 2. It shows that the value is supposed to be a valid unicode code point. 3. If the platform's wchar_t is 32bit it'll use it, which means you gain debugger support for printing those as wide strings (which is awesome). It's the same concept of Evas_Coord with the extra benefit of bullet #3. Vincent: Anyhow, no matter what you do, call it codepoint, or something like that, not glyph. -- Tom. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
