[MPEG-OTSPEC] Scheduling Zoom meeting to discuss new proposals and AHG recommendations

[Rod Sheeter]

I rather like the idea of a bitmap paint in COLR that pulls the actual
bitmap from another table, just like outlines. Compositing vectors and
bitmaps seems like it might open up some interesting possibilities.
Feedback on use cases where bitmaps are useful posted to
https://github.com/googlefonts/colr-gradients-spec/issues/272 would be most
appreciated. I added a comment for the example Georg provided.

For context, at the time COLRv1 was developed no bitmap format worked
consistently across platforms, the value of having paint bitmap was
unclear, and the pattern to add it later was very clear so it seemed safe
to defer. sbix looked like the best bitmap table but there was
inconsistency around interpretation of offsets (
https://github.com/MicrosoftDocs/typography-issues/issues/191).
https://gitlab.freedesktop.org/freetype/freetype/-/issues/998 is now closed
so hopefully that's now fixed.



On Sun, Jul 2, 2023 at 11:10 AM Adam Twardoch (Lists) <
list.adam at twardoch.com> wrote:

> COLR could be made towork with sbix+PNG (which is a good format). Since
> COLR does overlaying and compositing, and takes existing glyphs as sources,
> these sources could he glyf/CFF for vectors and sbix for bitmaps.
>
> On Sun, 2 Jul 2023 at 18:14, Georg Seifert <typogeorg at gmail.com> wrote:
>
>> Or add a Bitmap Paint type to COLRv2?
>>
>>
>>
>> On 2. Jul 2023, at 16:11, Dave Crossland <dcrossland at google.com> wrote:
>>
>> Seems to me that glyf2 should support bitmaps then.
>>
>>
>> On Sun, Jul 2, 2023, 2:15 AM Georg Seifert <typogeorg at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Pixel based fonts might seem to be obsolete but there are many things
>>> that can’t be easily expressed with vectors. So I strongly recommend to
>>> keep support for pixels. A very nice example of a commercially color pixel
>>> font: https://liebefonts.com/fonts/liebeheide
>>>
>>> Best
>>> Georg Seifert
>>>
>>>
>>> > On 2. Jul 2023, at 00:17, Hin-Tak Leung <htl10 at users.sourceforge.net>
>>> wrote:
>>> >
>>> > On Saturday, 1 July 2023 at 23:44:23 GMT+8, Chris Lilley <chris at w3.org>
>>> wrote:
>>> >
>>> >> With COLRv1, I now regard that as the sole viable format for chromatic
>>> >> fonts and thus, SVG-in-OT (and the various pixel-based color formats)
>>> >> are purely legacy.
>>> >
>>> > Hmm, OT-SVG support was only added to Freetype in 2021. Having just
>>> experienced some problems a few weeks ago with it, and sent in the fix
>>> myself, I went a bit further and ported the OT-SVG support to freetype-py
>>> in the last few days. (I.e. just landed last night, you can draw with
>>> OT-SVG color font with python...).
>>> > _______________________________________________
>>> > mpeg-otspec mailing list
>>> > mpeg-otspec at lists.aau.at
>>> > https://lists.aau.at/mailman/listinfo/mpeg-otspec
>>>
>>>
>> _______________________________________________
>> mpeg-otspec mailing list
>> mpeg-otspec at lists.aau.at
>> https://lists.aau.at/mailman/listinfo/mpeg-otspec
>>
> _______________________________________________
> mpeg-otspec mailing list
> mpeg-otspec at lists.aau.at
> https://lists.aau.at/mailman/listinfo/mpeg-otspec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/mailman/private/mpeg-otspec/attachments/20230702/0151f40c/attachment-0001.html>