Copy caveats from RELEASE-NOTES to UPGRADING

This commit is contained in:
Scott Kostyshak 2018-02-22 23:23:32 -05:00
parent 88f4cb4999
commit b12156255d

View File

@ -9,26 +9,14 @@ to add new templates or modify existing ones. If you have modified
the external_templates file, you will have to move the modifications to the external_templates file, you will have to move the modifications to
the respective *.xtemplate file manually. the respective *.xtemplate file manually.
By default, LyX 2.3 forces output of all en and em dashes as -- and --- By default, LyX 2.3 outputs en- and em-dashes as -- and --- respectively,
when exporting to LaTeX. This can lead to incorrect line breaks, wrong so that a line break can occur in the output immediately after the dash.
characters in typewriter fonts, and problems with some LaTeX packages. Sometimes, this results in undesired line breaks or overfull lines due to
Unselect "Document->Settings->Fonts->Output em- and en-dash as ligatures" suppression of hyphenation in the word preceding the dash.
to keep the LyX 2.2 behaviour and avoid these problems. See chapter 3.9.1.1 Select "Document->Settings->Fonts->Disallow line breaks after dashes"
"Dashes and line breaks" of the User Guide for details. to keep the LyX 2.2 behaviour.
See chapter 3.9.1.1, "Dashes and Line Breaks", of the User Guide
ZWSP characters (u200b) following literal em- and en-dashes are deleted by for details.
lyx2lyx when converting to 2.3 format. If you used them as optional line
breaks after dashes, convert them to 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
unicodesymbols file of that LyX version:<br>
0x200b "\\hspace{0pt}" "" "" "" "" # ZERO WIDTH SPACE<br>
This avoids "uncodable character" issues if the document is actually
loaded by that LyX version. LyX 2.1 and later versions already have the
necessary definition in their unicodesymbols file.
If trying to compile documents using R scripts and sweave/knitr, LyX If trying to compile documents using R scripts and sweave/knitr, LyX
2.3.x would not allow for re-running the R scripts, unless the user: 2.3.x would not allow for re-running the R scripts, unless the user: