[mpeg-OTspec] Updated 4th edition working draft available for review

[Levantovsky, Vladimir]

Thank you Peter and John for your comments and for taking care of this issue. 

FYI - the 4th edition of the ISO OFF text has been promoted to the Committee Draft stage at the last MPEG meeting but there is a slight change of rules at ISO - unlike it was done in the past [when the approval ballot for the new CD and the CD publication ballot itself were issued at the same time] we now need to process two ballots in sequence - once the ISO subcommittee approves CD publication via ballot, the CD will be published and then the associated CD ballot will be issued. A bit of a procedural delay, but nothing that will affect our work or timing to any significant degree.

Once the CD ballot is issued (and hopefully while we hear from Martin to confirm that the proposed changes resolve the concern he raised), we will need to submit this proposed change as a ballot comment (I am sure there will be more). I expect the ballot to be issued within the next couple of weeks, and then we will have about two more months to prepare ballot comments and address other changes we discussed (maxstack, etc.)

Thank you,
Vlad


-----Original Message-----
From: Peter Constable [mailto:petercon at microsoft.com] 
Sent: Friday, April 14, 2017 5:06 PM
To: John Hudson
Cc: Martin Hosken; Levantovsky, Vladimir; mpeg-OTspec at yahoogroups.com
Subject: RE: [mpeg-OTspec] Updated 4th edition working draft available for review

Thanks, John. Given your reply, I think I'll drop the latter part of the last sentence.


Peter

-----Original Message-----
From: John Hudson [mailto:john at tiro.ca] 
Sent: Wednesday, April 12, 2017 12:56 PM
To: Peter Constable <petercon at microsoft.com>
Cc: Martin Hosken <martin_hosken at sil.org>; Levantovsky, Vladimir <Vladimir.Levantovsky at monotype.com>; mpeg-OTspec at yahoogroups.com
Subject: Re: [mpeg-OTspec] Updated 4th edition working draft available for review

Thanks, Peter. That's better in several respects.

Maybe the last sentence could say something like

     Applications should support use of a non-default language system table
     that is associated with 'DFLT' script, although older applications may not
     do so and might retain this behaviour.

I'd like to encourage everyone going forward to handle this in a consistent way, so not imply that this is something to opt out of.

JH


PS. With regard to the note, I wonder if we might be able to actually define recommended behaviour — not in this part of the spec, but somewhere — for handling of script=Common characters in OpenType Layout, so that we can get some kind of predictability? It's an area in which there's incompatibility between shaping engine implementations, which is very frustrating. In general, we'd do better if there were a singe standard for run itemisation.

cf. My IUC39 presentation
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftiro.com%2FJohn%2FHudson_IUC39_Beyond_Shaping.pdf&data=02%7C01%7Cpetercon%40microsoft.com%7C28a540d3e2b949576f4608d481dde7ed%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636276237459641505&sdata=N6yePP0U%2FB266jw1F03CIy7%2BelT1f3leNYwMgJa7mZw%3D&reserved=0


-- 

John Hudson
Tiro Typeworks Ltd    https://na01.safelinks.protection.outlook.com/?url=www.tiro.com&data=02%7C01%7Cpetercon%40microsoft.com%7C28a540d3e2b949576f4608d481dde7ed%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636276237459641505&sdata=bcRE6dTwJY2i5s%2FDfY6fwqyzcBLWdznNdU4j0GZ9PWE%3D&reserved=0
Salish Sea, BC        tiro at tiro.com

NOTE: In the interests of productivity, I am currently dealing with email on only two days per week, usually Monday and Thursday unless this schedule is disrupted by travel. If you need to contact me urgently, please use some other method of communication. Thank you.