On 2017-08-23, Scott Kostyshak wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> On Fri, Jul 28, 2017 at 03:45:28PM +0200, Pavel Sanda wrote:
>> I tend to agree with f). It's not nice that we have such option in the prefs,
>> but since we screw the situation already we at least give user some power to
>> fix things onwards from 2.3 in his own way.
>> And some exclamation mark in RELEASE_NOTES.
> Can someone who understands the consequences please add an appropriate
> note to RELEASE-NOTES ?
Suggested patch:
diff --git a/lib/RELEASE-NOTES b/lib/RELEASE-NOTES
index 591fcae476..07f1831568 100644
--- a/lib/RELEASE-NOTES
+++ b/lib/RELEASE-NOTES
@@ -13,11 +13,34 @@
be safely dissolved, as it will be automatically inserted at export time
if needed, as usual.
-* LyX now outputs en- and em-dashes as -- and --- ligatures when exporting to
- latex using TeX fonts, as done in version 2.1 and earlier. In version 2.2
- they were instead output as the macros \textendash and \textemdash, causing
- changed output with old documents and bugs. The 2.2 behavior can be restored
- by don't allowing using dash ligatures in Document->Settings->Fonts.
+* Since version 2.2, -- and --- in the LyX source are output as -{}- and
+ -{}-{}- because otherwise some fonts ligate them to en- and em-dash.
+ Occurences in pre-2.2 documents are converted to literal Unicode dashes.
+ In some cases this leads to different line breaks:
+ + There is an optional line break after hyphens (also -- and ---) but not
+ after literal dashes.
+ + Hyphenation is suppressed in words following hyphens but allowed after
+ literal dashes.
+
+ The new setting
+ "Document->Settings->Fonts->Output em- and en-dash as ligatures" forces
+ output of en- and em-dashes as -- and --- when exporting to LaTeX.
+ The setting is on by default, unselected when opening documents edited
+ with LyX 2.2, and ignored for documents using non-TeX fonts.
+ As with all settings, the default for new documents can be
+ configured via templates.
+
+ + Select it, if you want optional line breaks after all en- and em-dashes
+
+ + Unselect it to prevent unwelcome line breaks in range specifications
+ using an en-dash (like 13–15) or between a dash and a non-breaking space
+ (e.g. opening "quotation dashes" in French) and to avoid conversion of
+ an em-dash into en-dash+hyphen or three hyphens in "typewriter"
+ (monospaced) fonts. If required, optional line breaks can be inserted
+ with Insert>Formatting>Optional line break.
+
+ See also "Caveats when upgrading from earlier versions to 2.3.x".
+
* The following UI translations were dropped, because the lack of translation
maintenance: Russian, Danish, Greek, Serbian, Galician, Catalan, Romanian,
@@ -154,6 +177,22 @@
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 line break behaviour.
+
+ It is no longer possible to differentiate dashes with/without optional
+ line break using --- and -- vs. literal dashes. Either convert one sort to
+ ERT or insert optional line break characters.
+
+ lyx2lyx deletes ZWSP characters following literal em- and en-dashes when
+ converting to 2.3 format. If you used literal ZWSP characters (u200b) as
+ optional line breaks after dashes, convert them to 0dd wide space insets
+ before opening your document with LyX 2.3 or the optional line breaks will
+ be lost.
+
+
* If using TeX fonts and en- and em-dashes are output as font ligatures,
when exporting documents containing en- and em-dashes to the format of
LyX 2.0 or earlier, the following line has to be manually added to the
Some of the problems can be avoided with minor changes to lyx2lyx:
* setting use-ligature-dashes according to content instead of file
version
* convert dashes to "\twohyphens" rsp. "\threehyphens" if
use-ligature-dashes is true.
I can provide a patch.
Günter
