Mirror of Lyx repo
Go to file
José Matox fb475b55ed Release 1.4.5.1
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_4_X@19218 a592a061-630c-0410-9148-cb99ea01b6c8
2007-07-26 10:53:29 +00:00
boost boost works perfectly with gcc 4.1 2006-12-19 06:33:29 +00:00
config * configure.ac: add LYX_DATE variable for release date. 2006-08-16 21:57:14 +00:00
development include unicodesymbols 2007-07-25 22:43:45 +00:00
intl Was forgetting this. 2006-11-24 06:11:11 +00:00
lib Prepare for 1.4.5.1 2007-07-25 23:00:22 +00:00
m4 Delete all .cvsignore files from trunk 2006-02-10 22:09:45 +00:00
po Italian update 2007-04-05 10:50:20 +00:00
sourcedoc Delete all .cvsignore files from trunk 2006-02-10 22:09:45 +00:00
src 2007-07-12 André Pönitz <poenitz@lyx.org> 2007-07-12 14:17:22 +00:00
ABOUT-NLS Whitespace, nothing but whitespace. 2004-10-26 21:16:44 +00:00
ANNOUNCE Prepare for 1.4.5.1 2007-07-25 23:00:22 +00:00
autogen.sh automake 2.10 works (backport from 1.5) 2007-07-24 16:38:41 +00:00
ChangeLog Hopefully last update in this branch 2007-07-25 10:58:15 +00:00
ChangeLog.1 Whitespace, nothing but whitespace. 2004-10-26 21:16:44 +00:00
configure.ac Release 1.4.5.1 2007-07-26 10:53:29 +00:00
COPYING update FSF address 2006-11-13 14:19:08 +00:00
INSTALL Change python requirement to 2.2 2006-09-21 12:07:09 +00:00
INSTALL.autoconf update files 2003-02-06 20:21:11 +00:00
INSTALL.MacOSX update from Bennett 2007-03-15 15:35:31 +00:00
INSTALL.OS2 drop reLyX like it is hot, and setup to use tex2lyx instead (and remerged po files + no.po small update) 2005-07-16 15:18:14 +00:00
INSTALL.scons Scons: backport some 1.5.x scons features, fix qt translation 2006-12-30 20:12:24 +00:00
INSTALL.Win32 * Custom NSIS plug-ins will be included in the dependency packages 2006-11-06 21:48:00 +00:00
lyx.man fix hyphens in man pages 2006-07-06 14:26:07 +00:00
Makefile.am Distribute README.Cygwin and some source files of boost/regex 2006-09-22 14:33:07 +00:00
NEWS Prepare for 1.4.5.1 2007-07-25 23:00:22 +00:00
OLD-CHANGES Whitespace, nothing but whitespace. 2004-10-26 21:16:44 +00:00
README Change python requirement to 2.2 2006-09-21 12:07:09 +00:00
README.Cygwin Scons: produce cygwin-compatible binary package 2006-09-08 01:51:57 +00:00
README.OS2 Whitespace, nothing but whitespace. 2004-10-26 21:16:44 +00:00
README.Win32 updated information about LyX for Windows 2006-10-29 16:05:08 +00:00
RELEASE-NOTES remove outdated "status" file 2007-04-23 09:23:44 +00:00
status.14x 2007-07-12 André Pönitz <poenitz@lyx.org> 2007-07-12 14:17:22 +00:00
UPGRADING Document that python 2.2.0 is required. 2006-10-05 13:09:10 +00:00

What is LyX?

    LyX is a document processor that encourages an approach to
    writing based on the structure of your documents, not their
    appearance. It is released under a Free Software / Open Source
    license.

    LyX is for people that write and want their writing to look great,
    right out of the box. No more endless tinkering with formatting
    details, 'finger painting' font attributes or futzing around with
    page boundaries. You just write. In the background, Prof. Knuth's
    legendary TeX typesetting engine makes you look good.

    On screen, LyX looks like any word processor; its printed output
    -- or richly cross-referenced PDF, just as readily produced --
    looks like nothing else. Gone are the days of industrially bland
    .docs, all looking similarly not-quite-right, yet coming out
    unpredictably different on different printer drivers. Gone are the
    crashes 'eating' your dissertation the evening before going to
    press.

    LyX is stable and fully featured. It is a multi-platform, fully
    internationalized application running natively on Unix/Linux and
    the Macintosh and modern Windows platforms.

What do I need to run LyX?

    Either of :
    * a Unix-like system (including Windows with cygwin)
    * Windows 98 or newer  
    * Mac OS 10.2 or newer  

    A decent LaTeX2e installation (e.g. teTeX for unix) not older
       than 1995/12/01.
    Python 2.2 or later

How does the LyX version scheme work?

    LyX 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
    are labeled with a "pre" suffix. Thus there are three possible
    file names:

       lyx-1.4.0.tar.gz       -- stable release
       lyx-1.4.5.tar.gz       -- fifth maintenance release of the
                                 1.4 stable release
       lyx-1.4.0pre1.tar.gz   -- potentially unstable test release

    The maintenance releases are designed primarily to fix bugs. The
    goal here is not to have parallel development as for the linux
    kernel (the team is too small to afford that), but rather to
    include all the simple (so that the maintenance burden on us
    is not too high) and safe (so that system administrators can
    install them without fear) bug fixes.  Experience shows that
    these releases will contain a few new features, and that the
    bulk of the patches will be documentation updates.

    If you get the source from Subversion, the version string will
    look like one of:

       1.4.1svn     -- this is the stable branch on which maintenance
               release 1.4.1 will eventually be tagged.
       1.5.0svn     -- this is the main branch on which stable
               release 1.5.0 will eventually be tagged.

What's new?

    Read NEWS.

How do I upgrade from an earlier LyX version?

    Read the file UPGRADING for info on this subject.

What do I need to compile LyX from the source distribution?

    * A good C++ compiler.  Development is being done mainly with
      gcc/g++, but some others work also. As of LyX 1.4.0, you need at
      least gcc 3.x.

    Either:
    * The Xforms library, version 1.0.
    * LibXpm, version 4.7 or newer.

    Or:
    * The Qt library, version 3.0 or newer (although version 2.3
    may work).

    Read the file "INSTALL" for more information on compiling.

Okay, I've installed LyX. What now?

    Once you've installed it, and everything looks fine, go read
    the "Introduction" item under the Help menu.  You should follow
    the instructions there, which tell you to read (or at least skim)
    the Tutorial. After that, you should also read "Help>LaTeX
    configuration" which provides info on your LaTeX configuration
    as LyX sees it.  You might be missing a package or two that you'd
    like to have.

    User-level configuration is possible via the Tools>Preferences menu.

Does LyX have support for non-English speakers/writers/readers?

    Yes. LyX supports writing in many languages, including
    right-to-left languages like Arabic or Hebrew. There is a port
    of LyX named CJK-LyX which adds support for Chinese, Korean
    and Japanese (http://cellular.phys.pusan.ac.kr/cjk.html)

    Menus and error messages have been translated to 17 languages.
    For the status of the different translations, see
    http://www.lyx.org/devel/i18n.php

    Keymaps can ease typing in many languages.

Internet resources of relevance to LyX

    The LyX homepage contains valuable information about LyX and the
    various LyX mailing lists, as well as links to mirrors and other
    LyX homepages around the world:
    http://www.lyx.org/

    The LyX Wiki is the place where users can share information on
    setting up and using LyX.
    http://wiki.lyx.org/

    The main LyX archive site:
    ftp://ftp.lyx.org/pub/lyx/

    The LyX Development page has information about the development
    effort. LyX is under Subversion control, so you can get the very
    latest sources from there at any time.
    http://www.lyx.org/devel
    ftp://ftp.devel.lyx.org/pub/lyx/

How do I submit a bug report?

    If possible, read the Introduction found under the Help menu in LyX.
    You'll find detailed info on submitting bug reports there.

    If you can't do that, send details to the LyX Developers' mailing
    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?

    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.
    Read about those rules in development/Code_rules/.

    If you don't know C++, there are many other ways to
    contribute. Write documentation. Help to internationalize LyX
    by translating documentation or menus/error messages, or by
    writing a new keymap. Write a new textclass. 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).

Thank you for trying LyX. We appreciate your feedback in the mailing
lists.

The LyX Team.