Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3877 - Please reenable fontconfig support for bitmap fonts!

Attached to Project: Arch Linux
Opened by name withheld (Gullible Jones) - Wednesday, 01 February 2006, 01:10 GMT
Last edited by Judd Vinet (judd) - Monday, 06 February 2006, 19:31 GMT
Task Type Feature Request
Category Packages: Current
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Yes, I know xorg-fonts-100dpi and xorg-fonts-75dpi are ugly as hell, but not all bitmap fonts are, and some of us actually *like* to use bitmap fonts. Disabling bitmap fonts prevents Artwiz fonts from being displayed, which is quite vexxing for users of those fonts... Also, it should be noted that the new fontconfig package comes with *no* clear documentation concerning how to enable bitmap fonts. If you're going to pull things like this, it would be nice if you'd provide a note about how to undo them, rather than pointing to a tiny readme file which contains no relevent information.

Sorry if I come across as rude, but I would much prefer it if you guys would think a bit about the potential annoying consequences of minor changes like this before implementing them.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 10 February 2006, 22:27 GMT
Reason for closing:  Won't fix
Additional comments about closing:  I've gotten replies from many users stating "hey my fonts look good for the first time in my whole life using linux".
If you want to use bitmap fonts, follow the postinstall description or go read the wiki about it. Once you update the symlink, postinstall won't touch it ever again.
Comment by name withheld (Gullible Jones) - Wednesday, 01 February 2006, 02:48 GMT
Hmm, on second thought enabling bitmap fonts is not hard if you bother to look in the directory containing the readme... Still, I rather fail to see the necessity of this change.
Comment by Torsten Evers (Nightwulf) - Wednesday, 01 February 2006, 10:41 GMT
I second that. There is a post_install() message but it's very annoying that configs are changed based on the personal taste of the packager. If you think it should be disabled at least backup the config even better ask the user wether he wants all or only non-bitmap fonts. build() is a bash function and post_install()/upgrade() too...so just ask the user!

I was in luck to have the old package stored in /var/cache/pacman/pkg
Please remember that there are people out there *working* with their machines and especially when using only current/extra one wouldn't expect that kind of changes. Less experienced users would not have been able to fix that in a reasonable amount of time.


Comment by Jan de Groot (JGC) - Wednesday, 01 February 2006, 11:10 GMT
The bitmap fontsetting is made in /etc/fonts/conf.d/10no-bitmaps.conf. This is a symlink, when you delete it, fontconfig will use bitmap fonts again.
I will change the behaviour of the package to place the symlink by default, but when 10bitmaps.conf is symlinked, it won't touch it.
Comment by Judd Vinet (judd) - Monday, 06 February 2006, 19:31 GMT
Re-opened by Gullible Jones:

Bitmap fonts are still automatically disabled by default. Why not just have a post-install message telling the user how to disable them if they want to? Once a user creates the symlink, it's not going to disappear...

Loading...