mirror of
https://git.lyx.org/repos/lyx.git
synced 2024-11-25 10:58:52 +00:00
2a7deb802a
This fixes bug #9615. The "notermination" flag tells LyX, that terminating an LICR macro with {} is not necessary. This is normally the case for all macros with non-alphabetical name (e.g. \{). However, combining diacritical characters are converted to *accent macros*, which expect an argument (the base character). In Unicode, the base character precedes the combining character, in LaTeX the combining character precedes the base character. LyX changes the order of the two characters to get this right, e.g. "x" + "combining tilde" becomes "\~{x}". In the special case there is no preceding character (e.g. at the start of the document or a paragraph), Unicode shows the combining diacritical character without base character. The replacement is currently not "terminated" (e.g. "\~"), because of the "notermination=text" flags in "unicodesymbols". The accent macros take the *following* character as base character, which is clearly not intended. In case of a paragraph consisting of just one combining diacritical character, LaTeX compilation fails with an error. With the patch, LyX writes the accent macros with an empty argument, e.g. "\~{}", the output is similar to the view in the GUI with the diacritical character on its own, not on the follwoing character. |
||
---|---|---|
.. | ||
bind | ||
commands | ||
doc | ||
examples | ||
fonts | ||
images | ||
kbd | ||
layouts | ||
lyx2lyx | ||
scripts | ||
templates | ||
tex | ||
ui | ||
.gitignore | ||
appdata.xml | ||
autocorrect | ||
build-listerrors | ||
chkconfig.ltx | ||
configure.py | ||
CREDITS | ||
encodings | ||
external_templates | ||
generate_contributions.py | ||
languages | ||
latexfonts | ||
layouttranslations | ||
layouttranslations.review | ||
lyx.desktop.in | ||
Makefile.am | ||
RELEASE-NOTES | ||
symbols | ||
syntax.default | ||
unicodesymbols |