Slashdot Mirror


Best Fonts for Linux Browsers?

BladeMelbourne asks: "As a web developer with a healthy love of Linux, I was wondering which fonts look great in Linux web browsers (particularly Mozilla/Netscape). Using 'Arial,Helvetica,sans-serif' just doesn't look nice. Do different distro's have different fonts? Which fonts resemble Arial/Helvetica? Which fonts are anti-aliased? Speaking of anti-aliased, does anyone know concisely how to get AA fonts with Mozilla on RedHat 8.0? I have my TTFs working, but don't seem to display correcly and look rather ugly on my display."

40 of 60 comments (clear)

  1. Use georgia ... by kousik · · Score: 3, Interesting

    ... and courier. After 2 yrs of experiments I found them to make the best combination.

    1. Re:Use georgia ... by Twirlip+of+the+Mists · · Score: 2

      Second. I'm using Georgia as my regular font-- serifs beat the pants off of sans-serifs any day, plus I love old style figures-- and Courier as my monospaced font. They look great.

      Then again, I'm also using OmniWeb on OS X, so your mileage may end up sucking because X11's antialiasing looks like chiseled spam.

      --

      I write in my journal
  2. Please do just one thing by Anonymous Coward · · Score: 5, Insightful

    You say you are a web developer, so please pick those fonts out for yourself and just for yourself. Don't pick fonts for me, I like the ones I already have thanks.

    1. Re:Please do just one thing by Twirlip+of+the+Mists · · Score: 2

      Default fonts are usually serif, which have readability problems at small size

      You have that backwards. Serif fonts are far more readable at small sizes than sans serif fonts.

      --

      I write in my journal
    2. Re:Please do just one thing by Mark+Pitman · · Score: 2, Informative
      Serif fonts are far more readable at small sizes than sans serif fonts.

      That is true on paper, but not on computer screens.

    3. Re:Please do just one thing by Twirlip+of+the+Mists · · Score: 2

      Beg to differ. If you find a sans-serif font to be easier to read than a serif font, it may be because the serif font is poorly designed, your font renderer isn't doing its job properly, or your antialiasing algorithm is fundamentally broken. (Note that most antialiasing algorithms are fundamentally broken because they use integer math instead of floating-point math.)

      In other words, if you don't think serif fonts are easier to read, then something's broken in your software.

      --

      I write in my journal
    4. Re:Please do just one thing by Mark+Pitman · · Score: 3, Informative
      OK, here's a few references. I don't know if any of these sources are considered "experts" on the subject, but they seem to make sense.
    5. Re:Please do just one thing by Twirlip+of+the+Mists · · Score: 2

      Yup. Those three links all refer to fonts displayed on computers running Windows or Mac OS 9. Neither Windows nor OS 9 could antialias fonts worth a damn.

      --

      I write in my journal
    6. Re:Please do just one thing by JimDabell · · Score: 2

      If you really care about your fonts that much (people rarely do), then use a user stylesheet. Everybody else can get what the page author suggests (which can have usability benefits; serif is easier to read at larger sizes, sans-serif at smaller sizes, for instance).

    7. Re:Please do just one thing by npietraniec · · Score: 2

      You obviously know nothing about web development. If specific fonts/font sizes are important to you, configure your browser accordingly.

      All /I/ ask is that this is made possible. Some assholes think it's a good idea to incorporate a 6 point font in an all flash website... Making the site totally not accessible to anyone using a resolution over 640x480

  3. personal preference by Satai · · Score: 3, Interesting

    I always use Konqueror with Bitstream Charter, Bitstream Courier, Adobe Times and Adobe Helvetica.

    In addition, I've found that my eyes are accustomed to having fonts with smaller spaces and no hinting, so with Xft1 I compiled with the xft-quality patch from Keith Packard, and for Xft2 I compile with the spacing part applied and then manually set /etc/fonts/fonts.conf to turn off hinting on the Bitstream fonts.

    1. Re:personal preference by Satai · · Score: 2

      Also, I forgot to mention -- subpixel rendering definitely helps keep down the fuzziness with hinting turned off.

  4. Disabling Arial by Brian+Hatch · · Score: 5, Informative
    In a recent slashdot post (I forget where) there was a reference to a Customizing Mozilla page that has a bunch of cool tricks to add to your user.prefs, etc. One of the things they noted was the problem with bad Arial fonts being installed on your machine. Here are the relevant snippets:

    Various Linux distributions have problems with fonts; in particular, Arial, used in many web pages, may map to a font that looks blocky and is smaller than the requested size. A full discussion is in bug 46415, but an easy solution for Redhat users is this:

    mv /usr/share/fonts/ISO8859-2 /usr/share/fonts.ISO8859-2 and then log out of X and log back in again.

    You can always undo this, if necessary, with the command:

    mv /usr/share/fonts.ISO8859-2 /usr/share/fonts/ISO8859-2

    It's also worth reading this excellent discussion on fuzzy Linux fonts.

    Or, add things like this to user.js in your .mozilla/.... directory:

    // X font banning: see bug 104075.
    // Ban all arial fonts, because abiword installs an ugly one
    // and there doesn't seem to be a good one available:
    user_pref("font.x11.rejectfontpattern", "fname=.*arial.*");

    // Some alternate forms for rejectfontpattern:
    //"fname=.*arial.*;scalable=.*;outline_scaled=.*;\
    // xdisplay=.*;xdpy=.*;ydpy=.*;xdevice=.*");
    // "fname=-zz-abiword.*;scalable=false;outline_scaled =false;");
    // Alternately, reject font if accept pattern does not match it:
    //user_pref("font.x11.acceptfontpattern", ".*");

  5. Oddly Enough... by ruineraz · · Score: 5, Informative

    Microsoft Verdana & Tahoma fonts. They common fonts for MS systems, and work under linux if you install the fonts. It's really hard to tell the difference between sites using IE on Windows and Mozilla on Linux with these fonts installed.

    I typically use "Verdana, Arial, Helvetica" or "Tahoma, Arial, Helvetica"

    1. Re:Oddly Enough... by Jodrell · · Score: 2
      There are a few projects to bring Microsoft's Core Fonts to Linux/Unix systems in easy steps: The license for the core fonts Microsoft released permitted them to be redistributed in an unmodified form. These packages basically download and install the fonts for you - but you can do it yourself using wget, ttmkfdir and chkfontpath without much extra work.
    2. Re:Oddly Enough... by mr3038 · · Score: 3, Informative
      I typically use "Verdana, Arial, Helvetica" or "Tahoma, Arial, Helvetica"

      I hope you don't touch the font-size. Or at least specify it as "100%" or "1em". This is important because otherwise correctly configured browsers display the characters too small.

      Way too many websites use styles like p {font-family: verdana, sans-serif; font-size: 85%;}. This rule is saying that the author of the page thinks that the page looks best when viewed with font face called "verdana" with a font size of 85% of the size the user has selected she is comfortable with. I'm ok with suggesting a font face but no way normal text should be made smaller than I've set in the preferences. This situation is caused by two reasons:

      • Microsoft decided to not provide an UI to define default font size in the Internet Explorer. Consider this being equivalent to a TV set without an option to adjust volume. Some web "designers" feel that they have to compensate the fact that the MS engineer decided to specify "too large" default font size. (MSIE does have view-text size menu but it has only 5 choices and in addition the feature has many bugs.)
      • Verdana looks better with small font sizes. The problem is, verdana looks bigger than most other fonts so the font-size "has to" be modified to be much smaller for verdana to look good. This results to really small fonts if user's system cannot provide font face called "verdana" or it's different from the one distributed by Microsoft

      The above issues, joined with the fact that MSIE is the most common browser and verdana is distributed alongside MSIE practically guarantee that change to the better isn't going to happen unless majority of web "designers" get a clue. I've already lost faith that majority of the users would have some clue (MSIE with all the latest patches applied: still 11 security holes with publicly available exploits. Scary, eh?).

      Fortunately, Mozilla does have minimum font-size setting. Unfortunately, some web sites define such a small font sizes that my minimum of 9px is hit with H1 level headers--so all headers look the same and paragraph text is the same size as all the headers.

      --
      _________________________
      Spelling and grammar mistakes left as an exercise for the reader.
    3. Re:Oddly Enough... by GiMP · · Score: 2

      Using font-size: small should not post a significant problem with any browser if implimented properly. It is true that it may provide a smaller font than the user has requested of their browser; however, the browser should render it at a slightly smaller, yet readable size.

      With the default settings of every browser I've tried (Opera5/6-mac, IE4.5/5.1-mac, Galeon/Mozilla-linux, Mozilla-mac, Netscape4-mac), font-size: small provides readable fonts..

      Not that I terribly condone the practice of making the font smaller than the user's preferences.. I personally think that everyone should have their browser properly configured and let designers make their pages accessible; however, if you must make the font smaller.. font-size: small is the safest and most accessible-friendly way to change it.

      YMMV.

    4. Re:Oddly Enough... by mr3038 · · Score: 2
      Using font-size: small should not post a significant problem with any browser if implimented properly.

      Yes, it's fine as long as it isn't used for normal text. Sure, it's still readable, but far from optimal. If you make a page and don't specify font size at all, the font size will be optimal (because I've set up my browser preferences correctly). Why to make things complicated and decrease readability by changing the font size from default? Notice that I'm not saying that one shouldn't use font sizes smaller than default for something like navigation or text based advertisement.

      I repeat my point: it's a mistake to compensate for MSIE's default settings even if you feel that that default is "too large". Some people may feel that its default is optimal (there must be some reason for the decided default size) and changing the font size from it makes the text look too small [or large]. In addition to those MSIE users, anybody with correctly configured browser also sees text too small.

      This issue is often compared to a Joe Sixpack calling local TV station and asking them to turn the volume down because it's too loud. Do you think the local TV station would do that, or do you think they would tell the user to turn down the volume level in his own TV set? You can be pretty sure that the former would happen in reality. But why are web "designers" thinking they should turn the volume own instead?

      --
      _________________________
      Spelling and grammar mistakes left as an exercise for the reader.
    5. Re:Oddly Enough... by npietraniec · · Score: 2

      Microsoft decided to not provide an UI to define default font size in the Internet Explorer. Consider this being equivalent to a TV set without an option to adjust volume. Some web "designers" feel that they have to compensate the fact that the MS engineer decided to specify "too large" default font size. (MSIE does have view-text size menu but it has only 5 choices and in addition the feature has many bugs.)

      I'm so SICK of hearing people bitch about this. Maybe you morons should use a different browser if your current shitty one doesn't support such rudimentary features. It's not like there's not better (& free) alternatives out there.

      "But I'm at work and we don't have mozilla" download the zip file, extract it to your desktop, and run the executable from there. It works fine.

  6. Re:So why's this still an issue? by nathanh · · Score: 2
    I may be trolling in this, but I've always wondered why this is an issue at all? Why hasn't someone taken the time to make the UI more User-Friendly?

    They are, but it's a difficult problem and it's taking a lot of time. The situation is significantly better than it was 2 years ago, and hardly recognisable to the mess we had 5 years ago.

  7. Freetype 2.1 by jdclucidly · · Score: 2
    I could have sworn that RedHat was distributing Mozilla with anti-aliasing support via a GTK+ 1 patch to support Freetype. Certain fonts do not anti-alias and I have found that you may need to set these options manually in Mozilla > Edit > Preferences > Appearance > Fonts > Fonts for: Western and Unicode:
    • Proportional: Serif
    • Serif: Georgia
    • Sans-serif: Arial
    • Cursive: Lucida
    • Fantasy: PostAntiqua
    • Monospace: Courier New
    You installed the Microsoft Fonts Add-On .rpm, right? I'm a Gentoo user, myself ... use the source, Luke!
  8. Use the XFT RPM by linuxkrn · · Score: 4, Informative

    The easist way to get Mozilla to use rpms that had support for XFT (AA Fonts). for 1.2.1 http://ftp.mozilla.org/pub/mozilla/releases/mozill a1.2.1/Red_Hat_8x_RPMS/xft/ Of course, you could always download the source and compile it with --enable-xft. :) As for my own pref, I like Luxi Sans. AA support looks great on mine, and even the menus use the default font. Nice when you are running 1600x1200+!

  9. Antialiasing and fonts by 0x0d0a · · Score: 2

    For antialiasing, you're going to have to compile your own mozilla -- Red Hat's packages aren't built with --enable-xft.

    For fonts, I say Verdana and Epsy Sans are the two best proportional on-screen text fonts. Unfortunately, neither can be freely distributed.

    1. Re:Antialiasing and fonts by JoeBuck · · Score: 2

      Incorrect, Verdana can be distributed, though only in the form Microsoft originally packaged them in. See this Sourceforge project, however, for an easy way to get these fonts installed as an RPM. Or install the Debian msttcorefonts package.

    2. Re:Antialiasing and fonts by Captain+Large+Face · · Score: 2

      The Debian msttcorefonts package was broken last time I tried to use it. If I remember correctly, it connects to an FTP server to download the TTF files. Unfortunately, the owner of the FTP server has either moved or deleted these files from their previous location.

    3. Re:Antialiasing and fonts by Captain+Large+Face · · Score: 2

      Just tried it again (it had been a while). Works perfectly.

  10. Best Fonts for Linux Browsers by jsse · · Score: 3, Informative

    Utopia

  11. use standard old fonts by Anonymous Coward · · Score: 2, Informative

    Do not use Arial or Times New Roman, Courier New or Georgia, use just Courier, Helvetica, and Times. Arial etc. are Microsoft fonts that should just go to hell. Even though Apple recommends Arial, Times New Roman, Georgia for the Web, they are nonstandard fonts when it comes to publishing.

  12. Mozilla with XFT and GTK theme support by Reality_X · · Score: 4, Informative

    mkdir moz1.3
    cd moz1.3
    lftp ftp.mozilla.org:/pub/mozilla/releases/mozilla1.3a/ Red_Hat_8x_RPMS/xft/RPMS/i386
    mget *
    [close mozilla]
    rpm -Uvh *

    You now have a beautiful browser.

    1. Re:Mozilla with XFT and GTK theme support by HRbnjR · · Score: 3, Informative

      Heh, lftp, that's a new one for me, thanks! It looks like we all go with what we know, that is, heres the little Makefile I use:
      ---
      RSYNC_RHOST := archive.progeny.com
      RSYNC_RDIR := mozilla/releases/mozilla1.3a/Red_Hat_8x_RPMS/xft/R PMS/i386/
      RSYNC := rsync -v
      RPM := rpm
      rsync:
      $(RSYNC) -r $(RSYNC_RHOST)::$(RSYNC_RDIR) .
      RPMS := $(wildcard ./*.rpm)
      upgrade:
      $(RPM) -U $(RPMS)
      ---

  13. Use MS core fonts with Mozilla-ttf by wotevah · · Score: 3, Informative

    This has been on ./ very recently. In addition to downloading the ttf mozilla rpm for RH8.0, you also need to "build" and install the MS core font set for the web from corefonts.sourceforge.net.

  14. Antialiased Fonts in Mozilla by JimR · · Score: 3, Informative

    I did the following to enable antialiased fonts in Mozilla - I didn't compile my own Mozilla, but I do tend to use recent nightlies:

    // for anti-aliased fonts
    pref("font.FreeType2.enable", true);
    pref("font.freetype2.shared-library", "libfreetype.so.6");
    pref("font.directory.truetype.1", "/home/jim/apps/mozilla-fonts");
    // if libfreetype was built without hinting compiled in
    // it is best to leave hinting off
    pref("font.FreeType2.autohinted", false);
    pref("font.FreeType2.unhinted", false);
    // below a certian pixel size anti-aliased fonts produce poor results
    pref("font.antialias.min", 6);
    pref("font.embedded_bitmaps.max", 1000000);
    pref("font.scale.tt_bitmap.dark_text.min", "64");
    pref("font.scale.tt_bitmap.dark_text.gain", "0.1");

    I had the libfreetype6 Debian package installed.

    I made made my own font directory and copied the *.ttf files that I needed to it, because one of my more esoteric fonts would cause Mozilla to crash.

    In the end I gave up on anti-aliased fonts because they gave me a headache unless I made them much bigger than I'm used to with my normal "crisp" X11 fonts.

    --
    #exclude <ms/windows.h>
  15. Verdana by blwrd · · Score: 2, Insightful
    Both Verdana and Tahoma are great fonts. Personally I prefer Verdana a bit more as for me it seems to be more readable in small size.
    But then again, when you do your website, it is usually enough to define the font family that you want to be used, rather than the exact font.
    Althought my magick line in css is usually
    font-family: Verdana, sans-serif;
    .. to prefer that verdana bit more over other sans-serif fonts. :)
  16. Arial != Helvetica by Captain+Pedantic · · Score: 2

    Do not use Arial. Arial is a pig ugly font. It does not look like Helvetica. It is a second rate knock-off.

    Read this and this, and don't use Arial again.

    While those pages are loading, how can you say you are a webdesigner, when you haven't learnt that web pages are not wysiwyg? I bet your pages look shit.

    In any case. Don't specify Arial, or at the very least, specifiy it last. Put "san serif" in the list in front. Arial is an abomination, and should be killed. If you want Helvetica, say so, but don't ever imagine that Arial can take the place of Helvetica.

    --

    None are more hopelessly enslaved than those who falsely believe they are free. Johann Wolfgang von Goethe.
  17. This is the users responsibility by mnmn · · Score: 2, Troll


    They have to setup nice TTFs and AA fonts. This responsibility has been dumped onto the users by the distros who couldnt care what text looks like.

    So web developers shouldnt bend and break to be Linux compatible, Linux has been far more standards based than other OSes, and should too in font display. Web developers already are trying to be flexible to allow IE weirdocities, lets not let Linux do the same to them.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
  18. Verdana,Arial,Helvetica size=-1 by Tom7 · · Score: 3, Interesting

    I've been using face="Verdana,Arial,Helvetica" size=-1 for a few years, and that seems to work right in the default install of all the computers I use. (My school's sun lab included.) Arial looks really bad in Mozilla on linux.

    Also, do yourself a favor and use CSS. I use this, which also displays text at the right size on Macs (which like to make fonts smaller when browsing the web):

    P { font: 11px Verdana,Arial,Helvetica }

    I can't say much for what the "right way" to do this is without offending those folks who believe the web should not have any markup for design.

    1. Re:Verdana,Arial,Helvetica size=-1 by nagora · · Score: 2
      I've been using face="Verdana,Arial,Helvetica" size=-1 for a few years

      I agree with the earlier poster: Arial should be last after "sans serif"; it is the ugliest font in common usage today. At home I have Opera set to use Gill Sans (anti-aliased under X) for the base font but obviously I don't expect many people to have that setup for reading webpages.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  19. Re:So why's this still an issue? by MrResistor · · Score: 2

    may be trolling in this, but I've always wondered why this is an issue at all? Why hasn't someone taken the time to make the UI more User-Friendly?

    It has been done. The font tool in the KDE Control Center works great for enabling AA and installing new fonts.

    Oh, and whatever happened to unifying all these various hacks into one standardized way of doing things. How many ways are there to enable anti-aliased fonts? How many ways are there to make the text readable?

    I have no idea how many ways there may be, but unifying them all into one tool is anathema to the OSS developement process. Every single OSS tool has competition, and I think that is vital to the continued health of the community.

    --
    Under capitalism man exploits man. Under communism it's the other way around.
  20. XFree 4.2 ships with good looking truetype fonts by Nailer · · Score: 2

    ...as standard.

    They're called Lucidux or Luxi, and they're installed into /usr/X11R6/lib/X11/fonts/TTF/luxi*

    Use them. They'll become the standard fonts for Linux web browsers once the rest of the distros get XFree 4.2

  21. Better fonts in X the easy way by FeatureBug · · Score: 2

    Folks love to comment how ugly they think GUIs look under X in Netscape/Mozilla, and the same folks often suggest the solution is to use anti-aliased fonts. Sure, anti-aliased fonts are good.

    However, I'd like to share my experience with a very simple alternative method of getting really great looking fonts in X without installing or changing any software.

    • Change your X11 display resolution so pixels are about the same size as the dot pitch of your monitor. For a dot pitch of 0.25mm, the ideal resolution may be 1600x1200.
    The jagged edges of the unaliased X fonts totally disappear. Quasi font anti-aliasing is as good as true anti-aliased fonts but without the hassle! If I had my macro lens handy I'd take a photo of my monitor screen running 1600x1200 and show you the incredibly smooth font outlines I've got with this very ordinary variable width Times Roman 18pt font in Netscape. Using this method I've got perfect results on every CRT display I've tested including cheap Iiyama CRT displays like 19" (USD$150), 17" (USD$120) and 15" (USD$90) monitors. If I reduce X to a resolution much less than 1600x1200 like 1024x768, of course, the jagged edges return.