W3C home > Mailing lists > Public > spec-prod@w3.org > January to March 2018

Re: [Restyle] Auto hyphenation can make the spec ambiguous

From: fantasai <fantasai.lists@inkedblade.net>
Date: Tue, 13 Feb 2018 16:03:41 -0800
To: Chris Lilley <chris@w3.org>, spec-prod@w3.org
Message-ID: <15284864-89b7-51f3-ec18-09c44c1dd74a@inkedblade.net>
On 02/12/2018 07:16 PM, Chris Lilley wrote:
> A bug was raised against a CSS specification, because it seemed as if a hyphen was allowed in a keyword ("open-type" as well 
> as "opentype").
> https://github.com/w3c/csswg-drafts/issues/2307
> It turned out not to be a bug in the grammar but to be introduced by the styling. Furthermore, that bug is in base.css and 
> thus affects all W3C specs, not just CSS WG ones.
> The rule in question is
> body { hyphens: auto}
> Hyphenation is fine in general, but not when it alters the technical content of a specification.

Code should be wrapped in <code>. Then you would not run into such problems. :)

We can turn off hyphenation on W3C specs altogether if you prefer, though.

Received on Wednesday, 14 February 2018 00:07:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 14 February 2018 00:07:09 UTC