Re: Fix "the two" decoder issues

Returning at last to this, https://github.com/google/woff2/pull/84 fixes
#53, #55.

I believe that leaves https://github.com/google/woff2/issues/54 Reject
empty glyph with bounding box as the last person standing.

On Tue, Aug 1, 2017 at 8:36 AM Levantovsky, Vladimir <
Vladimir.Levantovsky@monotype.com> wrote:

> Hi Rod,
>
>
>
> The issues that triggered action 205 were discussed at our May 10 WG
> telcon (http://www.w3.org/2017/05/10-webfonts-minutes.html), and are also
> related to what Khaled mentioned earlier in his email response to one of
> the previous call topic:
> https://lists.w3.org/Archives/Public/public-webfonts-wg/2017Mar/0019.html
>
>
>
> Cheers,
>
> Vlad
>
>
>
>
>
> *From:* Roderick Sheeter [mailto:rsheeter@google.com]
> *Sent:* Monday, July 31, 2017 12:48 PM
> *To:* WebFonts WG
> *Subject:* Fix "the two" decoder issues
>
>
>
> https://www.w3.org/Fonts/WG/track/actions/205 doesn't seem to specify
> what "the two" decoder issues are. So I fixed two decoder issues :D (
> https://github.com/google/woff2/pull/81).
>
>
>
> However, I see a couple more that I suspect we want fixes for before
> advancing spec state:
>
>
>
> https://github.com/google/woff2/issues/53 Reject loca with mismatching
> origLength
>
> https://github.com/google/woff2/issues/54 Reject empty glyph with
> bounding box
>
> https://github.com/google/woff2/issues/55 Reject transformed hmtx table
> with reserved flags bits set
>
>
>
>
>