I know that many projects don't want to consider that fonts should be included, however, when you include a specific set of fonts and install them as a part of the build/installation process, you are giving a bit of polish to your application.
Likewise, making it easy for the user to specify specific fonts applicable to them also shows polish on your part. If you leave it up to some possible set of standard fonts that you expect to already exist then people who may have been interested can and do walk away as they can often think that your application is not worth the effort. Something to consider. On Fri, 20 Jun 2025, 1:04 am Waldek Hebisch, <de...@fricas.org> wrote: > On Thu, Jun 19, 2025 at 01:23:55AM -0400, James Cloos wrote: > > btw, speaking of hyperdoc, > > > > have the default fonts ever been updated to ones available in recent > > distributions? > > > > the original probably were fine on an ibm box, but were never okon an > > xfree or xorg box. > > I do not think that we changed anything in font setting. In the past > I have looked at available fonts and they seem to differ quite a lot > between systems. AFAICS the best thing that we can do in general > (as opposed to customised user settings) is to pick default system > font. And IIUC current configuration is more or less doing this. > It is possible that we could do better to respect default system > choices, but we should make fonts less (and no more) specific. > > > i currently have: > > > > FriCAS.hyperdoc.RmFont: > -bitstream-charter-medium-r-normal--*-120-*-*-p-*-iso8859-1 > > FriCAS.hyperdoc.TtFont: > -b&h-lucidatypewriter-medium-r-normal-sans-*-120-*-*-m-*-iso8859-1 > > FriCAS.hyperdoc.ActiveFont: > -bitstream-charter-bold-r-normal--*-120-*-*-p-*-iso8859-1 > > FriCAS.hyperdoc.FriCASFont: > -bitstream-charter-bold-i-normal--*-120-*-*-p-*-iso8859-1 > > FriCAS.hyperdoc.EmphasizeFont: > -bitstream-charter-medium-i-normal--*-120-*-*-p-*-iso8859-1 > > FriCAS.hyperdoc.BoldFont: > -bitstream-charter-bold-r-normal--*-120-*-*-p-*-iso8859-1 > > > > on this laptop. and used this on my workstation before it died: > > > > ! FriCAS.hyperdoc.RmFont: > -b&h-lucidabright-medium-r-normal--20-*-*-*-p-*-iso8859-1 > > ! FriCAS.hyperdoc.TtFont: > -b&h-lucidatypewriter-medium-r-normal-sans-20-*-*-*-m-*-iso8859-1 > > ! FriCAS.hyperdoc.ActiveFont: > -b&h-lucidatypewriter-bold-r-normal-sans-20-*-*-*-m-*-iso8859-1 > > ! FriCAS.hyperdoc.FriCASFont: > -b&h-lucidatypewriter-bold-r-normal-sans-[20 0 2 20]-*-*-*-m-*-iso8859-1 > > ! FriCAS.hyperdoc.EmphasizeFont: > -b&h-lucidatypewriter-medium-r-normal-sans-[20 0 2 20]-*-*-*-m-*-iso8859-1 > > ! FriCAS.hyperdoc.BoldFont: > -b&h-lucidatypewriter-bold-r-normal-sans-20-*-*-*-m-*-iso8859-1 > > > > not as good as client-side fonts would look, of course, > > but at least readable. > > > > (I don't recall why i used [20 0 2 20] rather than 20. > > that bit of slant must have had some meaning....) > > > > In any case, using faces which are directly available as bfd or pcf and > > thus do not require scaling by the X server is vital to readability. > > AFAIK current X font are mostly scalable, so scaling should be > non-critical. > > > client-side font support would be better, but using unscaled server-side > > fonts gets the job done. defaulting to widely installed faces is > therefore > > important. > > I understand that some applications want custom fonts. But simple > application like HyperDoc should be able to work with system > fonts, we are not in font business. > > -- > Waldek Hebisch > > -- > 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/aFQnED_pH5oqBgDI%40fricas.org > . > -- 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/CAEnaMTEAjOtFzcTEu42Ou2RaCEJVpL8zryoz4d%3DPGzosr-SC7A%40mail.gmail.com.
