Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[HOWTO]Freetype subpixel font rendering - lcd monitors Pt 2
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... , 27, 28, 29  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
Hypnos
Advocate
Advocate


Joined: 18 Jul 2002
Posts: 2867
Location: Omnipresent

PostPosted: Wed Jan 02, 2013 11:40 pm    Post subject: Reply with quote

_______0 wrote:
what do you reccomend for 1080p monitor?

I like the eselect settings:

infinality = linux

lcdfilter = infinality


But, most people use:

infinality = infinality

lcdfilter = infinality
_________________
Personal overlay | Simple backup scheme
Back to top
View user's profile Send private message
PaulBredbury
Watchman
Watchman


Joined: 14 Jul 2005
Posts: 7310

PostPosted: Sun Jan 06, 2013 9:53 am    Post subject: Reply with quote

Infinality has a 2013-01-04 release, based on freetype 2.4.11 - seems good, as initial impression :)

I didn't notice a difference to the parameters in infinality-settings.sh

The patches keep coming in freetype git also.
Back to top
View user's profile Send private message
_______0
Guru
Guru


Joined: 15 Oct 2012
Posts: 521

PostPosted: Sun Jan 06, 2013 8:11 pm    Post subject: Reply with quote

hat's off!! great job infinality, your work has decreased my glasses prescription.

This guy singlehandedly fix the state of fonts in linux?? Now radeon is able to render fonts same as nvidia blobz oO

I had another question what are the tools to make a font?? I know inkscape has an option for crafting fonts, but I missing the step where it converts to ttf, otf, bitmap, etc.
Back to top
View user's profile Send private message
alexcortes
Tux's lil' helper
Tux's lil' helper


Joined: 18 Dec 2011
Posts: 124
Location: Rio de Janeiro, Brazil

PostPosted: Sun Feb 10, 2013 7:43 pm    Post subject: Reply with quote

Hello,

I don't know if it is expected (or I did something wrong) but i get this warnings when I run fc-cache:

Code:
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/infinality/conf.d/41-repl-os-linux.conf", line 16: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/41-repl-os-linux.conf", line 29: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/41-repl-os-linux.conf", line 39: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/41-repl-os-linux.conf", line 48: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/41-repl-os-linux.conf", line 60: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/41-repl-os-linux.conf", line 71: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/41-repl-os-linux.conf", line 82: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/41-repl-os-linux.conf", line 92: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/60-group-non-tt-fonts.conf", line 483: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/60-group-tt-fonts.conf", line 262: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-monospace-rendering.conf", line 27: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-traced-bitmap-rendering.conf", line 21: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-traced-bitmap-rendering.conf", line 50: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 16: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 31: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 102: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 119: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 138: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 158: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/59-google-droid-sans.conf", line 61: Having multiple values in <test> isn't supported and may not work as expected


Code:
Available fontconfig .conf files (* is enabled):
  [1]   10-autohint.conf *
  [2]   10-no-sub-pixel.conf
  [3]   10-sub-pixel-bgr.conf
  [4]   10-sub-pixel-rgb.conf *
  [5]   10-sub-pixel-vbgr.conf
  [6]   10-sub-pixel-vrgb.conf
  [7]   10-unhinted.conf
  [8]   11-lcdfilter-default.conf *
  [9]   11-lcdfilter-legacy.conf
  [10]  11-lcdfilter-light.conf
  [11]  20-unhint-small-dejavu-sans-mono.conf *
  [12]  20-unhint-small-dejavu-sans.conf *
  [13]  20-unhint-small-dejavu-serif.conf *
  [14]  20-unhint-small-vera.conf *
  [15]  25-unhint-nonlatin.conf
  [16]  30-metric-aliases.conf *
  [17]  30-urw-aliases.conf *
  [18]  40-nonlatin.conf *
  [19]  45-latin.conf *
  [20]  49-sansserif.conf *
  [21]  50-user.conf *
  [22]  51-local.conf *
  [23]  52-infinality.conf *
  [24]  57-dejavu-sans-mono.conf
  [25]  57-dejavu-sans.conf
  [26]  57-dejavu-serif.conf
  [27]  59-google-droid-sans-mono.conf *
  [28]  59-google-droid-sans.conf *
  [29]  59-google-droid-serif.conf *
  [30]  60-latin.conf *
  [31]  60-liberation.conf *
  [32]  62-croscore-arimo.conf
  [33]  62-croscore-cousine.conf
  [34]  62-croscore-symbolneu.conf
  [35]  62-croscore-tinos.conf
  [36]  63-source-pro.conf *
  [37]  65-fonts-persian.conf
  [38]  65-khmer.conf
  [39]  65-nonlatin.conf *
  [40]  69-unifont.conf *
  [41]  70-no-bitmaps.conf *
  [42]  70-yes-bitmaps.conf
  [43]  80-delicious.conf *
  [44]  90-synthetic.conf *
  [45]  99pdftoopvp.conf


@Hypnos, very nice indeed:

Quote:
I like the eselect settings:

infinality = linux

lcdfilter = infinality


Thanks!!! :)
Back to top
View user's profile Send private message
poncho
n00b
n00b


Joined: 06 Mar 2011
Posts: 58

PostPosted: Sun Feb 10, 2013 7:54 pm    Post subject: Reply with quote

media-libs/fontconfig-infinality needs a version bump to work with media-libs/fontconfig-2.10.2

see http://www.infinality.net/forum/viewtopic.php?f=2&t=79
and https://github.com/Infinality/fontconfig-infinality/blob/master/infinality/CHANGELOG

edit:
and this https://bugs.gentoo.org/show_bug.cgi?id=456652


Last edited by poncho on Sun Feb 10, 2013 11:29 pm; edited 1 time in total
Back to top
View user's profile Send private message
alexcortes
Tux's lil' helper
Tux's lil' helper


Joined: 18 Dec 2011
Posts: 124
Location: Rio de Janeiro, Brazil

PostPosted: Sun Feb 10, 2013 8:06 pm    Post subject: Reply with quote

poncho wrote:
media-libs/fontconfig-infinality needs a version bump to work with media-libs/fontconfig-2.10.2

see http://www.infinality.net/forum/viewtopic.php?f=2&t=79
and https://github.com/Infinality/fontconfig-infinality/blob/master/infinality/CHANGELOG


Thanks! :lol:
Back to top
View user's profile Send private message
wvmmhxkh
n00b
n00b


Joined: 26 Feb 2013
Posts: 2

PostPosted: Tue Feb 26, 2013 1:23 am    Post subject: Reply with quote

Sooo, it's been what, half a year since infinality ebuild have been updated? The strange thing, to me, is that git repo seems fairly maintained and not abandoned at all. Seeing how old versions have some annoying bugs should we switch to overlay?
Back to top
View user's profile Send private message
Heimfrost
n00b
n00b


Joined: 02 Jul 2007
Posts: 21
Location: in the swapspace of Germany

PostPosted: Sat Mar 02, 2013 4:16 pm    Post subject: Reply with quote

I have the problem, that with fontconfig-2.9 and greater from lcd-filtering overlay or gentoo, "Webdings" font in my .conkyrc isn't displayed any longer. Has anyone the same problem or a solution?
Back to top
View user's profile Send private message
PaulBredbury
Watchman
Watchman


Joined: 14 Jul 2005
Posts: 7310

PostPosted: Sat Mar 02, 2013 4:31 pm    Post subject: Reply with quote

A bit of debugging:
Code:
$ fc-match Webdings
webdings.ttf: "Webdings" "Normal"

pango-view --font "Webdings 10" --dpi 96 --text "the quick brown fox jumps over the lazy dog. THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG."

Works fine for me, with fontconfig 2.10.2
Back to top
View user's profile Send private message
Heimfrost
n00b
n00b


Joined: 02 Jul 2007
Posts: 21
Location: in the swapspace of Germany

PostPosted: Sun Mar 03, 2013 9:04 am    Post subject: Reply with quote

With fontconfig <2.9:
Code:
fc-match Webdings
webdings.ttf: "Webdings" "Regular"

pango-view shows me the correct Webdings symbols of "the quick brown fox jumps over the lazy dog. THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG."

with fontconfig =2.9.0::lcd-filtering:
Code:
fc-match Webdings
webdings.ttf: "Webdings" "Normal"

pango-view shows me "the quick brown fox jumps over the lazy dog. THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG." with no Webding font symbols
Back to top
View user's profile Send private message
PaulBredbury
Watchman
Watchman


Joined: 14 Jul 2005
Posts: 7310

PostPosted: Sun Mar 03, 2013 10:48 am    Post subject: Reply with quote

Sounds like bug in fontconfig 2.9

So, try 2.10.2
Back to top
View user's profile Send private message
Heimfrost
n00b
n00b


Joined: 02 Jul 2007
Posts: 21
Location: in the swapspace of Germany

PostPosted: Sun Mar 03, 2013 11:04 am    Post subject: Reply with quote

Same with 2.10.2.
Back to top
View user's profile Send private message
AustinMatherne
n00b
n00b


Joined: 25 Jul 2012
Posts: 32
Location: Minneapolis, Minnesota, USA

PostPosted: Sat Mar 16, 2013 1:58 am    Post subject: Reply with quote

I just finished reading both this entire thread, and the previous one dating back to 2006.

Firstly, I'd like to thank Infinality, PaulBredbury, bi3l, yngwin, and the many others that have helped us get to where we are today.

Now, what I'd like to do is summarize the current state of affairs, clear up any misconceptions I might still have, and then stick it all in this post so others can more easily improve and customize their fonts by simply following a how-to. If anyone would like to add and/or modify anything below, please let me know.


Initial Setup:
Enable the infinality use flag on freetype so it will bring in the patches and eselect-infinality and fontconfig-infinality packages.
Code:

echo "media-libs/freetype infinality -bindist" >> /etc/portage/package.use

Emerge freetype with the new use flags applied.
Code:

emerge -av --oneshot media-libs/freetype

Set your preferred styling. Use the list functionality in eselect to see what options are available other than infinality, such as linux, osx, win7, etc. Style descriptions are in /etc/fonts/infinality/infinality.conf.
Code:

eselect infinality set infinality
eselect lcdfilter set infinality

Enable the infinality fonts configuration.
Code:

eselect fontconfig enable 52-infinality.conf


Extra Credit:
Put the DPI value of your display in /etc/fonts/infinality/infinality.conf using this tool (PPI == DPI) to calculate the DPI of your display. Override the generic value of 75 set by infinality.
Code:

...
<match target="pattern">
  <edit name="dpi" mode="assign">
    <double>75</double>
  </edit>
</match>
...

Setup .Xresources for applications that still use libXft. Use the tool above to claculate your display's DPI and this tool to figure out the correct rgba setting for your display (which will most likely be "rgb").
Code:

echo "Xft.dpi: 75" >> ~/.Xresources
echo "Xft.autohint: 0" >> ~/.Xresources
echo "Xft.lcdfilter: lcddefault" >> ~/.Xresources
echo "Xft.hintstyle: hintfull" >> ~/.Xresources
echo "Xft.hinting: 1" >> ~/.Xresources
echo "Xft.antialias: 1" >> ~/.Xresources
echo "Xft.rgba: rgb" >> ~/.Xresources


Things To Watch Out For:
If you are running a Desktop Environment (KDE, Gnome, etc) it may be writing settings in ~/.fonts.conf or ~/.fonts.conf.d/. You can prevent these files from being read by running:
Code:

eselect fontconfig disable 50-user.conf


Setting an incorrect DPI or rgba value can make your fonts look weird. Make sure you set them to their correct values.


Last edited by AustinMatherne on Sat Mar 16, 2013 8:15 am; edited 2 times in total
Back to top
View user's profile Send private message
AustinMatherne
n00b
n00b


Joined: 25 Jul 2012
Posts: 32
Location: Minneapolis, Minnesota, USA

PostPosted: Sat Mar 16, 2013 2:09 am    Post subject: Reply with quote

Something I'm not sure about yet. Does enabling configuration files such as 10-autohint.conf interfere with infinality? My understanding is that it should, since it applies autohinting to all fonts, while infinality intelligently only targets certain fonts? If that's correct, then eselect fontconfig should only be used to enable 52-infinality, while everything else should be left alone?
Back to top
View user's profile Send private message
PaulBredbury
Watchman
Watchman


Joined: 14 Jul 2005
Posts: 7310

PostPosted: Sat Mar 16, 2013 12:06 pm    Post subject: Reply with quote

AustinMatherne wrote:
interfere with infinality?

Look at the numbers in the filenames - that's the precedence order.

Personally, my /etc/fonts/local.conf has this near the top:
Code:
    <match>
        <edit mode="assign" name="rgba"><const>rgb</const></edit>
        <edit mode="assign" name="autohint"><bool>true</bool></edit>
        <edit mode="assign" name="hintstyle"><const>hintslight</const></edit>
        <edit mode="assign" name="hinting"><bool>true</bool></edit>
        <edit mode="assign" name="antialias"><bool>true</bool></edit>
        <edit mode="assign" name="lcdfilter"><const>lcddefault</const></edit>
    </match>

I don't even have 10-autohint.conf, but of course, it would be overruled by the above.
Back to top
View user's profile Send private message
poncho
n00b
n00b


Joined: 06 Mar 2011
Posts: 58

PostPosted: Sat Mar 16, 2013 1:13 pm    Post subject: Reply with quote

AustinMatherne wrote:
Setup .Xresources for applications that still use libXft. Use the tool above to claculate your display's DPI and this tool to figure out the correct rgba setting for your display (which will most likely be "rgb").
Code:

echo "Xft.dpi: 75" >> ~/.Xresources
echo "Xft.autohint: 0" >> ~/.Xresources
echo "Xft.lcdfilter: lcddefault" >> ~/.Xresources
echo "Xft.hintstyle: hintfull" >> ~/.Xresources
echo "Xft.hinting: 1" >> ~/.Xresources
echo "Xft.antialias: 1" >> ~/.Xresources
echo "Xft.rgba: rgb" >> ~/.Xresources


fontconfig-infinality installs /etc/X11/Xresources. I don't think ~/.Xresources is necessary.

AustinMatherne wrote:
If anyone would like to add and/or modify anything below, please let me know.

We could make a page on wiki.gentoo.org. I moved your post to my sandbox.
You can have a look/edit here: https://wiki.gentoo.org/wiki/User:Poncho/Sandbox
Back to top
View user's profile Send private message
AustinMatherne
n00b
n00b


Joined: 25 Jul 2012
Posts: 32
Location: Minneapolis, Minnesota, USA

PostPosted: Sun Mar 17, 2013 6:26 am    Post subject: Reply with quote

PaulBredbury wrote:
Look at the numbers in the filenames - that's the precedence order.

That's what I thought; however, if I put a DPI rule in /etc/fonts/local.conf with 51-local.conf enabled by eselect, it doesn't take effect. I have to overwrite the DPI value in /etc/fonts/infinality/infinality.conf for it to do anything. Do you know if the infinality config is doing something special that's preventing local.conf from taking precedence? Just to make sure I'm not doing something completely stupid, this is my /etc/fonts/local.conf file.
Code:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>

<match target="pattern">
  <edit name="dpi" mode="assign">
    <double>108.79</double>
  </edit>
</match>

</fontconfig>


poncho wrote:
fontconfig-infinality installs /etc/X11/Xresources. I don't think ~/.Xresources is necessary.

Thanks, and good catch. It would still appear to me that ~/.Xresources should be set with the users correct DPI setting, along with the rbga value if it isn't rgb.


Edit:
PaulBredbury, did you mean that the file name 20-* takes precedence over 10-*? That would contradict what I've read elsewhere, but it would explain my inability to set DPI in local.conf.
Back to top
View user's profile Send private message
PaulBredbury
Watchman
Watchman


Joined: 14 Jul 2005
Posts: 7310

PostPosted: Sun Mar 17, 2013 6:51 am    Post subject: Reply with quote

AustinMatherne wrote:
file name 20-* takes precedence over 10-*?

Yes. Which is the same as in Udev.

conf.d/README in fontconfig-2.10.2.tar.bz2 says:
Code:
The files are loaded in numeric order, the structure of the configuration
has led to the following conventions in usage:

 Files begining with:   Contain:
 
 00 through 09      Font directories
 10 through 19      system rendering defaults (AA, etc)
 20 through 29      font rendering options
 30 through 39      family substitution
 40 through 49      generic identification, map family->generic
 50 through 59      alternate config file loading
 60 through 69      generic aliases, map generic->family
 70 through 79      select font (adjust which fonts are available)
 80 through 89      match target="scan" (modify scanned patterns)
 90 through 99      font synthesis


Easy evidence is this test file:
Code:
<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>

   <match>
      <edit mode="assign" name="antialias"><bool>false</bool></edit>
   </match>
   
</fontconfig>

As /etc/fonts/conf.d/91-test.conf , fonts become ugly as expected, but as 11-test.conf, the rule is overriden by /etc/fonts/local.conf (via 51-local.conf) :)

I've corrected the Arch wiki.
Back to top
View user's profile Send private message
AustinMatherne
n00b
n00b


Joined: 25 Jul 2012
Posts: 32
Location: Minneapolis, Minnesota, USA

PostPosted: Sun Mar 17, 2013 9:20 pm    Post subject: Reply with quote

Thanks, that clears up quite a bit. Since 52-infinality is going to take precedence over both 50-user and 51-local, what do you think would be the best way to change the DPI setting? As I see it, there are three options.

1. Modify /etc/fonts/infinality/infinality.conf directly. This seems like a bad idea for maintainability.
2. Move 51-local.conf to 53.local.conf, allowing it to override infinality. I don't particularly like this option either, since 51-local may be reintroduced by whichever package is responsible for creating it, and if two files both import the same thing, the second import is ignored (in this case, 53-local.conf).
3. Create an entirely new file, say /etc/fonts/infinality-override.conf and import it with another new file, 53-infinality-override.conf. I don't like introducing my own files into /etc, but I think this option is the least likely to break.

Thoughts?
Back to top
View user's profile Send private message
PaulBredbury
Watchman
Watchman


Joined: 14 Jul 2005
Posts: 7310

PostPosted: Sun Mar 17, 2013 9:46 pm    Post subject: Reply with quote

DPI is strange, and I wouldn't change it, unless it's obviously wrong.

Roughly, I think the precedence order should probably be:
    Infinality
    system ("local")
    user

So then DPI would be set, if appropriate to be set, in system ("local").

Which contradicts the current fontconfig defaults of 50-user.conf and 51-local.conf :(

Fontconfig's DPI setting is just one value, whereas in xorg.conf it's x & y. Which kinda shows that it's a bit of a joke calculation - but it can affect font appearance.
Back to top
View user's profile Send private message
AustinMatherne
n00b
n00b


Joined: 25 Jul 2012
Posts: 32
Location: Minneapolis, Minnesota, USA

PostPosted: Mon Mar 18, 2013 6:00 pm    Post subject: Reply with quote

Interesting. Turns out DPI is a lot more complicated than I thought. It appears that the users correct DPI needs to be either detected by Xorg or manually set in it's configuration. But fontconfig is better off using a standard DPI of 96 (or 72 in some cases), because some applications expect it to be one of those and scale accordingly.

Given that infinality sets sane defaults depending on the user's selected styling (infinality, linux, OSX, OSX2, win7, winxp, win98) for rgba, autohint, hitstyle, hinting, antialias, and lcdfilter, unless the user has a good reason, it doesn't appear that anything should be changed beyond enabling infinality and selecting a styling. The README indicates as much.
Quote:
The local.conf is now obsolete and completely replaced by this configuration.

So what about configuration files that are installed for specific fonts? Let's take the DejaVu fonts as an example, they install the files below. Should they be enabled, or do they interfere with infinality in some way?
From what I can tell, the 20-*s are probably a good idea, but the 50-*s will override the order of preferred fonts set by infinality. So I should stick something in the wiki explaining the option and why the user might want to enable them.

20-unhint-small-dejavu-sans-mono.conf
20-unhint-small-dejavu-sans.conf
20-unhint-small-dejavu-serif.conf
57-dejavu-sans-mono.conf
57-dejavu-sans.conf
57-dejavu-serif.conf
Back to top
View user's profile Send private message
PaulBredbury
Watchman
Watchman


Joined: 14 Jul 2005
Posts: 7310

PostPosted: Mon Mar 18, 2013 7:15 pm    Post subject: Reply with quote

AustinMatherne wrote:
fontconfig is better off using a standard DPI

No, that's the wrong conclusion. People have widescreen monitors these days, e.g. mine has DPI 131x119 - let's not add distortion by assuming for the old-style sake of simplicity that a rectangle is a square ;) The font-rendering calculations probably should be a bit smarter.

The filename numbering is a bit of a mess. The default fontconfig rules are assuming default-style freetype rendering, rather than the superior Infinality rendering, so they may not even be appropriate. In which case, having 50-base-rendering.conf, rather than 10-base-rendering.conf, sensibly overrules e.g. 20-unhint-small-vera.conf :lol:
Back to top
View user's profile Send private message
AustinMatherne
n00b
n00b


Joined: 25 Jul 2012
Posts: 32
Location: Minneapolis, Minnesota, USA

PostPosted: Mon Mar 18, 2013 8:30 pm    Post subject: Reply with quote

PaulBredbury wrote:
No, that's the wrong conclusion. People have widescreen monitors these days, e.g. mine has DPI 131x119 - let's not add distortion by assuming for the old-style sake of simplicity that a rectangle is a square ;) The font-rendering calculations probably should be a bit smarter.

So I shouldn't use the default DPI in infinality.conf, nor should I overwrite it. Am I correct in assuming that means the DPI should not be set in fontconfig at all and simply left to Xorg to figure out? If that's the case, the DPI rule in infinality.conf should be deleted.

PaulBredbury wrote:
In which case, having 50-base-rendering.conf, rather than 10-base-rendering.conf, sensibly overrules e.g. 20-unhint-small-vera.conf :lol:

I can't test this until later because I'm not in front of my computer. Are you saying that a file numbered 20-* will be overridden by a file numbered 50-* from another directory which is read from an include statement in a file numbered 52-*?

Thanks again. I really do appreciate you taking the time to answer my questions.
Back to top
View user's profile Send private message
PaulBredbury
Watchman
Watchman


Joined: 14 Jul 2005
Posts: 7310

PostPosted: Mon Mar 18, 2013 9:20 pm    Post subject: Reply with quote

AustinMatherne wrote:
simply left to Xorg to figure out?

Yes. Unless Xorg gets it wrong, which can happen if it can't read the EDID.

Quote:
will be overridden

Depends what the rules are. If 50-blah says set hinting (a single variable) unconditionally to true, it doesn't matter what 20-blah sets hinting to.

Unless 30-blah tests the value of hinting and sets some other variable from it - but that would be weird ;)
Back to top
View user's profile Send private message
AustinMatherne
n00b
n00b


Joined: 25 Jul 2012
Posts: 32
Location: Minneapolis, Minnesota, USA

PostPosted: Mon Mar 18, 2013 10:06 pm    Post subject: Reply with quote

PaulBredbury wrote:
Yes. Unless Xorg gets it wrong, which can happen if it can't read the EDID.

Unfortunately, I know all too well about corrupt EDID. I'll stick something in the wiki about testing and setting the correct display dimensions in xorg.conf.d/. I'm assuming this applies to Xresources, as well? Or are there legacy issues that would result in treating Xresources differently than fontconfig?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3 ... , 27, 28, 29  Next
Page 28 of 29

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum