>>>>> "WH" == Waldek Hebisch <de...@fricas.org> writes:
WH> I understand that some applications want custom fonts. But simple
WH> application like HyperDoc should be able to work with system
WH> fonts, we are not in font business.
i cettainly never suggested custom fonts.
axiom from its initial floss release defaulted to fonts ibm x servers
supported due to ibm licensing adobe's t1 fonts.
floss distributions only eber had a small, fixed number of bitmap
strikes of those fonts. and the sizes axiom specified were not amoung
those available to users of xfree86 (and later xorg) servers.
thus hyperdoc was entirely unreadable.
one had to come up with values for each of:
Axiom.hyperdoc.RmFont
Axiom.hyperdoc.TtFont
Axiom.hyperdoc.ActiveFont
Axiom.hyperdoc.AxiomFont
Axiom.hyperdoc.EmphasizeFont
Axiom.hyperdoc.BoldFont
which were listed in the output of xlsfonts(1) on one's server to be able
to read any of the hyperdoc output.
when the xserver has to scale bitmap strikes the output is crap.
as i recall, xorg dropped support for type1 and ttf fonts some time ago.
they certainly do not show up in xlsfonts(1)'s output on this xserver.
so if fricas still defaults to the faces ibm used to specify, hyperdoc
will be unreadable without local customization until it switches to
client-side fonts.
so until that occurs (not demanding that or anything!) the default fonts
should be chosen from what xlsfonts(1) reports, which means not only the
face's name but also the pointsize.
-JimC
--
James Cloos <cl...@jhcloos.com>
OpenPGP: https://jhcloos.com/0x997A9F17ED7DAEA6.asc
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to fricas-devel+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/fricas-devel/m3sejuzj24.fsf%40lugabout.jhcloos.org.
