W3C home > Mailing lists > Public > www-style@w3.org > March 2016

Re: [css-text] Shaping for break-all/word-break

From: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
Date: Thu, 10 Mar 2016 11:36:49 -0700
Message-ID: <CAFDDJ7w-s-f_8DW-_3sXLuhwBX7J_++7sPyR8OLTcU_v3wf_Fw@mail.gmail.com>
To: Koji Ishii <kojiishi@gmail.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, Behdad Esfahbod <behdad@behdad.org>, "www-style@w3.org" <www-style@w3.org>
>From Koji:

> But is the requirements for text-on-path the same as break-all? If you
> place them on a path, they can keep the shape, but each shape are not
> really connected unless the shape is a line, no? Does Gecko do something
> special to connect them?
> Text-on-path is more complicated than break-all, yes.  In some cases, a
path may have a complete break in it, so it would be the same. In other
cases, it just has a bend. I should have clarified: SVG does allow
ligatures in text-on-a-path (unlike manually positioned characters), and
the entire glyph is drawn as a single block, even if it no longer nicely
fits the curve of the path.  So we will still need special wording for that.

It's true, the resulting string of glyphs may no longer connect up nicely
like in straight-line text. There is an SVG property to stretch the glyphs
into non-rectangles so they connect, but it is not implemented in the
browsers (not even Gecko).  Gecko also turns off required ligatures when
the letters are stroked.  When I said Firefox was the best for Arabic text
on a path, it is only in comparison to the others, which use all-isolated
Arabic letterforms, order the letters backwards, use incorrect alignment so
the text gets pushed off the path, and/or otherwise fail completely!

(You can play with some of my test cases here:
I need to create more comprehensive tests of both script font and RTL test
cases for the SVG 2 test suite.)

Received on Thursday, 10 March 2016 18:37:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:01 UTC