Follow-up Comment #34, bug #66392 (group groff): [comment #33 comment #33:] > Maybe a better model is for the hyphenation code _and_ language > to be global instead. Dave suggested this,
This is a misreading of what I said. (Or possibly a miswriting on my part.)
My suggestion was to retain the historical behavior (the mode per-environment,
and the language global) based on what I expect is the commonest usage--which
is what default behavior is for. Any deviation from the default can still be
managed manually.
> bug #66387 astonished me. And it appears to be astonishing
> others, including Tadziu. That this aspect of formatter
> behavior kinks even _his_ eyebrow should give us pause.
I agree. It's worth considering and not insane to change it. However, onf
called for the behavior to change, and Tadziu did not--he even wrote "There's
nothing really wrong with the way it is now, and arguments can even be made
for keeping it this way." (It might be unclear because "the way it is now" is
ambiguous, since it recently changed in git. But the challenge specifically
cited 1.23 or earlier, and the context of his comments make clear he's talking
about the 1.23 behavior.) So it's also not insane to leave it as it
historically has been. I don't think list opinion has coalesced around one
option or the other. But probably not a lot of people are writing
multilanguage documents where languages are separated by environment, so there
may not be much more input.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66392>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
