-- 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:
-
-#! /bin/sh
-
-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
-
-- 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).
-
-- RTL and keymaps
-
-Currently there is a bug where you can't use two non-RTL language keymaps if
-the RTL preference is set (which is now the default). If you need to use two
-non-RTL keymaps, for now you should just turn off the RTL preference (Tools ->
-Preferences... -> Language settings -> Language, uncheck "Right-to-left
-language support").
-
-We hope to offer more comprehensive support for multiple keymaps in the future,
-which will solve this bug, as well as allow more than just two keymaps. If you
-have any input on this issue, please chime in on the developers mailing list,
-or add your comments to http://bugzilla.lyx.org/show_bug.cgi?id=4051.
+LyX 2.0 introduces support for some new external helper programs/libraries,
+while the support for some existing programs has been dropped. This
+particularly applies to spell checking and the thesaurus.
+
+1.) SPELLCHECKING:
+
+* Direct support for ispell and hspell has been dropped. However, ispell
+ and hspell are still accessible via the enchant wrapper (see below).
+
+* Support for the aspell command line program has been dropped. Note that
+ the aspell library (aspell 0.60.x) is still supported.
+
+* As well as the aspell library, LyX now also supports hunspell (the spell
+ checker used by OpenOffice and Firefox) and enchant, a wrapper that
+ provides automatic access to many spell checking libraries (ispell,
+ aspell, hspell, hunspell, etc.).
+
+* On Mac OSX, Apple's Spell Server is preconfigured as the "native" spell
+ checker.
+
+LyX 2.0 is configured for any and all of these three possibilities,
+given that the various libraries are installed on the machine where LyX is
+configured. The actual spell checker can be selected in Tools > Preferences.
+Packagers are advised to pre-select whatever is most common on their
+platform/distribution.
+
+2.) THESAURUS:
+
+* Support for the aiksaurus library has been dropped in favour of the
+ MyThes thesaurus library (the thesaurus library used by OpenOffice).
+
+* LyX ships the MyThes library itself, so unlike in LyX 1.6.x, no extra
+ thesaurus library needs to be installed. However, LyX does not ship any
+ thesaurus dictionaries, and those do have to be installed separately.
+
+* The OpenOffice thesaurus dictionaries can be used, but the path to those
+ dictionaries needs to be set in Tools > Preferences. Please refer to the
+ UserGuide, sec. 6.14, for further instructions.
+
+Packagers are advised to preset the thesaurus for their distribution/
+platform. Packagers of installation bundles (on Windows and the Mac)
+are advised to provide automatic installation of thesaurus dictionaries
+in the installation process (analoguous to the spellchecker installation).
+
+3.) LILYPOND:
+
+There is now direct support for Lilypond-book. Note that LyX requires at
+least version 2.14 for proper work.
+
+4.) INSTANT PREVIEW:
+
+Make sure that dv2dt (often part of LaTeX distributions) is installed
+on your system. Instant preview wil be disabled if dv2dt is not found.
+
+5.) LuaTeX support
+
+For proper LuaTeX support you need to have at least TeXLive 2010.
+
+
+Known issues in version 2.0.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.0.x
+-------------------------------------------------------
+
+- The typeset of your documents with non-english language can slightly
+ change in case of math environments and floats (this is usually the case
+ with certain modules which provide specific environments like AMS ones
+ or provide specific floats like the linguistic one).
+
+ LyX now uses its own translation machinery which will automatically provide
+ localization strings used so far only in GUI. The status of translation to
+ your language can be seen in lib/layouttranslation file. This is not meant as
+ a babel replacement (still used), but rather extension for strings not
+ translated by babel at all.
+
+- The syntax of the languages file has been changed. If you use a modified
+ languages file, you will need to adapt it to the new syntax, as LyX 2.0
+ is not able to read old languages file anymore.
+ Please refer to the beginning of the languages file for an explanation
+ of the new syntax.
+
+- There has been a large change in how Flex insets are named. Previously,
+ they tended to have names like "CharStyle:Noun". Now, they just have
+ names like "Flex:Noun" (where the "Flex" prefix is now required). When
+ LyX 2.0 reads older files, it silently converts the old-style names
+ to new-style names; this direction works almost perfectly. The one place
+ it does not work is with CopyStyle declarations, IF your old InsetLayout
+ was NOT named "CharStyle:..." or "Custom:..." or "Element:...", but, say,
+ just "MyInset". In that case, "InsetLayout MyInset" will be changed to
+ "InsetLayout Flex:MyInset", but "CopyStyle MyInset" will be left as is.
+ Users will need to make that kind of change manually. The best way to do
+ this is to use the layout2layout.py script, which gets installed in
+ $LYXDIR/scripts/layout2layout.py, to convert your custom layout files to
+ the new format, and then check them for correctness.
+
+ LyX will also silently revert new-style names to old-style names when
+ exporting to 1.6.x format, but only for the pre-defined LyX insets. This
+ means that user-defined flex insets will not be properly reverted. To solve
+ this problem, you can modify the file $LYXDIR/lyx2lyx/lyx_2_0.py. In that
+ file, you will find the following:
+ flex_insets = {
+ "Alert" : "CharStyle:Alert",
+ "Code" : "CharStyle:Code",
+ "Concepts" : "CharStyle:Concepts",
+ "E-Mail" : "CharStyle:E-Mail",
+ "Emph" : "CharStyle:Emph",
+ "Expression" : "CharStyle:Expression",
+ "Initial" : "CharStyle:Initial",
+ "Institute" : "CharStyle:Institute",
+ "Meaning" : "CharStyle:Meaning",
+ "Noun" : "CharStyle:Noun",
+ "Strong" : "CharStyle:Strong",
+ "Structure" : "CharStyle:Structure",
+ "ArticleMode" : "Custom:ArticleMode",
+ "Endnote" : "Custom:Endnote",
+ "Glosse" : "Custom:Glosse",
+ "PresentationMode" : "Custom:PresentationMode",
+ "Tri-Glosse" : "Custom:Tri-Glosse"
+ }
+ This is a map from new-style names (minux "Flex") to old-style names (and
+ there is a similar for DocBook elements). To get a user-defined CharStyle
+ to revert properly, it simply needs to be added to this list.