Re: [css-text] feedback on hyphenation

On 02/12/2014 06:17 AM, Håkan Save Hansson wrote:
> Hi,
>
> Please consider additional sub properties to “hyphens:auto” for
> more control over the hyphenation. As it is (tested in FF) the
> auto-hyphenation is too “strong”, meaning that any word that can
> be hyphenated will be, regardless the suitability and the will
> of the page editor.
>
> Examples:
>
> hyphens-[Don't hyphenate words shorter than]: 10
>
> hyphens-[Minimum count of characters before hyphen]: 3
>
> hyphens-[Minimum count of characters after hyphen]: 3
>
> hyphens-[Minimum count of characters after hyphen on the last paragraph line]: 6
>
> ..and a bit more advanced..
>
> hyphens-[Maximum count of subsequent lines with hyphens]: 2
>
> ..and so on (these were just from the top of my head).

These will be addressed in Level 4, as mentioned.
So deferred for now, but definitely on the list
of things we will work on once Level 3 is stabilized!

> Second suggestion:
>
> There are some language specific special cases with hyphenation. In Swedish for instance, if you write the two words “matta”
> (carpet)and “tjuv” (thief) as one you write it as “mattjuv”, with two t letters. This should hyphenate into “matt-tjuv”, with
> three t letters. This is not a hyphenation rule, but rather a type rule: when you write two words as one, there may never be
> more than two of the same letters where then two words concatenate.
>
> If you want to use a manual soft hyphen (­) for such a word you're in trouble. My suggestion is that when you write
> “matt­tjuv” in text and it is displayed without hyphenation, it respects this rule and suppresses one of the three letters
> t. I don’t know if such a rule could have a negative effect on texts in other languages, but I don’t know of any language
> allowing three subsequent letters. If needed maybe it could be controlled in CSS something like this:
>
> hyphens-[Maximum count of same letter before and after hyphen]: 2
>
> One could argue that this is not a CSS thing, rather up to the browser to handle (maybe with different behavior for different
> languages). Well, in my opinion it is certainly related to the rules how the soft hyphen (­) should be handled and without
> a standardno browser vendor would probably even think of implementing this behavior. Furthermore it must be handled, and
> handled in the same way, by all (modern) browsers before one can start using it on webpages. You dont want any “matttjuv” with
> three letters t out there (can't he even spell?). One should be able to check the support at for instance caniuse.com. This
> speaksin favor ofa CSS property like the one above.

I think James Clark's answer is the right one here:
   http://lists.w3.org/Archives/Public/www-style/2014Feb/0739.html

This would make an excellent test case.

Let me know if that addresses your concern~

~fantasai

Received on Friday, 9 May 2014 00:55:33 UTC