It sounds like you’re trying to encode glyphs or glyph fragments, not characters. There is a virtually endless repertoire of “shapes” that could be encoded, but unless each of these is a character actually used in a writing system (not just hypothetically), it’s probably not appropriate for a character encoding.
-- Doug Ewell | Thornton, Colorado, USA | RFC 5645, 4645, UTN #14 www.ewellic.org | www.facebook.com/doug.ewell | @DougEwell From: srivas sinnathurai Sent: Saturday, August 20, 2011 3:35 To: Christoph Päper Cc: [email protected] Subject: Re: Code pages and Unicode About the research works. I alone (with with my colleagues) researching the fact that Sumerian is Tamil / Tamil is Sumerian This requires quite a lot of space. Additionally I do research on Tamil alphabet as based on scientific definitions and it only represents the mechanical parts , ie only represents the places of articulation as alphabet and not sound based. And, what is call a mathematical multiplier theory on expanding the alphabets leads to not just long-mathematics (nedung kaNaku), but also to extra long mathematics. This is just a sample requirement from me and my colleagues. How many others are there who would require Unicode support? Do you think allocating 32,000 to the code page model would help? Regards Sinnathurai
