Private message by Michal Hoftich (tex4ht head developer):
oolatex is not recommended way to use Tex4ht for the ODT conversion.
It is better to use
make4ht -f odt mwe.tex
make4ht fixes some issues in ODT files
This is candidate for stable.
FontEncoding L7x required for hyphenation but no longer set
by Babel (since 2017-12-06).
The PostBabelPreamble now sets L7x for Lithuanian, if it is defined
and restores the previous font encodng on exit.
This has been done by reading the LaTeX sources (classes.dtx) to try
to get things right
* fix font sizes of chapters and parts. Note that the labels have
smaller size as the title itself.
* fix alignment of Part and put label on top
* add spacing between label and title.
Runs the compare via the command line, and then compares the output to the
expected result. Required adding a script to do the comparison, so that
the timestamps on changes in the lyx file are ignored.
Export to all formats seems to work well after removing the "ps2pdf"
option to the hyperref package.
Accordingly we uninvert the tests for the other formats. All ctests
pass on an updated TeX Live 2020.
More generally, ensures that paragraphs in abstracts do not have something else configured.
A major problem in making the layout more useful is that article titles are not supposed to be in TOC.
The hook that defines the "lastslide" label is interfered with for
some reason on an updated TeX Live 2020. We thus avoid referencing
the label and instead show only the current slide number on each
slide. We leave instructions in the preamble for how to get back the
previous behavior if desired.
We currently specify that dvips be used. This could potentially
change in the future. One issue is that with system fonts XeTeX and
LuaTeX do not correctly rotate pages.
This is only relevant on linux/unix if running the scripts from a shell.
These two were the last where the call still used an unversioned python.
This has no reflex on the way that lyx calls the scripts or the python
version used since the #! "shebang line" is ignored.
Compilation of our Seminar example file fails on updated TL20. The
maintainer of "Seminar" is not planning to fix the core issue and
states the following (in a private email with permission to quote):
it is a problem with the new hook management of the current latex.ltx
seminar is a quite old package and there is no reason to use it with a
new LaTeX format. It won't be fixed, so the usual way is to use the
package latexrealease to get the old hook management.
This commit adds a note to the example files explaining the
workaround of exporting to a .tex file and prepending the following
line:
\RequirePackage[2020-02-02]{latexrelease}
We now invert the relevant tests.
For elements that should behave like sections (for now, mostly prefaces).
A second paragraph of PartBacktext can only wreak havok: it should start a section, and nothing else (otherwise, it's a real nightmare to implement).
In cooperation with Thibaut Cuvelier:
lib/scripts/spreadsheet_to_docbook.py: Strip the document header and convert some flags
lib/xtemplates/gnumeric.xtemplate: use this output to be inserted in docbook5
lib/configure.py: Add needed conversion entries
Preparation to test docbook5 exports
'xhtml_table': Format used for inserting spreadsheet tables in docbook
'pdf9': Result format used by conversion docbook5 with pandoc to create a pdf
This is a minimal implementation, as DocBook lacks a serious way of encoding all of this. Maybe a <formalpara> could do the trick, but I'd need to find a way to shoehorn a title through the styles (i.e. a first complete tag):
Theorem: Bla bla
<formalpara>
<title>Theorem</title>
<para>Bla bla</para>
</formalpara>
This would also only be a solution for single-paragraph things, as formalpara only allows one paragraph. Or a sidebar, but it's semantically very remote.
Includes: semantic markup (sorry about noun: Additional.lyx uses it to mark menus; there is something better in DocBook, but it looks like the LaTeX equivalent is really for person names), boxes, info layouts.
Actually output something when list item is empty. XMLStream discarded the sequence StartTag/EndTag (nothing in between).
New-line behaviour around term in description lists.
That's mostly generating DocBook tags at an inappropriate place with some metadata, rather than outputting whatever you have at your disposal. Far from satisfying, but good enough for a generic tool (see details in the new TODO). Doesn't trigger assertions. Is valid XML.
Before, it directly wrote to the XMLStream, but it made implementation of new lines tricky. Now, it returns the XML for each sub-paragraph (delimited by new lines) as a string, so that the caller can adopt a more precise behaviour (such as in lists).
Set fonts to DejaVu to avoid the following error:
! Package polyglossia Error: The current latin font does not
contain the "Cyrillic" script!
This choice of font is consistent with the Russian intro and
tutorial manuals.
When the fonts distributed with texlive with same family name
as ours are also managed by fontconfig, Qt is not able to
discriminate ours by the style only. In order to be sure Qt
will load our fonts, we change the foundry name from 'PfEd'
to 'LyEd' and augment the font family name with this foundry
name. This only works on *nix, because adding a foundry name
seemingly breaks things on Windows. However, this is a *nix
only problem, seemingly.
