mirror of
https://git.lyx.org/repos/lyx.git
synced 2024-11-09 18:31:04 +00:00
Update documentation for 1.6.0 release (referring to rc3 where it makes sense)
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@26546 a592a061-630c-0410-9148-cb99ea01b6c8
This commit is contained in:
parent
f3a1cdabe9
commit
478bf0cf60
14
ANNOUNCE
14
ANNOUNCE
@ -1,9 +1,9 @@
|
||||
Public release of LyX version 1.6.0 (release candidate 2)
|
||||
Public release of LyX version 1.6.0 (release candidate 3)
|
||||
=========================================================
|
||||
|
||||
We are pleased to announce the first release candidate of LyX 1.6.0.
|
||||
We are pleased to announce the third release candidate of LyX 1.6.0.
|
||||
|
||||
LyX 1.6.0 will be the culmination of 12 months of hard work since the
|
||||
LyX 1.6.0 will be the culmination of 14 months of hard work since the
|
||||
release of the LyX 1.5 series. We sincerely hope you will enjoy the
|
||||
result.
|
||||
|
||||
@ -43,11 +43,11 @@ http://www.lyx.org/ has to say on the subject:
|
||||
internationalized application running natively on Unix/Linux and the
|
||||
Macintosh and modern Windows platforms.
|
||||
|
||||
You can download LyX 1.6.0rc2 here (the .bz2 are compressed with bzip2,
|
||||
You can download LyX 1.6.0rc3 here (the .bz2 are compressed with bzip2,
|
||||
which yields smaller files):
|
||||
|
||||
ftp://ftp.devel.lyx.org/pub/lyx/devel/lyx-1.6.0rc2.tar.gz
|
||||
ftp://ftp.devel.lyx.org/pub/lyx/devel/lyx-1.6.0rc2.tar.bz2
|
||||
ftp://ftp.devel.lyx.org/pub/lyx/devel/lyx-1.6.0rc3.tar.gz
|
||||
ftp://ftp.devel.lyx.org/pub/lyx/devel/lyx-1.6.0rc3.tar.bz2
|
||||
|
||||
Note that due to the amount of change, no patch is provided to upgrade
|
||||
from version 1.5.6.
|
||||
@ -56,7 +56,7 @@ Prebuilt binaries (rpms for linux distributions, Mac OS X and Windows
|
||||
installers) should soon be available at
|
||||
ftp://ftp.devel.lyx.org/pub/lyx/devel/
|
||||
|
||||
If you find what you think is a bug in LyX 1.6.0rc2, you may either
|
||||
If you find what you think is a bug in LyX 1.6.0rc3, you may either
|
||||
e-mail the LyX developers' mailing list (lyx-devel at lists.lyx.org), or open
|
||||
a bug report at http://bugzilla.lyx.org
|
||||
|
||||
|
2
NEWS
2
NEWS
@ -1,4 +1,4 @@
|
||||
What's new in version 1.6.0rc2?
|
||||
What's new in version 1.6.0?
|
||||
-------------------------------
|
||||
|
||||
The new features in LyX 1.6 are detailed in
|
||||
|
67
UPGRADING
67
UPGRADING
@ -1,7 +1,16 @@
|
||||
How do I upgrade my existing LyX system to version 1.6.x?
|
||||
---------------------------------------------------------
|
||||
|
||||
* Upgrading from LyX 1.4.x and earlier:
|
||||
* Upgrading from LyX 1.5.x:
|
||||
|
||||
The format of preference and session files has changed. LyX 1.6.x is
|
||||
able to read old files but will save them in the new format.
|
||||
|
||||
The format of layout files has changed but, as before,
|
||||
layout2layout.py will convert older versions to the new format
|
||||
automatically.
|
||||
|
||||
* Upgrading from LyX 1.4.x:
|
||||
|
||||
The biggest change in 1.5 is the switch to Unicode. Please refer to
|
||||
the section "Document transfer" below for some things you might take
|
||||
@ -73,7 +82,7 @@ have to update them
|
||||
Build requirements
|
||||
------------------
|
||||
|
||||
LyX 1.5 uses the Qt 4.x toolkit (version 4.1.1 or newer). Contrary to
|
||||
LyX 1.6 uses the Qt 4.x toolkit (version 4.2.0 or newer). Contrary to
|
||||
previous versions of LyX, it won't build against Qt 2.x or 3.x.
|
||||
Furthermore, the XForms frontend was dropped.
|
||||
|
||||
@ -89,28 +98,28 @@ Document transfer
|
||||
|
||||
* Compatibility with older documents/layouts
|
||||
|
||||
LyX 1.5.x uses an external python script, lyx2lyx, to import documents
|
||||
LyX 1.6.x uses an external python script, lyx2lyx, to import documents
|
||||
written using previous versions of LyX. All versions of LyX as far back as
|
||||
0.12 are supported, so any klyx users still holding out for an alternative
|
||||
0.10 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 (at least version 2.3)
|
||||
installed in order to use LyX 1.5.x with your old documents.
|
||||
Of course, this means that you must have python (at least version 2.3.4)
|
||||
installed in order to use LyX 1.6.x with your old documents.
|
||||
|
||||
lyx2lyx also has the framework in place to be able to convert documents
|
||||
to an earlier format (which requires python 2.3.4 at least). However,
|
||||
these converters have only been written for the conversion from 1.5.x
|
||||
to 1.4.x and 1.3.x, so versions of LyX older than 1.3.0 will NOT be able
|
||||
to read documents saved with LyX 1.5.x. The conversion from 1.5.x to
|
||||
1.4.x/1.3.x is lossless as long as no new features are used. lyx2lyx
|
||||
tries hard to find something equivalent for new features such as boxes,
|
||||
but this is known to fail sometimes. LyX 1.4.5.1 contains an updated
|
||||
lyx2lyx that can read documents in 1.5.x format. LyX 1.5.x can also
|
||||
export to 1.4.x format for document transfer to older 1.4.x releases.
|
||||
lyx2lyx also has the framework in place to be able to convert
|
||||
documents to an earlier format (which requires python 2.3.4 at
|
||||
least). However, these converters have only been written for the
|
||||
conversion from 1.6.x to 1.5.x, 1.4.x and 1.3.x, so versions of LyX
|
||||
older than 1.3.0 will NOT be able to read documents saved with LyX
|
||||
1.6.x. The conversion from 1.6.x to 1.5.x-1.3.x is lossless as long as
|
||||
no new features are used. lyx2lyx tries hard to find something
|
||||
equivalent for new features such as boxes, but this is known to fail
|
||||
sometimes. LyX 1.5.7 contains an updated lyx2lyx that can read
|
||||
documents in 1.6.x format.
|
||||
|
||||
Furthermore, LyX uses a converter layout2layout.py, also written in python
|
||||
that will convert old layout files on the fly. You can also call it manually
|
||||
on your layout files if you want to convert them to 1.5.x format permanently.
|
||||
on your layout files if you want to convert them to 1.6.x format permanently.
|
||||
|
||||
* Preparing for Unicode:
|
||||
|
||||
@ -138,17 +147,19 @@ transition as smooth as possible for you. However, there are some caveats:
|
||||
|
||||
- Inset encodings and Conversion from earlier LyX versions
|
||||
|
||||
As part of the transition to unicode, lyx2lyx (the scripts used for converting
|
||||
back and forth between different versions of the lyx files) converts old .lyx
|
||||
files, which may use a number of different encodings, to UTF-8. This conversion
|
||||
depends on correctly identifying the language of the text. There were previously
|
||||
some edge-cases (insets embedded in different-language text type scenarios) in
|
||||
which the language was incorrectly identified, which caused some text to
|
||||
appear incorrectly after having upgraded from older versions. This has now been
|
||||
fixed. Unfortunately, however, the fix cannot be applied to files which have
|
||||
already been converted past format 249. So if you have already converted
|
||||
your old files (using a development version or release candidate), this fix
|
||||
won't help, unless you still have the originals lying around (and haven't
|
||||
As part of the transition to unicode, lyx2lyx (the scripts used for
|
||||
converting back and forth between different versions of the lyx
|
||||
files) converts old .lyx files, which may use a number of different
|
||||
encodings, to UTF-8. This conversion depends on correctly
|
||||
identifying the language of the text. There were previously some
|
||||
edge-cases (insets embedded in different-language text type
|
||||
scenarios) in which the language was incorrectly identified, which
|
||||
caused some text to appear incorrectly after having upgraded from
|
||||
older versions. This has now been fixed. Unfortunately, however, the
|
||||
fix cannot be applied to files which have already been converted
|
||||
past format 249. So if you have already converted your old files
|
||||
(using a development version or release candidate), this fix won't
|
||||
help, unless you still have the originals lying around (and haven't
|
||||
yet made too many changes to the newer versions ;) ).
|
||||
|
||||
Generally, it is probably wise to keep a backup of the old version of your
|
||||
|
Loading…
Reference in New Issue
Block a user