+----------------------------------------------------+
bg cs da de el en eo es et fi fr gl he hr id it ja
0 14 24 32 11 1 8 23 13 1 33 22 4 0 7 9 18
-
+
ko lv nb nl nn no pl pt pt_BR ru sk sl sv tr uk zh
+----------------------------------------------------+
a2ps | [] [] [] | 6
ftp://ftp.lyx.org/pub/lyx/bin/1.3.0
If you find what you think is a bug in LyX 1.3.0, you may either
-e-mail the LyX user's mailing list (lyx-users@lists.lyx.org), or open
+e-mail the LyX developers' mailing list (lyx-devel@lists.lyx.org), or open
a bug report at http://bugzilla.lyx.org
If you're having trouble using the new version of LyX, or have a question,
-first check out http://www.lyx.org/help/, and e-mail the LyX user's list if you
-can't find an answer there.
+first check out http://www.lyx.org/help/, and e-mail the LyX users' list
+(lyx-users@lists.lyx.org) if you can't find an answer there.
Enjoy!
of the dialogs are slightly different in design, but are generally
functionally equivalent.
-Note that if Qt is using Xft2/fontconfig, you may need to install the
-latex-ttf-fonts package on ftp://ftp.lyx.org/ to get maths symbols
-displayed properly.
-
** Xforms frontend
The advent of the Qt frontend does not mean that the historical xforms
many bugs that have been plaguing LyX have been fixed in xforms. You
are advised to upgrade to xforms 1.0 to enjoy all these new fixes.
In fact, LyX 1.3.0 no longer supports versions of xforms older than 0.89.5.
+Moreover, support for xforms older than 1.0 will be removed in the next
+release. You have been warned ;-)
In most cases the dialogs have been designed to make it impossible to input
invalid parameters. The exception to this rule is the input of length data.
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
- In addition, as a special exception, the LyX Team gives permission to
- link the code of this program with the XForms library (or with modified
- versions of XForms that use the same license as XForms), and distribute
- linked combinations including the two. You must obey the GNU General
- Public License in all respects for all of the code used other than XForms.
- If you modify this file, you may extend this exception to your version of
- the file, but you are not obligated to do so. If you do not wish to do so,
+ In addition, as a special exception, the LyX Team gives permission to
+ link the code of this program with the XForms library (or with modified
+ versions of XForms that use the same license as XForms), and distribute
+ linked combinations including the two. You must obey the GNU General
+ Public License in all respects for all of the code used other than XForms.
+ If you modify this file, you may extend this exception to your version of
+ the file, but you are not obligated to do so. If you do not wish to do so,
delete this exception statement from your version.
The GNU General Public License version 2 is included below for your reference.
+2003-02-06 Angus Leeming <leeming@lyx.org>
+
+ * ANNOUNCE: email the devel list with bugs. Move fontconfig stuff to
+ install.
+
+ * INSTALL: a chunk on using fontconfig with the Qt frontend.
+
+ * ABOUT-NLS:
+ * ANNOUNCE:
+ * COPYING:
+ * INSTALL:
+ * lyx.man:
+ * NEWS:
+ * README:
+ * README.OS2:
+ * README.Win32:
+ * UPGRADING: whitespace
+
2003-02-04 Angus Leeming <leeming@lyx.org>
* Makefile.am: allow lyx.xpm to be found when making rpmdist in
2003-02-04 Jean-Marc Lasgouttes <Jean-Marc.Lasgouttes@inria.fr>
- * ANNOUNCE:
- * INSTALL:
+ * ANNOUNCE:
+ * INSTALL:
* README: mention that all qt 3.x should work (not only 3.0.x).
* INSTALL: mention python 1.5.2.
4) make install
will install it. You can use "make install-strip" instead
- if you want a smaller binary.
+ if you want a smaller binary.
Note for CVS checkouts
files and proceed as stated below.
You will also probably need GNU m4 (perhaps installed as gm4).
-
+
Requirements
------------
It is imperative that you have the correct versions of these
libraries, and their associated header files.
-The xforms library has been very recently updated to version 1.0.
-This version has been released under the LGPL (Lesser General Public
-License), and the availability of the source means that many bugs that
-have been plaguing LyX have been fixed in xforms. You are advised to
+The xforms library has been very recently updated to version 1.0.
+This version has been released under the LGPL (Lesser General Public
+License), and the availability of the source means that many bugs that
+have been plaguing LyX have been fixed in xforms. You are advised to
upgrade to xforms 1.0 to enjoy all these new fixes.
In fact, LyX 1.3.0 no longer supports versions of xforms older than 0.89.5.
If you use a rpm-based linux distribution, such as RedHat or Mandrake,
we recommend that you grab a version of xforms from
- ftp://ftp.lyx.org/pub/lyx/contrib
+ ftp://ftp.lyx.org/pub/lyx/contrib
Look for the xforms-1.0-release.src.rpm or the binary libforms*.i386.rpm.
In addition, you must have libXpm version 4.7 or newer.
point to make is that you must ensure that both LyX and the Qt libraries
are compiled with the same C++ compiler.
+Note that if Qt is using Xft2/fontconfig, you may need to install the
+latex-ttf-fonts package, tobe found on ftp://ftp.lyx.org/ to get maths
+symbols displayed properly. To find out, type:
+ ldd `which lyx` | grep fontconfig
+at the console. Both RH8 and Debian unstable distributions are known
+to use fontconfig.
+
+If, however, your version of Qt does not use fontconfig, then the
+/usr/local/share/lyx/xfonts directory (or equivalent) should be added to
+the font path. This is done automatically by LyX if LyX is run on
+the local machine, and the X server supports Postscript fonts. If, however,
+you're running LyX remotely, then you'll have to do this step yourself.
+'man xset' is your friend.
+
+* Other things to note
If you make modifications to files in src/ (for example by applying a
patch), you will need to have the GNU gettext package installed, due
To use the thesaurus, you will need to install libAikSaurus, available
from:
- http://aiken.clan11.com/aiksaurus/
-
+ http://aiken.clan11.com/aiksaurus/
+
The two following programs should be available at configuration time:
o Perl (at least 5.002) is needed for the reLyX script. reLyX will
variable PERL is set to point to some program, this value will be
used, even if the program does no exist (this can be useful if
the machine on which LyX is built is not the one where it will
- run).
+ run).
o LaTeX2e should be correctly setup for the user you are logged in
as. Otherwise, LyX will not be able to run a number of tests. Note
Creating the Makefile
---------------------
-LyX can be configured using GNU autoconf utility which attempts to guess
-the configuration needed to suit your system. The standard way to use it
-is described in the file INSTALL.autoconf. In most cases you will be able
+LyX can be configured using GNU autoconf utility which attempts to guess
+the configuration needed to suit your system. The standard way to use it
+is described in the file INSTALL.autoconf. In most cases you will be able
to create the Makefile by typing
./configure
flags:
o --with-extra-lib=DIRECTORY that specifies the path where LyX will find
- extra libraries (Xpm, xforms) it needs. Defaults to NONE (i.e. search
+ extra libraries (Xpm, xforms) it needs. Defaults to NONE (i.e. search
in standard places). You can specify several directories, separated
by colons.
o --disable-optimization - you can use this to disable compiler
optimization of LyX. The compile may be much quicker with some
- compilers, but LyX will run more slowly.
-
+ compilers, but LyX will run more slowly.
+
o --enable-debug will add debug information to your binary. This
requires a lot more disk space, but is a must if you want to try to
debug problems in LyX. The default is to have debug information
LyX:
o --disable-nls suppresses all internationalization support,
- yielding a somewhat smaller code.
+ yielding a somewhat smaller code.
o --with-included-gettext forces the use of the included GNU gettext
library, although you might have another one installed.
care.
o You can also set the environment variable LINGUAS to a list of
- language in case ou do not want to install all the translation
+ language in case ou do not want to install all the translation
files. For example, if you are only interested in German and
Finnish, you can type (with sh or bash)
export LINGUAS='de fi'
o --prefix=DIRECTORY specifies the root directory to use for
installation. [defaults to /usr/local]
- o --datadir=DIRECTORY gives the directory where all extra LyX
+ o --datadir=DIRECTORY gives the directory where all extra LyX
files (lyxrc example, documentation, templates and layouts
- definitions) will be installed.
+ definitions) will be installed.
[defaults to ${prefix}/share/lyx${program_suffix}]
o --bindir=DIRECTORY gives the directory where the lyx binary
Note that the --with-extra-* commands are not really robust when it
comes to use of relative paths. If you really want to use a relative path
-here, you can prepend it with "`pwd`/".
+here, you can prepend it with "`pwd`/".
-If you do not like the default compile flags used (-g -O2 on gcc), you can
+If you do not like the default compile flags used (-g -O2 on gcc), you can
set CXXFLAGS variable to other values as follows:
o CXXFLAGS='-O2' (sh, bash)
o setenv CXXFLAGS '-O2' (csh, tcsh)
-Similarly, if you want to force the use of some specific compiler, you can
+Similarly, if you want to force the use of some specific compiler, you can
give a value to the CXX variable.
-If you encounter problems, please read the section 'Problems' at the end of
-this file.
+If you encounter problems, please read the section 'Problems' at the end of
+this file.
In particular, the following options could be useful in some desperate
cases:
o --enable-assertions that make the compiler generate run-time
code which checks that some variables have sane values. Opposite
is --disable-assertions. By default, this flag is on for
- development versions only.
+ development versions only.
o --without-latex-config that disables the automatic detection of your
latex configuration. This detection is automatically disabled if
latex cannot be found. If you find that you have to use this
- flag, please report it as a bug.
+ flag, please report it as a bug.
Compiling and installing LyX
o Compile LyX with the right compiler switches for your
architecture. Make sure you use the --without-latex-config switch
of configure, since others might not be interested by your
- configuration :-)
+ configuration :-)
o Create a file README.bin describing your distribution and
- referring to *you* if problems arise. As a model, you can use the
+ referring to *you* if problems arise. As a model, you can use the
file development/tools/README.bin.example, which can be a good
- starting point.
+ starting point.
o Type `make bindist'. This will create a file
- lyx-1.xx.yy-bin.tar.gz. Rename it to reflect you architecture
+ lyx-1.xx.yy-bin.tar.gz. Rename it to reflect you architecture
and the peculiarities of your build (e.g. static vs. dynamic).
- o Check that everything is correct by unpacking the distribution
- in some private place and running it. In particular, check the
+ o Check that everything is correct by unpacking the distribution
+ in some private place and running it. In particular, check the
output of `ldd lyx' to know which libraries are really needed.
o Upload your binary file to ftp.devel.lyx.org:/pub/incoming, and
- notify larsbj@lyx.org.
+ notify larsbj@lyx.org.
Problems
notify us.
o If you have problems indicating that configure cannot find a part of
- the xforms or Xpm library, use the --with-extra-lib and --with-extra-inc
- options of configure to specify where these libraries reside.
+ the xforms or Xpm library, use the --with-extra-lib and --with-extra-inc
+ options of configure to specify where these libraries reside.
o Configure will seemingly fail to find xpm.h and forms.h on linux
- if the kernel headers are not available. Two cases are possible:
+ if the kernel headers are not available. Two cases are possible:
- you have not installed the kernel sources. Then you should
install them or at least the kernel-headers package (or
- you have the sources, but you did a 'make mrproper' in the
kernel directory (this this removes some symbolic links that
are needed for compilation). A 'make symlinks' in linux kernel
- sources fixes that.
+ sources fixes that.
o if you are using RedHat Linux 7.x, you must make sure you have the
latest updated gcc and related packages installed (at least -85),
or LyX will not compile or will be mis-compiled.
-
+
o if you get an error message when compiling LyX that looks like this :
../../src/minibuffer.h:17: using directive `Object' introduced
cxx V6.2 will compile LyX out of the box.
cxx V6.3-020 is also known to work, although there is a bug in
/usr/include/cxx/deque that will break compilation in FormPreferences.C.
- Compaq are investigating, but a patch that works /now/ is:
+ Compaq are investigating, but a patch that works /now/ is:
--- /usr/include/cxx/deque_safe Mon Mar 4 21:09:50 2002
+++ /usr/include/cxx/deque Mon Mar 4 21:09:00 2002
As with the previous major version 1.2.0, many things make this new
release an exciting one. One of the major projects that has been going
on behind the scenes is the so-called GUI-independence project. We are
-glad to announce that version 1.3.0 shows the first results of this.
+glad to announce that version 1.3.0 shows the first results of this.
LyX now comes in two flavours: Qt-LyX and xforms-LyX!
Although this is the most visible change in version 1.3, this should not
version 1.0. This version has been released under the LGPL (Lesser
General Public License), and the availability of the source means that
many bugs that have been plaguing LyX have been fixed in xforms. You
-are advised to upgrade to xforms 1.0 to enjoy all these new fixes.
+are advised to upgrade to xforms 1.0 to enjoy all these new fixes.
In fact, LyX 1.3.0 no longer supports versions of xforms older than 0.89.5.
-In most cases the dialogs have been designed to make it impossible to input
-invalid parameters. The exception to this rule is the input of length data.
-Power LaTeX users can still input obtuse "glue lengths", but the widgets are
-highlighted in red if this input is invalid or incomplete. This visual
+In most cases the dialogs have been designed to make it impossible to input
+invalid parameters. The exception to this rule is the input of length data.
+Power LaTeX users can still input obtuse "glue lengths", but the widgets are
+highlighted in red if this input is invalid or incomplete. This visual
feedback makes it easy to see why LyX won't allow you to Apply your changes.
** Gnome frontend
** Instant preview
preview-latex is an emacs package for LaTeX that allows "instant previews"
-of LaTeX code, so you can immediately see the visual rendering of the
-LaTeX in the document. Its project home page can be found at
+of LaTeX code, so you can immediately see the visual rendering of the
+LaTeX in the document. Its project home page can be found at
http://sourceforge.net/projects/preview-latex. With the help of David
Kastrup, the author, LyX 1.3.0 can harness this functionality to
allow instant previews in the LyX window of math equations and
formula itself and revealing the names of the nesting levels in the
minibuffer. There is now native support for symbols from the wasy
package containing e.g. the zodiac symbols. New also is the internal
-structure of font changes which are now proper "insets", just like
+structure of font changes which are now proper "insets", just like
anything else from a square root to an array. This not only simplifies
the code greatly but also allows the same editing tricks as for the
"regular" math. However, it was not possible to tweak the visible
** Reading old files
LyX now has a new script lyx2lyx which enables the reading of any file
-produced by LyX versions as old as 0.12. Work is in progress on files
-created with LyX 0.10 (LyX 1.4 time-line) and still older files are
+produced by LyX versions as old as 0.12. Work is in progress on files
+created with LyX 0.10 (LyX 1.4 time-line) and still older files are
in the forge. Basically if lyx wrote it LyX will read it. :-)
There is also a strong demand to be able to read files produced by
equations if they are available (it is not necessary anymore to
configure your font server).
-- The Insert>Short Title allows the addition of an optional text
- for section headings and captions that is designed to be used in
+- The Insert>Short Title allows the addition of an optional text
+ for section headings and captions that is designed to be used in
tables of contents.
-- The Insert>Float>Floatflt Figure menu item restores the ability
+- The Insert>Float>Floatflt Figure menu item restores the ability
to wrap text around an image which was present in 1.1.6 and
removed in 1.2.0
** Updates
- it is now possible to build LyX with xforms 1.0rc4 (and probably 1.0
- when this gets released)
+ when this gets released)
- partial rewrite of the find & replace feature. This should solve most of
the performance problems
further developments. As of this version, we use (yet another) new
versioning scheme: next major version will be 1.3.0, and 1.2.x will
be just incremental fixes (like the `fix' series used to be for 1.1.5
-and 1.1.6).
+and 1.1.6).
This version sees the introduction of the so-called `new' insets,
which can contain arbitrary text. As a consequence, many new features
float-by-float
- Most problems with the new table inset of 1.1.6 have been addressed
- (memory consumption, file bloat, spell-checking, search and replace...).
+ (memory consumption, file bloat, spell-checking, search and replace...).
Better longtable header/footer support was implemented.
- TeX mode has been superseded by the ERT inset, which is foldable, or
Commands: xrightarrow, xleftarrow, substack, underset, dddot
over/under arrows (e.g. underleftarrow).
Environments: align, alignat, xalignat, xxalignat, multline, gather
- split, gathered, aligned, cases, subarray, pmatrix, bmatrix, vmatrix,
+ split, gathered, aligned, cases, subarray, pmatrix, bmatrix, vmatrix,
Vmatrix
- Preliminary support for xymatrix
- Improvements to math text mode
-- (Better) support for nested macros
+- (Better) support for nested macros
- Enable size changes to arrays after creation (add/delete rows/columns)
- New ligature break special character, useful for words like
"shelfful", or many german words
-- Support for parsing preamble when converting LaTeX files. Along
- with changes in the LaTeX production of alignment options, this
- improves round-trip work where you export a LyX document as
+- Support for parsing preamble when converting LaTeX files. Along
+ with changes in the LaTeX production of alignment options, this
+ improves round-trip work where you export a LyX document as
LaTeX, and later reimport it from LaTeX.
- Updated documentation
-- a few more document classes for journals: dtk, ltugboat, spie and
+- a few more document classes for journals: dtk, ltugboat, spie and
svprobth.
- Support for setting bookmarks and jumping to them
New features:
- documentation has been updated to remove errors due to interface
- change
+ change
- new italian user guide; updated french localisation of menus and
documentation; new dutch translations of some examples
- the `history' and `revert' functionalities have been implemented in CVS
- support
+ support
- it is now possible to enter directly characters in an encoding
different from latin1 (providing one is using a correct screen font)
- new encts class for Elsevier Science's Electronic Notes in
- Theoretical Computer Science
+ Theoretical Computer Science
- new cv class for writing curriculum vitae
working --with-lyx-suffix.
- in default cua bindings, change C-k from font-noun to
- line-delete-forward.
+ line-delete-forward.
- Add the prefix "key-" to the default keys for bibliography insets.
- new external material inset: this is a new kind of very powerful
inset which will allow LyX to interface intelligently with external
- applications. Among other good things, it will finally allow you to
+ applications. Among other good things, it will finally allow you to
include GIF, JPEG, TIF, PNG, or just about any other raster format
images in your document. It will even do an approximate ascii
rendering when you do Ascii export if you have gifscii installed.
rewritten. In particular, it is now possible to export to PDF, and to
import from HTML/MSWord. In fact it's now possible to add new import/export
formats without recompiling LyX by specifying external programs or scripts
- in lyxrc settings
+ in lyxrc settings
(note that the old import/export lyxrc settings no longer work).
- LyX can do command line exports without opening any GUI components.
docbook-book.
- PSpell library and Aspell spell checker support now included thanks
- largely to Kevin Atkinson (PSpell and Aspell maintainer).
+ largely to Kevin Atkinson (PSpell and Aspell maintainer).
And finally, there have been a lot of smaller changes, which are
mentioned here for your information
What's new in LyX version 1.1.5?
--------------------------------
-Lots of internal code rewritten, fixed, changed and added.
+Lots of internal code rewritten, fixed, changed and added.
We are using the C++ Standard Library more each day.
This will in most cases make the code clearer and easier to maintain
and expand.
paragraph-spacing (default,single,onehalf,double,other) [float]
- New visual feedback for environment depth of paragraphs (also the !
- in the margin for margin notes has been removed).
+ in the margin for margin notes has been removed).
- End-of-proof box, for layouts where it makes sense.
- new lyxrc variables: \show_banner [true|false] to remove the banner
screen, \backupdir_path to tell where the backup files created
- by lyx should be stored, and \override_x_deadkeys to tell whether
- lyx should provide its own accent keys handling (default is true).
+ by lyx should be stored, and \override_x_deadkeys to tell whether
+ lyx should provide its own accent keys handling (default is true).
What's new in LyX version 1.1.4?
More internals have been rethought. In particular, most of the file IO
routines of LyX have been rewritten to use real C++ streams. Many
changes have also been done to help compile LyX with Sun CC 5.0 and
-SGI STL 3.2.
+SGI STL 3.2.
In the user-visible department, we find:
- The first line of a .lyx file does not contain anymore the file
creator name and the date of creation; this was causing various
- problems.
+ problems.
- the -dbg command line switch is enhanced. For example, "-dbg lyxrc"
- works now.
+ works now.
- Slightly better handling of dependency tracking for bibtex files.
very similar to version 1.0.4, many things happened under the hood. As
a consequence of this: expect that some new bugs have crept in.
-User visible changes in lyx 1.1.1:
+User visible changes in lyx 1.1.1:
- New export to HTML feature
- Better multipart document support.
- LyX is now able to parse your BibTex files and show a list of
- entries.
+ entries.
- New broadway textclass (for plays).
- Support for literate programming with the 'noweb' program
-- New LaTeX document classe: APA
+- New LaTeX document classe: APA
version 0.12.0, it adds the following features:
- much improved reLyX script: many bugs have been fixed, new options
- have been added, many constructs are now correctly handled. reLyX is now
+ have been added, many constructs are now correctly handled. reLyX is now
installed along with LyX and has its own man page. Separate upgrades
of reLyX will be made available later. The reLyX script is utilized
by the File->Import LaTeX command in LyX.
Note that your existing global lyxrc file will not be overwritten by
default since now LyX only installs a file lyxrc.example to use as
-template.
+template.
In September of 1999 the LyX Team decided that we could no
longer successfully use the two strand development process
like the Linux kernel. The idea was to to switch to a
- development model similar to that used by Fetchmail where
+ development model similar to that used by Fetchmail where
we would make only small stable changes between releases
and release more often. This lead to the 1.1.x series of LyX
- releases during which the inhards of the program were rewritten
+ releases during which the inhards of the program were rewritten
to make use of the C++ Standard Library features, establish
the foundations of GUI/system independence, and generally
clean up the data structures used in the core of LyX.
As of April 2002, this transition phase is completed and we
- feel it is time to switch to (yet) another version scheme.
+ feel it is time to switch to (yet) another version scheme.
This new series will be in a state of continual advancement.
Note the word "advancement" and not "development." Development
will be occurring in branches of CVS and once the
LyX still uses a continuous numbering scheme in which odd or
even numbering is not significant. Instead a number '1.x.y'
- indicates stable release '1.x', fix level 'y'. Prereleases
+ indicates stable release '1.x', fix level 'y'. Prereleases
are labeled with a "pre" suffix. Thus there are three possible
file names:
lyx-1.2.0.tar.gz -- stable release
lyx-1.2.2.tar.gz -- second maintenance release of the
- 1.2.0 stable release
+ 1.2.0 stable release
lyx-1.2.0pre1.tar.gz -- potentially unstable test release
The maintenance releases are designed primarily to fix bugs. The
software.
You can read more about this concept in the documentation,
- which you'll find under the Help menu. If you plan to use LyX,
- you really should read about it to be able to make the best of
+ which you'll find under the Help menu. If you plan to use LyX,
+ you really should read about it to be able to make the best of
it.
What is LyX not?
LyX is not just another word processor that claims to be a
Desktop Publishing program. It's a more modern way of
- creating documents that look much nicer, but without wasting
- time with layout-fiddling. For these reasons you might need
+ creating documents that look much nicer, but without wasting
+ time with layout-fiddling. For these reasons you might need
little time to get used to the differences.
If you are looking for a free Desktop Publishing program for
Unix, you will be disappointed.
How do I upgrade from an earlier LyX version?
Read the file UPGRADING for info on this subject.
- If you are upgrading from version 0.12.0 or later, you don't
+ If you are upgrading from version 0.12.0 or later, you don't
need to do anything special.
What do I need to compile LyX from the source distribution?
list, or use the LyX bug tracker at http://bugzilla.lyx.org/.
Don't forget to mention which version you are having problems with!
-How can I participate in the development of LyX?
+How can I participate in the development of LyX?
Any help with the development of LyX is greatly appreciated--
after all LyX wouldn't be what it is today without the help
of volunteers. We need your help!
- If you want to work on LyX, you should contact the developer's
- mailing list for discussion on how to do your stuff. LyX is being
- cleaned up, and therefore it's important to follow some rules.
+ If you want to work on LyX, you should contact the developer's
+ mailing list for discussion on how to do your stuff. LyX is being
+ cleaned up, and therefore it's important to follow some rules.
Read about those rules in development/Code_rules/.
If you don't know C++, there are many other ways to contribute.
documentation or menus/error messages, or by writing a new keymap.
Write a new textclass. Work on reLyX (Perl). Find bugs (but please
read the list of known bugs first). Contribute money. Or just offer
- feature suggestions (but please read the online TODO list first).
+ feature suggestions (but please read the online TODO list first).
Thank you for trying LyX, and we appreciate your feedback in the mailing
lists.
modified by Arnd Hanses <Arnd.H.Hanses@rz.ruhr-uni-bochum.de>
##############################################################
-- This README.OS2 addresses experienced users of XFree86 and
- LyX on OS/2 and covers in very short form the steps for
+- This README.OS2 addresses experienced users of XFree86 and
+ LyX on OS/2 and covers in very short form the steps for
updating (installing) LyX.
- For general information on LyX please refer to the generic
README. For generic compiling instructions refer to INSTALL.
-- For a more detailed step by step guide on installing (or compiling)
- LyX and other related useful (or even necessary) optional programs
+- For a more detailed step by step guide on installing (or compiling)
+ LyX and other related useful (or even necessary) optional programs
on OS/2 please refer to INSTALL.OS2. If you are not already an
experienced user of LyX an OS/2 you are advised to read it.
-- For a description of the binary distribution and any necessary
+- For a description of the binary distribution and any necessary
support libraries please refer to README.bin, which comes with the
binary distribution.
LyX has been ported to OS/2 with XFree86 by Shigeru Miyata and
-has been installed and used successfully by many people.
+has been installed and used successfully by many people.
Unfortunately there is yet no easy to install and complete distribu-
tion of XFree86-related software for OS/2. Despite increasing popula-
-rity of X on OS/2, extensive printed documentation about XFree/2 and
-related programs like LyX is still not available. So you will
+rity of X on OS/2, extensive printed documentation about XFree/2 and
+related programs like LyX is still not available. So you will
have to study the available documentation (man pages, READMEs, faq,
-etc.) thoroughly to avoid unnecessary grief for you and for other
-people, trying to help you on the net. Nevertheless, there are
+etc.) thoroughly to avoid unnecessary grief for you and for other
+people, trying to help you on the net. Nevertheless, there are
existing tutorials and manuals covering X on UNIX family operating
-systems, which do contain some valuable information even for X on
-OS/2.
- [A hint as a starting point for users speaking German:
+systems, which do contain some valuable information even for X on
+OS/2.
+ [A hint as a starting point for users speaking German:
http://www.rrzn-uni-hannover.de/Umdrucke/WSC.5/WSC5_1.html].
-This release is considered to be stable for general use, but - like
+This release is considered to be stable for general use, but - like
any other piece of software - certainly is not bug free.
-So take the usual precautions like adopting a regular backup policy.
+So take the usual precautions like adopting a regular backup policy.
Standard disclaimers of non liability apply.
-As this is a voluntary project with a large number of contributions
-by many people, hints and bug fixes to the program and/or the
+As this is a voluntary project with a large number of contributions
+by many people, hints and bug fixes to the program and/or the
documentation are always appreciated and thoroughly considered. If
-you have the necessary skills (or want to take the chance to acquire
+you have the necessary skills (or want to take the chance to acquire
them) for programming in LaTeX or C++ you can become a LyX developer.
-You can support further development by making a donation, if you feel
+You can support further development by making a donation, if you feel
that LyX made your live a bit easier or you want to support open source
software.
Please refer to the links at www.lyx.org for details.
------------
0) Only for update: If you are upgrading from LyX v. 0.12.0,
- any old documentation files in %HOME%/.lyx/doc/ and
- %X11ROOT%/XFree86/lib/X11/lyx/doc should be removed before
- unpacking (since they are read only). You might wish to make
+ any old documentation files in %HOME%/.lyx/doc/ and
+ %X11ROOT%/XFree86/lib/X11/lyx/doc should be removed before
+ unpacking (since they are read only). You might wish to make
a backup, if you want to keep old docs.
-1) Unpack the archive at %X11ROOT%.
+1) Unpack the archive at %X11ROOT%.
2) Run lyx and let the program copy configuration files to
%HOME%\.lyx\.
-3) If you don't have %HOME%\.lyx\lyxrc then move
- %X11ROOT%\XFree86\lyxrc.example to %HOME%\.lyx\lyxrc.
+3) If you don't have %HOME%\.lyx\lyxrc then move
+ %X11ROOT%\XFree86\lyxrc.example to %HOME%\.lyx\lyxrc.
If updating, make a backup of old version, if you want.
- Read README and WHATSNEW about updating and run
+ Read README and WHATSNEW about updating and run
Options->Reconfigure as indicated.
-4) Verify if LYX is able to find the programs mentioned
- in %HOME%\.lyx\lyxrc and in %HOME%\.lyx\lyxrc.defaults; if not,
+4) Verify if LYX is able to find the programs mentioned
+ in %HOME%\.lyx\lyxrc and in %HOME%\.lyx\lyxrc.defaults; if not,
change name and path as required.
Note: Remember to repeat the check after any 'Reconfigure'!
-5) In config.sys SET LANG and LANGUAGE according to
+5) In config.sys SET LANG and LANGUAGE according to
your preferences. Beware: All programs supporting local
languages will be affected, e.g.:
* If you encounter apparently OS/2 specific bugs, (i.e. bugs not
already mentioned in the documentation or the buglist) you can report
- them to the XFree86/OS2 mailing list as well as to the LyX developer
- mailing list.
+ them to the XFree86/OS2 mailing list as well as to the LyX developer
+ mailing list.
-* For any questions on using LyX please subscribe to the the LyX user
+* For any questions on using LyX please subscribe to the the LyX user
mailing list.
- To subscribe to the XFree86 mailing list send mail to
* Hints:
-----
-1. To prevent 'file not found' with EmTeX and some non-US versions
+1. To prevent 'file not found' with EmTeX and some non-US versions
of Warp, I recommend:
- 1) In filenames use only A-Z, a-z, 1-9.
+ 1) In filenames use only A-Z, a-z, 1-9.
2) Use a recent LaTeX package inputenc.sty. Select
- Layout->Document->Encoding:latin1, so that LyX adds
+ Layout->Document->Encoding:latin1, so that LyX adds
the LaTeX command '\usepackage[latin1]{inputenc}'.
-2. LaTeX import occasionally produces buggy *.lyx files. LyX tries
+2. LaTeX import occasionally produces buggy *.lyx files. LyX tries
to save data in case of problems (and does a good job here),
but I recommend:
To import LaTeX close down and restart LyX (or close all
- documents, you are working on) and try the import, so that
- in case of any problems none of your existing documents will
+ documents, you are working on) and try the import, so that
+ in case of any problems none of your existing documents will
be affected.
3. Inline preview of inline images sometimes does not show the
- image: If you want to preview the image, just click on it and
- select fullscreen preview.
+ image: If you want to preview the image, just click on it and
+ select fullscreen preview.
4. Some XFree/2 programs (as ported from UNIX) expect a sh.exe
- in \bin directory: I recommend to install sh.exe of pdksh.zip
+ in \bin directory: I recommend to install sh.exe of pdksh.zip
in x:\bin (x: drive of %X11ROOT%). To work around problems you
- can try the commands
+ can try the commands
set EMXSHELL=x:\bin\sh.exe
- before starting the programs. As far as I know, LyX runs without
+ before starting the programs. As far as I know, LyX runs without
problems in this way.
2) Please check against the file list, if you did install all files of
the distribution.
-3) Remove all installed files and
- %.home%/.lyx/
- and perform a
- chkdsk /f
+3) Remove all installed files and
+ %.home%/.lyx/
+ and perform a
+ chkdsk /f
and a consistency check of your lyx binary package (unzip -tv
- foo.zip).
+ foo.zip).
4) Reinstall the complete package and check out if everything appears,
no truncated files, no crc errors, etc.
-5) Run
+5) Run
lyx -dbg 1026 >lyxerrors.log 2>&1
or, if you have tee.exe,
lyx -dbg 1026 2>&1|tee lyxerrors.log
- and watch out for any error messages. Report any remaining problems.
+ and watch out for any error messages. Report any remaining problems.
As this is a completely voluntary project, everybody involved will be
grateful for user efforts like detailed bug reports, suggestions,
- fixes, additions to the documentation, etc.
+ fixes, additions to the documentation, etc.
6) Have fun! (I'm sure).
C. Tips for Advanced Users:
-----------------------
-* You can start LyX automatically by adding
+* You can start LyX automatically by adding
'start/min/n xconsole.exe'
'set EMXSHELL=x:\bin\sh.exe'
'start/min/n lyx >/dev/console$ 2>&1'
- to xinitrc.cmd before the line that invokes the
- window manager, so that LyX' messages appear in the
+ to xinitrc.cmd before the line that invokes the
+ window manager, so that LyX' messages appear in the
console window and LyX appears in the pm-task list.
-* You can start LyX automatically by adding
+* You can start LyX automatically by adding
'detach xconsole.exe'
'detach lyx >/dev/console$ 2>&1'
- to xinitrc.cmd before the line that invokes the
- window manager, so that LyX' messages appear in the
+ to xinitrc.cmd before the line that invokes the
+ window manager, so that LyX' messages appear in the
console window and LyX does not appear in the PM task list.
The prerequisites are (obviously?):
-* cygwin installation (http://www.cygwin.com/).
+* cygwin installation (http://www.cygwin.com/).
* decent X server; eXceed, X-Win32, or maybe even Cygwin/XFree86.
* working TeX installation; fpTex, MikTex.
One of the perennial bug bears of LyX users in the past has been that
they have had to run Edit->Reconfigure when starting their new version
of the code for the first time. Strange and wonderful things would
-often result if they forgot to do this, so LyX 1.3.0 now runs
+often result if they forgot to do this, so LyX 1.3.0 now runs
Edit->Reconfigure automatically the first time the program is run.
If you have your own layout files, you may need to update them a little:
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).
-
+
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
sets system directory. Normally not needed.
.TP
.BI \-userdir " directory"
-sets user directory. Needed if you want to use LyX with different lyxrc
+sets user directory. Needed if you want to use LyX with different lyxrc
settings.
.TP
.BI \-dbg " feature[,feature...]"
specifies the server to connect to.
.TP
.BI \-bw " borderwidth"
-specifies the border width to use to built-in objects.
+specifies the border width to use to built-in objects.
.TP
.BI \-visual " visualName"
requests a visual by name such as TrueColor etc. By default the
.TP
.BI \-debug " level"
generates some info about the state of the
-.B XForms.
-where
+.B XForms.
+where
.I level
is an integer between 1-5 and controls the amount of
information to output. Depending on the options used
was built, a level more than 3 might not be available.
.TP
.B \-sync
-runs the application in synchronous mode with debug level set to 4.
+runs the application in synchronous mode with debug level set to 4.
.TP
.B \-private
requests a private colormap for the application.
.TP
.B \-name " newname"
specifies the application name under which resources are to be
-obtained, rather than the default executable file name.
+obtained, rather than the default executable file name.
.SH ENVIRONMENT
.TP
.B LYX_DIR_13x
.br
3) Maybe <path of binary>/TOP_SRCDIR/lib
.br
-4) <path of binary>/../share/<name of binary>/
+4) <path of binary>/../share/<name of binary>/
.br
5) hardcoded lyx_dir (usually /usr/local/share/lyx on UNIX and %X11ROOT%\\XFree86\\lib\\X11\\lyx on OS/2 with XFree)
.TP
.B LYX_USERDIR_13x
can be used to specify which user directory to use.
.PP
-The user directory is, in order of precedence:
+The user directory is, in order of precedence:
.br
1) -userdir command line parameter
.br
.nf
.ta \w'\fILIBDIR\fR/lyxrc.in 'u
~/.lyx/preferences Personal configuration file
-~/.lyx/lyxrc.defaults Personal autodetected configuration file
+~/.lyx/lyxrc.defaults Personal autodetected configuration file
\fILIBDIR\fR/lyxrc System wide configuration file
-\fILIBDIR\fR/lyxrc.defaults System wide autodetected configuration file
+\fILIBDIR\fR/lyxrc.defaults System wide autodetected configuration file
\fILIBDIR\fR/configure Updates \fBLyX\fR if config has changed
\fILIBDIR\fR/bind/ Keybindings
\fILIBDIR\fR/clipart/ Clipart pictures
projects / features.git / commitdiff