FW: Proposed Script tag additions

[Levantovsky, Vladimir]

Hello Behdad, all,

Apologies for the delayed response. The shaping of Syriac that you're referring to is a part of the different specification that is related to OT/OFF. Since it's not the part of the "OFF proper", it cannot be part of the ISO OFF amendment, but your proposal does bring up the important issue to consider - do we want language-specific shaping specification be kept "as is" (i.e. as separate specifications), or would be useful and reasonable to make them part of the ISO OFF standard, e.g. add them as annexes to establish a compliance point for text layout engine implementations?

Thank you,
Vladimir


> -----Original Message-----
> From: Behdad Esfahbod [mailto:behdad.esfahbod at gmail.com] On Behalf Of
> Behdad Esfahbod
> Sent: Wednesday, November 17, 2010 2:00 PM
> To: Levantovsky, Vladimir
> Cc: Mansour, Kamal; John Hudson; mpeg-OTspec at yahoogroups.com
> Subject: Re: FW: Proposed Script tag additions
> 
> Hi Vlad,
> 
> At this time I would like to propose a fix to the Syriac OpenType
> standard only.
> 
>   https://www.microsoft.com/typography/otfntdev/syriacot/shaping.htm
> 
> The most urgent fix being:
> 
> Instead of: "g. Apply feature 'med2' to replace the 'Alaph' glyph in
> the
> middle of Syriac words when the preceding base character cannot be
> joined to."
> 
> it should say: "g. Apply feature 'med2' to replace the 'Alaph' glyph in
> the
> middle of Syriac words when the preceding base character can be joined
> to."
> 
> That is, should read "can be joined to" instead of "cannot be joined
> to".  For
> details see:
> 
>   http://behdad.org/syriac/
> 
> 
> Thanks,
> behdad
> 
> 
> On 11/09/10 18:12, Levantovsky, Vladimir wrote:
> > Hello Kamal, John and Behdad,
> >
> >
> >
> > I am forwarding you the email I just sent to the AHG OFF email list.
> I
> > apologize for a duplication if you already received it.
> >
> >
> >
> > I remember that earlier this year each of you have sent some
> proposals
> > on OpenType list for consideration as part of the changes in the next
> > version of the OpenType / OFF spec. The ISO process doesn’t provide
> an
> > easy mechanism for making changes in the existing spec, so each time
> a
> > change is going to be made we need to initiate an amendment process.
> We
> > now have an opportunity to add new items or change the existing text
> of
> > the OFF/OT specs as part of this new amendment that was proposed by
> > Microsoft. If you would like your ideas to be considered for the
> > amendment, please send them to the AHG email list.
> >
> >
> >
> > Thank you and regards,
> >
> > Vladimir
> >
> >
> >
> >
> >
> > *From:* mpeg-OTspec at yahoogroups.com [mailto:mpeg-
> OTspec at yahoogroups.com]
> > *On Behalf Of *Levantovsky, Vladimir
> > *Sent:* Tuesday, November 09, 2010 6:01 PM
> > *To:* Michelle Perham; mpeg-OTspec at yahoogroups.com
> > *Subject:* [mpeg-OTspec] RE: Proposed Script tag additions
> >
> >
> >
> >
> >
> > Thank you Michelle for bringing this up for consideration of the AHG.
> >
> >
> >
> > I agree that it is important to keep the text of the 14496-22 current
> > and in sync with the recent new additions introduced by the Unicode
> > standard. I would like to ask all members of the AHG to review this
> > proposal and consider recommending to start a new amendment.
> >
> >
> >
> > Also, if we decide to recommend a new amendment for 14496-22,  are
> there
> > any other proposed changes or new items that we should discuss and/or
> > consider for inclusion in this future amendment? I would like to ask
> all
> > AHG members to please bring your ideas and proposals for the AHG
> > discussion as part of this new work item.
> >
> >
> >
> > Thank you,
> >
> > Vladimir
> >
> >
> >
> >
> >
> > *From:* mpeg-OTspec at yahoogroups.com [mailto:mpeg-
> OTspec at yahoogroups.com]
> > *On Behalf Of *Michelle Perham
> > *Sent:* Monday, November 08, 2010 6:40 PM
> > *To:* mpeg-OTspec at yahoogroups.com
> > *Subject:* [mpeg-OTspec] Proposed Script tag additions
> >
> >
> >
> >
> >
> > The most recent versions of Unicode (versions 5.2 and 6.0) have added
> > several new script tags that are missing in the second edition of
> > ISO/IEC 14496-22 “Open Font Format” specification and the
> corresponding
> > version of the OpenType 1.6. The current list of script tags can be
> > found in the subclause 6.4.1 of 14496-22 and is available here:
> > http://www.microsoft.com/typography/otspec160/scripttags.htm.
> >
> >
> >
> > The newly defined Unicode script tags include the following:
> >
> >
> >
> > Tag
> >
> >
> >
> > Description
> >
> >
> >
> > Comment
> >
> > armi
> >
> >
> >
> > Imperial Aramaic
> >
> >
> >
> > Unicode 5.2
> >
> > avst
> >
> >
> >
> > Avestan
> >
> >
> >
> > Unicode 5.2
> >
> > bamu
> >
> >
> >
> > Bamum
> >
> >
> >
> > Unicode 5.2
> >
> > batk
> >
> >
> >
> > Batak
> >
> >
> >
> > Unicode 6.0
> >
> > brah
> >
> >
> >
> > Brahmi
> >
> >
> >
> > Unicode 6.0
> >
> > egyp
> >
> >
> >
> > Egyptian hieroglyphs
> >
> >
> >
> > Unicode 5.2
> >
> > kthi
> >
> >
> >
> > Kaithi
> >
> >
> >
> > Unicode 5.2
> >
> > lana
> >
> >
> >
> > Tai Tham (Lanna)
> >
> >
> >
> > Unicode 5.2
> >
> > lisu
> >
> >
> >
> > Lisu (Fraser)
> >
> >
> >
> > Unicode 5.2
> >
> > mand
> >
> >
> >
> > Mandaic, Mandaean
> >
> >
> >
> > Unicode 6.0
> >
> > mtei
> >
> >
> >
> > Meitei Mayek (Meithei, Meetei)
> >
> >
> >
> > Unicode 5.2
> >
> > orkh
> >
> >
> >
> > Old Turkic, Orkhon Runic
> >
> >
> >
> > Unicode 5.2
> >
> > phli
> >
> >
> >
> > Inscriptional Pahlavi
> >
> >
> >
> > Unicode 5.2
> >
> > prti
> >
> >
> >
> > Inscriptional Parthian
> >
> >
> >
> > Unicode 5.2
> >
> > samr
> >
> >
> >
> > Samaritan
> >
> >
> >
> > Unicode 5.2
> >
> > sarb
> >
> >
> >
> > Old South Arabian
> >
> >
> >
> > Unicode 5.2
> >
> > tavt
> >
> >
> >
> > Tai Viet
> >
> >
> >
> > Unicode 5.2
> >
> >
> >
> > We propose to start a new amendment and include the new script tags
> in
> > the text of the ISO OFF standard and in the OpenType 1.6.
> >
> >
> >
> > An illustration of the proposed changes can be found here:
> >
> > http://www.microsoft.com/typography/otspec160/scripttagsProposed.htm
> >
> >
> >
> > Michelle
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > 
> >