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. Günter diff --git a/lib/RELEASE-NOTES b/lib/RELEASE-NOTES index c605cb4850..12699f07f0 100644 --- a/lib/RELEASE-NOTES +++ b/lib/RELEASE-NOTES @@ -212,10 +212,14 @@ the external_templates file, you will have to move the modifications to the respective *.xtemplate file manually. -* If you used literal em- and en-dashes in pre-2.2 documents, - you must manually unselect - "Document->Settings->Fonts->Output em- and en-dash as ligatures" - to ensure unchanged behaviour. +* LyX 2.3 forces output of all en and em dashes as -- and --- when exporting + to LaTeX by default (exceptions are documents last saved with LyX 2.2 and + documents using non-TeX fonts). This can lead to incorrect line breaks, + wrong characters in typewriter fonts, and problems with + some LaTeX packages. + Unselect "Document->Settings->Fonts->Output em- and en-dash as ligatures" + to ensure unchanged behaviour. See chapter 3.9.1.1 "Dashes and line + breaks" of the User Guide for details. * ZWSP characters (u200b) following literal em- and en-dashes are deleted by lyx2lyx when converting to 2.3 format. If you used them as optional line
