Re: [Fonts]Problems with Xft and pcf/bdf fonts...
> Please check the FT_Bitmap_Size structure. It has two components, the > size in the X direction and the size in the Y direction. > > You should walk the available_bitmaps array of the FT_Face structure > and make sure that the size you requested is available. I believe > that doing that should be under the responsibility of fontconfig. In this particular to that 6x13 fonts, I have: num_fixed_sizes = 1 available_sizes->height = 13 available_sizes->width = 13 Does this sound right at all? You've mentioned fontconfig. Should I be using that to make life easier (cos I'm not using that lib for the moment)? Pigeon. ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]ttmkfdir and mkfontscale again
On Thursday 14 November 2002 13:10, Juliusz Chroboczek wrote: > GC> While I am talking about these two programs, I do prefer the way > GC> ttmkfdir creates its output better than mkfontscale -- mkfontscale > GC> creates the font.scale file in the directory it is scanning > GC> whereas ttmkfdir outputs to stdout which can be redirected via the > GC> -o (--output) command line parameter. > > Mkfontscale can do multiple directories in a single run, so you'll > have to specify the exact behaviour that you want. It is not clear to me which way is better (or worse). Given that mkfontscale can handle multiple directories with one invokation, I would not lean toward your current approach. -- -- Gene ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]Xft2 without Xrender
Around 21 o'clock on Nov 14, Fred RISS wrote: > - Is the compilation of Xrender from fcpackage required/beneficial > with X servers not providing Xrender ? Xft always links to the Xrender library and it exposes some Xrender datatypes, so it's not possible to build Xft without Xrender. But, it's not helping you in any real way. Of course, if you run applications over the network to machines with Render, it will suddenly help quite a lot. > - Is there a way to get rid of the warning dumped by applications > about the mising render extension ? Yes. Xft now silently checks and caches the availability of Render to avoid annoying you. Keith PackardXFree86 Core TeamHP Cambridge Research Lab ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
[Fonts]Xft2 without Xrender
Hello, I hope to post those questions on the good list. I want to use fcpackage to get AA on a Solaris 8 box (with Gtk2.1 or Qt3.1). Of course the X server doesn't support Xrender. I compiled fontconfig and Xft from the package, but not Xrender. I can see antialiased fonts, so everything seems to be fine. Now here are my questions : - Is the compilation of Xrender from fcpackage required/beneficial with X servers not providing Xrender ? - Is there a way to get rid of the warning dumped by applications about the mising render extension ? Thanks in advance, -- Fred RISS <[EMAIL PROTECTED]> ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]ttmkfdir and mkfontscale again
Around 19 o'clock on Nov 14, Juliusz Chroboczek wrote: > > Would that be of any use to mkfontscale? > Quite likely. Could you please point me at the code? The language orthographies can be found in xc/lib/fontconfig/fc-lang. You may actually want to consider rewriting mkfontscale as a Fontconfig application instead of having it use FreeType2 directly; fontconfig vets glyphs in each font for non-emptiness which plagues many downloadable faces. Keith PackardXFree86 Core TeamHP Cambridge Research Lab ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]ttmkfdir and mkfontscale again
KP> Fontconfig uses a precise scheme to measure language coverage; it has KP> required characters for languages including Korean, Chinese (Big5, GB18030 KP> and Big5+HKS) and Japanese. Would that be of any use to mkfontscale? Quite likely. Could you please point me at the code? Juliusz ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]ttmkfdir and mkfontscale again
Around 19 o'clock on Nov 14, Juliusz Chroboczek wrote: > For large fonts, deciding which characters are important is beyond my > competence, so I implemented a scheme similar to the one in ttmkfdir, > which is controlled by the -f (fuzz) flag to mkfontscale. Fontconfig uses a precise scheme to measure language coverage; it has required characters for languages including Korean, Chinese (Big5, GB18030 and Big5+HKS) and Japanese. Would that be of any use to mkfontscale? Keith PackardXFree86 Core TeamHP Cambridge Research Lab ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]Problems with Xft and pcf/bdf fonts...
>> Worse than that. The pixel size must match in both the X and the Y >> direction. (FreeType and, to a certain extent, X11 support non-square >> pixels). P> Hmm so what exactly I can try in this particular case? Please check the FT_Bitmap_Size structure. It has two components, the size in the X direction and the size in the Y direction. You should walk the available_bitmaps array of the FT_Face structure and make sure that the size you requested is available. I believe that doing that should be under the responsibility of fontconfig. There is a lot of confusion about what these dimensions mean, so let me explain. With every font is associated an arbitrary dimension known as a quad. When you request an eight-point instance of a font, you request the font to be scaled so that one quad is eight points. A bitmap strike in TTF (and hence in FreeType) is described by the size of the em in units of one pixel. If pixels are square, that's well defined. If pixels are non-square, the value depends on whether you use the width or the height of pixels to measure; hence the two values in FT's FT_Bitmap_Size. The thing to know is that a strike designed for square pixels has the same X- and Y- sizes. The other thing to know is that the BDF driver in current FreeType releases is buggy in assigning the size 8 by 13 to the X11 font called ``8x13''. And I hate Macintosh keyboards. Juliusz ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]ttmkfdir and mkfontscale again
GC> Now ttmkfdir has a -m (--max-missing) command line parameter which is GC> described as "max # of missing characters per encoding, default is 5". Mkfontscale has two distinct ways of operating, one for eight-bit encodings, one for large encodings. For eight-bit encodings, mkfontscale decides which characters are important, and will only generate entries for fonts that cover all the important characters. There's a specific notion of what is important for KOI fonts, a different one for other fonts. For example, both mkfontscale and ttmkfdir will consider that a font with no non-breaking space covers Latin 1, but for very different reasons: mkfontscale considers nbsp to be unimportant, while ttmkfdir merely notices that fewer than 5 characters are missing. They will give different results for a font missing capital A: ttmkfdir will accept it, while mkfontscale will reject it on the grounds that A is too important to live without. For large fonts, deciding which characters are important is beyond my competence, so I implemented a scheme similar to the one in ttmkfdir, which is controlled by the -f (fuzz) flag to mkfontscale. I hope the above makes sense. If you have any particular examples where it yields bad results, please inform me. GC> While I am talking about these two programs, I do prefer the way GC> ttmkfdir creates its output better than mkfontscale -- mkfontscale GC> creates the font.scale file in the directory it is scanning GC> whereas ttmkfdir outputs to stdout which can be redirected via the GC> -o (--output) command line parameter. Mkfontscale can do multiple directories in a single run, so you'll have to specify the exact behaviour that you want. Juliusz ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]ttf files
On Thursday 14 November 2002 10:35, Keith Packard wrote: > Current fc-list sources will print the file name when requested. The > filename has to be printed separately as the regular font name printing > code explicitly excludes it as that code is generally used to write out > cache files which don't want the file name in that format. > > $ fc-list 'Nimbus Mono L' family style file Thank you. With this description I now understand what is going on. -- -- Gene ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
[Fonts]ttmkfdir and mkfontscale again
I am using Red Hat 8.0 so the program version are with respect to those distributed by Red Hat. I have been playing with ttmkfdir and mkfontscale and the Microsoft webfonts and I noticed some differences. If I run mkfontscale against a directory with the webfonts, I get 411 fonts listed. However, if I run ttmkfdir, I get 398 fonts listed. Now ttmkfdir has a -m (--max-missing) command line parameter which is described as "max # of missing characters per encoding, default is 5". If I run "-m 0", I get 323 fonts listed and with "-m 100" I get 466 fonts listed. I am not sure what is correct, good, bad, or what. Any comments? If "max-missing" is a good idea, should it be incorporated into mkfontscale? Obviously (at least to me), mkfontscale must be doing some allowance for missing characters since it lists a number of fonts greater than 323. While I am talking about these two programs, I do prefer the way ttmkfdir creates its output better than mkfontscale -- mkfontscale creates the font.scale file in the directory it is scanning whereas ttmkfdir outputs to stdout which can be redirected via the -o (--output) command line parameter. -- -- Gene Czarcinski ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]ttf files
Around 10 o'clock on Nov 14, "Gene C." wrote: > Looking at the source code for fc-list, it appears that the file name should > print but it never does. Current fc-list sources will print the file name when requested. The filename has to be printed separately as the regular font name printing code explicitly excludes it as that code is generally used to write out cache files which don't want the file name in that format. $ fc-list 'Nimbus Mono L' family style file /usr/share/fonts/type1/gsfonts/n022003l.pfb: Nimbus Mono L:style=Regular /usr/share/fonts/type1/gsfonts/n022023l.pfb: Nimbus Mono L:style=Regular Oblique /usr/X11R6/lib/X11/fonts/Type1/n022004l.pfb: Nimbus Mono L:style=Bold /usr/X11R6/lib/X11/fonts/Type1/n022023l.pfb: Nimbus Mono L:style=Regular Oblique /usr/X11R6/lib/X11/fonts/Type1/n022024l.pfb: Nimbus Mono L:style=Bold Oblique /usr/X11R6/lib/X11/fonts/Type1/n022003l.pfb: Nimbus Mono L:style=Regular /usr/share/fonts/type1/gsfonts/n022004l.pfb: Nimbus Mono L:style=Bold /usr/share/fonts/type1/gsfonts/n022024l.pfb: Nimbus Mono L:style=Bold Oblique Keith PackardXFree86 Core TeamHP Cambridge Research Lab ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
[Fonts]ttf files
Is there some way to find out what files are associated with what fonts? Looking at the source code for fc-list, it appears that the file name should print but it never does. -- Gene Czarcinski ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
