You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Section https://w3c.github.io/low-vision-a11y-tf/requirements.html#hyphenation
talks about hyphenation. Not all script use hyphens. And maybe the issue is not whether there is a hyphen or not, but whether the two parts of a word are on separate lines. Or maybe those are two different issues?
The latest CSS draft, e.g., proposes two separate properties to control the breaking of words:
hyphens - for scripts that use hyphens, to allow breaking at language-defined places.
word-break - break without using hyphens, using language-dependent rules about separable letter-pairs.
(Hyphenation may not just cause parts of a word to be separated and a hyphen to be added, but it may even change the spelling of each of the parts. But maybe that is already implied by the text.)
The text was updated successfully, but these errors were encountered:
Section
https://w3c.github.io/low-vision-a11y-tf/requirements.html#hyphenation
talks about hyphenation. Not all script use hyphens. And maybe the issue is not whether there is a hyphen or not, but whether the two parts of a word are on separate lines. Or maybe those are two different issues?
The latest CSS draft, e.g., proposes two separate properties to control the breaking of words:
hyphens - for scripts that use hyphens, to allow breaking at language-defined places.
word-break - break without using hyphens, using language-dependent rules about separable letter-pairs.
(Hyphenation may not just cause parts of a word to be separated and a hyphen to be added, but it may even change the spelling of each of the parts. But maybe that is already implied by the text.)
The text was updated successfully, but these errors were encountered: