When pasting "\big" without any following delimiter, avoid
processing the same token again and again. For unknown reasons,
the delim docstring turns out to always be not empty: even when
it simply contains a '0' (no delimiter follows), its length is 1.
Fixes bug #11027.
(cherry picked from commit 8e8b3f610495493f4f1bff3f4a0ff48f4eab4539)
Several problems:
* The regex failed at names such as 1_text_2_text.tex
(returned "2_text.tex)
* The regex failed at names such as 12_text.tex
(returned "2_text.tex)
* Masters with digits in the name (2018_text.tex) were
tracked as their own children
(cherry picked from commit 398e026250f6d7d1687bdf04a8a27a61946d088f)
Do not attempt to load, nor allow to set, a different engine in this
case.
Fixes: #11022
(cherry picked from commit 2f6ada6644614df5f402efc7cbc1d27911b45376)
The number of paragraphs can change here, so pit() can become invalid.
Fixes: #9983
(cherry picked from commit 6e4e0869006aa4c225162164aaa14a70d041facf)
When we switched from r'...' to b'...', this required strings used
as input to re.compile to be double-escaped. It's not an issue with
"\s", because "\s" has no special meaning in a string.
Also, printing in binary mode did not output a line ending.
(cherry picked from commit 6b5a7116cd6697d1121a5ffb76d54102a8e265ba)
breakRow should only produce an empty row when there is nothing left
in the paragraph.
Fixes bug #10996.
(cherry picked from commit 253b935f65759ba15b6af02117f8316e2aaf676e)
At some time it seemed like a good idea in breakRow() to return early
when the row was bound to be empty. It turns out that this creates two
symptoms:
* empty paragraphs will not have an end of paragraph marker
* since row width is not correctly computed in this case, caret ghosts
can appear in master.
This commit removes the oprimization and replace the do {} while()
construct to a straightforward while() {}.
Related to bug #10952.
(cherry picked from commit 76f0a3dd4ee5c7958c6dea79628ef8c2ac2c59bd)
The former need to be translated to the buffer language, the latter to
the GUI language.
Fixes: #10946
(cherry picked from commit 5db4d712ef660273c1c12f211fdb4adf5a792ec3)
This is currently only relevant fo InsetListings, which falls back to
a fixed-width encoding under specific conditions. It is now possible
to query the inset about that and report the correct encoding in
DocIterator::getEncoding.
Addresses the second part of #10995
(cherry picked from commit f924ef29660af5afd22b96744a3e0bb128e1a58d)