Hi,
it seems that it is no longer possible to keep the trunk and the 1.5.X
branch in sync :-( Therefore, I quickly browsed through all commits to
the trunk in order to identify potential patches for the stable branch.
AFAICS there are several huge patches that do not qualify for 1.5.X
simply due to their size and complexity. Below please find a list of
smaller patches that might be considered.
http://www.lyx.org/trac/changeset/19331 - Deal with a UI bug
http://www.lyx.org/trac/changeset/19332 - Make LYX_ALIGN_LAYOUT always
be an available layout
http://www.lyx.org/trac/changeset/19398 - Update to latest from boost
1.34.x branch
http://www.lyx.org/trac/changeset/19409 - Get rid of a few warnings
http://www.lyx.org/trac/changeset/19415 - UserGuide.lyx - add a BibTeX
bibliography
http://www.lyx.org/trac/changeset/19472 - fix crash after assertion when
using %s with integer arguments
http://www.lyx.org/trac/changeset/19473 - more verbose message
http://www.lyx.org/trac/changeset/19513 - QLPainter::text():use a pixmap
cache for word drawing
http://www.lyx.org/trac/changeset/19616 - disable pixmap cache under X11
http://www.lyx.org/trac/changeset/19552 - fix MSVC warning
http://www.lyx.org/trac/changeset/19609 - Fix color of \Omega.
http://www.lyx.org/trac/changeset/19644 - Fix bug 4117
http://www.lyx.org/trac/changeset/19645 - rev 19644: I forgot this
http://www.lyx.org/trac/changeset/19631 - small optimisation: avoid a
Font copy
http://www.lyx.org/trac/changeset/19632 - cosmetic (MG: To me, it
doesn't look like cosmetics)
http://www.lyx.org/trac/changeset/19633 - leftMargin, rightMargin,
labelsep, labelindent, parindent are now docstring
http://www.lyx.org/trac/changeset/19638 - redoParagraph() simplify the
changed calculation
http://www.lyx.org/trac/changeset/19643 - Fix bug 4123
Regarding documentation, I noticed several differences between trunk and
branch, too. IMHO we should only work on the stable branch for the
moment. At a later stage in development, we can copy the documentation
back to trunk. We should also follow this strategy for the po files (as
we have done in the past).
Best regards,
Michael
