Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 23 Apr 2014, 17:13
All times are UTC - 4
 Forum index » House Training » HOWTO ( Solutions )
[HowTo] Turn On/Off Font Antaliasing
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 4 [47 Posts]   Goto page: Previous 1, 2, 3, 4 Next
Author Message
puppyite


Joined: 23 Jul 2009
Posts: 758
Location: U.S., Midwest, Central Time Zone, GMT-6

PostPosted: Mon 31 Aug 2009, 13:55    Post subject:  

After experimentation here's what I've settled on for .fonts.conf:

Code:
<match target="font">
 <edit name="antialias" mode="assign">
<bool>true</bool>
</edit>
<edit name="hinting" mode="assign">
<bool>false</bool>
</edit>
 <edit name="autohint" mode="assign">
<bool>false</bool>
</edit>
<edit name="hintstyle" mode="assign">
<const>hintnone</const>
</edit>
</match>


I can't see any difference between hintfull or hintnone but it does no harm either way. Antialise "true" is what makes a difference for me. I chose this not because it had anything to offer over the default antialising in Puppy but because of the profound effect it has on kearning in Abiword. Without this improvement I found it very difficult to compose in Abiword and as a result I had to keep turning on the Formatting Marks otherwise I couldn't tell where spaces should or should not be in my documents.

Thank you Iguleder, now I can use Abiword!

PS: I might try disciple's method but he didn't give enough information on exactly how he achives his result.

_________________
Learn more about Puppy Linux: Puppy Linux FAQ
Protect your privacy: Scroogle.org - Ixquick
Back to top
View user's profile Send private message Visit poster's website 
disciple

Joined: 20 May 2006
Posts: 6378
Location: Auckland, New Zealand

PostPosted: Tue 01 Sep 2009, 08:46    Post subject:  

IIRC "my" method is the same as SHS's method, except I wait for fonts to get bigger before turning on antialiasing, and I don't bother with all the weird dejavu fonts etc - I just use Arial for pretty much everything.

fonts.conf
Code:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<!-- /etc/fonts/fonts.conf file to configure system font access -->
<!-- Modified version for Puppy Linux versions up through February 2008 by P.N. Courier a.k.a. -->
<!-- "SitHeelSpeak" or "Sit Heel Speak" on the Puppy Linux forums -->
<!-- SHS version 0.05 beta -->
<!-- Maintainer Keith Packard says not to edit this file, but I did. -->
<!-- Make a backup copy, in case this gets overwritten! -->
<!-- ...and, back up your original first! -->

<fontconfig>

<!-- Set dpi to match actual display reality as shown by Seamonkey/Mozilla -->
<!-- on my display this is 91, yours may vary -->
<match target="pattern">
   <edit name="dpi" mode="assign">
   <double>91</double></edit>
</match>


<!-- (maintainer Keith Packard says...)
   DO NOT EDIT THIS FILE.
   IT WILL BE REPLACED WHEN FONTCONFIG IS UPDATED.
   LOCAL CHANGES BELONG IN 'local.conf'.

   The intent of this standard configuration file is to be adequate for
   most environments.  If you have a reasonably normal environment and
   have found problems with this configuration, they are probably
   things that others will also want fixed.  Please submit any
   problems to the fontconfig bugzilla system located at fontconfig.org

   Note that the normal 'make install' procedure for fontconfig is to
   replace any existing fonts.conf file with the new version.  Place
   any local customizations in local.conf which this file references.

   Keith Packard
-->

<!-- Font subdirectories list for all Puppy Linuxes 1 and 2 up though 2.10 -->
<!-- Depending on whether it's Puppy 1 or 2, one or more of these subdirs may -->
<!-- not exist.  Doesn't matter, no harm will result. -->
<!-- Should work in Puppy 2.10 since /usr/X11R6 is a symlink to /usr/X11R7. -->
<!-- If not, add corresponding X11R7 subdirs -->
<dir>~/.fonts</dir>
<dir>/usr/share/fonts/default/fonts</dir>
<dir>/usr/X11R6/lib/X11/fonts/TTF</dir>
<dir>/usr/X11R6/lib/X11/fonts/Type1</dir>
<dir>/usr/X11R6/lib/X11/fonts/misc</dir>

<!-- Font cache directory list -->

   <cachedir>/var/cache/fontconfig</cachedir>
   <cachedir>~/.fontconfig</cachedir>

<!-- Alternate-spellings section begins here. -->
<!-- Accept deprecated 'mono' alias, replacing it with 'monospace' -->
<match target="pattern">
   <test qual="any" name="family">
      <string>mono</string>
   </test>
   <edit name="family" mode="assign">
      <string>monospace</string>
   </edit>
</match>

<!-- Accept alternate 'sans serif' spelling, replacing it with 'sans-serif' -->
<match target="pattern">
   <test qual="any" name="family">
      <string>sans serif</string>
   </test>
   <edit name="family" mode="assign">
      <string>sans-serif</string>
   </edit>
</match>

<!-- Accept deprecated 'sans' alias, replacing it with 'sans-serif' -->
<match target="pattern">
   <test qual="any" name="family">
      <string>sans</string>
   </test>
   <edit name="family" mode="assign">
      <string>sans-serif</string>
   </edit>
</match>
<!-- Alternate-spellings section ends here. -->

<!-- The aliases list begins here. -->
<!-- Mark common families with their generic names as aliases -->
<!-- so we'll get something reasonable if only generic face, not family, is specified -->

<!-- Serif faces -->
<alias>
   <family>Times New Roman</family>
   <family>DejaVu Serif</family>
   <family>Gentium</family>
   <family>Bitstream Vera Serif</family>
   <family>URW Bookman L</family>
   <family>Nimbus Roman No9 L</family>
   <family>Century Schoolbook L</family>
   <family>New Century Schoolbook</family>
   <family>Georgia</family>
   <family>Times</family>
   <family>Luxi Serif</family>
   <family>Kochi Mincho</family>
   <family>AR PL SungtiL GB</family>
   <family>AR PL Mingti2L Big5</family>
   <family>Baekmuk Batang</family>         
   <default><family>serif</family></default>
</alias>

<!-- Sans-serif faces -->
<alias>
   <family>Arial</family>
   <family>DejaVu Sans</family>
   <family>Humnst777 BT</family>
   <family>Tahoma</family>
   <family>Verdana</family>
   <family>Lucida Sans Unicode</family>
   <family>URW Gothic L</family>
   <family>Trebuchet MS</family>
   <family>Helvetica</family>
   <family>Microsoft Sans Serif</family>
   <family>Nimbus Sans L</family>
   <family>Luxi Sans</family>
   <family>Bitstream Vera Sans</family>
   <family>Kochi Gothic</family>
   <family>AR PL KaitiM GB</family>
   <family>AR PL KaitiM Big5</family>
   <family>AR PL ZenKai Uni</family>
   <family>AR PL ZenKai Uni MBE</family>
   <family>Kai PC .TTF</family>
   <family>Baekmuk Dotum</family>
   <family>SimSun</family>
   <default><family>sans-serif</family></default>
</alias>

<!-- Monospace faces -->
<alias>
   <family>Courier New</family>
   <family>Andale Mono</family>
   <family>DejaVu Sans Mono</family>
   <family>Bitstream Vera Sans Mono</family>
   <family>Courier</family>
   <family>Luxi Mono</family>
   <family>Nimbus Mono L</family>
   <family>NSimSun</family>
   <family>Kochi Gothic</family>
   <family>AR PL KaitiM GB</family>
   <family>Baekmuk Dotum</family>
   <default><family>monospace</family></default>
</alias>

<!-- If a font is not in the above lists, consider it sans-serif -->
<match target="pattern">
   <test qual="all" name="family" compare="not_eq">
      <string>sans-serif</string>
   </test>
   <test qual="all" name="family" compare="not_eq">
      <string>serif</string>
   </test>
   <test qual="all" name="family" compare="not_eq">
      <string>monospace</string>
   </test>
   <edit name="family" mode="append_last">
      <string>sans-serif</string>
   </edit>
</match>

<!-- The aliases list ends here. -->

<!-- Asian font fixups begin here. -->   
<!--
  Some Asian fonts misadvertise themselves as monospaced when
  in fact they are dual-spaced (half and full).  This makes
  FreeType very confused as it forces all widths to match.
  Undo this magic by disabling the width forcing code -->
<match target="font">
   <test name="family"><string>GulimChe</string></test>
   <edit name="globaladvance"><bool>false</bool></edit>
</match>
   
<match target="font">
   <test name="family"><string>DotumChe</string></test>
   <edit name="globaladvance"><bool>false</bool></edit>
</match>

<match target="font">
   <test name="family"><string>BatangChe</string></test>
   <edit name="globaladvance"><bool>false</bool></edit>
</match>

<match target="font">
   <test name="family"><string>GungsuhChe</string></test>
   <edit name="globaladvance"><bool>false</bool></edit>
</match>
<!-- Asian font fixups end here. -->   

<!-- Bitstream Vera font fixups begin here. -->
<!--
   The Bitstream Vera fonts have GASP entries suggesting that hinting be
   disabled below 8 ppem, but FreeType ignores those, preferring to use
   the data found in the instructed hints.  The initial Vera release
   didn't include the right instructions in the 'prep' table. Fix this
   by disabling hinting manually at smaller sizes (< 8ppem)
 -->
   
<match target="font">
   <test name="family">
      <string>Bitstream Vera Sans</string>
   </test>
   <test name="pixelsize" compare="less">
      <double>7.5</double>
   </test>
   <edit name="hinting">
      <bool>false</bool>
   </edit>
</match>
   
<match target="font">
   <test name="family">
      <string>Bitstream Vera Serif</string>
   </test>
   <test name="pixelsize" compare="less">
      <double>7.5</double>
   </test>
   <edit name="hinting">
      <bool>false</bool>
   </edit>
</match>
   
<match target="font">
   <test name="family">
      <string>Bitstream Vera Sans Mono</string>
   </test>
   <test name="pixelsize" compare="less">
      <double>7.5</double>
   </test>
   <edit name="hinting">
      <bool>false</bool>
   </edit>
</match>
<!-- Bitstream Vera font fixups end here. -->
   
<!-- Load per-user customization file (not present in Puppy Linux) -->
<include ignore_missing="yes">~/.fonts.conf</include>

<!-- Load local system customization file -->
<include ignore_missing="yes">local.conf</include>

<!-- Keith Packard says here, -->
<!-- "Alias well known font names to available TrueType fonts" -->
<!-- ...but, I've commented these out because I LIKE fixed-width fonts... -->
<!-- ...at small sizes, that is.  I disallow them at larger sizes, in local.conf. -->
<!-- ...and, I have no problem with Arial. -->
   <alias>
      <family>DejaVu Sans</family>
      <accept><family>Arial</family></accept>
   </alias>
<!--    <alias>
      <family>Times</family>
      <accept><family>Times New Roman</family></accept>
   </alias>
   <alias>
      <family>Helvetica</family>
      <accept><family>Verdana</family></accept>
   </alias>

   <alias>
      <family>Arial</family>
      <accept><family>Verdana</family></accept>
   </alias>

   <alias>
      <family>Courier</family>
      <accept><family>Courier New</family></accept>
   </alias>
-->

   <alias>
      <family>Times</family>
      <accept><family>Times New Roman</family></accept>
   </alias>

<!--
 Keith Packard says, "Check user preference to avoid bitmap fonts and replace
 bitmap face names with equivalent scalable fonts"
 -->

<!-- no, I've commented this out; I do not know whether TrueType Helvetica -->
<!-- and Times are good or not -->
<!--   <match target="pattern">
           <test name="prefer_outline">
                   <bool>true</bool>
           </test>
           <test name="family">
                   <string>Helvetica</string>
           </test>
           <edit name="family" mode="prepend" binding="same">
                   <string>Arial</string>
           </edit>
   </match>
   
   <match target="pattern">
           <test name="prefer_outline">
                   <bool>true</bool>
           </test>
           <test name="family">
                   <string>Times</string>
           </test>
           <edit name="family" mode="prepend" binding="same">
                   <string>Times New Roman</string>
           </edit>
   </match>
-->

<!-- Preference list begins here. -->
<!-- This is the order in which fonts will be chosen when just -->
<!-- "serif," "sans-serif," or "monospace" is specified on the web page. -->
<!-- I believe it should match the "alias" lists, above, but am not sure. -->

<alias>
   <family>serif</family>
      <prefer>
         <family>Times New Roman</family>
         <family>DejaVu Serif</family>
         <family>Gentium</family>
         <family>Bitstream Vera Serif</family>
         <family>URW Bookman L</family>
         <family>Nimbus Roman No9 L</family>
         <family>Century Schoolbook L</family>
         <family>New Century Schoolbook</family>
         <family>Georgia</family>
         <family>Times</family>
         <family>Luxi Serif</family>
         <family>Kochi Mincho</family>
         <family>AR PL SungtiL GB</family>
         <family>AR PL Mingti2L Big5</family>
         <family>Baekmuk Batang</family>         
      </prefer>
</alias>

<alias>
   <family>sans-serif</family>
      <prefer>
         <family>Arial</family>
         <family>DejaVu Sans</family>
         <family>Humnst777 BT</family>
         <family>Tahoma</family>
         <family>Verdana</family>
         <family>Lucida Sans Unicode</family>
         <family>URW Gothic L</family>
         <family>Trebuchet MS</family>
         <family>Helvetica</family>
         <family>Microsoft Sans Serif</family>
         <family>Nimbus Sans L</family>
         <family>Luxi Sans</family>
         <family>Bitstream Vera Sans</family>
         <family>Kochi Gothic</family>
         <family>AR PL KaitiM GB</family>
         <family>AR PL KaitiM Big5</family>
         <family>AR PL ZenKai Uni</family>
         <family>AR PL ZenKai Uni MBE</family>
         <family>Kai PC .TTF</family>
         <family>Baekmuk Dotum</family>
         <family>SimSun</family>
      </prefer>
   </alias>

<alias>
   <family>monospace</family>
      <prefer>
         <family>Courier New</family>
         <family>Andale Mono</family>
         <family>DejaVu Sans Mono</family>
         <family>Bitstream Vera Sans Mono</family>
         <family>Courier</family>
           <family>Luxi Mono</family>
         <family>Nimbus Mono L</family>
         <family>NSimSun</family>
         <family>Kochi Gothic</family>
         <family>AR PL KaitiM GB</family>
         <family>Baekmuk Dotum</family>
      </prefer>
</alias>
<!-- Preference list ends here. -->

<!-- Artificial oblique (italic) for fonts without an italic or oblique version -->
<match target="font">
   <!-- check to see if the font is roman -->
   <test name="slant">
      <const>roman</const>
   </test>
   <!-- check to see if the pattern requested non-roman -->
   <test target="pattern" name="slant" compare="not_eq">
      <const>roman</const>
   </test>
   <!-- multiply the matrix to slant the font -->
   <edit name="matrix" mode="assign">
      <times>
         <name>matrix</name>
         <matrix><double>1</double><double>0.2</double>
            <double>0</double><double>1</double>
         </matrix>
      </times>
   </edit>
   <!-- pretend the font is oblique now -->
   <edit name="slant" mode="assign">
      <const>oblique</const>
   </edit>
</match>

<config>

<!--
  These are the default Unicode chars that are expected to be blank
  in fonts.  All other blank chars are assumed to be broken and
  won't appear in the resulting charsets
 -->
      <blank>
         <int>0x0020</int>   <!-- SPACE -->
         <int>0x00a0</int>   <!-- NO-BREAK SPACE -->
         <int>0x00ad</int>   <!-- SOFT HYPHEN -->
         <int>0x115f</int>   <!-- HANGUL CHOSEONG FILLER -->
         <int>0x1160</int>   <!-- HANGUL JUNGSEONG FILLER -->
         <int>0x1680</int>   <!-- OGHAM SPACE MARK -->
         <int>0x2000</int>   <!-- EN QUAD -->
         <int>0x2001</int>   <!-- EM QUAD -->
         <int>0x2002</int>   <!-- EN SPACE -->
         <int>0x2003</int>   <!-- EM SPACE -->
         <int>0x2004</int>   <!-- THREE-PER-EM SPACE -->
         <int>0x2005</int>   <!-- FOUR-PER-EM SPACE -->
         <int>0x2006</int>   <!-- SIX-PER-EM SPACE -->
         <int>0x2007</int>   <!-- FIGURE SPACE -->
         <int>0x2008</int>   <!-- PUNCTUATION SPACE -->
         <int>0x2009</int>   <!-- THIN SPACE -->
         <int>0x200a</int>   <!-- HAIR SPACE -->
         <int>0x200b</int>   <!-- ZERO WIDTH SPACE -->
         <int>0x200c</int>   <!-- ZERO WIDTH NON-JOINER -->
         <int>0x200d</int>   <!-- ZERO WIDTH JOINER -->
         <int>0x200e</int>   <!-- LEFT-TO-RIGHT MARK -->
         <int>0x200f</int>   <!-- RIGHT-TO-LEFT MARK -->
         <int>0x2028</int>   <!-- LINE SEPARATOR -->
         <int>0x2029</int>   <!-- PARAGRAPH SEPARATOR -->
         <int>0x202a</int>   <!-- LEFT-TO-RIGHT EMBEDDING -->
         <int>0x202b</int>   <!-- RIGHT-TO-LEFT EMBEDDING -->
         <int>0x202c</int>   <!-- POP DIRECTIONAL FORMATTING -->
         <int>0x202d</int>   <!-- LEFT-TO-RIGHT OVERRIDE -->
         <int>0x202e</int>   <!-- RIGHT-TO-LEFT OVERRIDE -->
         <int>0x202f</int>   <!-- NARROW NO-BREAK SPACE -->
         <int>0x205f</int>   <!-- MEDIUM MATHEMATICAL SPACE -->
         <int>0x2060</int>   <!-- WORD JOINER -->
         <int>0x2061</int>   <!-- FUNCTION APPLICATION -->
         <int>0x2062</int>   <!-- INVISIBLE TIMES -->
         <int>0x2063</int>   <!-- INVISIBLE SEPARATOR -->
         <int>0x206A</int>   <!-- INHIBIT SYMMETRIC SWAPPING -->
         <int>0x206B</int>   <!-- ACTIVATE SYMMETRIC SWAPPING -->
         <int>0x206C</int>   <!-- INHIBIT ARABIC FORM SHAPING -->
         <int>0x206D</int>   <!-- ACTIVATE ARABIC FORM SHAPING -->
         <int>0x206E</int>   <!-- NATIONAL DIGIT SHAPES -->
         <int>0x206F</int>   <!-- NOMINAL DIGIT SHAPES -->
         <int>0x3000</int>   <!-- IDEOGRAPHIC SPACE -->
         <int>0x3164</int>   <!-- HANGUL FILLER -->
         <int>0xfeff</int>   <!-- ZERO WIDTH NO-BREAK SPACE -->
         <int>0xffa0</int>   <!-- HALFWIDTH HANGUL FILLER -->
         <int>0xfff9</int>   <!-- INTERLINEAR ANNOTATION ANCHOR -->
         <int>0xfffa</int>   <!-- INTERLINEAR ANNOTATION SEPARATOR -->
         <int>0xfffb</int>   <!-- INTERLINEAR ANNOTATION TERMINATOR -->
      </blank>

<!--
  Rescan configuration every 30 seconds when FcFontSetList is called
 -->
      <rescan>
         <int>30</int>
      </rescan>
   </config>

</fontconfig>


local.conf
Code:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>

<match target="font">
   <test qual="all" name="rgba">
   <const>unknown</const>
   </test>
   <edit name="rgba" mode="assign"><const>rgb</const></edit>
</match>

<match target="font">
   <test name="pixelsize" compare="more"><double>10.5</double></test>
   <edit mode="assign" name="hinting" ><bool>true</bool></edit>
   <edit name="hintstyle" mode="assign"><const>hintfull</const></edit>
</match>

 <match target="font" >
   <edit name="antialias"><bool>false</bool></edit>
   <edit name="rgba" mode="assign"><const>rgb</const></edit>
 </match>

<match target="font">
   <test name="pixelsize" compare="more"><double>26</double></test>
   <edit name="antialias"><bool>true</bool></edit>
</match>

<dir>/usr/local/share/fonts</dir>
</fontconfig>

I also changed the gtk font in ~/.gtkrc-2.0 to Arial or Helvetica, and changed the jwm font in /etc/xdg/templates/_root_.jwmrc (run fixmenus), and probably the default fonts my browsers use. Can't remember if in Puppy 4.x I still had to change that other setting to get Firefox and Thunderbird to use a proper font in their menus.
Also, I changed the menu font in Openoffice, and turned off antialiasing in its settings... I posted how to do the former a couple of years back Smile

_________________
DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!
Back to top
View user's profile Send private message 
puppyite


Joined: 23 Jul 2009
Posts: 758
Location: U.S., Midwest, Central Time Zone, GMT-6

PostPosted: Tue 01 Sep 2009, 09:30    Post subject:  

disciple wrote:
Also, I changed the menu font in Openoffice, and turned off antialiasing in its settings…


I’m using Abiword so on joy there because kearning is fubar (for document text) with antialiasing turned off in: .fonts.conf Sad Thanks for the reply. Smile

_________________
Learn more about Puppy Linux: Puppy Linux FAQ
Protect your privacy: Scroogle.org - Ixquick
Back to top
View user's profile Send private message Visit poster's website 
DaveS


Joined: 09 Oct 2008
Posts: 3726
Location: UK

PostPosted: Tue 01 Sep 2009, 11:59    Post subject:  

puppyite wrote:
After experimentation here's what I've settled on for .fonts.conf:

Code:
<match target="font">
 <edit name="antialias" mode="assign">
<bool>true</bool>
</edit>
<edit name="hinting" mode="assign">
<bool>false</bool>
</edit>
 <edit name="autohint" mode="assign">
<bool>false</bool>
</edit>
<edit name="hintstyle" mode="assign">
<const>hintnone</const>
</edit>
</match>


.


I set up .fonts.conf as above, and the results aer astonishing! Everything is displaying smoother and a little smaller. Firefox is especially clear.
Thanks for such a simple fix. The daft thing is, I am running JWM, which I understood was set up by default!

_________________
Spup Frugal HD and USB
Root forever!
Back to top
View user's profile Send private message 
puppyite


Joined: 23 Jul 2009
Posts: 758
Location: U.S., Midwest, Central Time Zone, GMT-6

PostPosted: Tue 01 Sep 2009, 13:02    Post subject:  

DaveS,
You're welcome, I'm happy to help. Some thanks should go to Iguleder though because without his OP I wouldn't have a clue how to do this.

_________________
Learn more about Puppy Linux: Puppy Linux FAQ
Protect your privacy: Scroogle.org - Ixquick
Back to top
View user's profile Send private message Visit poster's website 
Sit Heel Speak


Joined: 30 Mar 2006
Posts: 2595
Location: downwind

PostPosted: Tue 01 Sep 2009, 15:01    Post subject:  

Sorry not to get back to you all in a timely fashion; I've discovered the Linux Kernel Driver Database (LKDDb) Project and, since I'm an experienced database programmer, am quite excited about it, and have decided to devote a week or two of intense concentration to the quest to bring LKDDb's goodness into the Puppy universe. So, no time to answer questions here in the detail they deserve. I will only just briefly comment:

1. My current local.conf antialiases only at size 13 pixels and larger.

2. There is definitely a difference between with and without my PET on my own 16" CRT. Perhaps a screenshot does not adequately convey it, perhaps the detailed settings in the mtPaint screen capture code are degrading the image.

3. Menu items and webpage rendering are two separate issues--gtk renderer versus the renderer the browser was compiled to use. AbiWord rendering is still another issue. PDF rendering is yet another issue. I will look into these after through with my current projects.

4. Where bci hinting (or equivalent) is compiled into cairo (or its build-chain), iguleder's simple method is the correct one to use. Where not, my PET. I foresee that as the patents expire, cairo will by default, in bits and pieces, begin to get bci or equivalent hinting compiled-in by default (obviously, this is starting to happen already, otherwise iguleder's method would not work) and everyone will meanwhile start programming to the simple convention which was stated by iguleder above. And then, when everyone has finished converting their code over to the convention and is programming a hinting facility into cairo --the new, right way-- iguleder's method will render mine unnecessary and obsolete.

5. But for now, on Puppy 4.21, my PET still gives better results. At least, on my CRT.

6. upup-466 is a woof-built Puppy (woof alpha-(9?)) which draws its source from the Ubuntu repositories. My surmise is that Ubuntu has cairo (or some key dependency) already compiled with bci-or-equivalent hinting in it, therefore addition of a PET such as mine is gilding the lily, i.e. performs hinting and antialiasing on fonting which has already had these operations performed, and so the result looks awful. I surmise that Puppy 4.12, unlike newer Puppies to 4.21, was built using Ubuntu's cairo (and/or dependencies) which is why it behaves well with iguleder's method but not mine. Newer Puppies will behave more or less well with iguleder's method, and less or more well with mine, depending on to what extent cairo has better-or-worse-quality hinting compiled in. The more skillful and up-to-date-on-his-programming-conventions the cairo-programmer was, the better iguleder's method and the worse my method will work.

And now, periscope down, back to autoconfiguration-of-kernel-compile-time-switches land...

Last edited by Sit Heel Speak on Wed 02 Sep 2009, 02:26; edited 1 time in total
Back to top
View user's profile Send private message 
disciple

Joined: 20 May 2006
Posts: 6378
Location: Auckland, New Zealand

PostPosted: Wed 02 Sep 2009, 01:40    Post subject:  

No. The screenshot I posted I took the day I posted it, running my 4.1.1 setup which uses an antique freetype package and the configuration files I posted in my last post.

Quote:
I’m using Abiword so on joy there because kearning is fubar (for document text) with antialiasing turned off in: .fonts.conf Sad Thanks for the reply.

I don't have any kerning issues with Abiword, probably because I'm using Windows fonts like Arial and they are being rendered exactly the same as they would be in Win98. I do have another problem with fonts in Abiword - they are invisible some of the time. But I believe that is an Abiword bug. The only reason I mentioned Openoffice is because it has its own settings, separate from the system-wide freetype settings. This I believe is annoying - programs should obey the system settings by default. Not that anyone else seems to believe it.

_________________
DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!
Back to top
View user's profile Send private message 
DaveS


Joined: 09 Oct 2008
Posts: 3726
Location: UK

PostPosted: Wed 02 Sep 2009, 02:10    Post subject:  

Actually Disciple, I use Open Office all the time, and their anti-alias system aint that great Sad
I too wish they could just use system defaults. Turning it off makes matters worse. On/Off/System Default would be a better menu option.

_________________
Spup Frugal HD and USB
Root forever!
Back to top
View user's profile Send private message 
disciple

Joined: 20 May 2006
Posts: 6378
Location: Auckland, New Zealand

PostPosted: Wed 02 Sep 2009, 06:59    Post subject:  

Quote:
Turning it off makes matters worse.

Only if you don't fix the rest of the problem.
test.png
 Description   
 Filesize   8.24 KB
 Viewed   1132 Time(s)

test.png


_________________
DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!
Back to top
View user's profile Send private message 
DaveS


Joined: 09 Oct 2008
Posts: 3726
Location: UK

PostPosted: Wed 02 Sep 2009, 12:00    Post subject:  

disciple wrote:
Quote:
Turning it off makes matters worse.

Only if you don't fix the rest of the problem.

Quite!

_________________
Spup Frugal HD and USB
Root forever!
Back to top
View user's profile Send private message 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Thu 03 Sep 2009, 15:47    Post subject:  

Quote:
I set up .fonts.conf as above, and the results aer astonishing! Everything is displaying smoother and a little smaller. Firefox is especially clear.
Thanks for such a simple fix. The daft thing is, I am running JWM, which I understood was set up by default!


I too am running jwm in 4.1.2. I tried that exact mod you did, and compared screen snapshots. The snapshot with the default condition (no .fonts.conf file) was sharper than the other case, just the opposite of what you found. Guess it depends on the hardware...
Back to top
View user's profile Send private message 
Anniekin


Joined: 24 Feb 2009
Posts: 186

PostPosted: Thu 03 Sep 2009, 21:41    Post subject: Interesting.  

Subscribed
Back to top
View user's profile Send private message 
disciple

Joined: 20 May 2006
Posts: 6378
Location: Auckland, New Zealand

PostPosted: Thu 10 Sep 2009, 09:08    Post subject:  

Quote:
I don't have any kerning issues with Abiword, probably because I'm using Windows fonts like Arial and they are being rendered exactly the same as they would be in Win98. I do have another problem with fonts in Abiword

OK, obviously I don't use Abiword enough... I do have kerning problems in it after all.

_________________
DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!
Back to top
View user's profile Send private message 
Anniekin


Joined: 24 Feb 2009
Posts: 186

PostPosted: Sat 12 Sep 2009, 01:25    Post subject:  

What in your opinion about sub-pixel rendering?
Code:
   <match target="font">
      <test qual="all" name="rgba">
         <const>unknown</const>
      </test>
      <edit name="rgba" mode="assign"><const>rgb</const></edit>
   </match>

Is it worth it?
Back to top
View user's profile Send private message 
disciple

Joined: 20 May 2006
Posts: 6378
Location: Auckland, New Zealand

PostPosted: Sat 12 Sep 2009, 07:40    Post subject:  

Whose opinion? All of us?
My opinion is:
- It is essential for fonts that are really designed for it (The latest generation of Microsoft fonts - Cambria and Calibri or something. Note that I have not actually seen these fonts on linux, so I can't say for sure that the effect is the same as in Windows). But these fonts should never be used because they are hard on my eyes compared to things like Arial Smile
- Old fashioned well-hinted fonts like Arial should not use antialiasing or sub-pixel rendering at small sizes. At large sizes they look better with it, but I don't really care as it isn't ruining my eyes either way. It's not costing me anything, so I guess it's worth it Smile
- BCI hinting is essential
- Badly hinted fonts should never be used.

_________________
DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 3 of 4 [47 Posts]   Goto page: Previous 1, 2, 3, 4 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » HOWTO ( Solutions )
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
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1550s ][ Queries: 13 (0.0050s) ][ GZIP on ]