Hi all,
we use mediawiki + mwlib + mwlib.rl for our documentation; we have two
documentation servers running mwlib-0.12.13 + mwlib.rl-0.12.5 (on the
production system) and mwlib-0.12.14 + mwlib.rl-0.12.8 (on the testing
system).
A couple of questions:
- font-selection does not seem to work: defining two variables
"default_font" and "special_font" in pdfstyles.py and customconfig.py
has no visible effect, although the designated font is embedded in the
resulting .pdf file.Furthermore, even overwriting the
"sans_font"/"serif_font" variables in both files also does not seem to
have any effect, the resulting .pdf still embeds "AAAAAA+FreeSerif"
and "AAAAAA+FreeSerifBold". How can I get other fonts to be used per
default for text?
- it would be nice to be able to use <para>...</para> commands in an
wiki-article to have somewhat more control over the creation of the
pdf if those could be escaped in mwlib and sent to platypus;
apparently, here the '<' and '>' chars get replaced by mwlib, however,
this does not happen for e.g. <br> tags. Is this possible?
- on the production system, {{command|...}} and {{filename|...}} are
displayed similarly to <tt>...</tt> in the online-article, and when
exported to pdf they also employ a monospaced font, but on the testing
system these to tags are apparently translated to <code>...</code>
tags - and these won't get a monospace font in a pdf created on the
testing system! (Whereas something in <tt>...</tt> tags will.) I
suspect this might also be due to differing mediawiki-versions, but
shouldn't the text between <code>...</code> tags use a monospace font
in the pdf?
Best regards,
Stefan Birkholz
--
You received this message because you are subscribed to the Google Groups
"mwlib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mwlib?hl=en.
