So I changed the Substitute for MS shell dlg + Ms Shell dlg 2 to Tahoma, TTF, 10. Most interestingly, I also noticed, "Tahoma" written like this : "Tahoma, TTF, 10"
Wandering through the registry, around Fonts and Font Substitute keys I noticed several folders containing fonts settings. So don't expect too much from the changes indicated above. Windows 10 keeps "breaking" things badly and it's quite impossible to keep things steady either in Segoe UI or in Arial and even Tahoma (often preferred to Segoe by many people). W10 anniversary is a true mess for fonts ! Imgur: The magic of the Internetġ.) Look at the Ok and Cancel buttons in Thunderbird, on the right, cut off a little on the bottomĢ.) Column headers for C: seem a little bigīut, other than that, fine, so, I stick with it, at this time The only things I've noticed recently are (2 screenshots). If you mess things up, restore to your backup, or take a look at the screenshots of what mine are, and you should be fine. I was just able to download AFSC v1.1.3.34, which I presume will work just as well, even though it's been changed a bit. This took some experimentation.Ģ) I noticed you used AFSC v1.1.2.33. Then, I just made the font sizes larger, or Bold. Then, I just left it on Segoe UI, the one MS likes, due to my previous, unpleasant experience using other fonts (dots where colons should be in the clock, bottom right) - I don't think you gain anything with Arial.
Screenshots of what they are can't hurt, for reference purposes, and since you're in the learning process. I think I must have had it on the OS default, which as you know is very small.Īfter I opened ASFC, the first thing I did was to make a backup of the current font settings with it. I didn't change anything before I used AFSC. 1) Did you not perform a system font change to Arial Bold before you used AFSC?
0 kommentar(er)
