Bugzilla

Are there any medium to longer-term thoughts about providing a way out of this for site authors as well? While it's nice that end-users can configure this, too, I'd think that site authors should actually be in a better position to judge whether hyphenation of capitalised words in English is a net benefit for their particular content or not.

So while I can understand the reasoning behind bug 1575513, I would like to note that for my present use case, this change still seems rather like a net *negative*:
I'm doing transcripts of radio shows with a [cue style](http://downloads.bbc.co.uk/writersroom/scripts/bbcradiocue.pdf)-like layout, and on mobile in portrait mode the column containing the character's name must by necessity get rather narrow in order to leave enough space for the actual dialogue.

Now a lot of the character's names are rather descriptive in nature and not true proper nouns and are only capitalised because
a) the first word needs to be capitalised anyway (but would occasionally still benefit from hyphenation if it's longer than average), and
b) otherwise because I've opted for writing them in title case (and if I was fully copying the BBC cue style, I'd actually have to go for all caps),
but bug 1575513 now means that I'm therefore opting them out from hyphenation whether I actually want it or not.

So for me being able to instruct the browser to hyphenate anyway (as Firefox used to) and then fixing the few instances of over-eager hyphenation with a Word Joiner would therefore be far preferable than having to go and litter soft hyphens around everywhere, which is rather annoying and precisely the reason I wanted to turn on auto-hyphenation in the first place. Okay, so I might have to do that anyway, because Chrome's hyphenation on Android seems so conservative such as to be mostly useless for my content anyway (it doesn't disable it just because a word has been capitalised, though, by the way)... but still.

Are there any medium to longer-term thoughts about providing a way out of this for site authors as well? While it's nice that end-users can configure this, too, I'd think that site authors should actually be in a better position to judge whether hyphenation of capitalised words in English is a net benefit for their particular content or not.

So while I can understand the reasoning behind bug 1550532, I would like to note that for my present use case, this change still seems rather like a net *negative*:
I'm doing transcripts of radio shows with a [cue style](http://downloads.bbc.co.uk/writersroom/scripts/bbcradiocue.pdf)-like layout, and on mobile in portrait mode the column containing the character's name must by necessity get rather narrow in order to leave enough space for the actual dialogue.

Now a lot of the character's names are rather descriptive in nature and not true proper nouns and are only capitalised because
a) the first word needs to be capitalised anyway (but would occasionally still benefit from hyphenation if it's longer than average), and
b) otherwise because I've opted for writing them in title case (and if I was fully copying the BBC cue style, I'd actually have to go for all caps),
but bug 1550532now means that I'm therefore opting them out from hyphenation whether I actually want it or not.

So for me being able to instruct the browser to hyphenate anyway (as Firefox used to) and then fixing the few instances of over-eager hyphenation with a Word Joiner would therefore be far preferable than having to go and litter soft hyphens around everywhere, which is rather annoying and precisely the reason I wanted to turn on auto-hyphenation in the first place. Okay, so I might have to do that anyway, because Chrome's hyphenation on Android seems so conservative such as to be mostly useless for my content anyway (it doesn't disable it just because a word has been capitalised, though, by the way)... but still.

Are there any medium to longer-term thoughts about providing a way out of this for site authors as well? While it's nice that end-users can configure this, too, I'd think that site authors should actually be in a better position to judge whether hyphenation of capitalised words in English is a net benefit for their particular content or not.

So while I can understand the reasoning behind bug 1550532, I would like to note that for my present use case, this change still seems rather like a net *negative*:
I'm doing transcripts of radio shows with a [cue style](http://downloads.bbc.co.uk/writersroom/scripts/bbcradiocue.pdf)-like layout, and on mobile in portrait mode the column containing the character's name must by necessity get rather narrow in order to leave enough space for the actual dialogue.

Now a lot of the character's names are rather descriptive in nature and not true proper nouns and are only capitalised because
a) the first word needs to be capitalised anyway (but would occasionally still benefit from hyphenation if it's longer than average), and
b) otherwise because I've opted for writing them in title case (and if I was fully copying the BBC cue style, I'd actually have to go for all caps),
but bug 1550532 now means that I'm therefore opting them out from hyphenation whether I actually want it or not.

So for me being able to instruct the browser to hyphenate anyway (as Firefox used to) and then fixing the few instances of over-eager hyphenation with a Word Joiner would therefore be far preferable than having to go and litter soft hyphens around everywhere, which is rather annoying and precisely the reason I wanted to turn on auto-hyphenation in the first place. Okay, so I might have to do that anyway, because Chrome's hyphenation on Android seems so conservative such as to be mostly useless for my content anyway (it doesn't disable it just because a word has been capitalised, though, by the way)... but still.