Update it.po

[lyx.git] / lib / RELEASE-NOTES

diff --git a/lib/RELEASE-NOTES b/lib/RELEASE-NOTES
index 4e6a9b899204c92c509523688e5b29e6faa18469..dccd1f10ed42ba337107ee75984fcccd2f3b8edd 100644 (file)
--- a/lib/RELEASE-NOTES
+++ b/lib/RELEASE-NOTES
@@ -14,11 +14,10 @@
   if needed, as usual.
 
 * 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.
-  It is is "true" by default but "false" when opening documents edited
-  with LyX 2.2.
-  See chapter 3.9.1.1 "Dashes and line breaks" of the User Guide and
+  "Document->Settings->Fonts->Disallow line breaks after dashes"
+  turns off the conversion of em- and en-dash characters to --- and --
+  respectively for LaTeX export. It is is "false" by default.
+  See chapter 3.9.1.1 "Dashes and Line Breaks" of the User Guide and
   "Caveats when upgrading from earlier versions to 2.3.x" below.
 
 * The following UI translations were dropped, because the lack of translation
@@ -186,11 +185,20 @@
 
 !!Changes with respect to external programs and libraries in 2.3:
 
+* LyX now supports only macOS 10.9 and higher (due to using Qt 5.9).
+
 * Inkscape SVG with separate LaTeX + PDF or PS output is supported via External
   Material.
 
 * Add some editor/viewer applications to (re)configure checks.
 
+* The included Hunspell has been upgraded to version 1.6.2.
+
+* The included libiconv has been upgraded to version 1.15.
+
+* LyX now includes a Qt-based fallback-converter for Mac to compensate missing
+  ImageMagick convert utility.
+
 
 !!Known issues in version 2.3.0
 
@@ -205,24 +213,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.
-
-* 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
-  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.
+* By default, LyX 2.3 outputs en- and em-dashes as -- and --- respectively,
+  so that a line break can occur in the output immediately after the dash.
+  Sometimes, this results in undesired line breaks or overfull lines due to
+  suppression of hyphenation in the word preceding the dash.
+  Select "Document->Settings->Fonts->Disallow line breaks after dashes"
+  to keep the LyX 2.2 behaviour.
+  See chapter 3.9.1.1, "Dashes and Line Breaks", of the User Guide
+  for details.
 
 * 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:
@@ -237,3 +235,9 @@
   example, create a document with a title layout, then a standard layout, and
   then an author layout, and you will see in the PDF that the author is not
   typeset as an author.
+
+
+!! If upgrading from a LyX version before 2.2.0
+
+* Please additionally see the release notes from the versions in-between:
+  https://wiki.lyx.org/LyX/ReleaseNotes