Re: code breaks at -_ in non-TeX

[Patrice Dumas]

On Wed, Sep 05, 2012 at 04:20:34PM +0000, Karl Berry wrote:
> Patrice,
> 
>     -Ordinarily, @TeX{} will consider breaking lines at @samp{-} and
>     +Ordinarily, lines may be broken at @samp{-} and
>      @samp{_} characters within @code{@@code} and related commands.  This
>      can be controlled with @code{@@allowcodebreaks}
>      (@pxref{allowcodebreaks,,@code{@@allowcodebreaks}}).
> 
> Does this really apply to non-TeX?  I couldn't get Info output to break
> at - or _ in @code.  Is it supposed to?  Example input sentence:

It only applies to HTML (and TeX).

> And as for HTML, what I see in our output for codebreaks=no is
> white-space:nowrap; whose description
> (http://www.w3schools.com/cssref/pr_text_white-space.asp) indicates it's
> about whitespace, not hyphenation.  Furthermore, white-space:nowrap
> seems wrong to me.  Breaks at whitespace should not be affect by
> @allowcodebreaks; I think the only time they should be disallowed is
> inside @w text.

It also prevents from breaking at -.  If not in @w, the words are in 
white-space:nowrap, not the whole text.

> Of course, browsers nowadays (stupidly IMHO) break at any explicit
> hyphen by default.  It looks like this can be turned off with css
> hyphens:none.  Perhaps we should do that when codebreaks = no?
> http://www.w3.org/TR/css3-text/ (section "6.1. Hyphenation Control").

This doesn't prevent firefox from breaking lines at -.

> I couldn't find anything about breaking at _'s in HTML, and thankfully
> browsers aren't stupid-smart enough to do it yet, that I've seen.

Indeed.

> I don't really want to document all this, since we control very little
> of it.  How about if we say something like @allowcodebreaks applies to
> TeX, and to the other output formats as far as is possible?

Looks good.

-- 
Pat