[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: Allegro Developers <alleg-developers@xxxxxxxxxx>
- Subject: [AD] Unicode limitations
- From: guilt <karthikkumar@xxxxxxxxxx>
- Date: Wed, 30 Mar 2005 08:51:09 +0530
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=Jg9A5tpOCCw+ZqnkR93Ta1XBZAd4GfNLSOnXVtclhkay6eltCRKjqfH4hXr+sRffKLfPoxkoFhde6vpLNmIuUkbYZDnE07q+iu3S56H3mr61/WgiWEQSOn8JCBoPnbxdFqxX+lz23By5kUBHocJ/dFCSvaCcKdFPchQ5W4VIrLk=
Hi,
(looks like I'm the one who's currently doing the passive work over here :P !!)
I just hit upon this idea .. for the unicode and font rendering
routines... if we do manage to make a vtable based interface, we
should then find a way of applying "production rules" to glyphs of
certain languages and locales, (tamil and kannada included!) ... The
whole point is, some glyph sequences may have to be concatenated
together to make sense.. while it might appear sensible to keep them
written horizontal (left to right), there are some limitations in
making text "look" other ways .. for instance, scroll top to bottom
... in that case, we shouldn't do it integer by integer .. rather,
glyph by glyph.. and a glyph might be a sequence of one or more
integers ...
Well, I just got this idea.. anybody with a similiar language
limitation can let us know what they feel about this idea.
--
Karthik
http://guilt.bafsoft.net