W3C home > Mailing lists > Public > www-style@w3.org > June 2015

Re: [css-text][css-conditional] language specific support for hyphenation and justification

From: Dave Cramer <dauwhe@gmail.com>
Date: Tue, 16 Jun 2015 10:36:31 -0400
Message-ID: <CADxXqOy2-qFF6bp5Qyh5Qzf8QikWTNqJ74zmXytEBEy5yn2MNA@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>
Cc: Florian Rivoal <florian@rivoal.net>, www-style list <www-style@w3.org>, www International <www-international@w3.org>
On Tue, Jun 16, 2015 at 9:29 AM, Alan Stearns <stearns@adobe.com> wrote:

> While hyphenation is often necessary for nice justification, it isn’t the
> only thing that can contribute. There are also features that browsers
> don’t support yet like min/max word spacing and multi-line justification
> algorithms. Using nice-justification for just the list above would be
> premature, I think.

Prince has a reasonable, minimal set of hyphenation properties:

1. prince-hyphenate-patterns (none | url(patterns-url) to link to a
hyphenation dictionary, which would be specific to a language
2. prince-hyphenate-lines (no-limit | integer) to restrict how many
consecutive lines may end with a hyphen
3. prince-hyphenate-before (integer), which describes the minimum number
characters before the hyphen
4. prince-hyphenate-after (integer), which describes the minimum number of
characters after the hyphen. The sum determines the shortest word that
could be hyphenated

I'd be happy to see min/opt/max word- and letter-spacing, too. And if you
can convince Adobe to open-source InDesign's justification engine and
rewrite it for the browsers, that would be great ;)

Received on Tuesday, 16 June 2015 14:36:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:54 UTC