Now layout files and modules can extend the cite engines or completely
overwrite them, and modify the cite formats.
Any CiteEngine definition in a layout/module will completely overwrite
those by cite engine files.
AddToCiteEngine will extend them (add if they do not exist yet).
Any CiteFormat definition in a layout will be preferred to those in cite
engines. CiteFormat definitions that are not touched by the former are
still active, though (so, as opposed to CiteEngine, a CiteFormat does
not completely overwrite those by the engine files).
Layout format change.
"Benutzerdefiniert" means "user defined", which is not what "custom"
means here (custom insets/text styles are usually not user defined,
but provided by a class/module).
Combining accent charactrs were not supported at the time the Russian
documentation was written. Eventual display problems with some GUI
fonts are still less distracting than ERT.
A Note inset contained two example files. The linguistics example
file caused terminal messages like
step: Counter does not exist: examplei
An alternative to removing the example file would be to add the
module, but it is not clear we want example files in the merged
file anyway.
Otherwise utf8 inputenc chokes.
It is also possible to enter those accented chars directly, but this
results in display problems in the workarea (the line is shifted downwards).
Following a request by Günter, we consider the document fonts (only rm
for now) when selecting an appropriate font encoding.
See #9741
The new default font encoding setting "auto" does
* consider the font encoding needed by the language(s), which can now
have fallback alternatives
* Consider which font encoding is provided by the document font
Thus, cm now will result in OT1 fontenc, if the language can deal with
that.
The font_enc pref is ditched: it is no longer needed.
The automatism is still very basic and is subject to extension.
File format and prefs format change.
This allows (some) verbatim contents in macros, such as \url's with
specific chars (#, % etc.) in section headings or footnotes (#449)
or comments in captions (#9313).
The mentioned two bugs are fixed by this commit.
Note that the implementation is still rather basic and might need
extension for other cases.
This is mandatory for some features (such as bookmarks,pdfusetitle)
to work, and only a handful of drivers can be auto-detected by hyperref.
Fixes: #6418
- new file
- it is just a start and put into git to assure that we keep a compilable version
- Hatim will bit by bit translate it
- can be removed if it should not be ready before the next major release
In Spanish and French, dashes around parenthetical statements
are treated similar to brackets: line breaks are not allowed
on the inner side. Use of "breakable" dashes risks accidential
line breaks after the "opening" dash.
(Ligature dashes allow line breaks even if a no-break space follows.)
Change markup to use semantic markup instead of hard-coded
typewriter for code examples containing --.
Works around false positive warning on changed dashes
leading to lyx2lyx export ctest failures.
Remove warnings for issues fixed in lyx2lyx.
Update the GUI name of the ligature-dash Option.
Fix example for preventing unwanted line break in French.
lyx2lyx erroneousely merged -- to en dash in text with logical
markup "code".
Revealed by recent (but now silenced) ctest fails.
Also add space around en dash in examples.
This is complementary to AutoNests: Styles can determine which other
style should auto-nest them. This is particularly useful for modules
that add new styles which should be auto-nested in a given context.
Now layouts can specify other layouts that should be nested in and
after the current one (if the layout is switched from the current one
and if it follows a paragraph in the current one).
This is particularly useful for things such as the beamer frames, where
particular layouts are practically always nested.
