[MPEG-OTSPEC] OT 1.8.4 public beta review

[Levantovsky, Vladimir]

Hi Norbert, all,

In my experience of many years of ISO related work, any input contributions suggesting new changes to an existing ISO standard can come as a result of either a private development or public work, and can be submitted either to AHG for continued discussion or directly to the WG. Since recent updates to the OpenType spec (published by Microsoft) have been the result of many public contributions via OT GitHub pages, my interpretation of the message from Peter is that after reviewing and incorporating these public comments he intends to submit a proposal to this AHG introducing new changes to the OFF standard. At the same time, because the OT changes are a consolidation of many public comments (made by many people, including the members of this AHG who also conduct their work outside of AHG), the announcement below is soliciting a review of those changes to ensure their correctness and clarity.

To answer your question – I interpreted Peter’s message as an FYI that many public comments consolidated in the new OT draft will soon be presented as a proposal to this AHG for consideration as part of the amendment to the OFF specification. Once the proposal is actually submitted, we will discuss it in details, using both this list and GitHub, as we find appropriate. Meanwhile (as Peter mentioned in his response) any additional clarifications, if needed, should be submitted using the existing issues.

Thank you,
Vlad


From: Norbert Lindenberg <mpeg-otspec at lindenbergsoftware.com>
Sent: Monday, November 2, 2020 2:25 AM
To: Levantovsky, Vladimir <Vladimir.Levantovsky at monotype.com>
Cc: Peter Constable <pgcon6 at msn.com>; MPEG OT Spec list (mpeg-otspec at lists.aau.at) <mpeg-otspec at lists.aau.at>
Subject: Re: [MPEG-OTSPEC] OT 1.8.4 public beta review

Vlad, Peter,

How should members of the AHG understand the message below: As an FYI that Microsoft is doing work that will eventually be submitted to the AHG and at that point reviewed for suitability for OFF? Or as a request to AHG members to immediately review the proposed update for suitability for OFF? If the latter, I would assume that comments should be submitted in the AHG GitHub repository, not in the Microsoft Typography repository.

Best regards,
Norbert
Lindenberg Software LLC



> On Oct 24, 2020, at 14:50, Peter Constable <pgcon6 at msn.com<mailto:pgcon6 at msn.com>> wrote:
>
> Some weeks back, I mentioned that work was being done to prepare a dot-dot update to the OpenType spec. The OpenType 1.8.4 update is now publicly available for a “beta” review:
>
> https://docs.microsoft.com/en-us/typography/opentype/otspec184beta/ot184beta<https://protect-us.mimecast.com/s/V-O1CjRkM0ujp7Z8f5TdAm>
>
> When work started in August, there was a backlog of 99 issues that had been reported in the prior two years. After the new work began, another 141 issues were filed—a 141% increase in the past two months. Altogether, there were 240 different pieces of feedback on the OT spec that were taken into consideration, and changes made in response to over 200 of these issues (85%). There are 27 remaining issues still open that can be considered in a subsequent version—a cut-off for this release was needed at some point.
>
> How is this relevant for the AHG?
>
> Most or all of the feedback given on the OT spec is also relevant for OFF. So, after considering feedback from the review period and making last changes, the result will be submitted as proposed revisions for a future edition* of OFF. Of course, any of it would be in scope for discussion within the AHG.
>
> *Because there are so many edits in so many parts of the spec, it wouldn’t lend itself for the amendment process that was recently started. It might be feasible, however, to incorporate a limited selection of changes into an amendment.
>
> The content is available at the link above for a public review period of three weeks—until November 13. Note that the beta content will get taken down after OT 1.8.4 is considered complete and becomes the current version. The beta content includes two variants of each changed page/section: a “delta” version showing all edits with “change tracking” formatting; and a “final” version showing the results of the edits (all the deletions and “change tracking” formatting are removed). Feedback can be submitted on any of the beta content “final” version pages using a feedback link at the bottom of the page. A best effort will be made to respond to feedback on the proposed changes. Any entirely new issues reported will likely be left for a future update.
>
> I understand that this process isn’t everything that everyone here would like to see (e.g., people wanting the content to be treated like an OSS project), but hopefully this is seen to be a step in a good direction.
>
> I’d like to acknowledge and thank Google Fonts and Microsoft who have made this possible.
>
>
>
> Peter Constable
> _______________________________________________
> mpeg-otspec mailing list
> mpeg-otspec at lists.aau.at<mailto:mpeg-otspec at lists.aau.at>
> https://lists.aau.at/mailman/listinfo/mpeg-otspec<https://protect-us.mimecast.com/s/V66ICkRlKrunmMo9i9Pb3n>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20201102/0fe13ece/attachment-0001.html>