This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
ideas:hyphenation [2018/11/04 06:54] – created nhthvhvbh | ideas:hyphenation [2018/11/04 10:51] (current) – old revision restored (2016/10/26 05:11) fantasai | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | < | + | ====== Ceci n'est pas un trait d'union ====== |
+ | |||
+ | ===== Detecting whether hyphenation and/or justification is applicable ===== | ||
+ | There' | ||
+ | |||
+ | This is to allow opting in into justification (or other forms of layout, such as narrow column layout) that only work well if things like hyphenation are not only supported by the browser, but also supported for the language actually used by the document. | ||
+ | |||
+ | By the end of the thread, the proposal is something like this: | ||
+ | |||
+ | p { | ||
+ | text-align: left; | ||
+ | } | ||
+ | p: | ||
+ | hypens: auto; | ||
+ | text-align: justify; | ||
+ | } | ||
+ | p: | ||
+ | text-align: justify; | ||
+ | } | ||
+ | |||
+ | The second one would match on elements where the declared language is one the browser can hyphenate, and the third one would match on elements where the declared language is not one the browser can hyphenate but is one where the browser knows how to justify nicely. For example arabic if the browser supports kashida, or Japanese where nothing in particular is needed. | ||
+ | |||
+ | This assumes we define '': | ||
+ | |||
+ | This is just a summary of the conclusion. For the rationale and justification, |