[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Question about small noon
- To: "General Arabization Discussion" <general at arabeyes dot org>
- Subject: Re: Question about small noon
- From: "Meor Ridzuan Meor Yahaya" <meor dot ridzuan at gmail dot com>
- Date: Tue, 14 Mar 2006 08:08:23 +0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ro+QJLFFeJ220JJa6LqgrvmZZoYvpyzEkJVZBBi567JKOEPsnRd8gopBZLrM2o2Oh4fw7cReQt8lPxqg+hyqlLaMw4V+usqyT/+6PnBlEpbR2ANVWkIfJkjt48Eilrgpu3/DH16L8FV+tjkNV9wRYpaot7rcybMGotMSpJZ/YiA=
Tom,
Who are "we"? Will this introduce a new code for hamza? Care to eloborate?
On 3/14/06, Thomas Milo <t dot milo at chello dot nl> wrote:
> Gregg Reynolds wrote:
> >> Thomas Milo wrote:
> >>
> >>>
> >>> Tatweel is not a grapheme. I have come to the conclusion, that the
> >>> letter shaping mechanism needs a new catagory: amphibuous
> >>> (literally "between both", between skeleton and vowel as a
> >>> category, as well as placed between two surrounding letters - with
> >>> optional and separately encoded tatweel. This idea handles the
> >>> problems with hamza U+0621, superscript alef, trailing/superscript
> >>> retroflex and possibly even the superscript waw. Think of it, if
> >>> you will.
> >> It's a lot simpler if you define tatweel as a chameleon instead of a
> >> frog. ;) It takes on ink or not depending on the inking of its
> >> neighbors, and it can bear stacking characters. Simple and elegant.
>
> We have now a working amphibious hamza, as well as a Trashideh mechanisme
> that deals with callgraphically misplaced tatweels.
>
> t
>
>
>
> _______________________________________________
> General mailing list
> General at arabeyes dot org
> http://lists.arabeyes.org/mailman/listinfo/general
>