GNOME Bugzilla – Bug 118138
balsa: DEFAULT_PRINT_BODY_FONT is in invalid Type1 font instead of TrueType.
Last modified: 2021-06-01 22:42:37 UTC
Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=202579 Submitter: Michael Piefel <piefel@debian.org> Summary: As a GNOME application, Balsa should use the GNOME fonts instead of asking for specific ones. My comments: Why aren't Type1 fonts available for printing? "Courier Regular 10", the default body font cannot be found by Balsa on Debian GNU/Linux systems even though it is avaiable to all other Pango-using applications.
One short initial comment: libgnomeprint did not use same fonts names as pango last time I checked.
I did some testing basically to confirm that valid Pango font names like "Sans 10" are invalid libgnomeprint fontnames. I am tempted to re-file this as gnomeprint-pango integration problem unless suggested otherwise.
Is this still the same in 2.4.x?
tested with gnome2.4, seems like the pango alias don't show up in gnomeprint in balsa.
Now that Debian has moved onto GNOME 2.8 and beyond and Balsa 2.3 seems to functioning perfectly with Pango aliases, I'm closing this bug.
Doh! I was looking at the wrong dialog. i.e. display fonts instead of printing fonts. src/balsa-app.h has: #define DEFAULT_PRINT_BODY_FONT "Courier Regular 11" which leaves us with the exact same problem as before. Balsa with a Type1 default when gnomeprint can only use TrueType fonts. The dialog is also missing Pango aliases such as "Monotype" and "Sans" which would make very sane defaults compared to what we have now.
Thanks--cvs now uses only Monospace and Sans (I also took out Helvetica as the subject font--I haven't tried it, but mixing faces like that must look pretty bad!).
Hey Peter, I'm not sure if simply substituting the printing fonts with "Sans" and "Monospace" will work. Even in 2.3.3-1 the font selection box for (Print Message -> Fonts) didn't list Pango aliases. Has that been fixed yet, or is there a deeper problem within gnomeprintui?
Balsa uses GnomeFontDialog to change fonts, and the API includes no method for controlling the list of fonts, afaict. A quick glance at gnome_font_family_list() suggests that it explicitly excludes aliases, but perhaps there's a way to get them included. Printing is such a mystery...
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/balsa/-/issues/ Thank you for your understanding and your help.