Since we process layouts sequentially, we export LaTeX code for the
title once we arrive to a layout that has InTitle false. If the
document then later has a layout with InTitle true, we do not
(currently) go back to add it to the title and just output it
in-place. We previously warned with LYXERR0, but since this can
cause missing or unexpected output we now warn in the GUI.
For more information, see the following lyx-devel thread:
https://www.mail-archive.com/search?l=mid&q=a65ae226-d3bd-8fc5-a93b-7bb23f1cda82%40lyx.org
(cherry picked from commit 0b1cf1330d850b21313f5e68a83bb5053e52e6ec)
The name of the layout is now included in an error message about
layouts. This will help with finding the root issue of several
documents we have.
(cherry picked from commit c949268da7a56368cf848199f37659c218a57808)
On Windows, runCommand has never returned the exit code of the
spawned process but the result of correctly closing the input handle.
Fixes#10327
(cherry picked from commit fb46b3a1ee642b66b9712c6f376f543c47a2695e)
There was an oddity in the manual that exposed a problem with the
test for the "special case" of an inset all by itself in a pargraph.
If a font change is applied to that inset, we still need to open the
paragraph.
(cherry picked from commit 3be23d18b64d1409d14e0c1c95f4192e9a23e543)
care of much of what we need to do for RTL languages. It does not
take care of inline language changes, probably.
(cherry picked from commit 07dcb1c525435c6f22de4314ba31150c53502429)
As of this commit, this is ineffective, since no changes have been
made to external_templates.
(cherry picked from commit daf7cd4c05f55c7eb957df7076ec91dcd2eca543)
The second argument here is the length of the string to replace,
not the position of the final character.
(cherry picked from commit 6b97f2c0751ff79fc19ea0e11b4ef957fd71324c)
dealing properly with the paragraph separator tag.
We really need to use that tag as a kind of general marker for which
tags we're responsible for in a given paragraph and which tags we are
not. So the changes to InsetText.cpp use the tag as that kind of marker.
Note that, as of this commit, the User Guide again exports without any
kind of error. I haven't yet checked the other manuals.
This fixes bug #8022.
(cherry picked from commit 31e25c8ec695f864bec3679c3e11495e3011a0e2)
In redoParagraph, this should be done before coping with the insets,
other wise some graphic gliches may occur. This is a better fix for
Fixes bug #10163.
(cherry picked from commit 71374b38c26585dc060e923452f2dd873ef00f15)
Moreover enforce better the lower limit of 10 and avoid overflow due
to unsigned int.
Fixes bug #10212.
(cherry picked from commit 8884c4044d7c1d29526aca7b0be1734231c89207)
was not English: We return the the abbreviated author "One and Two",
but translated to the GUI language; then we search that for " and "
in order to pull the authors apart again.
I've just replaced the distinct routines with a single one that handles
both cases, depending upon whether a Buffer is provided as one argument.
(cherry picked from commit fb84ccd9fb8fbe1eeb764580964a333acb2e6c0d)
Add a new checkbox "Save transient properties" to the "Output" panel in the
document properties dialog (now renamed as "Format").
This provides the front-end for the change at 5c2d04999.
(cherry picked from commit 5d292fce2dfdcdb0951f43fd023db4b20e0ed76c)
XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740)
and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts.
However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's
encoding of the LaTeX file:
keep this also for "XeTeX with TeX fonts".
The user is responsible to ensure all characters can be processed and are
correctly shown in the output. The provided test sample shows the problems
with this encoding without special measures (like loading fontspec in the
user-preamble or a document class).
(cherry picked from commit b170b6e40fe38e79e97c049e7b727d75bd23ed52
I just converted the test to format 508. Thanks Scott for running the
tests. -Guillaume)
be called when we do not have a cloned Buffer, namely, if we do not
have EXPORT_in_THREAD defined.
(cherry picked from commit d8aab4af9e6e72c835f78ba54a46687b870c25fa)
A window manager could be configured such that to maintain a certain
stack order for the windows. It would be annoying that opening a new
file through menu brings up the window, so do this only if we are
loading a file through the lyx-server.
This commit amends f5f8c6fd, so no status line is needed.
This is the well known file locking problem: The TempFile class keeps the
created file locked for the own process, and this prevents the CAS to read it.
