Changeset 512479
- Timestamp:
- 02/29/2012 07:26:47 PM (14 years ago)
- Location:
- hyphenator
- Files:
-
- 2 edited
-
tags/4.0.0/readme.txt (modified) (4 diffs)
-
trunk/readme.txt (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
hyphenator/tags/4.0.0/readme.txt
r511209 r512479 42 42 43 43 == Frequently Asked Questions == 44 = Supported Browsers = 45 * Mozilla Firefox 3+ 46 * Google Chrome 1+ 47 * Opera 7.1+ 48 * Internet Explorer 6+ 49 * Apple Safari 2+ 50 * Konqueror 3.5+ 51 52 And any other modern browser that supports JavaScript and the soft hyphen (­). 53 54 = Shouldn't hyphenation be done on the server side? = 55 > There are some arguments against client side hyphenation - true. It costs a lot of computing time and the patterns have to be loaded for each language, everytime. But I believe that hyphenation belongs to the client: 56 > 57 > * Only the client «knows» where to break a line (and if at all). 58 > * A html file that has been hyphenated on the server would be full of ­'s. That's ugly and nobody knows how that would be treated by search engines… 59 > * Hyphenation on the client can be turned off to work around copy&paste- and search-bugs in most browsers. 60 > * as JavaScript-engines are in focus of development, they become faster and faster. 61 > * there are billions of mostly underworked clients vs. millions of often overloaded servers. 62 63 *([Source](http://code.google.com/p/hyphenator/wiki/en_FAQ#Shouldn't_hyphenation_be_done_on_the_server_side?))* 64 65 = Hyphenator breaks the search functionality of my browser = 66 > Your browser has a bug (currently, only Firefox3 finds hyphenated words). So I don't want/can't fix this in Hyphenator.js. The only thing we can do is to turn hyphenation off before searching. 67 68 *([Source](http://code.google.com/p/hyphenator/wiki/en_FAQ#Hyphenator_breaks_the_search_functionality_of_my_browser))* 69 70 = When I copy/paste hyphenated texts from a website, spaces/hyphens are inserted in allmost all words = 71 > This is fixed since version 3.0.0. 72 73 *([Source](http://code.google.com/p/hyphenator/wiki/en_FAQ#When_I_copy/paste_hyphenated_texts_from_a_website,_spaces/hyphen))* 74 75 = JavaScript is insecure and evil. It should be turned off in every browser! = 76 > Welcome to Web 2.0, the world of AJAX and modern browsers! It's true, JavaScript had a very bad reputation - not because JavaScript itself is bad, but because of a very poor implementation in some browsers. As of today JavaScripts influence is growing and browser developers put a lot of work in making their JavaScript engines better, secure and really fast. There are a lot of webpages using JavaScript in a good manner. Further, Hyphenator.js follows the rules of **[unobtrusive JavaScript](http://en.wikipedia.org/wiki/Unobtrusive_JavaScript)**. 77 78 *([Source](http://code.google.com/p/hyphenator/wiki/en_FAQ#JavaScript_is_insecure_and_evil._It_should_be_turned_off_in_ever))* 79 80 = How about Accessibility? = 81 > Following the rules of **[unobtrusive JavaScript](http://en.wikipedia.org/wiki/Unobtrusive_JavaScript)** Hyphenator.js has AFAIK no influence on accessibility of your webpage. It just adds a feature that will not be missed by a screen reader. 82 > 83 > Some screen readers have issues with words that contain soft hyphens (they read syllables instead of words). Please note that this is not an issue of Hyphenator but a bug in the screen reader. Please contact the makers of the screen reader application. 84 85 *([Source](http://code.google.com/p/hyphenator/wiki/en_FAQ#How_about_Accessibility?))* 86 44 87 = Why shows my WordPress no update to 1.0.0.1? = 45 88 * **Reason:** I have relaunched the version numeration for Hyphenator version 1.0.0 so that it answers to the new version of the Hyphenator.js project. The downside is people using the previous version won't be notified due to the new versions 1.0.0 and 1.0.0.1. Sorry, I fizzled it. … … 60 103 * new default language option 61 104 62 = older versions =105 = Older Versions = 63 106 * 0.0.7 (12.10.2008) - first version (released first as version 1.0) 64 107 * 0.0.8 (15.10.2008) - updated to Hyphenator.js v8 (beta) … … 90 133 91 134 == License == 92 * Plugin licensed under G LP3: Copyright (C) 2008-2012 Benedict B. alias e2b135 * Plugin licensed under GPLv3: Copyright (C) 2008-2012 Benedict B. alias e2b 93 136 * Hyphenator.js licensed under LGPLv3: Copyright (C) 2011 Mathias Nater, Zürich 94 137 … … 97 140 This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the [GNU General Public License](http://www.gnu.org/licenses/gpl.html "The GNU General Public License - GNU Project - Free Software Foundation (FSF)") for more details. 98 141 142 Some patterns in the pattern files have different licenses specified in the pattern files. 143 99 144 The custom header used in the Wordpress Plugin Directory is based on the image [Compositor by Stephen Hampshire](http://www.flickr.com/photos/stephenhampshire/3337704597/) and licensed under [Creative Commons Attribution 2.0](http://creativecommons.org/licenses/by/2.0/). -
hyphenator/trunk/readme.txt
r511209 r512479 42 42 43 43 == Frequently Asked Questions == 44 = Supported Browsers = 45 * Mozilla Firefox 3+ 46 * Google Chrome 1+ 47 * Opera 7.1+ 48 * Internet Explorer 6+ 49 * Apple Safari 2+ 50 * Konqueror 3.5+ 51 52 And any other modern browser that supports JavaScript and the soft hyphen (­). 53 54 = Shouldn't hyphenation be done on the server side? = 55 > There are some arguments against client side hyphenation - true. It costs a lot of computing time and the patterns have to be loaded for each language, everytime. But I believe that hyphenation belongs to the client: 56 > 57 > * Only the client «knows» where to break a line (and if at all). 58 > * A html file that has been hyphenated on the server would be full of ­'s. That's ugly and nobody knows how that would be treated by search engines… 59 > * Hyphenation on the client can be turned off to work around copy&paste- and search-bugs in most browsers. 60 > * as JavaScript-engines are in focus of development, they become faster and faster. 61 > * there are billions of mostly underworked clients vs. millions of often overloaded servers. 62 63 *([Source](http://code.google.com/p/hyphenator/wiki/en_FAQ#Shouldn't_hyphenation_be_done_on_the_server_side?))* 64 65 = Hyphenator breaks the search functionality of my browser = 66 > Your browser has a bug (currently, only Firefox3 finds hyphenated words). So I don't want/can't fix this in Hyphenator.js. The only thing we can do is to turn hyphenation off before searching. 67 68 *([Source](http://code.google.com/p/hyphenator/wiki/en_FAQ#Hyphenator_breaks_the_search_functionality_of_my_browser))* 69 70 = When I copy/paste hyphenated texts from a website, spaces/hyphens are inserted in allmost all words = 71 > This is fixed since version 3.0.0. 72 73 *([Source](http://code.google.com/p/hyphenator/wiki/en_FAQ#When_I_copy/paste_hyphenated_texts_from_a_website,_spaces/hyphen))* 74 75 = JavaScript is insecure and evil. It should be turned off in every browser! = 76 > Welcome to Web 2.0, the world of AJAX and modern browsers! It's true, JavaScript had a very bad reputation - not because JavaScript itself is bad, but because of a very poor implementation in some browsers. As of today JavaScripts influence is growing and browser developers put a lot of work in making their JavaScript engines better, secure and really fast. There are a lot of webpages using JavaScript in a good manner. Further, Hyphenator.js follows the rules of **[unobtrusive JavaScript](http://en.wikipedia.org/wiki/Unobtrusive_JavaScript)**. 77 78 *([Source](http://code.google.com/p/hyphenator/wiki/en_FAQ#JavaScript_is_insecure_and_evil._It_should_be_turned_off_in_ever))* 79 80 = How about Accessibility? = 81 > Following the rules of **[unobtrusive JavaScript](http://en.wikipedia.org/wiki/Unobtrusive_JavaScript)** Hyphenator.js has AFAIK no influence on accessibility of your webpage. It just adds a feature that will not be missed by a screen reader. 82 > 83 > Some screen readers have issues with words that contain soft hyphens (they read syllables instead of words). Please note that this is not an issue of Hyphenator but a bug in the screen reader. Please contact the makers of the screen reader application. 84 85 *([Source](http://code.google.com/p/hyphenator/wiki/en_FAQ#How_about_Accessibility?))* 86 44 87 = Why shows my WordPress no update to 1.0.0.1? = 45 88 * **Reason:** I have relaunched the version numeration for Hyphenator version 1.0.0 so that it answers to the new version of the Hyphenator.js project. The downside is people using the previous version won't be notified due to the new versions 1.0.0 and 1.0.0.1. Sorry, I fizzled it. … … 60 103 * new default language option 61 104 62 = older versions =105 = Older Versions = 63 106 * 0.0.7 (12.10.2008) - first version (released first as version 1.0) 64 107 * 0.0.8 (15.10.2008) - updated to Hyphenator.js v8 (beta) … … 90 133 91 134 == License == 92 * Plugin licensed under G LP3: Copyright (C) 2008-2012 Benedict B. alias e2b135 * Plugin licensed under GPLv3: Copyright (C) 2008-2012 Benedict B. alias e2b 93 136 * Hyphenator.js licensed under LGPLv3: Copyright (C) 2011 Mathias Nater, Zürich 94 137 … … 97 140 This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the [GNU General Public License](http://www.gnu.org/licenses/gpl.html "The GNU General Public License - GNU Project - Free Software Foundation (FSF)") for more details. 98 141 142 Some patterns in the pattern files have different licenses specified in the pattern files. 143 99 144 The custom header used in the Wordpress Plugin Directory is based on the image [Compositor by Stephen Hampshire](http://www.flickr.com/photos/stephenhampshire/3337704597/) and licensed under [Creative Commons Attribution 2.0](http://creativecommons.org/licenses/by/2.0/).
Note: See TracChangeset
for help on using the changeset viewer.