Hyphenation for node and Polyfill for client-side hyphenation.
Note: The API for using Hyphenopoly on websites changed with version 5.
This is a minimal embedding of Hyphenopoly on a website:
<script src="../Hyphenopoly_Loader.js"></script>
<script>
Hyphenopoly.config({
require: {
"en-us": "supercalifragilisticexpialidocious"
}
});
</script>
The first script tag loads Hyphenopoly_Loader.js which registers the global object window.Hyphenopoly. This is the one and only global that is set by Hyphenopoly.
In the second script tag Hyphenopoly gets configured. This also runs every step necessary to hyphenate the page.
To configure Hyphenopoly you pass an object with the values defined here to the function Hyphenopoly.config(). The settings in this object have multiple layers and each layer (if present) has mandatory and optional settings.
The first layer contains settings for the general behavior of Hyphenopoly_Loader.js (require, handleEvent etc.). This first layer may contain a property setup wich contains the second layer.
The second layer defines the behavior of Hyphenopoly.js. There are global settings (like defaultLanguage, safeCopy etc.) that are independent of the respective element selectors. And there are selector based settings (like minWordLength, leftmin etc.) that apply only to the given selectors.
The config-Object must contain exactly one field called require. It defines the language(s) used on the page.
The require field must be an object of key-value-pairs, where the keys are language codes and the values are a long word (>=12 characters) in the required language.
Hyphenopoly.config({
require: {
"en-us": "supercalifragilisticexpialidocious",
"de": "Silbentrennungsalgorithmus"
}
});
Hyphenopoly_Loader.js feature tests the browser for CSS-hyphenation support of the required languages using the long word. If the feature test indicates that the browser doesn’t support CSS-hyphenation for at least one language, all necessary resources will be loaded and Hyphenopoly.js gets executed.
Use this to test support for every language used on the current page. If e.g. the language of the page is lang="de-DE" you must require de-de (case doesn’t matter). For languages that aren’t in the patterns directory a fallback must be defined (see below).
To force the usage of Hyphenopoly.js (e.g. for testing or if you prefer to use your own patterns) the special keyword "FORCEHYPHENOPOLY" can be used as value. Note: Disable CSS-hyphenation while using "FORCEHYPHENOPOLY".
By default Hyphenopoly looks in ../Hyphenopoly/patterns/ for .wasm-files and in ../Hyphenopoly/ for other resources.
These paths can be reconfigured:
The paths field must be an object with two key-value-pairs:
Hyphenopoly.config({
require: {...},
paths: {
"patterndir": "../patterns/", //path to the directory of pattern files
"maindir": "../" //path to the directory where the other ressources are stored
}
});
In some cases a fallback-language need to be defined:
E.g. you’d like to use en-gb patterns for en-au and de for de-DE:
Hyphenopoly.config({
require: {
"en-au": "FORCEHYPHENOPOLY", //or a long string
"de-DE": "FORCEHYPHENOPOLY" //or a long string
},
fallbacks: {
"en-au": "en-gb", //use en-gb for en-au
"de-DE": "de". //use de for de-DE
},
setup: { ... }
});
On the first run Hyphenopoly_Loader.js feature tests the client for support of CSS-hyphenation
for each language in Hyphenopoly.require.
The result of these tests is stored in Hyphenopoly.cf (cf = client features). Because these tests take
some time and may cause a reflow of the document, Hyphenopoly_Loader.js can store their
results and retrieve these stored results for other pages in the same browsing session.
The test results are stored in sessionStorage to assure that the tests are rerun when the browser occasionally gets updated.
Because the law in some countries require a user opt-in or opt-out or whatever if you store
data on the client, cacheFeatureTests is deactivated by default and has to be activated
explicitly by hand in the Hyphenopoly global object:
Hyphenopoly.config({
"require": {...},
"cacheFeatureTests": true
});
It’s up to you to comply to the cookie-regulations of your country.
The setup field gives access to the second level of configuration. It defaults to the following configuration:
Hyphenopoly.config({
"require": {...},
"setup": {
CORScredentials: "include",
defaultLanguage: "en-us",
dontHyphenateClass: "donthyphenate",
hide: "element",
keepAlive: true,
normalize: false,
processShadows: false,
safeCopy: true,
timeout: 1000,
selectors: {
".hyphenate": {}
}
}
});
This list is not conclusive. For full documentation see Setup.
With selectors elements can be selected very precisely without the need of adding classes to the HTML. The selectors-object is a list of key-value-pairs where the key is a selector and the value is an object of settings specific to the selected elements.
setup: {
selectors: {
"p": {}, // This selects all <p> elements for hyphenation with default settings
".content, .title": { // This selects all elements with class .content and .title and sets minWordLength to 4 for these elements
minWordLength: 4
}
}
}
See CSS-Selectors on MDN for a complete reference on CSS-Selectors.
See Events
See Hyphenators
To remove all hyphenation previously applied by Hyphenopoly call Hyphenopoly.unhyphenate();.
This method asynchronously returns the elements that have been unhyphenated in the data structure used internally.
Hyphenopoly.unhyphenate().then((elements) => {
console.log(elements);
});
A typical init could look like this:
Hyphenopoly.config({
require: {
"en-us": "supercalifragilisticexpialidocious"
},
setup: {
selectors: {
".text": {}
}
},
handleEvent: {
error: function (e) {
e.preventDefault(); //don't show error messages in console
}
}
});
If you console.dir(Hyphenopoly) you’ll see lots of other data that is internally used by Hyphenopoly_Loader.js and Hyphenopoly.js but isn’t meant to be changed by the user.