|
That's exactly right. OT gives you complete
freedom - inside a font. On the business end you have to conform to the
standard. The latter is, unfortunately, not fully clear in matters
Qur'anic.
Cheers,
t
----- Original Message -----
Sent: Wednesday, August 22, 2007 5:49
PM
Subject: Re: Arabic Unicode
Thanks Mr. Thomas for the replay which made things clear
now.
So, I assume that it is safe to define whatever code points in
private
use area or even completely outside Unicode to use it
internally in
our font as long as those code points aren't exposed to
actual data
entery.
On 8/20/07, Thomas Milo <t dot milo at chello dot nl> wrote:
> Dear
Afief,
>
> From your message I understand that you guys are using
the Unicode Standard
> as a glyph list for font
construction.
>
> From a Unicode point of view, the regular Arabic
characters are te obe found
> in the U06xx and U07xx areas only. The
Presentation Forms located in uFxxx
> should be totally
ignored.
>
> As for the internal encoding of your glyphs to work
as an open type font,
> anything is allowed as long as the front end -
the input - works with
> regular Arabic Unicode. For instance, you can
build any internal bridges and
> supports for vowels or other
diacritics, but you have to take care that they
> are not reflected on
the outside as text code.
>
> Plase compare the discussion below
on the Typophile panel where similar
> issues are discussed:
> http://www.typophile.com/node/16858
>
>
I hope this helps,
>
> Best regards,
>
> Thomas
Milo
> DecoType
>
> ----- Original Message
-----
> From: Afief Halumi
> To: t dot milo at chello dot nl
> Sent:
Saturday, August 18, 2007 2:14 AM
> Subject: Arabic
Unicode
>
>
> Hello
mr.Milo,
>
> Me and a few other guys have been working
on the Arabeyes font
> collection(www.arabeyes.org), up until now it has
generally only been fixing
> the anchors for the diacritics, but now
that we're finally done with that
> part and the new version is being
tested for release we ran into something
> we didn't understand and
hoped you could help.
>
> The unicode glyphs uniFC5E -
uniFC63 are defined in the unicode standards
> as
follows:
>
> FC5E: ARABIC LIGATURE SHADDA WITH
DAMMATAN ISOLATED FORM
>
<Space><Dammatan><Shaddah>
>
>
>
The first thing we thought those glyphs were for was ligatures to make
>
working with a Shaddah easier(as in not having to put the shaddah extra
high
> on all letter so we could fit in the Kasra with Mark2Mark
Anchors) but the
> <Space> in the definition is kind of confusing
to us. Could you tell us what
> the "right" use for those glyphs should
be?
>
> Also there appears to be no ligature for
Shadda with Fathatan in the
> unicode definition, is there something we
have overlooked?
>
>
> Thanks in
advance,
> Afief Halumi
>
--
Khaled
Hosny
Egyptian GNU/Linux user
Member of Arabeyes team
[www.arabeyes.org]
My Blog: [www.khaledhosny.org]
Support Free
Knowledge
[ar.wikipedia.org]
_______________________________________________
General
mailing list
General at arabeyes dot org
http://lists.arabeyes.org/mailman/listinfo/general
|