- From: Brad Kemper <brad.kemper@gmail.com>
- Date: Mon, 16 May 2011 13:44:37 -0700
- To: Jonathan Kew <jonathan@jfkew.plus.com>
- Cc: "robert@ocallahan.org" <robert@ocallahan.org>, Mathias Nater <mathiasnater@gmail.com>, "www-style@w3.org" <www-style@w3.org>
On May 16, 2011, at 9:02 AM, Jonathan Kew <jonathan@jfkew.plus.com> wrote: > On 16 May 2011, at 16:28, Brad Kemper wrote: > >> >> On May 16, 2011, at 5:56 AM, Robert O'Callahan wrote: >> >>> I'm not too excited about implementing hyphenate-resource. It seems unlikely to me that a significant number of Web developers will bother developing and deploying their own hyphenation dictionaries. >> >> I think it would be very useful for authors to be able to include their own supplemental hyphenation dictionaries, containing words they use in their industry, brand names, product names, jargon, etc. that wouldn't be in any built-in resource or algorithm. Is that what we are talking about here? > > I'd consider this an application for a hyphenation-exceptions list, which would be a different kind of resource from the main hyphenation patterns used by TeX- or libhyphen-style algorithms. > > I don't think it's practical to combine author-provided TeX-style hyphenation patterns "on the fly" with the browser's built-in patterns, nor is it realistic to expect authors to know how to specify such patterns and understand their interaction with the standard ones. An "exceptions list" that overrides the built-in hyphenation for specific words only is simple, understandable, and adequate for this need. Could that still be an external resource? Something that could be exported from another piece of software and linked to? It doesn't seem like the kind of thing a web designer would often want to edit himself by hand, especially if it ended up being a not-tiny list. >
Received on Monday, 16 May 2011 20:45:15 UTC