Re: Proposal for the Basis ofaCodepointExtensiontoUnicodeforthe Encoding of theQuranicManuscripts

[Abdulhaq Lynch <al-arabeyes at alinsyria dot fsnet dot co dot uk>]

It seems to me that two encodings would be useful:

Advanced Encoding: suitable for the future, incorporating the best of the 
encoding ideas floated here, which assumes a powerful renderer such as 
OpenType.

Primitive Encoding: works with truetype and bitmap fonts, uses composite 
glyphs whenever and wherever necessary, as many as required for the most 
basic environment such as the console, pda etc.

Both encodings will need some extension to the current Unicode map.

A simple piece of software will convert from the Advanced Encoding (AE) to the 
Primitive Encoding (PE) though will not be required if using OpenType.

I think, Meor, that you know better than anyone else what is required for the 
Primitive Encoding (PE). Why not just tell us what is required and invent a 
series of codepoints that will set a de facto standard. In the meantime we 
can work on the AE.

wassalaam
abdulhaq

> Ok, now for my suggestion. Seems that we have a few opinion. So, I
> would suggest anyone who really would like to get this going, to
> create a complete document , basically recomendation on how the quran
> should be encoded. Then, I can encode the quran the mention in that
> specification (I think this process wont take long. Maybe 1/2 to 1
> hour of my time, assuming the there is mistake in the current file)
> Seriously, this won't take much of my time , since most of the
> encoding process is automated . Then, we can work on testing the file
> against the targeted technologies, such as windows, linux, console,
> pda etc. After this have been tested, maybe then we can have a
> consensus agreement among us, on which method is the way to go, or it
> might be a combination of the specification, who knows.
>