On 10-05-2020 20:43, Paul Vinkenoog wrote:
Mark Rotteveel wrote:
[PDF]:
Be aware that some tables are currently a bit mangled (both in spacing,
and in some cases having wrong number of columns), which might make this
look worse than normal. I'll see if I can clean it up, but that might be
better done as a cleanup step after migration.
I also see it in simple, straightfoward tables without spans etc., e.g. tables
34-36 and in paragraph 7.5.2 (DML Triggers) under 'Trigger options'.
That last one is not a formal table btw. I hope this is not how a description
list is rendered?
For table 34 (and 35 and 36) the primary difference is that it is
currently rendered at 100% width (for HTML, with PDF that is also the
case in the old documentation), and with wrong column proportions (1,1)
instead of (1,3). The proportions I will fix, and I'll look at options
for the width (eg %autowidth, or I might change it to a description list).
As for the table in 7.5.2, it is an informaltable in docbook. Asciidoc
doesn't really distinguish between table and informaltable, except by
the exact properties specified on them (for asciidoc, the distinguishing
property between a table and informaltable is the presence or absence of
a title). For the asciidoc version, the problem is that the width is now
100% (in HTML), which I need to disable.
However the rendering of this table is very similar in the old and new
PDF docs, while in the new HTML it has striping, which it doesn't have
in the old HTML.
This looks like something I will need to manually fix after conversion,
because I'm not sure if I can properly automate that. In fact, the
current rendering of informaltable in our old docs is likely a property
of our stylesheets.
Same for unnecessary parentheses
around language elements in tables.
Do you have a specific example of this last thing, so I know what I
should look for?
Same 'table' under 'Trigger options', but also a similar one under 7.5.3,
'Database Triggers'.
Right, now I understand what you mean.
Also, in these examples the text isn't vertically aligned on the baseline.
The stuff within parentheses floats higher - not because of the parentheses
I assume, but because of the different font.
Interesting, it might have to do with the parentheses though. In most
monospace fonts, the parentheses dip below the baseline, but it looks
like in the PDF the bottom of the parentheses is used as the baseline,
so the text is elevated. I'm not sure if that is something I can fix, it
might be a bug in asciidoctor-pdf. I'll check what happens with a
different font or if I remove the parentheses.
Mark
--
Mark Rotteveel
_______________________________________________
Firebird-docs mailing list
Firebird-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-docs
