-This file lists interface changes that might affect users in 1.5.0 and
-also some known problems in LyX 1.5.0 that did not occur in
-1.4.5. Note that fixes are available for many of these, but they have
-not yet been applied because of incomplete testing.
+This file lists interface changes that might affect users in 2.2.0, some
+known problems in LyX 2.2.0 and some things you have to take into account
+when upgrading from earlier versions to a version of the 2.2.x series.
Interface changes
-----------------
-Some of the LyX functions have changed names :
-
-
-Known issues with version 1.5.0
-------------------------------------
-
-- User layout files must be converted to UTF-8
-
-In previous version, layout styles were allowed to use non-ASCII names
-using the local encodings. LyX-1.5 now assumes that all layout files are
-UTF-8 encoded. This means that non-ASCII style names are still allowed
-but they nust be valid UTF-8 strings. One way of doing the conversion
-is to use iconv. Using bash, the script below should work:\r
-\r
-cd /path/to/layouts\r
-for l in *\r
-do\r
- cp $l tmp.txt\r
- iconv -f latin1 -t utf8 tmp.txt -o $l\r
-done
-rm tmp.txt
-
-- Cursor restoration problems with Multiple-View
-
-When using multiple Windows to edit different parts of the
-same document, the cursor position is sometimes not correctly restored
-when you switch from one view to the other.
-
-- Languages/encodings and insets
-
-One of the bugs fixed in LyX 1.5.0 is that previously, there were certain
-specific cases in which the LaTeX generated did not correctly reflect
-language/encoding transitions in and around insets (footnotes, LyX notes).
-After much deliberation, it was decided not to change older files such that
-they will still reflect the old LaTeX output; rather, they will now correctly
-reflect the situation as it appears in the GUI. This means, however, that if
-you mangled the text in the GUI in the older versions, in order that it
-generate the correct LaTeX output, the LaTeX will now generate the mangled
-text. If this is problematic for you, please get in touch with us on the
-developers mailing list, we do have some possible solutions for this.
-
-The effects of this will be more pronounced for RTL (Hebrew, Arabic, Farsi)
-users --- though they affect users of other languages as well.
-
-- Inset encodings and Conversion from earlier LyX versions
-
-One of the main new features in version 1.5.0 is Unicode. As part of the
-transition, lyx2lyx (the scripts used for converting back and forth between
-different versions of the lyx files) converts old .lyx files, which may use
-a number of different encodings, to UTF-8. This conversion depends on
-correctly identifying the language of the text. There were previously some
-edge-cases (insets embedded in different-language text type scenarios) in
-which the language was incorrectly identified, which caused some text to
-appear incorrectly after having upgraded from older versions. This has now been
-fixed. Unfortunately, however, the fix cannot be applied to files which have
-already been converted past format 249. So if you have already converted
-your old files (using a development version or release candidate), this fix
-won't help, unless you still have the originals lying around (and haven't
-yet made too many changes to the newer versions ;) ).
-
-Generally, it is probably wise to keep a backup of the old version of your
-files, at least until you are sure that the upgrade went smoothly (which it
-almost always will).
-
-
-Note: There may later be an updated list of known issues online at
- http://wiki.lyx.org/LyX/ReleaseNotes
+
+The following pref variables were added in 2.2:
+
+
+
+The following pref variables were changed in 2.2:
+
+
+
+The following pref variables are obsoleted in 2.2:
+
+- \\rtl
+ This variable was introduced to guard against any bad consequence of
+ the then-new right-to-left languages support. It is no longer needed
+ because of improvements. Now right-to-left support is always enabled.
+
+
+The following new LyX functions have been introduced in 2.2:
+
+- buffer-view-cache
+ Opens the last previewed output of the buffer, if it exists.
+
+- buffer-move-next
+ Moves the current tab one spot to the right.
+
+- buffer-move-previous
+ Moves the current tab one spot to the left.
+
+
+The following LyX functions have been changed in 2.2:
+
+
+
+The following LyX key bindings have been changed in 2.2:
+
+- For bindings where Control + {PgDn, PgUp} switches to the
+ {next, previous} tab, Control + Shift + {PgDn, PgUp} moves the current
+ tab to the {next, previous} tab.
+
+
+The following LyX documents have been moved in 2.2:
+
+
+
+The following metadata files have been added to the tarball in 2.2:
+
+
+
+Changes with respect to external programs and libraries in 2.2:
+--------------------------------------------------------
+
+- LyX is not yet supposed to work with Qt5. It is advised to compile and
+ run LyX against Qt 4.8.x. On Windows, Qt 4.8.5 suffers from a bug that
+ breaks the use of shortcuts, so on Windows Qt 4.8.4 is advised.
+
+- LyX now gives an error if the underlying LaTeX command exited with error.
+
+
+Known issues in version 2.2.0
+-----------------------------
+
+- LyX needs to be run under Python 2 and will not work properly on systems
+ where Python 3 is the default binary. See bug #7030 to know how to fix
+ this properly, since simple sheebang conversion in *.py files will not
+ be enough.
+
+
+Caveats when upgrading from earlier versions to 2.2.x
+-------------------------------------------------------
+
+- BibTeX errors are now processed and cause LyX to show the errors dialog.
+ Before, these errors were ignored, which means that it may happen that
+ documents that compiled without error with a previous version now
+ compile with error. However, because now in 2.2.x users can click on
+ the "Show Output Anyway" button, the document can still be viewed.
projects / lyx.git / blobdiff