- From: r12a <ishida@w3.org>
- Date: Thu, 5 Oct 2017 10:01:47 +0100
- To: David Singer <singer@apple.com>, Glenn Adams <glenn@skynav.com>
- Cc: David Ronca <dronca@netflix.com>, Timed Text Working Group <public-tt@w3.org>, Pierre-Anthony Lemieux <pal@sandflow.com>
On 04/10/2017 15:42, David Singer wrote:
>> On Oct 3, 2017, at 22:49 , Glenn Adams <glenn@skynav.com> wrote:
>> Actually, I was responding to David Singer regarding the CSS WG having discussed oblique. While that is true, I don't know whether they have discussed shear.
>
> Yes, I searched for both words, as the usage sometimes overlaps, though oblique is usually used for a designed oblique face, and shear for a generated one. (However, there is plenty of practice that mixes it up; the original Mac did italic by shearing iirc.)
Here is some relevant text from CSS:
--
oblique
selects a font that is labeled as an oblique face, or an italic
face if one is not
If no italic or oblique face is available, oblique faces can be
synthesized by rendering non-obliqued faces with an artificial obliquing
operation. The use of these artificially obliqued faces can be disabled
using the ‘font-synthesis’ property. The details of the obliquing
operation are not explicitly defined.
Authors should also be aware that synthesized approaches may not be
suitable for scripts like Cyrillic, where italic forms are very
different in shape. It is always better to use an actual italic font
rather than rely on a synthetic version.
Many scripts lack the tradition of mixing a cursive form within text
rendered with a normal face. Chinese, Japanese and Korean fonts almost
always lack italic or oblique faces. Fonts that support a mixture of
scripts will sometimes omit specific scripts such as Arabic from the set
of glyphs supported in the italic face. User agents should be careful
about making character map assumptions across faces when implementing
support for system font fallback.
--
from https://www.w3.org/TR/css-fonts-3/#oblique
ri
Received on Thursday, 5 October 2017 09:01:58 UTC