![]() ![]() scaling takes time, especially if several parameters are used.limited sizes by points and pixel sizes.several different files for a single font.In other words fontconfig is an attempt of configuring all the font types above in a manner that can exploit the attributes that the distinct fonts have with a common syntax. FontConfigĪnd fontconfig needs to deal with all the discrepancies of the above. And XFT parameters can be configured in your Xresources. Several other attributes, like hinting or hintstyle, were added to define attributes of these fonts.Īll that can be found in subfolders of /usr/share/fonts. Moreover XFT allows scaling of the old bitmap fonts to look like Type1 fonts. XFT not only allows the usage of Type1 and FreeType fonts but it also other formats: OTF by Adobe and Microsoft, TTF by Apple. And it created the XFT (well X FreeType is an interface to FreeType which is a GPL/BSD library that mimics and extends Type1). Vector based fonts are scaled and do not require several files. antialias, embolden, dpi, or size (not necessarily point based this time). Vector fonts are configured with several configuration values, e.g. Postscript (and TeX to some extent) created Type 1 fonts which are vector based fonts. The bitmap fonts already introduce the concept of font family. The bitmap fonts have different files for different pixel sizes of the font. Using xfontsel you can configure a Xorg string to define the points, spacing, pixel size, terminal weight (bold, slant), encoding, among others of the font. There have been other formats of binary fonts but I need to admit that I never needed to use any other format than PCF for binary fonts. Today these can be found in /usr/share/fonts/misc, the PCF (portable compiled format) is used for pretty much all of them today. Original UNIX fonts were simply bitmap fonts. The Arch Linux wiki has a lot of info on this too A bit of history But, I believe that an understanding of the concepts behind the evolution of fonts may prove a decent starting point.ĭisclaimer: I deal a lot with fonts on Linux, but I never really needed to change Xorg code relating to fonts. Reading the source of fontconfig without a good understanding of the source of Xorg is probably very difficult. ![]() That require a lot of understanding of Xorg.įont configuration on UNIX machines went through different phases and fontconfig is simply one of the possibilities you can use to use fonts through Xorg. TL DR: Understanding fontconfig requires understanding why it was created and what problems it is trying to solve. What do I have to do? Will just compiling work, or do I have to register some thing in the Makefile. Lets suppose I want to modify a fontconfig file, like Fcquery.c, to make it call some other function which resides in some other shared library. $ fc-query /usr/share/fonts/truetype/fonts-japanese-gothic.ttf So I have decided to understand the source myself but I'm facing lots of troubles as I don't know what's the actually starting point, like when we write command on terminal like below, what is actually happening. I tried to search about them but couldn't find any great detail of how they actually work. When I went into the main source directory I saw many sub modules like fc-cache, fc-list, fc-query etc. So for this sake I have downloaded the fontconfig source code and I have compiled it and it's ready to use. I have read that fontconfig is the library which actually deals with the font management in Linux. I am new to the Linux environment, and I have started research on fonts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |