X-Git-Url: https://git.lyx.org/gitweb/?a=blobdiff_plain;f=RELEASE-NOTES;h=63b6f5a5fbab726f979b808ae30d8e8b27088922;hb=ff294eb17349538a23f7759886734f8f8d1e5b0d;hp=2d30ae60cc34da8b769e55a3f282ca2134dad5d3;hpb=563bcdb437eca400f459572755503d089f4b4fa1;p=lyx.git diff --git a/RELEASE-NOTES b/RELEASE-NOTES index 2d30ae60cc..63b6f5a5fb 100644 --- a/RELEASE-NOTES +++ b/RELEASE-NOTES @@ -1,79 +1,59 @@ -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.0.0, some +known problems in LyX 2.0.0 and some things you have to take into account +when upgrading from earlier versions to a version of the 2.0.x series. +Note that fixes are available for some of these, but they have not yet +been applied because of incomplete testing. Interface changes ----------------- -Some of the LyX functions have changed names : +There have been some changes to the LyX command line. There is a new option +"--batch" that causes LyX to run the given commands without opening a GUI +window. Thus, something like: + lyx --batch -x "buffer-print printer default dvips" myfile.lyx +will cause LyX to print myfile.lyx to the default printer, using dvips and +the default print settings (which, of course, have to have been configured +already). At present, not many commands can be used this way, but there will +be more eventually. +The following variables are obsoleted in 2.0 -Known issues with version 1.5.0 ------------------------------------- +- \plaintext_roff_command (was not used anymore) +- \spell_command and \use_spell_lib (ispell support has been removed) +- \custom_export_command and \custom_export_format -- User layout files must be converted to UTF-8 -In previous versions, 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 must be valid UTF-8 strings. One way of doing the conversion -is to use iconv. Using bash, the script below should work: +The following new LyX functions have been introduced: -#! /bin/sh +- LFUN_WORD_FINDAD ("word-findadv"). -cd /path/to/layouts -for l in * -do - cp "$l" tmp.txt - iconv -f latin1 -t utf8 tmp.txt -o "$l" -done -rm -f tmp.txt +- LFUN_REGEXP_MODE ("regexp-mode"). -- Cursor restoration problems with Multiple-View +The following LyX functions have been removed: -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. +- LFUN_NEXT_INSET_TOGGLE ("next-inset-toggle"): use "inset-toggle" instead. -- Languages/encodings and insets +The following LyX functions have been changed: -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. +- LFUN_INSET_TOGGLE ("inset-toggle"): For some insets, this function was used + to show the settings dialog. This is no longer possible and one should use + inset-settings for this purpose. -The effects of this will be more pronounced for RTL (Hebrew, Arabic, Farsi) -users --- though they affect users of other languages as well. +Known issues in version 2.0.0 +----------------------------- -- 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 ;) ). +Caveats when upgrading from earlier versions to 2.0.x +------------------------------------------------------- + -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 +TODO +---- +Somebody should create a rc2rc script... +http://www.lyx.org/trac/changeset/27531