Upadate NEWS and some small other tweaks

git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@682 a592a061-630c-0410-9148-cb99ea01b6c8

diff --git a/ChangeLog b/ChangeLog
index c39564bc9bc9c99a927c17c2026b7ebf8bc3af4b..0dfc16f1495b702493a833c4a8f4b046a5c404de 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2000-04-19  Jean-Marc Lasgouttes  <Jean-Marc.Lasgouttes@inria.fr>
+
+       * src/mathed/formulamacro.C (Latex): remove CHECK comment, since
+       code seems to be alright (it is code changed by Dekel, and the
+       intent is indeed that all macros should be defined \protect'ed)
+
+       * NEWS: a bit of reorganisation of the new user-visible features.
+
 2000-04-19  Juergen Vigna  <jug@sad.it>
 
        * src/insets/insettext.C (init): using a LyXCursor now for cursor

diff --git a/INSTALL b/INSTALL
index 515c9fcc548ef6038500d21194b20d9de26a397a..969b86571a208aa9f5d5b3ee5aa3ac507548009c 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -58,11 +58,11 @@ libXpm can be found at:
            (or similar locations at other sunsites like sunsite.unc.edu)
 
 You will also need a recent C++ compiler, where recent means that the
-compilers are close to C++ standard conforming. Compilers that are known
-to compile LyX are gcc 2.8.1 and 2.95.x, the various versions of egcs
-and Digital C++ version 6.1. Please tell us your experience with other
-compilers. It is _not_ possible to compile LyX with gcc
-2.7.x, and this is not likely to change in the future. 
+compilers are close to C++ standard conforming. Compilers that are
+known to compile LyX are gcc 2.8.1 and 2.95.x, the various versions of
+egcs and Digital C++ version 6.1. Please tell us your experience with
+other compilers. It is _not_ possible to compile LyX with gcc 2.7.x,
+and this is not likely to change in the future.
 
 Note that, contrary to LyX 1.0.x, LyX 1.1.x makes great use of C++
 Standard Template Library (STL); this means that gcc users will have
@@ -191,7 +191,7 @@ desperate cases:
     this flag is on for development versions only.
 
   o --enable-assertions that make the compilier generater run-time
-    code which checks that some variables have sane values.  Opposite
+    code which checks that some variables have sane values. Opposite
     is --disable-assertions.  By default, this flag is on for
     development versions only. 
 

diff --git a/NEWS b/NEWS
index 47fd131905fb10873b67dc456a5b58032e17668e..38e926216f0c3b080be14f8e2d4847472e7b4739 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -13,28 +13,29 @@ User-visible changes:
 - Right-to-Left support for Hebrew and Arabic, this is a first attempt
   only and is likely to improve in future versions.
 
-- Removed support for XForms older than 0.88.
-
-- Some commandline options and X resources are not supported anymore
-  (The color ones, and -mono -fastselection, -reverse)
+- Per-paragraph spacing, currently only settable wrom the
+  command-line/window:
+      paragraph-spacing (default,single,onehalf,double,other) [float]
 
 - More accurate error reporting from LaTeX runs.
 
 - Better definition for LyXList style.
 
-- option \show_banner [true|false] added to .lyxrc commands.
-
 - A couple of changes to the LyX format, so that files written with
   1.1.5 will not be parsed correctly by older LyX versions if protected
   spaces or the new per-paragraph spacing are used. Also the RtL
   support is of course not supported in older versions.
 
-- Per-paragraph spacing, currently only settable wrom the
-  command-line/window:
-      paragraph-spacing (default,single,onehalf,double,other) [float]
+- Removed support for XForms older than 0.88.
+
+- Some commandline options and X resources are not supported anymore
+  (The color ones, and -mono -fastselection, -reverse)
+
+- new lyxrc variables: \show_banner [true|false] to remove the banner
+  screen, and \backupdir_path to tell where the backup files created
+  by lyx should be stored. 
+
 
-- .lyxrc feature: \backupdir_path that tells where the backup files
-  created by lyx will be stored.
 
 
 What's new in LyX version 1.1.4?

diff --git a/src/bufferlist.C b/src/bufferlist.C
index 6fc5fbad2422e181bc44e728801fa6d0d23590bf..e4497ba2343298619a505eef8b2dd88d9a08af2f 100644 (file)
--- a/src/bufferlist.C
+++ b/src/bufferlist.C
@@ -466,7 +466,7 @@ Buffer * BufferList::loadLyXFile(string const & filename, bool tolastfiles)
                if (LyXVC::file_not_found_hook(s)) {
                        // Ask if the file should be checked out for
                        // viewing/editing, if so: load it.
-                       if (AskQuestion(_("Do you want to retrive file under version control?"))) {
+                       if (AskQuestion(_("Do you want to retrieve file under version control?"))) {
                                // How can we know _how_ to do the checkout?
                                // With the current VC support it has to be,
                                // a RCS file since CVS do not have special ,v files.

diff --git a/src/mathed/formulamacro.C b/src/mathed/formulamacro.C
index 6b8f706a8970b82d5b98cc6cd93dc8b669f439ed..27e28d51b19af0dfa24ac3521f98ffdf27c5b611 100644 (file)
--- a/src/mathed/formulamacro.C
+++ b/src/mathed/formulamacro.C
@@ -77,11 +77,7 @@ int InsetFormulaMacro::Latex(ostream & os, bool /*fragile*/,
                             bool /*free_spacing*/) const
 {
        tmacro->WriteDef(os, true); // or false?
-       // CHECK
-       // This is the only place where a '1' is used rather that '-1' or '0'
-       // for value of fragile. What is the reason behind it and does it make
-       // a difference? (Lgb)
-    return 1;
+       return 1;
 }