Fontconfig - Nov 2005 - Including/excluding fonts from the configuration

I came across the same problem. Keith said, "Looks like that
font is missing the ''ENCODING'' property". I opened it and
saved it with xmbdfed, and then fontconfig was able to see
it.

Noah

On Fri, Apr 18, 2003 at 22:45:08 +0200, Marcin ''Qrczak''
Kowalczyk wrote:
> On Friday 18 of April 2003 19:36, Keith Packard wrote:
> 
> > Now that FreeType handles .pcf.gz fonts, fontconfig users are about to
see
> > a dramatic increase in the number of (ugly) bitmap fonts available.
> 
> For me it''s much more important to make it see bitmap fonts that
it currently
> doesn''t see. For example
> unifont.pcf.gz -gnu-unifont-medium-r-normal--16-160-75-75-c-80-iso10646-1
> fc-cache just skips this font and many others.
> 
> -- 
>    __("<         Marcin Kowalczyk
>    \__/       qrczak@knm.org.pl
>     ^^     http://qrnik.knm.org.pl/~qrczak/
> 
> 
> _______________________________________________
> Fontconfig mailing list
> Fontconfig@fontconfig.org
> http://mail.fontconfig.org/mailman/listinfo/fontconfig

On Friday 18 of April 2003 19:36, Keith Packard wrote:
> Now that FreeType handles .pcf.gz fonts, fontconfig users are about to see
> a dramatic increase in the number of (ugly) bitmap fonts available.
For me it''s much more important to make it see bitmap fonts that it
currently
doesn''t see. For example
unifont.pcf.gz -gnu-unifont-medium-r-normal--16-160-75-75-c-80-iso10646-1
fc-cache just skips this font and many others.

-- 
   __("<         Marcin Kowalczyk
   \__/       qrczak@knm.org.pl
    ^^     http://qrnik.knm.org.pl/~qrczak/

On Friday 18 of April 2003 22:52, Noah Levitt wrote:
> I came across the same problem. Keith said, "Looks like that
> font is missing the ''ENCODING'' property". I opened
it and
> saved it with xmbdfed, and then fontconfig was able to see
> it.
Thanks. But since mkfontdir somehow generates a correct entry with iso10646-1 
encoding for such fonts, couldn''t fontconfig be fixed to accept them as
well?

-- 
   __("<         Marcin Kowalczyk
   \__/       qrczak@knm.org.pl
    ^^     http://qrnik.knm.org.pl/~qrczak/

Now that FreeType handles .pcf.gz fonts, fontconfig users are about to see 
a dramatic increase in the number of (ugly) bitmap fonts available.

Fontconfig 2.2 "works around" this by excluding the X bitmap font 
directories from the default configuration (users can explicitly add them 
back in if desired).

For fontconfig 2.3, I''ve considered several possible mechanisms to
allow
users to edit the set of available fonts, and I''ve implemented one of
them
which is designed to be efficient, rather than completely general:

	<selectfont>
		<acceptfont>
			<glob>/usr/X11R6/lib/X11/fonts/misc*</glob>
		</acceptfont>
		<rejectfont>
			<glob>*.pcf*</glob>
		</rejectfont>
	</selectfont>

File and directory names are matched against all of the
''acceptfont'' globs
and the ''rejectfont'' globs.  Those in
''rejectfont'' but not ''acceptfont''
are not added to the configuration; they will not be available for selection 
or listing.  A rejected directory excludes any fonts in that or inferior 
directories.

Globbing ignores ''.'' and ''/'' for matching
purposes; matching is done on
the complete path name.

This example includes all of the fonts from the ''misc''
directory but
excludes all other .pcf fonts (compresed or not).

I made the <acceptfont> syntax general enough so we could add additional 
kinds of matching (perhaps based on font patterns) if desired.

To get some testing of this functionality, I''m planning on releasing a 
2.2.90 (2.3 rc0) at approximately the same time as 2.2.0.

-keith