Hi,

Have a look at the definitions I used for the SCIM Wijesekera layout (see layout.h). It's quite close to the schemes you have come up with.

I think it meets your requirements...

Also note the compound definitions. They accomplish 2 things:

1. Testing for compound characters is easy (test 1 bit).
2. The low (n) bits can be used in a lookup table (see parser.cpp for what I mean).

දුෂාර

On 08/04/2008, Harshula <harshula@gmail.com> wrote:
Hi,

I've attached two files, both incomplete, that I was working on but gave
up on in 2005. It will be great to get some input from others.

REQUIREMENTS
============

1) The #defines should be as short/concise as possible.
2) Try and make the #defines visually unambiguous.
3) We have to get it right the first time. These are #defines, so once
we define them, it's unlikely we'll be allowed to change them.
4) Use ASCII characters.

ISSUES
======

a) I abandoned the fullnames version because they were ridiculously
long.

b) I then used the Unicode chart's shortnames, but how should we
differentiate between an independent vowel and a dependent vowel?
- Using case sensitivity to differentiate might be frowned upon.
- I tried adding "_pilla" for D/Vs but that made the name longer.
- I could add a suffix of "_p" for D/Vs.
- How should we name vocalic I/Vs and D/Vs?

cya,
#

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
sinhala-technical mailing list
sinhala-technical@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sinhala-technical