On 2017-10-14, Jürgen Spitzmüller wrote:
> Am Samstag, den 14.10.2017, 01:30 -0400 schrieb Scott Kostyshak:
>> On Mon, Oct 09, 2017 at 11:56:12AM +0000, Guenter Milde wrote:
>> > On 2017-10-07, Scott Kostyshak wrote:
>> > 
>> > > Any other important issues to consider before releasing rc1?
>> > 
>> > The current default behaviour for dash export is a regression on
>> > changeset 798ad9755a1ff43a06d2b from 16.06.2007
>> >   
>> >   unicodesymbols: use commands for the dashes for consistency
>> >   reasons and
>> >   to avoid potential problems with some LaTeX-packages
>> >   
>> > We should either change the default value of 
>> > Document->Settings->Fonts->Output em- and en-dash as ligatures
>> > to "false" or document the change in the release notes (patch
>> > below).
>> > 
>> > I vote for changing the default.

>> If you get support before rc1 for changing the default, we can
>> consider
>> it.

> Personally, I prefer to stick with the current default (i.e., use
> ligatures).

The current default in 2.3 differs from the 2.2 behaviour (use literal
dashes). Users upgrading to 2.3 will therefore experience a changed
typesetting behaviour with new documents unless they change the default:

a) optional line breaks after every em and en dash 
   (except for export with LuaTeX in documents using non-TeX fonts)
   
   +1 Useful for documents written in American English with many unspaced em
      dashes.
   
   -1 However, incorrect line breaks must be prevented by wrapping in a
      makebox or preceding with \nobreakdash in ERT.
   
      • pages~\mbox{369--378}
      • Les incises mbox{--}~même si tout le monde ne les aime pas~–
        sont très utiles.
      • En una frase \nobreakdash---un inciso con rayas--- se escribe así.
   
   * Documents written in other languages/styles than American English do
     not gain from the ligature dash setting.
   
   * The markup to prevent line breaks is more heavy (visually) and
     cumbersome (more keystrokes) than setting optional line breaks.  See
     examples in the UserGuide section 3.9.2):
      
   * An incorrect line break is easily overlooked because – in contrast
     to an overfull line – it does not trigger a warning in the LaTeX
     log.

b) Em dashes in typewriter fonts become –- or --- in the output.

c) Hyphenation is suppressed in words adjacent to hyphens and ligature
   dashes.


The original TeX convention was adapted by Knuth for American English.
The behaviour in LyX 2.2 follows the convention adapted by the LaTeX
community in 1994 to care for a wider international user base.

IMO, LyX should follow the LaTeX convention also with the 2.3 default
behaviour and switch to the Knuthian font ligatures as an opt-in.

Günter



Reply via email to