X-Git-Url: https://git.lyx.org/gitweb/?a=blobdiff_plain;f=RELEASE-NOTES;h=64a6fd639f533acb1a1078b6205c98428c1e7cd5;hb=653376087d4107e127d577d6a4f29351a9d46b05;hp=ff2f1bb00b46750fc364da311f315f52d28768c0;hpb=fcac124405f9fcf8b13e6de9b2f0a47748634c4c;p=lyx.git diff --git a/RELEASE-NOTES b/RELEASE-NOTES index ff2f1bb00b..64a6fd639f 100644 --- a/RELEASE-NOTES +++ b/RELEASE-NOTES @@ -25,6 +25,8 @@ this menu got too large. If the flag "menu=export" is not explicitly set, the formats are not included in the menu. This means that you might need to click "Show in export menu" in Preferences > File Formats for your customized file formats if you want them to appear in the menu. +Customized formats imported from a previous configuration are handled +by the prefs2prefs script, and should appear in the menu as before. Note, though, that you still can export to any possible format via File > Export > More Formats and Options ... @@ -189,7 +191,7 @@ platform/distribution. * 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.13, for further instructions. + 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) @@ -206,6 +208,10 @@ least version 2.14 for proper work. 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 ----------------------------- @@ -218,6 +224,17 @@ Known issues in version 2.0.0 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. @@ -226,14 +243,23 @@ Caveats when upgrading from earlier versions to 2.0.x - 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 "Flex" is a namespace that is optional). - When LyX 2.0 reads older files, it silently converts the old-style names - to new-style names; this direction works perfectly. It 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: + 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", @@ -253,7 +279,7 @@ Caveats when upgrading from earlier versions to 2.0.x "PresentationMode" : "Custom:PresentationMode", "Tri-Glosse" : "Custom:Tri-Glosse" } - This is a map form new-style names (minux "Flex") to old-style names (and + 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. @@ -261,3 +287,5 @@ Caveats when upgrading from earlier versions to 2.0.x Note: There may later be an updated list of known issues online at http://wiki.lyx.org/LyX/ReleaseNotes +- UI layout named "classic.ui" and some localized keyboard bindings (sv,pt,fi) + were long time unmaintained and we do not ship it anymore.