- From: Myles C. Maxfield <mmaxfield@apple.com>
- Date: Mon, 25 Jan 2021 17:13:27 -0800
- To: Garret Rieger <grieger@google.com>
- Cc: "w3c-webfonts-wg (public-webfonts-wg@w3.org)" <public-webfonts-wg@w3.org>
- Message-id: <76151E96-FF6B-48DE-BA6D-A8BF7219F5EF@apple.com>
(Also +1 for streaming of course) > On Jan 25, 2021, at 5:07 PM, Myles C. Maxfield <mmaxfield@apple.com> wrote: > > +1 for incremental > >> On Jan 25, 2021, at 4:35 PM, Garret Rieger <grieger@google.com <mailto:grieger@google.com>> wrote: >> >> At today's meeting we discussed some possible names that might be used for the "supports" token in CSS @font-face when specifying a URL which supports progressive font enrichment. For those who haven't seen the supports syntax before: >> >> @font-face { >> ... >> src: url(myfont.ttf) format(truetype supports <technology>); >> } >> >> Here's the list of names for <technology> that were mentioned at today's meeting, along with my thoughts on them: >> incremental >> My current favourite, describes pretty well what will be happening. >> progressive >> Draws parallels to progressively loaded images, however may have the incorrect connotation that you get a less good very of the font at first which is later improved upon. >> streaming >> Possibly implies that the transferred font is not retained between uses. Also streaming doesn't quite correctly describe the operation of patch/subset. Though it does work well for range request. >> augmentation >> This potentially has the same issues as progressive. >> enrichment >> This potentially has the same issues as progressive. >> partial >> This potentially has the same issues as progressive. >> What are your thoughts? Also please add other ideas for possible names to this thread if you have any additional ones. >
Received on Tuesday, 26 January 2021 01:13:42 UTC