Here another update to UPGRADING. Lars, is that OK?
Also, Lars could you update INSTALL.autoconf from the INSTALL file of
the version of autoconf you plan to use, and ABOUT-NLS from gettext?
We should tell somewhere which version of Python is needed (1.5?)
JMarc
? config.h.in
Index: ChangeLog
===================================================================
RCS file: /usr/local/lyx/cvsroot/lyx-devel/ChangeLog,v
retrieving revision 1.899
diff -u -p -r1.899 ChangeLog
--- ChangeLog 30 Jan 2003 12:40:01 -0000 1.899
+++ ChangeLog 4 Feb 2003 10:52:21 -0000
@@ -1,3 +1,9 @@
+2003-02-04 Jean-Marc Lasgouttes <[EMAIL PROTECTED]>
+
+ * NEWS: add entry for LyX 1.2.3
+
+ * UPGRADING: update for 1.3.0
+
2003-01-30 Kayvan A. Sylvan <[EMAIL PROTECTED]>
* Makefile.am: test for the presence of rpmbuild.
Index: NEWS
===================================================================
RCS file: /usr/local/lyx/cvsroot/lyx-devel/NEWS,v
retrieving revision 1.50
diff -u -p -r1.50 NEWS
--- NEWS 26 Jan 2003 16:57:47 -0000 1.50
+++ NEWS 4 Feb 2003 10:52:21 -0000
@@ -117,6 +117,22 @@ to do such things, the filters to `downg
multi-language documents, assuming you have the right dictionaries
installed.
+
+What's new in version 1.2.3?
+----------------------------
+
+LyX 1.2.3 is a maintenance release. It mainly fixes a very bad bug
+where configuring LyX as root could lead to deleting the /dev/null
+special device (this does not impact users of prebuilt binaries).
+Also, a bug where LyX would create zombie processes has been fixed.
+
+** Updates
+
+- updated italian User Guide
+
+- updated french localization
+
+
What's new in version 1.2.2?
----------------------------
Index: UPGRADING
===================================================================
RCS file: /usr/local/lyx/cvsroot/lyx-devel/UPGRADING,v
retrieving revision 1.15
diff -u -p -r1.15 UPGRADING
--- UPGRADING 27 Jan 2003 18:33:55 -0000 1.15
+++ UPGRADING 4 Feb 2003 10:52:21 -0000
@@ -9,6 +9,17 @@ Edit->Reconfigure automatically the firs
If you have your own layout files, you may need to update them a little:
+- floats are now defined in the layout file, using the "Float"..."End"
+ construct. In most cases, adding "Input stdfloats.inc" to your layout
+ file is enough.
+
+- counters are also defined in the layout files, using the
+ "Counter"..."End" construct. As for floats, adding "Input
+ stdfloats.inc" is probably a good idea.
+
+And of course, if you upgrade from LyX 1.1.x, remember that since
+1.2.0, you have to do the following changes:
+
- all layout files should have a "DefaultStyle" entry
- the "Latex" font style does not exist anymore. If you really need
@@ -47,20 +58,23 @@ written using previous versions of LyX.
0.12 are supported, so any klyx users still holding out for an alternative
to xforms will finally be able to put their dinosaur to rest ;-)
-Of course, this means that you must have python installed in order to
-use LyX 1.3.0 with your old documents.
+Of course, this means that you must have python (at least version 1.5)
+installed in order to use LyX 1.3.0 with your old documents.
lyx2lyx also has the framework in place to be able to convert documents
to an earlier format. However, these converters have not yet been written
so older versions of LyX will NOT be able to read documents saved with
LyX 1.3.0.
-If you were previously using the floatflt paragraph option to
-wrap text around a figure, you will need to modify this for LyX 1.2.0
-manually, as described in the manuals. Please ask on the lyx-users
-list for assistance if you have trouble with this.
+If you were previously (in LyX 1.1.x) using the floatflt paragraph
+option to wrap text around a figure, it was necessary to modify this
+for LyX 1.2.0 manually, as described in the manuals. The feature has
+been re-implemented as "Floting figure" inset in 1.3.0. Old files will
+be converted automatically, but you may want to convert the
+1.2.x-style ERT constructs with the native solution (see section 3.8
+of the Extended Features manual).
-The babel package is now loaded after the user-defined
+Since LyX 1.2.0, the babel package is loaded after the user-defined
preamble (because some packages really need to be loaded before
babel). If you relied, on babel being loaded before your own
definitions, you can add an extra "\usepackage{babel}" statement at
