* The prefix for subsections in labels and references has been changed from
"sub:" to "subsec:" in order to avoid a clash with subfloats (conflicting
- \subref command, see bug #7550). Files are automatically converted to the new
+ \subref command, see #7550). Files are automatically converted to the new
scheme. Please assure that you adapt external refstyle or prettyref
definitions and your own layout files.
* buffer-move-previous
Moves the current tab one spot to the left.
+* tabular-feature is reintroduced to allow more flexibility for user
+ commands, whereas "inset-modify tabular" is now reserved for the tabular
+ dialog. In particular, "inset-modify tabular" is no longer caught by math grid
+ insets. The name tabular-feature is kept to avoid renaming icons. For more
+ information, see #9794.
!!!The following LyX functions have been changed in 2.2:
position); this behaviour can be restored by using the argument
"partial".
+* Functionality of "inset-modify tabular" has changed. See description of the
+ new LyX function "tabular-feature" above.
+
!!!The following LyX key bindings have been changed in 2.2:
* For bindings where Control + {PgDn, PgUp} switches to the
* The shortcuts for "bookmark-save x" have been changed from C-M-S-x to S-Fx
("x" stands for the number of the bookmark.)
-
!!!The following LyX documents have been moved in 2.2:
several regressions with respect to Qt 4.x. See #9215 for a list of bugs
related to compiling LyX with different versions of Qt.
+* The Qt libraries must have support for the SVG graphic format, because
+ LyX now uses svg icons. If this support is lacking, icons cannot be shown.
+
+* If compiling LyX on Windows with Qt 5.6, it is recommended to use MSVC 2015
+ update 2 to avoid #9892.
+
* 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 shebang conversion in *.py files will not
- be enough.
+* LyX needs Python 2.7 at runtime. The python 2 interpreter needs to be named
+ either 'python' or 'python2'.
+ Building LyX usually works with Python 3 as well, but there might be cases
+ where it does not work properly on systems where Python 3 is the default
+ binary. See #7030 to know how to fix this properly, since simple shebang
+ conversion in *.py files will not be enough.
+
+* If using LyX with Qt 4, it is possible to suddenly get keyboard keys wrong,
+ and deadlock. To work around the issue, you can disable IBus for LyX by
+ starting LyX as 'XMODIFIERS= lyx'. For further discussion and alternative
+ workarounds, see #9362.
+
+* LyX can produce LuaTeX output that is not compatible with the newest versions
+ of the engine (e.g. 0.95.0, the version in TeX Live 2016). In a later 2.2.x
+ version we plan to implement exporting of LuaTeX code that is compatible
+ with the LuaTeX versions shipped with both TeX Live 2015 and TeX Live 2016.
+ For more information, see the following mailing list thread:
+ https://www.mail-archive.com/search?l=mid&q=20160520075810.yi3uspufehev5aln%40cotopaxi
!!Caveats when upgrading from earlier versions to 2.2.x
* Documents using Times fonts and containing Greek characters may now fail
to compile under pdflatex for users of MikTeX due to an automatically
half-installed "grtimes" package. A workaround in LyX was removed as it
- stands in the way of alternative approaches (see bug #6469).
+ stands in the way of alternative approaches (see #6469).
* With LuaTeX, LyX now uses polyglossia instead of babel if the language
package option "Automatic" is selected. In order to use babel, select
"Always babel" instead. This may be needed if a document uses code that
is specific to babel.
+
+* As usual, when opening and saving a document that was created by a previous
+ major version of LyX (in this case 2.1.x), the file format is changed to
+ the new file format (in this case 2.2.x). What is different starting with
+ 2.2.0 is that when we save a file that was not originally in the current LyX
+ format, we create a backup of the original file. We put it in the backup
+ directory, if one exists, otherwise in the directory the original file is
+ in. This is the same strategy as for normal backups. This backup file can be
+ helpful in case a bug in lyx2lyx caused data loss. For more information, see
+ #9554.
projects / lyx.git / blobdiff