[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Hamza U+0621
- To: General Arabization Discussion <general at arabeyes dot org>
- Subject: Re: Hamza U+0621
- From: Meor Ridzuan Meor Yahaya <meor dot ridzuan at gmail dot com>
- Date: Tue, 20 Sep 2005 16:56:38 +0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bEkNuDYDnHakvSYhM/SVgRJyrbt4qhDVxgoET0hj8tLkGOJtIDPucE14F7WtbyfJkEI9inHn9R4qBWBRFO7+krAXeMSBsML1x6TjMmDVnKtzhMSC+OQ3lgl4Zvz8VBTh5yQn/mcX7vsKLqF1Slhr/qtKBVmQ5dBwb4mLSY7Ctaw=
Tom,
I'm not sure it's OpenType (the spec) fault, or it's implementation
(uniscribe, pango) fault, or it might just be plain VOLT fault. I
think the problem lies between VOLT (the software the generate
opentype table) to Uniscribe/OTLS implementation. OpenType , the spec
is not the problem. Anyway, I've to admit, last time I did not test it
on Linux when the problems occurs, so not sure how it behaves. I only
test it after it works under windows (which still have some problems
under Linux).
I might be able to eliminate all of the problem by creating the
OpenType table (GSUB mostly) by hand and recompile it using TTX, but
that will take a lot of my time (unless I can work full time on it, I
might do it). I still think that somehow VOLT produces a buggy GSUB
table, but difficult to prove it.
Regards.
On 9/20/05, Thomas Milo <t dot milo at chello dot nl> wrote:
> Meor,
>
> I suppose you are discussing flaws of OpenType?
>
> t
>
>
> Meor Ridzuan Meor Yahaya wrote:
> > Mete,
> > Last time I tried, I did have problems to make it work in both
> > situation. If I were to make it work for the lam alef with floating
> > hamza, it does not work in the second case. If I were to make it work
> > for the second case, the first case does not work. That's why in the
> > text, for the first case it was encode as lam hamza alef, whereby the
> > second case was encoded with tatweel hamza above . This is just to
> > make it visually correct. There might be a way to accomplish this, but
> > we might need some help from experts it this (maybe from MS). This is
> > becasue I'm not sure why it does not work; It should have been. There
> > might be a bug somewhere (not sure where).
> >
> > Regards.
> >
> > On 9/20/05, Mete Kural <metek at touchtonecorp dot com> wrote:
> >> Hello Meor,
> >>
> >> Were you successful in getting U+0621 to render correctly in words
> >> like al-aakhira in aya 2:4 and ya'aadamu in aya 2:33 with the new
> >> font you're developing in both Windows and Linux? Can you use U+0621
> >> in al-aakhira and have your font render it correctly or does
> >> Uniscribe and Pango not allow you to do that?
> >>
> >> Thanks,
> >> Mete
> >>
> >> --
> >> Mete Kural
> >> Touchtone Corporation
> >> 714-755-2810
> >> --
> >>
> >>
> >> _______________________________________________
> >> General mailing list
> >> General at arabeyes dot org
> >> http://lists.arabeyes.org/mailman/listinfo/general
> >>
> >
> >
> >
> >
> >> _______________________________________________
> >> General mailing list
> >> General at arabeyes dot org
> >> http://lists.arabeyes.org/mailman/listinfo/general
>
>
> _______________________________________________
> General mailing list
> General at arabeyes dot org
> http://lists.arabeyes.org/mailman/listinfo/general
>