W3C home > Mailing lists > Public > www-style@w3.org > October 2013

Re: [css3-writing-modes] inconsistent handling of 'Tr' codepoints in 'text-orientation'

From: James Clark <jjc@jclark.com>
Date: Tue, 1 Oct 2013 13:12:48 +0700
Message-ID: <CANz3_EaACC-5e3rar49ztciy+=9jn4yF_=D5NugkdBfu2e7tuw@mail.gmail.com>
To: John Daggett <jdaggett@mozilla.com>
Cc: Koji Ishii <kojiishi@gluesoft.co.jp>, W3C Style <www-style@w3.org>
On Tuesday, October 1, 2013, John Daggett wrote:

> But to some degree, proper vertical text rendering
> will always be dependent upon font resources, starting with
> appropriate vertical metrics through appropriate support for vertical
> alternates.  The reason I don't see OpenType feature fallback like
> this as compelling is that fonts intended to support vertical text
> generally *do* provide these alternates.

You have convinced me.

The way I would state it is that UTR#50 compliance should be treated as a
property of the layout engine together with the font, rather than of the
layout engine alone.  It is better to have an architecture where there is a
clear allocation of responsibility between subsystems.  When you have an
OpenType font that declares support for vertical alternates, it is better
to allocate responsibility for providing appropriate alternate glyphs to
the font alone rather than splitting it between the layout engine and the

Received on Tuesday, 1 October 2013 06:13:15 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:15 UTC