On Thu, Apr 10, 2014 at 05:34:11PM +0400, Kirill Elagin wrote: > That's true, but there still might be packages that need this. > > This time, I've found that there is a patch for dmenu that enables Xft > (and this patch is actually in nixpkgs, one just has to enable it). So, > probably, you are right, and that's really no worth it.
There are plenty of X programs that don't use fontconfig, isn't it? If you use X over network, client side font rendering is also slower. > On Thu, Apr 10, 2014 at 1:06 PM, Eelco Dolstra > <[email protected]>wrote: > > > Hi, > > > > On 10/04/14 08:18, Kirill Elagin wrote: > > > > > I've glanced through all the fonts stuff in NixOS modules and it looks > > like there is > > > something wrong. That is, there are, basically, to different sets of > > fonts: > > > ordinary fonts > > > and X fonts. If you add and ordinary font to `config.fonts.fonts` it > > won't be > > > added to > > > the X config, because, most likely, it won't have a `fonts.dir` file. > > Basically, > > > this means > > > that almost no modern beautiful font can be registered within X server. > > > > Registering fonts with the X server has been obsolete for at least ten > > years, > > applications should use fontconfig to find fonts and render them > > client-side. > > > > -- > > Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ > > _______________________________________________ > > nix-dev mailing list > > [email protected] > > http://lists.science.uu.nl/mailman/listinfo/nix-dev > > > _______________________________________________ > nix-dev mailing list > [email protected] > http://lists.science.uu.nl/mailman/listinfo/nix-dev _______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
