- From: Pierre-Anthony Lemieux <pal@sandflow.com>
- Date: Mon, 16 Sep 2019 11:48:48 +0900
- To: TTWG <public-tt@w3.org>
- Message-ID: <CAF_7JxCmCQTAQNPxCnEq1gn8quPqgLfv+1zarOmKPPsf0OK-UQ@mail.gmail.com>
I have captured a strawman proposal at: https://github.com/w3c/imsc/issues/472#issuecomment-531626430 On Thu, Sep 5, 2019 at 12:27 AM Pierre-Anthony Lemieux <pal@sandflow.com> wrote: > FYI. As a data point, D-Cinema has the following constraints: one font > resource that is no larger than 10 MB. > > Best, > > -- Pierre > > On Sun, Sep 1, 2019 at 1:30 PM Pierre-Anthony Lemieux <pal@sandflow.com> > wrote: > > > > Good morning/evening, > > > > Issue #472 [1] suggests adding support for font resource to IMSC. > > > > IMSC implicitly specifies size limits for image resources through its > HRM [2]. > > > > The primary question in my mind is: are there any reason not to > > specify similar limits on font resources? > > > > If not, then some follow-up questions: > > > > - what are reasonable limits? > > - Should the limits be expressed in bytes and/or number of glyphs? > > - does a font/otf resource need to be processed/downloaded in its > > entirety if only a subset of glyps are used? > > > > I recommend reaching out to other groups for their input, either now > > or explicitly after FPWD. > > > > Looking forward to your feedback. > > > > Best, > > > > [1] https://www.w3.org/TR/ttml-imsc1.1/#hypothetical-render-model > > [2] https://github.com/w3c/imsc/issues/472 >
Received on Monday, 16 September 2019 02:49:23 UTC