- From: Glenn Maynard <glenn@zewt.org>
- Date: Fri, 2 Dec 2011 13:07:14 -0500
- To: David Singer <singer@apple.com>
- Cc: public-texttracks@w3.org, "whatwg@whatwg.org" <whatwg@whatwg.org>
Received on Friday, 2 December 2011 18:07:46 UTC
On Fri, Dec 2, 2011 at 4:03 AM, David Singer <singer@apple.com> wrote: > I guess I may be confused. > > I see two ways of rendering VTT (at least): > > 1) the UA interprets only VTT, and chooses 'suitable' fonts etc. > Without language metadata, this is impossible to do reliably for CJK text. 2) the UA interprets VTT with class markups and an associated CSS style > sheet or sheets, and the author and the UA between them can go hog wild. > > In case (2), you get to use any fancy (preferably legible :-)) font you > like, if the UA is willing to support it. > The only way you can do this with (2) is by naming fonts explicitly, which is a bad way to go about it. If content sets "MS Mincho" for JP, or MingLiU for zh-TW, or SimSun for zh-CN, then the content won't render correctly on any system that doesn't have those fonts (or know their names and provide appropriate aliases). It'll end up picking another CJK font, and likely render the wrong glyphs. (That's putting aside lesser things @lang helps with, like per-language user font overrides.) -- Glenn Maynard
Received on Friday, 2 December 2011 18:07:46 UTC