diff options
| author | http://smcv.pseudorandom.co.uk/ <smcv@web> | 2011-11-16 12:50:02 -0400 |
|---|---|---|
| committer | admin <admin@branchable.com> | 2011-11-16 12:50:02 -0400 |
| commit | 56b896f83549dd05fa8a440d72f99ece24d7b536 (patch) | |
| tree | 81b6d15dbdd28cb1de0e7afd789a73299afc78c8 /doc/todo | |
| parent | 73d094cf0c264fcdca66baa65f5d8f8836865a9e (diff) | |
| download | ikiwiki-56b896f83549dd05fa8a440d72f99ece24d7b536.tar ikiwiki-56b896f83549dd05fa8a440d72f99ece24d7b536.tar.gz | |
I think this is better done client-side
Diffstat (limited to 'doc/todo')
| -rw-r--r-- | doc/todo/hyphenation.mdwn | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/todo/hyphenation.mdwn b/doc/todo/hyphenation.mdwn index be1eebcb8..5b4aaf5c9 100644 --- a/doc/todo/hyphenation.mdwn +++ b/doc/todo/hyphenation.mdwn @@ -3,3 +3,27 @@ I recently found [Hyphenator](http://code.google.com/p/hyphenator/) which is quite cool ... but it should be possible to implement this functionality within ikiwiki and not rely on javascript and the client. A Perl implementation of the algorithm exists in [[!cpan TeX::Hyphen]]. + +> I'd be inclined to say that Javascript run in the client is a better +> place to do hyphenation: this is the sort of non-essential, +> progressive-enhancement thing that JS is perfect for. If you did it +> at the server side, to cope with browser windows of different sizes +> you'd have to serve HTML sprinkled with soft-hyphen entities at +> every possible hyphenation point, like +> +> pro­gress­ive en­hance­ment +> +> which is nearly twice the byte-count and might stop +> search engines from indexing your site correctly. +> +> A browser that supports Javascript probably also supports +> soft-hyphen marks, but I doubt all non-JS browsers support them +> correctly. +> +> It might be good to have a plugin to insert a reference to the +> hyphenation JS into the `<head>`, or a general way to enable +> this sort of thing without writing a plugin or changing your +> `page.tmpl`, though. Perhaps we should have a `local.js` +> alongside `local.css`? :-) +> +> --[[smcv]] |