mirror of
https://git.lyx.org/repos/lyx.git
synced 2024-11-21 17:51:03 +00:00
Upadate NEWS and some small other tweaks
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@682 a592a061-630c-0410-9148-cb99ea01b6c8
This commit is contained in:
parent
33868acd2c
commit
ff5ca3cd82
@ -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
|
||||
|
10
INSTALL
10
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
|
||||
|
23
NEWS
23
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?
|
||||
|
@ -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.
|
||||
|
@ -77,10 +77,6 @@ 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;
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user