- From: Ivan Herman <ivan@w3.org>
- Date: Tue, 7 Jul 2015 16:47:30 +0200
- To: Alan Stearns <stearns@adobe.com>
- Cc: Dave Cramer <dauwhe@gmail.com>, W3C Digital Publishing IG <public-digipub-ig@w3.org>
- Message-Id: <A1106298-8F41-42DA-8BA8-84B35D7E0D31@w3.org>
> On 07 Jul 2015, at 16:44 , Alan Stearns <stearns@adobe.com> wrote: > > On 7/7/15, 7:39 AM, "Ivan Herman" <ivan@w3.org> wrote: > >> >>> On 07 Jul 2015, at 16:30 , Alan Stearns <stearns@adobe.com> wrote: >>> >>> Ivan, >>> >>> There are several hyphenation polyfills, such as >>> >>> https://github.com/mnater/hyphenator >>> https://github.com/bramstein/Hypher >>> >>> It’s been a while since I looked at any of them. One problem I noticed >>> the >>> last time I looked was that they change the page source by adding tons >>> of >>> discretionary hyphens that then either cause problems with search and >>> copy/paste, or more and more code has to be added to accommodate the >>> discretionary hyphens in those cases. >> >> Ouch:-) >> >>> So I’d classify hyphenation as one >>> of those features that is *possible* to polyfill, but it’s really too >>> much >>> work to do it well. >>> >> >> O.k. Is this only a wrong example (ie, there are other features where >> polyfills could fill in for a missing browser implementation) or is it >> generally something to avoid? > > It’s not a wrong example - it’s definitely polyfillable, and lots of > people use those polyfills. I just couldn’t avoid mentioning the caveats. :-) Please, never avoid that! Ivan > > Thanks, > > Alan ---- Ivan Herman, W3C Digital Publishing Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704
Received on Tuesday, 7 July 2015 14:46:34 UTC