Isn't it strange that this gets posted as I'm futzing with my fonts? I open konqueror to test them and I see this!! Just confirms my fears that THEY are watching my every move...
"Isn't it strange that this gets posted as I'm futzing with my fonts?"
Not really. I think it makes sense - Linux users are often in the midst of fiddling about with some part of their system.
Not trying to be inflammatory, now, 'cause I know all about the embedded stuff, the server stuff, etc. It's just that this particular OS attracts tinkerers.
--
Writers imply. Readers infer.
Re:Strange
by
KnightStalker
·
· Score: 3, Informative
No kidding. I hosed my system this morning with a little "I'll install True Type fonts... it can't hurt anything..."
Now, KDE doesn't start, even after reinstalling it three times and reinstalling X once.
Here I am, looking at/. from within FVWM, and the gods are taunting me.
-- * And remember, it's spelled N-e-t-s-c-a-p-e, but it's pronounced "Mozilla."
Now that kde is being mean and not working, try out other wm's if you haven't before. I use fluxbox and will never use anything ever again. Besides, with only 128mb of ram, kde3 is a bit painful.
I agree, to the extent that "superior" is defined as "is less annoying, after hours of configuration work."
My big problem with "winXP Professional", is that, a, i can't open 5 or 6 terminal windows in one tabbed app, and b, if I ssh to a different server and start emacs, I don't get a nice pretty X window:-)
-- * And remember, it's spelled N-e-t-s-c-a-p-e, but it's pronounced "Mozilla."
Re:Strange
by
rob_from_ca
·
· Score: 3, Insightful
Yeah, statistically speaking the average Linux user spends 75.2% of their time at their computer trying to make their fonts look good, so it's actually not that strange at all.:-)
Re:Strange
by
Anonymous Coward
·
· Score: 1, Informative
if I ssh to a different server and start emacs, I don't get a nice pretty X window:-)
You're doing something wrong, then.
I do.
Another one of those newbies who can't tell a desktop environment from a window manager.
A wm is essential to use X -- though you can open windows in plain X it gets hard to move them -- a desktop environment adds possibility nifty but completely optional features
-- He saw some dirty arabs and fired. Too bad it was just some friendly kurds, BBC reporters and his fellow cowboys.
On Mozilla's website, under the nightly/experimental directory, there are RedHat 8.0 rpms for Mozilla 1.2 beta with XFT support. Now Mozilla fonts look the same as in KDE/GNOME2 programs!
--
"I keep looking in the want-ads under 'revolutionary'
but there don't seem to be any listings.. "
RH8 does have some beautiful fonts. But are most linux users concerned with fonts. I guess this is where linux is divided among those who like eyecandy and those who don't.
The former probably also thinks OSX is the coolest.
Spoken like somebody who never had to deal with Netscape Communicator 4.x in Linux four or five years ago.:)
Good fonts are a good thing whether you like eyecandy or not. Obviously this is less of a problem when you're just sitting at an 80x25 console all the time, but eye strain can be a serious problem.
Getting fonts right isn't just about
installing them. Examine the
screenshot from the article, and look at
the Tahoma sample text (fifth from top).
It is clear that the "q" and "r" and "Q"
and "R" need more space between them. The
"c" and "d" of Thorndale and Times New
Roman, on the other hand, have too much
space between them. Note also that you
can probably spot these anomalies without
even reading the text closely.
Also, it's not hard to confuse Qt (and maybe
also Gtk) or a window manager with fonts.
Pick a strange font or size, and the
resulting size of buttons and such often
become ugly or overlap incorrectly with
decorations.
So, no, despite FreeType and friends (which
are wonderful), we're not done with fonts yet.
Redhat 8 has serious issues for any web developer. I got burned buying it and have uninstalled it.
No apache 1.3x and perl 5.6x support to top it off. No perl 5.8 is not source compatible with perl 5.6 code. It is %90 but thats not good enough in alot of situations. My college text "Perl how to program" by Deitel & Deitel has many examples that will not compile properly on rh8. I tried it myself. I believe most of the problems have something to do with the new scoping rules for variables since that is what perl 5.8 complains about the most.
How about cgi support for apache2 in redhat 8? Redhat 8 does not even install mysql by default and installs the more postgreSQL utilities by default since redhat database uses postgresSQL. Mysql support is lacking in this version since alot of perl servlets use mysql to retrieve and store information.
No Java 1.3x support. Hell no java 1.4x support either! Licensing issues have got in the way.
I am not bashing redhat and causing a flamewar per say but rather just stating that redhat is not for everyone.
Yeah, I just grabbed Mozilla 1.2b yesterday and compiled with XFT support on RH 8.0.
But the AA fonts are too thick and damn blurry, plus the Gnome2 font properties doesn't affect Mozilla(i.e. "Constrast" option for AA fonts has not effect on moz). And EVERY font is AA'd, including menus and dialog boxes, which makes everything look muddy. It would be nice if AA fonts were only enabled for 16pts or higher. Also, with AA fonts, Mozilla is a lot slower at redrawing pages compared to all the other apps with AA enabled(OpenOffice,Nautilus,etc).
I hope people don't shoot me in the head, "RTFM and change/etc/blurryfontsoff.conf!". After reading all the howto's on fixing the butt-ugly fonts and using XftConfig, I don't have more time to invest to determine how to configure AA fonts in RH8.0 using fontconfig etc.
I mean, it just FONTS. Not a bloody driver I'm trying to get to work.
But are most linux users concerned with fonts. I guess this is where linux is divided among those who like eyecandy and those who don't.
Readable fonts are not eyecandy. Fonts are the
primary mechanism for translating computer information
into a form compatible with your brain. They are
therefore the most important visual part of the UI.
Going the other direction, you wouldn't accuse
of a good quality keyboard as being "fingercandy".
If readable fonts weren't important, bookstores
wouldn't sell anything more expensive to print
per word than the stock listings section of a newspaper.
How can someone settle for sloppy seconds in fonts? I mean, Linux fonts are one step away from being garbled gibberish!! You shouldn't HAVE to settle for anything less.
Meanwhile, the Mac has had nice looking fonts (hey guess what, the Chicago and Geneva fonts are still around!) since 1984.
Looks like Linux is 18 years behind the mainstream. Not like that surprises me or anything.
Fonts are important
by
Joey7F
·
· Score: 4, Insightful
I know someone will get on here saying (or at least think it), can't we concentrate on making the 2.5 kernel as stable as 2.2.x. Fonts are just for making things look 'purdy' which doesn't help if you are crashing, blah blah blah
Fonts are very important.
Fonts are one of the last barriers to a linux migration. That is also one of the first (negative) differences people notice on my monitor.
Never underestimate the lure of a goodlooking UI on the average user!
--Joey
Re:Fonts are important
by
Soul-Burn666
·
· Score: 5, Interesting
Ugly fonts are harder to read means you become less productive.
'nuff said.
-- ^_^
Re:Fonts are important
by
stratjakt
·
· Score: 1, Interesting
> Fonts are one of the last barriers to a linux migration.
Your average user doesn't know shit about whether fonts are antialiased or cleartype or whatnot.
No, a desktop thats as easily configurable and usable for an average user as a windows or mac osx is.
Not that I want to see linux become Windows - which seems to be where the momentum is. I would love to see it evolve into a truly superior desktop platform, through the creativity of the self-styled 'geniuses' coding for it.
If Mac could build OSX out of BSD, why is linux still a server platform with a slipshod desktop grafted on top? I guess its the lack of a single vision and a focused effort to make it happen.
Too many cooks. Oh well. It'll probably always be a good router or fileserver.
--
I don't need no instructions to know how to rock!!!!
Re:Fonts are important
by
wazootyman
·
· Score: 1, Interesting
I don't consider myself to be just the 'average user', yet I find attractive fonts to be VERY important. It's one of my biggest peeves with my Sparc/Solaris boxes. I really do think some nice fonts would REALLY clean up the unix/linux interfaces in general.
Re:Fonts are important
by
scotch
·
· Score: 5, Funny
I agree, with some modifications:
:%s/user/man/ :%s/fonts/women/g :%s/my Sparc\/Solaris/ugly\/skanky/ :%s/unix\/linux interfaces/shit hole apartment I live in/
-- XML causes global warming.
Re:Fonts are important
by
mindstrm
·
· Score: 3, Interesting
Really.
Well, most users I know who have windows Xp and a laptop can certainly tell if cleartype is turned off once it has been turned on.
I run a 1600x1200, 15.1" lcd with Cleartype, and with Windows set to 120DPI. I can't believe I'm saying it, but the fonts are leagues better looking than any other system I can get my hands on. Microsoft did something right.
This is so easy to read and so smooth looking, I've actually given up using an X desktop whenever possible. I would rather edit in Codewright in windows than work with the ugly fonts in X. IT's that much easier to read and easier on the eyes.
This is the first system I've ever had where I can really say the fonts look georgeous.
Re:Fonts are important
by
primus_sucks
·
· Score: 1
Right, Linux is already way more stable than it's major competitor. Developers have already figured this out - now time to convert grandma!
Hell, it's nothing about "average users" and UI-prettiness. It's about making sure you don't destroy your eyes reading text on your computer! That said, Linux fonts have been great for a long time. If you're fonts look bad, you're doing something wrong.
-- A deep unwavering belief is a sure sign you're missing something...
Take a look at my post about FreeType2 CVS. I'm in the same situation, and I actually prefer the FreeType rendering these days, even though sub-pixel AA isn't working with FreeType2 CVS (it's a very subtle effect, a lot of ClearType's improvement comes from a better algorithm for AA rather than the sub-pixel rendering).
-- A deep unwavering belief is a sure sign you're missing something...
Hear hear. The only way I can ever stand to use Linux at all is to ssh into it from Windows. While emacs looks the same pretty much everywhere, Web browsing is really annoying without proper fonts. And seeing as I program websites for a living, I have to browse a lot...
Well, if you are a Red Hat user you don't have to do anything wrong, you just have to have an older distro. Fonts in Mozilla under Red Hat 8.0 are pretty ugly unless you follow the font-deuglification howto. Then they are great.
Red Hat 8.0 seems fine to me so far, but I still want to add the ones in the article just so I have everything I might want for OpenOffice in the future.
Never underestimate the lure of a goodlooking UI on the average user!
Why not underestimate the lure of a goodlooking UI on an advanced user?
As an advanced [computer] user I enjoy configuring every aspect of my linux box, including the way it looks!
-eniacx
Re:The Before and after shots look backwards
by
twistedcubic
·
· Score: 1
Maybe there should be three picture? The one without and aliases (#930, helvetica and tahoma look sloppy), the fuzzy blurry one with antialiasing (#929) and one more. 929 still looks pretty fuzzy on my LCD screen.
Re:The Before and after shots look backwards
by
Qrlx
·
· Score: 2
Strange, the after (930.png)screenshot looks a lot better to me. All the fonts are at least as good if not better. There's less of those alias pixels evident. The fonts look a little thin, but sharp.
I'm on a Dell Inspiron 7000 running Windows 2000. That adds up to 9000, by the way. Maybe with a different combo of hw and os, I would see something differnet. Such as a big smiling Happy Mac icon.
They should build a "Do you want your fonts to look pretty?" wizard into the Linux installer. Because it's gonna look different on different hardware.
Re:The Before and after shots look backwards
by
skroz
·
· Score: 2
It's probably you. By default, MSIE will scale large images down to fit on screen, thus royally screwing up the images. Turn this feature off to see the proper screenshots.
-- --
Minds are like parachutes... they work best when open.
Re:The Before and after shots look backwards
by
mhesseltine
·
· Score: 2
And if I'm viewing this in Mozilla 1.1 at 1024x768 on a Geforce2 MX 400, then what? I can see how the definition is clearer on the after, but it also seems to be somewhat pixelated. Again, maybe it's just me.
Re:The Before and after shots look backwards
by
dhanav
·
· Score: 1
Yes I also thought the same when I saw the pictures. In fact I re-read the article to see if I was wrong. Seems that the anti-aliasing has been turned *off* in the "fixed" screenshot.
Also at the end of the article the following appears:
Note, several readers have pointed out that this technique seems to break anti-aliasing. It does, but not universally. Some fonts will have it and some won't.
So I think it is the case that, the screenshot was taken with one of those fonts that "dont have it".
If that is the case then, the author must have chosen the fonts wrongly !!!
Re:The Before and after shots look backwards
by
Elladan
·
· Score: 1
It's not just you. Well, except that the second one actually does look better, really...
Look at them under a magnifier. The first screenshot (the before) has antialiasing turned on. You can also tell this by looking at the 2 at the bottom. It's been antialiased into complete garbage, and is missing an entire stroke.
The second screenshot (after) has antialiasing turned off. This means that the spacing is a little less well-hinted, but on the other hand, you can at least see the strokes, and it doesn't look that blurry.
whatever happened to symlinks?
by
CableModemSniper
·
· Score: 5, Insightful
The author recommends you install the fonts in 2 or 3 different places. Whatever happened to installing them in one spot and symlinking to the others? Also removes the need to go thru the whole copy to the other directories rigamorale everytime you reinstall/upgrade.
-- Why not fork?
Re:whatever happened to symlinks?
by
AltGrendel
·
· Score: 3, Interesting
Not everyone is an admin and understands the usefullness of symlinks, seperate filesystems, and having (and acutally properly using)/usr/local.
I've had some "seasoned" admins that I've worked with for a few years actually look suprised when I mentioned that you could (gasp) mount/usr as a read only file system if you really needed to protect it.
-- The simple truth is that interstellar distances
will not fit into the human imagination
- Douglas Adams
Re:whatever happened to symlinks?
by
CableModemSniper
·
· Score: 1
*I*'m definitely not an admin. I'm a college freshmen who uses Linux. Most people use shortcuts right? I look on symlinks as kinda really useful shortcuts.
-- Why not fork?
Re:whatever happened to symlinks?
by
Art+Tatum
·
· Score: 1
Good grief! Now, will someone remind me again why I'm "too inexperienced" to get a job doing basic sysadmin?
Licensing Issues
by
bookroach
·
· Score: 3, Informative
-- Chicago2600.net more than a lifestyle, its a survival trait.
Am I the only one...
by
teamhasnoi
·
· Score: 5, Funny
who doesn't like the 'fuzzy' fonts? If you turn Clear Type on in XP or use IE for OS X the fonts seem to be *harder* to read. (to me) I want fonts to be antialiased on paper, not on the screen.
If you don't have ClearType or font smoothing, you can approximate the effect.
Just smear Vaseline evenly over your screen - voila! Antialiased fonts!
Aye. ClearType on my laptop rules. When I VNC to said box on my work CRT, however, everything looks nasty.
-- Game... blouses.
Re:Am I the only one...
by
Quarters
·
· Score: 5, Informative
I want fonts to be antialiased on paper, not on the screen.
You don't quite get the concept of anti-aliasing, do you? Aliasing is the stair-step pattern you get on non-orthogonal lines on a bitmap based display (e.g. a CRT or LCD). Anti-aliasing is the apparent removal of those artifacts by blending the line's color with the color behind it.
Printers do not anti-alias printed lines on an offset press. You gain sharpness in printing by increasing the resolution of your source material. A 1200 dpi (or greater) typesetter (or direct to press digital system) will create typography that is, for all intents and purposes, perfect.
Asking for anti-aliased letters on a printed page is like asking to buy someone's used Yugo. It's both dumb and useless.
Let me start by saying that I *despise* Windows XP, and not because I'm biased against Microsoft. I dual boot my desktop machine between Windows 2k and Linux and I have to say that the two are comparable in stability and performance (ie, neither ever crashes). I got XP Pro when it came preinstalled on my new laptop, and it is total crap. Applications crash far more often under XP with the *same* version as under 2k and I've seen the entire OS go down more than once in what little I've used it. And XP runs much slower than 2k does on my slower desktop machine! With UI bugs galore!
So, I basically use my laptop for Gentoo Linux now and only boot to XP when I need to use one of the few programs I have no replacement for under Linux (like Photoshop and Freehand). But, much as I dislike XP, I have to say that ClearType looks incredible on my laptop screen. It's the sharpest I've ever seen fonts (with the possible exception of Macs that friends had).
Now, why can't Linux have this kind of functionality? After much work, my fonts look pretty good in Fluxbox and various applications. But they still don't even come close to ClearType and I still often see misrendered fonts, etc. I personally think that X would benefit greatly from having some higher level functionality rolled into it (like fonts) so that fonts would look great in all apps with minimal effort. I know that isn't what X is meant for, but font rendering is pretty basic and necessary for most any GUI.
Check out Red Hat 8.0 and see what they did to fonts. XFT 2 rocks. The fonts are on par with Windows XP Cleartype which I have installed along with RH8 on my laptop. Here is a screenshot:
Now, why can't Linux have this kind of functionality? >>>>>>>>>> It does. Download freetype2-current from ftp.freetype.org/pub/unstable, install it, make sure there are no other freetype libs on your system (rm -rf/usr/lib/*freetype*/usr/X11R6/lib/*freetype*) and get some nice Type1 fonts (only $100 for the 65-font core collection from Adobe) and you'll be in heaven.
-- A deep unwavering belief is a sure sign you're missing something...
Re:Am I the only one...
by
Anonymous Coward
·
· Score: 1, Informative
Too bad that's exactly what inkjet and laser printers do to overcome the limitations of the media or lower physical resolution to improve text output. Ever hear of iRet?
Interesting about non-orthogonal lines causing a stair-step pattern. Does that mean if all of my lines were in a plane 37 degrees from horizontal, they would not exibit a stair-step pattern on the screen?
maybe... but I love Clear Type on my laptop. I can read the litte footnote numbering in my essays and italic text is so much more readable, but I would agree that some fonts do come across as a bit fuzzy
Re:Am I the only one...
by
Ninja+Programmer
·
· Score: 2, Informative
I want fonts to be antialiased on paper, not on the screen.
You don't quite get the concept of anti-aliasing, do you? Aliasing is the stair-step pattern you get on non-orthogonal lines on a bitmap based display (e.g. a CRT or LCD). Anti-aliasing is the apparent removal of those artifacts by blending the line's color with the color behind it. You don't quite seem to understand computer monitors, and human perception. Whether or not a particular solution to anti-aliasing works well or not, is dependent on the resolution you are at and the dot pitch of your monitor.
As the resolution drops below the natural resolution of the monitor (dictated by its dot pitch) the typical anti-aliasing strategy of proportional sampling becomes percieved as smudging. For very small fonts this will actually worsen their appearance.
As the resolution increases above the natural resolution of the monitor, the effect of anti-aliasing becomes unnoticable. I.e., its not worth the processing power to do it.
Anti-aliasing by proportional sampling really works best if the desktop resolution is optimally set according to the dotpitch of the monitor. For 0.28, for example, 1280x1024 is the resolution you should pick. The reason is because that monitor is already doing a form of proportional sampling close to the resolution of the actual pixels. By performing the proportional sampling in the source pixels, it improves the accuracy of the sampling (from an information theory point of view) that the monitor performs.
Anyhow the point of all this is that depending on the resolution the end user has set, and the actual dot pitch of their monitor, they can actually see "anti-aliased" fonts as looking worse (typically smudged.)
Re:Am I the only one...
by
datadictator
·
· Score: 1
F|rankly I have to concur here. XP sucks badly. Three times in the third week the system went into a dead crash. So far the only thing I can find seem to be a corrupt mp3 somewhere in my collection that makes winamp go bonkers - but then again the same happened whilest in games without mp3's a couple of times. And what's worse is that you don't even get the (minute) oppurtunity its predecessors had offered to kill the haywire app. The whole system goes into a complete input ignored freeze and you are forced to do a hard reset.
WinXP only appears more stable because the no longer use a blue screen to advertise a crash - the just pretend it's your keyboard.
For the record I since wiped it and I am back to Linux only, the same mp3 list here - never ever seen xmms crashed (not to mention it sounds better)
None of what you said had anything to do with my discussing the fact that he wants anti-aliased fonts on items printed on paper.
It has nothing to do with screens or monitor resolution. I was talking about offset presses.
Well actually it does. Because as I said, when the resolution goes above the dot pitch of the monitor, anti-aliasing is a wasted effort. This is because the smudging of the sampling is at a sufficiently macro-level that better sampling of what essentially are "sub-pixels" doesn't actually change its appearance.
The fact is that offset, and printing presses have far and away higher resolution than any display monitor. My 19" monitor essentially displays about 71 pixels per inch, while printers can do something closer to 1200 dots per inch.
The fact is, the resolution of printed material, at its highest quality setting challenges the resolution of the human eye. One is practically unable to see the "pixels" at which the printing press works at, and therefore we again run into the situation where anti-aliasing is a wasted effort, since the human eye will sample it at a macro level.
Now if you are printing.JPGs or.GIFs which just naturally have a much lower resolution than what your printer is capable of, then you will typically end up in the opposite case again, where the printer's resolution is far above that of the source image, and anti-aliasing will appear as smudging.
Actually, I'm running Freetype 2.1.2 under XFree86 4.2.1, and I have the subpixel hinting because I compiled everything myself (it does help). I'm using the exact same fonts as I do under Windows XP because I simply mounted my NTFS partition and copied all the fonts that came with Windows. I'm using the correct fonts (I checked), and I have tweaked all my applications like Mozilla, OpenOffice, etc. to use them. And my fonts DO look loads better than they've ever looked in Linux before. Believe me, I've put a lot of effort into beautifying my Linux font rendering.
But: they still don't look quite as nice as ClearType does under XP with the same fonts and the same laptop. They look pretty good, but they still aren't as sharp and readable.
Main things I think still need improvement:
1. Ironing out the occasional font rendering glitches I've seen under Freetype2. Sometimes my fonts are just plain misrendered under X (glitches like parts of letters missing, etc).
2. Integration/standardization of font interfaces across different applications: I shouldn't have to individually tweak every application under Linux with special settings to make the fonts look good (for example, having to set the point size ranges, hinting, etc in Mozilla or OpenOffice). All applications should just ask the central font renderer for these things without me having to go in and tell them to do that.
I'm not saying that Linux has no hope, because it's gotten much much better in the last little bit. And I'm going to continue using Linux as my main OS regardless. I'm just saying that this area still needs some work before it can match Microsoft, much as I loathe them. If I had any desire to boot into XP I would take screenshots to show you the difference and prove that I actually have my Linux fonts set up correctly (I do). Someday I'll get around to doing that and I'll put them on my site, but not today.
AA will kill your eyes
by
RomikQ
·
· Score: 5, Interesting
Well, personally, I prefer to read text without AA, because anti-aliased text is too blurry. Sure it looks pretty on screenshots and you can impress al your friends, but really, when I have to read large amounts of text from a pc screen my eyes get tired twice as wuickly with AA switched on. Sharp edges help.
Now, merely having TTFs or anti-aliasing isn't enough. Take a look at this screen shot of TTFs in an OpenOffice.org document. They're clunky and blocky and basically impossible to distinguish from each other. However, with a bit of tweaking we can make them look distinct, slick and refined, as you can see in this screen shot.
I think everyone agrees that the first one is horrible. And the second... well maybe it's just me, but I can't see a difference between their tweaked AA and my own no-tweaked non-AA...
-- Join the elite! Post at score:2! Ghostwheel is online.
Re:AA will kill your eyes
by
evilquaker
·
· Score: 1
I think everyone agrees that the first one is horrible.
I don't... could you please explain what's horrible about it? I flipped back and forth between the two pictures many times, and aside from a little blurriness with the first one, I couldn't see much different. What am I supposed to be looking for?
-- To within half a percent, pi seconds is a
nanocentury. -- Tom Duff
Re:AA will kill your eyes
by
mindstrm
·
· Score: 5, Interesting
If your antialiasing is blurry, then it's just not the right one for you.
Proper antialiased fonts are NOT blurry, and ARE easier to read than their blocky counterparts.
The reason screenshots of subpixel antialiasing look like shit is because you aren't using the same display to see them. If I took a screenshot of my 1600x1200 laptop screen, and you display it on your 1600x1200 monitor, the fonts will look crappy to you, because the subpixel rendering is tuned to the exact screen I have, and requires an LCD to boot. Even if you have a 1600x1200 LCD, it may not look the way it looks to me, because different LCDs display things different ways; that's why there are ways to tune the rendering to look right on your display.
Re:AA will kill your eyes
by
Anonvmous+Coward
·
· Score: 3, Interesting
"Well, personally, I prefer to read text without AA, because anti-aliased text is too blurry. Sure it looks pretty on screenshots and you can impress al your friends, but really, when I have to read large amounts of text from a pc screen my eyes get tired twice as wuickly with AA switched on. Sharp edges help."
Hrmm. Does Windows 2000 do it's font anti-aliasing differently then? (no, not Cleartype, just basic anti-aliasing) I haven't used Linux a whole lot so I can't really compare the two. I'm just curious if Win2k's idea of AA is different than KDE or Gnome's?
Anybody comment on that? If they are different, and Windows looks noticably better (My text isn't blurry), then what's MS doing different?
Is it possible that your monitor is a piece of shit and has a low DPI? I've seen AA fonts look like ass on monitors before, simply because the monitor sucked and had hugeass pixels/high DPI (like.28 or something) and each pixel bleeded into each other, rendering a horrendous appearence.
-- ~/ssh slashdot.org
ssh: connect to host slashdot.org port 22: too many beers
The difference between Windows machines and UNIX machines with XFT is that Windows only antialiases fonts over 12-14 points in size. UNIX/Linux on the other hand, by default in XF86 4.x will render all fonts antialiased (like Mac OSX, if I am not mistaken). It is a simple tweak that must be made by adding a few lines to the "XftConfig" file to turn antialiasing off on smaller fonts (you can tweak these numbers to your own preferred levels):
match
any size > 8
any size 15 edit
antialias = false;
Personally, I got quite partial to the antialiasing of all fonts. If you install some TTFs that look pretty good, your desktop can look pretty clean.
A suggestion for RH8 users.
by
e_n_d_o
·
· Score: 5, Informative
Red Hat 8 appears to have most of this set up from the factory, with the exception of the MS fonts.
There is an unbelievably irritating aspect of anti-alised fonts I've found with RH8 (and in previous experiences with Gnome2): GTK+2 apps will insist on using Anti-alised fonts for EVERYTHING, and there seems to be no way to turn it off. While I think anti-aliased fonts are wonderful most of the time, I believe most developers will agree they are not so great in terminal windows or when viewing source code.
If you change your font preferences to "monochrome", you can then set source code editor/terminal fonts to non-anti-aliasable ones, like LucidaTypewriter. Then switch the font prefs back to your previous anti-aliased setting, and the modified programs will retain the non-antialiased font setting.
I don't know whose fault it is that this workaround is required (GTK, Red Hat, the apps themselves, etc), but it would be most appreciated if non-antialiasable fonts appeared in the font-selection dialogs even when antialiasing is enabled.
Re:A suggestion for RH8 users.
by
foonf
·
· Score: 4, Informative
You can specify in/etc/XftConfig whether or not to anti-alias fonts based on name, type, and size. So for instance you can disable antialiasing on fonts size 12 and below, fixed-width fonts, italic fonts, etc. if you like.
Everything that uses Xft to render anti-aliased fonts (and, except for a few programs with lame software freetype support, this is everything) will be affected by this.
--
"(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
Re:A suggestion for RH8 users.
by
zdzichu
·
· Score: 5, Informative
GTK+2 apps will insist on using Anti-alised fonts for EVERYTHING, and there seems to be no way to turn it off.
You can turn them off:
export GDK_USE_XFT=0
-- :wq
Re:A suggestion for RH8 users.
by
foonf
·
· Score: 3, Informative
[CORRECTION]
XftConfig is usually in/etc/X11, not/etc
--
"(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
Re:A suggestion for RH8 users.
by
mindstrm
·
· Score: 1
"While I think anti-aliased fonts are wonderful most of the time, I believe most developers will agree they are not so great in terminal windows or when viewing source code."
That's because the fonts in X are fugly, and the antialiasing is not the greatest.
Proper antialiased fonts w/ subpixel smoothing on a digital LCD, with good fonts to start with produce something so easy on the eyes you wouldn't WANT to program on anything else.
Re:A suggestion for RH8 users.
by
Covener
·
· Score: 1
xterm -fa "andale mono" makes me go a big rubbery one
Re:A suggestion for RH8 users.
by
ljaguar
·
· Score: 1
Is this true? Does RH8.0 really have freetype with the correct byte code interpreter? Does RH8.0 really include the freetype that violates US patent laws?
I couldn't find the answer to above question on google; someone please give me definitive answer.
Re:A suggestion for RH8 users.
by
KiwiSurfer
·
· Score: 2, Informative
[CORRECTION]
XftConfig is usually in/etc/X11, not/etc
Who modded this up? It all depends on how you set up your system, there is NO standard filesystem structure for XFree86 configuration files. FreeBSD's port of XFree86 puts XftConfig in/usr/X11R6/share/X11/ for example -- and apparenly other OSes and/or disrributions (for some strange reason) decides to put it in/etc (despite the fact that/etc is for operating system-specific configuration files).
- James
Re:A suggestion for RH8 users.
by
CoolVibe
·
· Score: 3, Informative
It's a compile-time setting. Oh, and FreeBSD's XftConfig is in/etc/X11, just like everywhere else. It's just a symlink to that far away place you name./etc/X11/XftConfig is shorter:)
Oh, minor nitpick wrt the screenshots: What is it with people taking screenshots with The Gimp?!? Surely there are better ways to dump one's screen to a file like using xwd, ImageMagick's import, Ksnapshot, or whatever. Takes less time too. Taking screenshots with Gimp is like swatting a fly with a tactical nuke. It works, but it's overkill.
Re:A suggestion for RH8 users.
by
DigiBoi
·
· Score: 2, Funny
Who modded this up? It all depends on how you set up your system, there is NO standard filesystem structure for XFree86 configuration files.
i prefer putting every thing in/Documents\ and\ Settings/
;)
-- I put on my robe and wizard hat.
Re:A suggestion for RH8 users.
by
tau_
·
· Score: 1
Since we ARE talking about RH8.. RH8 does not have XftConfig, because it's based on fontconfig and uses/etc/fonts/fonts.conf (XML format) instead.
-- Ask a silly person, get a silly answer.
Some additional debian specific font info...
by
sc00p18
·
· Score: 3, Informative
...can be found here. It's really easy to follow his instructions to get true type fonts working right.
Re:Some additional debian specific font info...
by
n1k0
·
· Score: 1
Also, sarge's freetype comes with the byte-code interpreter enabled, but the maintainer may be "seriously deciding to turn it off in the near future."
Nick
What about Xft?
by
nothing_23
·
· Score: 5, Informative
That HOWTO seems to ignore the best option for getting pretty fonts on X, Xft.
I am currently running Redhat 8.0 with an XFT version of Mozilla, and I must may my screenies are much prettier.
With Xft, FreeType, and some good TrueType fonts, I finally have a Linux desktop with fonts prettier than WinXP.
If I had/needed a cluestick, I'd beat you with it. Sub-pixel hinting is available under RH8, with support for different orientations/ordering of the RGB lines.
I am currently running Redhat 8.0 with an XFT version of Mozilla [newaol.com], and I must may my screenies [zipcon.net] are much prettier. With Xft, FreeType, and some good TrueType fonts, I finally have a Linux desktop with fonts prettier than WinXP.
Enable the "ClearType" font smoothing option in WinXP. It renders fonts, thick and muddy like Xft.
Compiling as root again
by
sasquatchoflove
·
· Score: 2, Informative
With the recent sendmail trojan (which trojaned your system when you ran make), I would assume people would be more careful of this. The howto author compiles as root, just a warning...
Fontconfig and Xft2
by
ultor
·
· Score: 5, Insightful
I'm sorry to say that these people obviously haven't messed with the fonts stuff other than the top layer of complexity. I suggest if you are really interested in font antialiasing and configuration you look at Fontconfig and Xft2. Keith Packard has done an excellent job with these products along many other cool things within X (ie. Render Extension, RandR, the new XCursor system). Compiling everything with Fontconfig/Xft2 support is a little daunting at first, but when you're done it looks great.
(shameless rave) Keith Packard really is one of the best X hackers out there. I believe he is one of the few people who realize what X (and not only that, as fontconfig is the first universal, modern font mechanism for Linux) is lacking in *and* who is able to implement said lacking features just like they should be. I hope he keeps doing that a few more decades.
Step 1) Install Redhat 8.0 (If you can, f*cking.0 releases)
Step 2) Install MS core font package from http://corefonts.sourceforge.net/
Enjoy.
No really Redhat 8.0 has terrific looking fonts with the exception of Mozilla, but I'll wait a little longer for a 1.2 build with Xft support.
Anyhow KDE has had AA for a while and I'll admit I've been envy and now that Gnome has too, and Mozilla will have it soon, I don't suspect I'll even have to think about it again. Expect all distros to have this setup by default.
Re:Here is the HOWTO
by
Quikah
·
· Score: 3, Informative
There are XFT builds of Mozilla 1.2b already, here.
Thank you Quikah. Now if I could only find a build of Galeon2.;)
Re:Fonts in Linux?
by
The+Bungi
·
· Score: 3, Funny
Will this be a +1 insightful or a -1 troll? Ladies and gents, place your bets!
Who the fuck cares.
Subpixel hinting
by
Doug+Neal
·
· Score: 5, Informative
For those saying that ClearType style subpixel hinting is "too blurry", you should be aware that it only really works on TFT screens as the way it works requires a set pixel layout, which traditional CRTs don't have. Steve Gibson has a fairly good explanation of how it works on his website (if you can put up with his infuriating self-congratulatory writing style).
So yes - regular antialiasing should be all that's needed on a CRT.
And... I'm currently typing this from Konqueror 3, which renders subpixel antialiased Truetype and Type1 fonts absolutely beautifully, along with the rest of KDE 3, in fact I would say it looks a lot nicer than Cleartype. Especially on a 1600x1200 TFT. Mmm, shiny:D
... ClearType...requires a set pixel layout, which traditional CRTs don't have.
Actually, I prefer ClearType on my Sony monitor, but not on my "regular" monitor at work. Trinitron tubes use square/rectangular phosphor cells instead of dots. Seems to me that trinitron tubes might be close enough to a "set pixel layout" to have the same effect.
Anyone else out there who can compare tube/gun types?
-- I do not fail; I succeed at finding out what does not work.
... ClearType...requires a set pixel layout, which traditional CRTs don't have.
Actually, I prefer ClearType on my Sony monitor, but not on my "regular" monitor at work.
I was going to write saying exactly the same thing. I've used Xft's sub-pixel (aka ClearType-alike) rendering on my laptop for some time now. When I got a 20" Sun monitor (Sony Trinitron tube), I thought "hey, I wonder how s-p rendering looks on this, given it has a rectangular RGB pattern?", not really expecting it to work. Somewhat to my surprise, it does work, arguably better than a TFT!
Actually ClearType works very nice on CRT monitors, but you have to go to the ClearType Web Interface to fine tune ClearType. Does anybody know why they didn't integrate this in OS?
You got me, I was thinking the same thing. From what I could see only the first screenshot that he called "ugly" had any anti-aliasing at all. The rest of them were crappy jagged-edged fonts. I guess he thinks of them as "normal" because before Windows XP it didnt support good anti-aliasing.
Is Linux dead?
by
yeti+(dn)
·
· Score: 1, Insightful
Everybody cares about fonts not being perfect.
Nobody cares grep's -o option doesn't work with -i (well, it's actually already fixed in RawHide, but that's another matter).
After half a year we can expect articles about screensaver settings in Linux while RedHat will stop distributing xterm, because of no one using terminal any more.
Fonts ARE a big deal. Getting them right is a hell of a lot more important than some grep switch. Futhermore one has nothing to do with another. Why are even comparing the two?
Why would Redhat stop distributing xterm?
What are your talking about?
Why was this modded up?
Huh?
-- If you wanna get rich, you know that payback is a bitch
Ya'll should consider using Windows instead.... I think it's amazing that Linux is being pushed as a desktop operating system when it can't display fonts to save its life. Pretty pathetic, if you ask me.
First off: if you're basing your choice of operaing system on a windowing program's ability to render fonts, then something is seriously wrong. IMHO.
Second: I don't like anti-aliased fonts. I'd rather look at code/text in a non-AA, monospaced font. It gives me fewer headaches. Text in a magazine or on a newpaper is one thing, but when I'm looking at a monitor, I don't want anti-aliasing. "Linux" (those with a clue, just assume that X is Linux for a minute here for the sake of discussion; some people don't know that the GUI and the OS are two different things) displays fonts just fine for me. If I wanted AA fonts, I can have them. If I don't want them, I don't have to get them; nobody has made my choice for me. Being forced to put up with someone else's choices is really what is pathetic. (Although trolling with old Windows bigotry comes close.)
-B
--
Ash and Hickory, straight-grained and true, make excellent bludgeons, dandy for the cudgeling of vegetarians.
Another HOWTO
by
capnjack41
·
· Score: 5, Informative
HOWTO violate microsoft and apple patents
by
jrstewart
·
· Score: 5, Insightful
The flag that this article suggests turning on is off by default because the hinting algorithm in question may violate Microsoft and Apple patents. Not the average user really cares about this, but it was irresponsible of The Register to not explain this in the article. On the other hand, this is The Reg we're talking about here...
More info: http://freetype.sourceforge.net/patents.html
Re:HOWTO violate microsoft and apple patents
by
Anonymous Coward
·
· Score: 1, Interesting
heres a question, i dont know the answer to this though:
if you are building a device, that breaks a patent for your own personal use, is it legal?
i though patents were to protect companies from others stealing their hard work? since i am making it for my own use and not selling it, do patents apply?
i would say no, because patents protect companies for them to recoup the costs and make money. since i am not selling it, is it illegal?
Re:HOWTO violate microsoft and apple patents
by
Pengo
·
· Score: 2
Why pay for a product thats protected by a pattent and a company if it can be had for free? I think that is what they are worried about.
Re:HOWTO violate microsoft and apple patents
by
JanneM
·
· Score: 2, Informative
As I understand it, the patents have been granted in the US only. The Register is a British publication. So, for their target readership, there are no patent issues to worry about.
-- Trust the Computer. The Computer is your friend.
Re:HOWTO violate microsoft and apple patents
by
Espectr0
·
· Score: 2
Probably the reg does not care because they don't have a DMCA to worry about. Shame on them for being Free
Strongly Recommended
by
mickwd
·
· Score: 5, Informative
I've got to point out this site for improving fonts even more. The difference it made to my fonts was amazing - and I was already using sub-pixel rendering and a laptop display with freetype2-2.1.2 (with the bytecode interpreter compiled in).
I STRONGLY recommend you try it out - he even includes a pre-compiled libfreetype (built for Red Hat, I think, but works great on Mandrake 9.0). You'll need to put it in the right directory, and create the right symbolic links to it.
I don't know how much of the improvement is due to this guy's improvements, and how many are due to the upcoming freetype2-2.1.3, but whatever - Linux fonts are no longer inferior to look at.
Thanxs a lot! This version (libfreetype.so.6.3.2) dramtically improved the font rendering in my PC (mandrake 9.0 at 1152 X 864 resolution). Earlier I had re-compiled freetype with bytecode enabled as suggested by the author, but it did not have any visible effect. Now the fonts do look better, but still there is much room for improvement
Re:Maybe you should use those purty fonts...
by
NortWind
·
· Score: 1
...to read your XP EULA. Linux may not for the moment have "purty fonts", but it has no ugly EULA either. Anybody accepting the XP EULA is pretty pathetic, if you ask me.
Jus' a second thought.
Re:Why would you ever want to?
by
stratjakt
·
· Score: 2, Interesting
listen here.
you're preaching to the choir.
but your an asshat. take a deep breath and think before you speak.
and whether your OS is gui driven or cli driven is irrelevant. it's the use you make of it that is (or isn't) "mindless".
i for one am sick of typing everything, and sick of the tendonitis i've developed from years of doing so.
only do-nothing IT guys and admins brag about using a command line.
i do however have a problem with linux becoming windows, because noone seems to be able to think of anything better.
--
I don't need no instructions to know how to rock!!!!
Redhat makes adding fonts even easier
by
Sergeant+Beavis
·
· Score: 1
Just mkdir ~/.fonts and copy your TrueType fonts in there. WHAMMO, instant MS fonts.
Still though, I'm trying to get Mozilla looking better. Makes my website look like it got up on the wrong side of the bed.
-- There is nothing inherently safe about liberty. That's why so many people died protecting it.
Re:Redhat makes adding fonts even easier
by
IdleTime
·
· Score: 3, Informative
No problem.
Find your unix.js file under the mozilla directory, then make sure your TrueType Section looks like this:
// TrueType
pref("font.FreeType2.enable", true);
pref("font.freetype2.shared-library", "libfreetype.so.6"); // if libfreetype was built without hinting compiled in // it is best to leave hinting off
pref("font.FreeType2.autohinted", true);
pref("font.FreeType2.unhinted", true); // 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"); // sample prefs for TrueType font dirs
pref("font.directory.truetype.1", "/usr/share/fonts/truetype");
pref("font.directory.truetype.2", "/usr/X11R6/lib/X11/fonts/TTF");
pref("font.directory.truetype.3", "/usr/X11R6/lib/X11/fonts/truetype");
Just remember to change the path to your TT font directories.
--
If you mod me down, I *will* introduce you to my sister!
Re:Redhat makes adding fonts even easier
by
Lendrick
·
· Score: 2
Actually, your fonts will look better if you set unhinted to false (but leave autohinted to true)
Bart
Re:Redhat makes adding fonts even easier
by
santiag0
·
· Score: 1
Oh My God!!It is that easy. I have a dual boot (Win 2000 / SuSe 8) box, so I copied all the win fonts (c:\winnt\Fonts) to a dir I made (/usr/X11R6/lib/X11/fonts/win), edited my unix.js ( on suse it is/usr/local/bin/defaults/pref/unix.js) to look like the above post, except for the last three lines, which point to the new dir, and bammo! I can't believe how great it looks. I also can't believe I wasted 3 years looking at crappy linux fonts when it was this simple. I also had to go to Edit Preferences > Appearance > Fonts, and choose the appropriate new win fonts in the drop downs to tell Mozilla to use them for the serif, sans-serif, etc.
Thank you!!
Re:Redhat makes adding fonts even easier
by
santiag0
·
· Score: 1
I am following up to my own post to point out that if you modify the unix.js file as described above, then grab and install a new version of mozilla ( I upgraded from 1.0 to 1.1 this morning),it uninstalls everything - including the unix.js file. So I had to re - edit it to use my win truetype fonts. I also copied it to another dir, so If I forget and install over it again, I'll still have it.
Dave
Re:Redhat makes adding fonts even easier
by
IdleTime
·
· Score: 1
That is actually not true.
I have done tests with both and using:
pref("font.FreeType2.unhinted", true);
gives the best result. I even have screenshots to prove:)
--
If you mod me down, I *will* introduce you to my sister!
Re:Redhat makes adding fonts even easier
by
Lendrick
·
· Score: 2
If you're doing this under redhat 8, I'd love to see your screenshots (both with an without). Can you post links?
Re:Redhat makes adding fonts even easier
by
IdleTime
·
· Score: 1
I'm using Gentoo Linux with KDE 3.1Beta2 and Phoenix browser.
You can take a look at the hinted version and the unhinted version and tell me what you think.
--
If you mod me down, I *will* introduce you to my sister!
what about lower-case a?
by
misterhaan
·
· Score: 1
isn't it fun when autocorrect thinks you're writing a sentence when you're not?
Re:Why would you ever want to?-Be good.
by
Anonymous Coward
·
· Score: 2, Interesting
Well to start. Why shouldn't admins have a nice screen to look at? I use to work with a very very nice monitor (commercial OS) that had such a beautiful screen. Shame I couldn't take it home with me. Now I can have the same experience with my home OS. Two by unified userbase you wouldn't be forgetting all the different varieties of Unix out there would you? Three it is a myth that you have to give up control while having ease of learning as well as use. However the present problem I see with what's coming out is that an interface that "grows" with you as you transit from newbie to power-user is hard to do. Most interfaces commercial or otherwise hit either end, while being weak in the middle. Can an interface be for everyone? Yes, but it may mean more work and looking very hard at what we presently assume.
From the last time I did this:
1-an interface needs to be free of unnecessary elements at all time. In other words (does this contribute to the goal(s) being achieved?).
2-An interface needs to keep it's audiance in mind. Professional? Amateur? Artist? Blue-blood?
3-Organizing devices must leverage common elements while going from general to specific.
4-Make the interface playable by making the consequences of actions as reversable as possible.
5-If an action is unreversable let the user know in a non-threatening, non-insulting way.
6-Choose intelligent defaults.
7-Keep the perception as much as possible that the user is in control of the situation.
8-If control is needed in a situation (a certain sequence needs to be followed) guide the user as gently as possible.
9-As part of transiting from newbie to power-user. Have the interface show you some of the alternative ways to accomplich the same task.
10-User control of variable preferences is one way to accomplish gradual disclosure of the power that lies beneath without intimidating the user.
Anyone else want to add anything?
Look at this thread:
by
peterpi
·
· Score: 5, Insightful
You've obviously not used (insert distro here)
Well, you just need to edit your XF86Config.
I read code, so I don't need AA fonts.
Yes you should have the fonts there, but you actually need to symlink them over here, here, there, and there.
GUIs are for lusers, you are obviously not 1337.
Much as the work on getting fonts to work on X is to be commended, I don't think we're ready to start showing off just yet.
Get back to me in a few years when something approaching a workable standard is around.
I don't think it will be years. I think its safe to say Redhat 8 set a new standard in the "Out of Box experience" category. I think its also safe to say no distro will ship with shitty fonts in their next release now. I think that is something to celebrate and show off don't you? I know everyone I've shown OpenOffice to has been impressed with the fonts.
Regarding the arguing, well some things will never change. I sometimes get fed up with it as well, and I'm sure some people get fed up with me, but you gotta admit this would be one boring website without it.
-- If you wanna get rich, you know that payback is a bitch
About the distro thing, if you're not using a newbie distro, screw you if you have newbie complaints! There is a place for new users on Linux, but if they're not in their place, then they have no right to complain. In light of the first statement, the rest are irrelevent, because many distros (RedHat 8, for example, and Gentoo, even though it's not a newbie distro) do handle fonts correctly.
-- A deep unwavering belief is a sure sign you're missing something...
I don't get it. The two screenshots he shows to compare (923.png and 930.png) look identical to me, except that one has anti-aliasing and one doesn't. He claims the second one looks better, but I don't see it.
In fact, I think his screenshots look pretty ugly in general. He's managed to duplicate the blocky, hard-edged look of Windows 9x quite well, but I hardly consider this attractive. Red Hat 8.0's fonts look significantly better than his screenshots.
Mac OS X still has a wide lead on best look fonts, but IMO a modern Linux box has superior fonts to any version of Windows.
Mac OS X still has a wide lead on best look fonts, but IMO a modern Linux box has superior fonts to any version of Windows."
When you run Mac OS X, you are use some really fine and EXPENSIVE licensed fonts. Steve Jobs jokingly grouses about how much they are paying major font foundries, but it must be worthwhile or they wouldn't spend the money.
Font design today, like it was one-hundred years ago, is an art and not a science.
Wanna see a cheap font fall apart? Examine it at 500-point size.
The difference between the 929.png and the 930.png are the character spacing.. If you notice there is MUCH better spacing in the second picture.. as opposed to the first picture where the letters are all scrunched up.. Hence the second shot is significantly easier to read than the first.
Wow, you need glasses boy. First of all, you see the two PNG shots as identical. They're not. Second, you see a modern Linux box as having superior fonts to any version of Windows. Ever heard of Linux ppl trying to download Microsoft's TrueType fonts? Yes, those fonts are also used in *gasp* Windows.
IF you have a 1600x1200 laptop, I recommend setting XP to 120dpi instead. Yes, the fonts get larger, and some things are a bit out of whack due to bad programming.. but I assure you the increased resolution combined with cleartype makes things look sweeeeeet.
Also, if you use Acrobat Reader (which uses it's own font rendering engine), make sure you go into the settings and turn on CoolType to get similar results.
Just been messing with fonts myself
by
Anonymous Coward
·
· Score: 1, Interesting
Another trick to getting nice fonts is to insure you've installed any scalable fonts you can get your hands on.
This guy is whacked.
by
brunes69
·
· Score: 5, Insightful
I am posting the same thing here as I posted over at the dot 10 minutes ago. Just a glace at his two Openoffice screenshots showed me this guy is seriously whacked. The second screenshot, which he claimed is "more refined" is clearly much more jagged than the first. A simple look with Xmag sees the only difference between the two is that the second has anti-aliasing turned off. Same with the"results" screenshots at the end.... they look like crap compared to my fonts in KDE, and I did nothing speccial. Just apt-get install msttcorefonts in Debian. There is no anti-aliasing going on at all in these screenshots, they look horrible.
Now, I totally respect people who don;t like anti-aliased fonts. but in KDE (which this article seems to be mainly about) or OpenOffice, disbling anti-aliasing is as easy as unchecking a menu option... if you don't want it, don't use it. What is the point of the whole long process in this article exactly?
Re:Maybe you should use those purty fonts...
by
The+Bungi
·
· Score: 2
I did read it. And so your point is that if I accept the EULA I'm "pathetic"?
I guess stealing fonts from Microsoft so that you can have a decent-looking OS is heroic.
And please don't give me the stupid "M$ is evil" spiel. It's as tired as a hooker at a GeekWorld convention.
I guarantee that if you sat down in front of my windows laptop, you would fall instantly in love with programming on it, simply because of the fonts.
I know what you are saying about AA fonts giving you headaches.. but that's because they aren't properly antialiased.
Proper antialiasing yields fonts that look solid and smooth, and are easier on the eyes, not harder.
Re:Maybe you should use those purty fonts...
by
mindstrm
·
· Score: 1
Define acceptance? Some of us click "Agree" knowing full well we don't agree to anything, and that we will do what we want in spite of those alleged terms.
What kind of message does it send that there is actually a NEED for a "font how-to" in the first place?
I cannot comprehend what is so hard about making fonts work. TrueType is a known format. The OS loads it up and the programs use the OS to interact with the fonts, right? Windows and Mac handle it fine, what exactly is the cause of the difficulty under Linux?
For high-res screens
by
be-fan
·
· Score: 5, Informative
If you're running a high-res screen (currently this would be one of those 133 or 140 DPI LCDs) or if you like your fonts on the softer side, the TrueType hinting algorithm will tend to make your fonts too thin. I'm running a 1600x1200 LCD and the bytecode interpreter, which tends to snap fonts to integral numbers of pixels, distorts the shape and makes fonts too thin to read. A wonderful fix for this is to download and compile the FreeType2-current from FreeType's FTP site (under the unstable directory). Then, get some nice Type1 fonts (currently, a lot of fixes are in the pshinter) and make sure to disable the TrueType bytecode interpreter (it's disabled by default). Turn on AA, and you're treated to some wonderfully rendered fonts. Anti-aliased enough to be smooth, but still sharp enough to be easily readable. I've got a screenshot at: http://home.mindspring.com/~heliosc/fonts.png
-- A deep unwavering belief is a sure sign you're missing something...
0) Make sure that you've got Xft anti-aliasing already working in X. There are a lot of HOWTOs on the internet for this.
1) Download the freetype2-current sources from here.
2) Extract the sources, cd to the 'freetype2-current' directory, type 'make' twice to build, 'make install' once to install.
3) Back up any libraries of the form *freetype* in/usr/lib and/usr/X11R6/lib to somewhere safe, and then delete them from those directories.
4) Copy the newly built libraries from/usr/local/lib to/usr/lib.
5) Next, get some nice Type1 fonts. You can find these in a lot of places. I personally got the Adobe Type Basics package ($100 for 65 fonts) which is a very good deal. But the Luxi series of fonts that come with X are also pretty good. If you have any desktop publishing software or any Corel software, you might find some Postscript fonts that come with those. As a last resort, just search the internet for Postscript fonts. The nice thing is that with the new FreeType, all the smarts are in the auto-hinter and ps-hinter, so what the font looks like depends only on the glyph shapes themselves. This is a big step forward from the TrueType world, where the quality of the font depended very heavily the quality of the font's hinting. Since hinting TrueType was an extremely difficult process, only expensive professional fonts were any good for on-screen use. In comparison, there are tons of good Postscript fonts out there, since the hinting required for postscript fonts is rather minimal.
-- A deep unwavering belief is a sure sign you're missing something...
pretty != readable
by
g4dget
·
· Score: 5, Insightful
Some of the original X11 bitmapped fonts are probably among the most readable fonts anywhere. They were hand-designed and tuned over the years.
The point of TrueType is not to give you more readable fonts than good manually designed ones, it is to give you complete families of decent fonts at many screen resolutions and sizes; that's needed because it would be way too much work to design all those font instances by hand. Still, if you did, you'd only improve the TrueType output.
Furthermore, anti-aliasing, font smoothing, and similar tricks do make pages appear prettier, but they generally don't enhance readability, and may even degrade it. That's why, among other things, many systems let you turn off font smoothing below a certain size. Cleartype and its equivalents, however, may help with readability, since they really do increase spatial resolution (at the cost of color fidelity).
See, the thing is, I disagree with pretty much everything you said in your post. The original X11 bitmapped fonts are not very readable fonts. Readable fonts, as have been noted elsewhere time and time again, have just the right x-height, stroke width, serif size, and so on. Bitmapped computer fonts don't have any of those things. Ergo, they're not easy to read.
Now, at this point it's important for you to mind the distinction between fonts that are easy to read and fonts that you personally are accustomed to. If you sit in front of Bitstream Terminal 7 for fifteen years, it's probably going to be pretty easy to read for you. But that's not the same thing as being easy to read in general.
So what makes a font readable? A readable font is one in which the letters look like what you expect them to look like. Good serif fonts have glyphs that are easy for the eye to recognize at virtually any size from billboard down to postage stamp. Antialiasing helps make fonts more readable because it makes the glyphs look more like what you expect them to look like.
Some of the original work in antialiasing was done, if memory serves me right, with Japanese characters. Kanji characters, being much more intricate than Roman characters, are notoriously hard to render on a computer screen, particularly the low-resolution screens most common in the 1970's. Antialiasing, even at low resolution, makes kanji much easier to read. Antialiasing Roman type has the same effect: it makes type easier to read.
Of course, there's such a thing as bad antialiasing. I had a friend complain to me over the phone about how bad the antialiasing in Windows XP is. He said it made everything look fuzzy, and that he wished the type on his laptop could look as good as the type on my Apple LCD monitor. The next time I saw him I took a look at his laptop: it had an 800x600 screen! Of course antialiasing looks bad at 55 dots per inch! But on my 1280x1024 screen at home, type is well antialiased, properly kerned, and very easy on the eyes. So think twice before saying that antialiasing sucks.
He's probably AAing with ClearType. I use stand AA on my laptop as I find the ClearType was too blurry, even after using MSFT's ClearType tuning page. The choice is in the display properties. Then again... I don't remember what it's like to use 800x600, let alone whether AA is even sensible;)
The original X11 bitmapped fonts are not very readable fonts. Readable fonts, as have been noted elsewhere time and time again, have just the right x-height, stroke width, serif size, and so on. Bitmapped computer fonts don't have any of those things.
Come on, think about it. With bitmapped fonts, every single pixel is placed by hand--you can't get more control than that. A bitmapped font designer can choose whatever x-height, stroke width, and serif size, he wants.
So what makes a font readable? A readable font is one in which the letters look like what you expect them to look like. Good serif fonts have glyphs that are easy for the eye to recognize at virtually any size from billboard down to postage stamp. Antialiasing helps make fonts more readable because it makes the glyphs look more like what you expect them to look like.
Readability is influenced by lots of factors. Familiarity helps. But so do contrast and other features. At small sizes, antialiasing blurs out characters so much that readability suffers. And familiarity is easily acquired, while low contrast affects readability no matter how long you stare at a blurry font.
I suggest you try "micro" (a 3x5 font) or "5x7" (a, guess, 5x7 font) on X11. Then try to get something as readable at that size out of a scalable TrueType font. Good luck. Mini7 and SeveNet are other examples where Mac typographers, of all people, threw away scalable type or antialiasing to get readability at small sizes.
A bitmapped font designer can choose whatever x-height, stroke width, and serif size, he wants.
No, he can't. He's limited by the screen resolution for which the font is being designed. You can't make a readable font on an 8 x 14 pixel grid, sorry.
As for your 5 x 7 pixel font suggestions... no thanks. Your problem isn't with antialiased fonts, it's with fonts that are just too darned small. Use a type size on the screen that's large enough, antialias it, and your eye strain problems will disappear.
You can't make a readable font on an 8 x 14 pixel grid, sorry.
About 50 years of experience with bitmapped fonts prove you wrong. The
main thing you can't do with an 8x14 pixel grid is satisfy a snob.
As for your 5 x 7 pixel font suggestions... no thanks. Your problem isn't
with antialiased fonts, it's with fonts that are just too darned small. Use
a type size on the screen that's large enough, antialias it, and your eye
strain problems will disappear.
I don't have a problem with eye strain--I use well-designed bitmapped fonts for most of my text.
Ok so here I am with my first moderator points in who knows how long[0] and I wanted to use them so badly on this thread because I am really new to this whole X font thing having spent so much time in a self imposed exile to the command line for two years[1]. So I am back to using X and this font HOWTO sounded like a great idea. Until I started reading it. To paraphrase "Just unpack the src RPM". Well hell I thought HOWTOs were supposed to be distro independent because the HOWTO might outlive the distro and because not every one uses Uber_Distro_GNU/Linux. I fit in to that latter category. I run Slackware and some people run Debian. Now it is possible to unpack that RPM and futs with it for a little while and hope that it works no matter what distro you are on but the HOWTOs are supposed to "speak in a language that everyone can comprehend."[2] One of the tricks to Linux's success is that is very portable to any arch. Shouldn't the HOWTOs be written with the same idea?
I really did want to use those mod points here. Oh well better luck next thread.
[0] remember that 1000 mod pointed post? Well apparently I have served my time. [1] to better learn this thing called Linux better than a GUI will ever allow. [2] no thats not a Living Color song.
Because he's RIGHT.
by
Anonymous Coward
·
· Score: 3, Insightful
Windows 2000/XP: Install a font by dragging it to the fonts folder.
Mac OS X: Install a font by dragging it to the fonts folder.
Linux: Some convoluted thing that involves downloading the Microsoft (!) fonts and putting them in several different places.
Windows XP: Turn antialiasing or ClearType on by checking a box in the display properties. (Note: ClearType is only recommended for digital flat panels.)
Mac OS X: Turn antialiasing/sub-pixel rendering on by checking a box in the display properties.
Linux: Recompile this thing, and oh yeah you have to edit a header file, and then do this, and then it will work, except not in Mozilla, because then you have to do this and the other thing. (A three-page description follows.)
I agree with the first post here. Getting Linux to look good on the desktop is possible. Getting Windows XP or Mac OS X to look good on the desktop is easy. Thanks, but I don't want to f*ck with my computer just to make it look good.
well then what the hell are you doing reading and posting on slashdot? this isnt "News for Moms, Making Solitaire Easy". if you want to sit around and not bother doing things yourself, just go back to your aol channel and find some nice football chat.
Re:Because he's RIGHT.
by
SomeOtherGuy
·
· Score: 2
I agree. It not only should be easy -- but what is up with app font support relying on how you compile the app? X should be allowed to handle font rendering. As soon as each app and or toolkit has to worry about which libraries to use to render what fonts -- what ways....You end up with a mess. Imagine getting a shirt with no buttons and then having to buy 8 different buttons at 8 different stores, then sew them on and hope eveything matches. Is it not just easier to take care of the button issue at manufacture time...
Welcome to the wonderful world of software patents.
You should take it up with Apple, or perhaps hit up the maker of some Linux distribution and say you are willing to pay extra to Apple to get the full version of FreeType, or that you want an installation option that will let you pay Apple in return for installing the version of FreeType that does the hinting right.
Linux with Fontconfig: Install a font by dragging it to the fonts folder.
Linux with Gnome 2.1: Turn on antialiasing or subpixel AA and fine-tune it to your liking with a few checkboxes.
Getting Linux to look good on the desktop is easy. Support fontconfig. That, of course, means developers. Gnome 2.1 supports it, Mozilla does, I believe Trolltech is hacking on Qt. A bright future is very near.
Am I the only one who finds it rediculous all of this isn't in KDE already.
Why do we need to use MS True Type fonts isn't there a way for the community to make their own?
I know nothing about fonts just curious.
Re:C'mon
by
Anonymous Coward
·
· Score: 1, Insightful
There was a/. article a while back that asked this same question. It apparently is much, much, much harder to make your own fonts than to steal em from Microsoft.
I agree, computers are for everyone. Everybody should be able to use one.
What I'm saying is that I'll be damned if I'm going to worry about how granny writes her email. It's not my problem. I don't play the IT game so that you can have a good time, I do it so that I can have a good time. Let's see, I could hack together a console editor in a few days, or I could write an easy to use word processor that isn't going to make me a dime and will take months to complete, but it's for the "greater good". Tough call.
This may be a selfish attitude, but there's at least some of it in every developer.
Apple made OS X so damned sweet because they're selling it. Money, baby. Linux developers are still largely hobbyists and college kids, not the kind of people who really care what their word processor looks like, or if their fonts are nice and smooth. They don't have anybody to please but themselves.
Go ahead and mod it down, I know you're itching to.
I can guarantee you that if you saw my Linux desktop with fonts anti-aliased with David Chester's Xft hack, you'd instantly want to switch. Frankly, I have yet to see TTF fonts this beautiful on any system, Mac OSX included, especially in 1600x1200. I mean, look at this screenshot! Sorry, but I work on a Windows machine all day, with anti-aliased turned on, and it doesn't even come close to this.
The font battle has been won, and the winner is Xft+freetype+Chester's font hack.
Though I don't for one second doubt you... I'm willing to bet your desktop and mine are a close battle. Mac OSX doesn't hold a candle to what I see here.
If you have something that looks better than this... I'm all for it.
So.. how are we going to compare? The only thing I can think of is ultra high resolution photographs.
What kind of screen are you using?
I don't see it
by
praedor
·
· Score: 4, Insightful
Honestly, I do NOT see nice fonts displayed any time there is an article about fixing fonts in linux.
There is one place and one place only that I have ever seen a screen loaded with nicely antialiased fonts...my KDE desktop using the longtime antialiasing support from QT. The fonts I have are SMOOTH. Let me reiterate that, they are smooth. No jaggy lines, no stairstep angles, just smooth antialiasing. Beautiful.
I then read an article like that at the Register, look at the screen shots, and all I can do is say "What the fu*K are they talking about?! Those fonts are STILL jaggy and they are NOT aa.
I've recently read a few other articles about fonts, aa, and hinting. I look at the results in screenshots and the fonts are either STILL jaggy or they are horrifically smeared. If hinting means "smear the crap out of the font until it makes you think your glasses are greasy or you are developing cataracts" then that hinting crap is working great! Nice looking aa fonts do NOT have to be blurred out of recognition. AA means NO jaggy lines, just smooth, flowing, SLIGHTLY (EVER so slightly) blurred fonts.
So far, mozilla simply has ugly font rendering no matter how you slice it. Its fonts are jaggy/stairstepped. Period. Butt-ugly. Same with Gnome. I have tried to get fonts to look as nice in Gnome as they look in KDE but it just doesn't happen. I either get the greasy glasses effect or jaggy lines.
I have to come to the conclusion that when people SAY antialiasing, they really don't know what their are talking about. Or they are referring to a different antialiasing than I am aware of. If your fonts have jaggy lines, then you are NOT enjoying the fruit of aa. Sorry, but that is a fact.
-- In Bushworld, they struggle to keep church and state separate in Iraq as they increasingly merge the two in America.
RedHat 8, truetype fonts from your windows machine, mozilla 1.2, symlink your openoffice font dir to the truetype dir,... and you have got one smooth desktop
Re:I think he got it reversed!
by
Lobsang
·
· Score: 2
That's the only explanation. I was puzzled by it too! When I found the first, anti-aliased screen and he says he'll improve it a lot I thought "Wow, let me see the second screen now!".
That's nice. But "well, as far as I'm concerned" doesn't either validate your point or make it any more, well, relevant.
You seem to think that because you have figured out how to have beautiful fonts in Linux then ergo, Windows sucks and is not necessary. That's kind of a stretch, mmm?
Also, the "well, if I want them or not blah blah blah" choice (and I use the term lightly since I can't imagine myself thinking "hey, I want my apps to look crappy!") is pretty fucking irrelevant to the topic. I don't give a shit if you can do something like '#fontometric -i -r00 -l -pr3 -tti -font' or some such weird incantation to reach anti-aliasing Nirvana. If it doesn't do it out of the god damn box then it's pretty much useless.
Being forced to put up with someone else's choices
Spare me the communist claptrap bud.
Completely OT, but...
by
Stauf
·
· Score: 3, Informative
Trillian runs fine under wine, albiet without *any* alpha blending (not sure tho, it may work on a version of X that supports transparency)
(Just realised I'm using WineX 2.2 - may make a difference, but it works for me)
Two main reasons, both derive from IP issues. The freetype bytecode interpreter is possibly infringing on an Adobe patent. MS and Apple both shell out big bucks in licensing fees to Adobe for rights to the patented aspects of TrueType rendering, and it shows in the quality of their screen font rendering. Second, the fonts that are available freely (GNU free, not $0 free) are utter shite. They would look bad on any system. Microsoft has great fonts, which are available for free (as in no money) but there are some restrictions on distributing them, so they are never included in a Linux distro.
-- 0 1 - just my two bits
Re:Maybe you should use those purty fonts...
by
NortWind
·
· Score: 1
I did read it. And so your point is that if I accept the EULA I'm "pathetic"?
If you accept the EULA, you accept that MS owns your computer, owns any software that you buy from any vendor that you run on that computer, and owns any music or other data that you keep in there. If you are willing to accept that, then I do feel sad for you. Check "pathetic".
I guess stealing fonts from Microsoft so that you can have a decent-looking OS is heroic.
I do not advocate stealing those fonts from Microsoft. Microsoft did make those fonts available for free use, to establish them as a standard for web use, but you what? They decided to change the license. They have that right legally, just as they have the right to change your EULA. Now Linux doesn't have any pretty fonts. Somebody will make some open source fonts someday, I'm not worried. I'll wait.
And please don't give me the stupid "M$ is evil" spiel. It's as tired as a hooker at a GeekWorld convention.
I don't think Microsoft is evil. They are a corporation, they are just in the business of making money. They get the most money by controlling their software, your computer, and you. It's efficient. Profits are double what they were same quarter last year! I just don't want to be part of it anymore. I can't imagine why you do.
GNU/Linux needs good defaults
by
dh003i
·
· Score: 3, Insightful
GNU/Linux does have good defaults, for a server.
However, for the most part, it has very poor defaults for the average home-user desktop-user. I'm speaking as a Debian user here.
Distributions should offer a "desktop" option during setup, which will set things up nicely for the average desktop user: that means anti-aliasing, maximum resolution possible, 16-bit color, a reasonable font-set, and a good default GUI-configuration (this does not mean a aqua-esque theme; this means that, for example, if the WM is WindowMaker, icons for the internet, e-mail, spreadsheets, word processors, etc should be on the dock).
All of the right stuff is there to make GNU/Linux. All that developers need to do is set up good defaults. This is simply a configuration issue; it is not something which is going to prevent you from devoting enough time to core technical issues.
Re:GNU/Linux needs good defaults
by
Anonymous Coward
·
· Score: 1, Insightful
Sorry for pimping, but Redhat 8.0 does all of those things by default. I mean EXACTLY everything you just asked for is in Redhat 8.0's personal desktop install.
Also thanks to the beauty of opensource the rest of the distros can now look as good by default. I'm sure some will even improve on it and then Redhat can in return improve again.
The days of the ugly linux desktop are over and I couldn't be happier.
I copied over MS TTF fonts and X acknowledged them but looking at a webpage in Moz with Verdana shows huge disproportionate characters. Is this a problem with Mozilla or just a problem with raw TTF/xfs?
It refers to the Microsoft-provided font package, and that's been removed from Debian ever since MS pulled the fonts. The msttcorefonts.deb doesn't actually provide the fonts, it just downloads them from the MS web site -- and so, it's useless, as the web site no longer has them.
Pity, too, because I run Debian, and I've never been able to get decent fonts under any flavor of Linux.
-- You cannot apply a technological solution to a sociological problem. (Edwards' Law)
Somebody else told me that the MS fonts have been reposted somewhere on sourceforge, and that Debian now downloads them from there. That'd be neat.
I love typesetting, but I hate messing with fonts on my computer. Why the hell can't they look nice out of the box?
-- You cannot apply a technological solution to a sociological problem. (Edwards' Law)
Wrong Direction
by
SomeOtherGuy
·
· Score: 5, Insightful
Well if you look at the font fiascos in recent distributions and desktops (I am speaking of Mandrake 9.0 -- and from what I have heard RedHat), then you end up having about 5000 fonts and each application you run can use about 10 of them. So you end up with some applications able to use some fonts , and other applications able to see others. Depending on what type of app or window manager you are running -- you see a variety of "effects" that may or may not resemble AA. Gtk 1.x apps see some fonts, Gtk 2.x apps see others, QT sees others AND PLEASE don't even get me started on font sizes, most apps just asumme that size 12 is about all they want to use, and some gtk apps occasionally start up with a nice 72 point font staring back at you for some crazy reason or another -- Xfontsel can see a bunch of them but in itself does not do much. (to me it just looks like multiple levels of blur.)
I bet one could write a book with a chapter on each different method for displaying fonts in these new distributions. And if you want to get really confused you can look at the 7 or 8 different font configuration files used to put this clusterfuck together. Whatever happened to the good old days where I could just run XFSTT on a port and get all of my TT fonts pretty much the same as in Windows -- and this was even before XFree 4. With the advent of XFS and XFree 4 we got some primitive looking Jaggy things that "claimed" to be our TT fonts -- but at least where I was standing you could not pick them out from a lineup.
I still don't see how we are any better off in the "font world" than we were 4 years ago -- it seems that each toolkit has just decided to try to invent there own ways to render fonts.. Crazy -- Crazy -- Crazy.
Not a great screen, but reasonably priced: SyncMaster 955DF from Samsung (500$ canadian for 19"). It does the job!
I can always send you a screenshot (I don't have a digital camera...yet!). My email address at home can be found on my website, under the heading "Courriel" near the bottom of the right hand column (just above the "small type"). The link text is "m'écrire".
But if you say that your display is better than OSX, then I guess that our desktop are pretty close. I'm happy with calling it a draw (though I wouldn't mind a screenshot in any case). Your call.
--
Reminder: find a new sig
No, he's right about the visual effect
by
Reziac
·
· Score: 3, Insightful
I do understand anti-aliasing, but the parent post is right -- on some screens, at some resolutions, AA'd screen fonts look fuzzy (worst case, they can be almost unreadable). So I think it's good, even necessary, to allow anti-aliasing to be turned off if the user so desires.
BTW, I frequently need to resize image files of various sorts, and have learned that sometimes (depending on content) they look better when I turn off anti-aliasing.
-- ~REZ~
#43301. Who'd fake being me anyway?
Re:No, he's right about the visual effect
by
wadetemp
·
· Score: 2
on some screens, at some resolutions
You're talking about 320x200 CGA, right? One some days, in some fields,I can get struck by lightning too.
Re:No, he's right about the visual effect
by
Reziac
·
· Score: 2
No, I'm talking about this nice crisp Trinitron CRT that I run at 1024x768x32M.
-- ~REZ~
#43301. Who'd fake being me anyway?
Re:Why would you ever want to?
by
Greebz
·
· Score: 1
"look at what Apple have managed to achieve with MacOS-X.. although they're newbies when it comes to BSD they've managed to design it around the home user rather than the geek.. "
NeXTStep is over 15 years old.
MacOS X is pretty much an enhanced NeXTStep.
The engineers are not "newbies" at it.
Re:Maybe you should use those purty fonts...
by
The+Bungi
·
· Score: 2
That's very interesting indeed. Now we get to the meat, eh?
Please provide spacific examples of how my freedoms are being abridged and limited, and how Microsoft owns my computer(s). Please, be specific and don't rely on what you've "heard" here in Slashdot since that's about as balanced and valid as sexual guidance from the Vatican.
The freetype bytecode interpreter is possibly infringing on an Adobe patent. MS and Apple both shell out big bucks in licensing fees to Adobe for rights to the patented aspects of TrueType rendering, and it shows in the quality of their screen font rendering.
Sounds like it's time for somebody like RedHat to shell out some of the big bucks they're making.
BTW your reason about not being able to distribute the Microsoft fonts is bogus. If that was the only problem, we could all just download them to the right folder and it would work, right? But it doesn't, and that is the problem, not a few missing fonts.
Your "reason" about the bytecode interpreter is also lame. You have explained why the fonts are RENDERED badly. But none of this explains the needlessly complex methods that are used for installing and using fonts under Linux. As usual, it's a bunch of excuses and no action.:(
Actually, those problems have been solved ...
by
shellbeach
·
· Score: 3, Informative
Have a look at these XFT/Freetype hacks. The author of these initially started off hacking XFT to remove hinting, then added back an improved "slight-hinting" model, and is now working on making the changes directly to the FreeType library (which has the added advantage of fixing OOo's fonts and making them look decent (finally!)).
I've been using this FreeType hack for a while now and Windows and MacOS look far worse in comparison. Just check out the screenshots on the page if you don't believe me!
Just change unix.js
by
shellbeach
·
· Score: 2, Informative
It's a simple matter of changing unix.js in *mozilla-directory*/defaults/pref/
Here's a diff of the default unix.js file against my customised one - note that there's a size for minimum aa'ing (which I have set at 1, but you could set at 16 if that's what you want), and that you can change the "bluriness" via dark_text.gain/light_text.gain settings.
Also note that this mod works with any version of mozilla - 1.0 or 1.1, you don't need to get 1.2b and you don't need to recompile - and all you have to do is edit this file. (And yes, I was cursing when I found out just how easy it was to enable aa'ing!)
I could swear I recently read a/.'d article about how it's actually "illegal" to extract fonts from one OS (particularly Microsoft) to another OS (particularly Linux).
Am I way off base?
--
Jerry Fletcher,
Privacy Protection By:
http://www.cotse.net/servicedetails.html
Re:I could swear....
by
terraformer
·
· Score: 2, Insightful
That is correct. Fonts (the files) themselves can be copyrighted but I not know if the ones that ship with the OS are. Just as an example, Adobe charges about $30 - $50 for recently released decorative fonts when purchased in individual packs. They get $8,999 (yes, that's right) for 2,750 ($3.27 per) fonts if you buy them in bulk.
Imangine what the printing houses that publishers use to print their stuff have to pay for all of those fonts. Adobe is not the only one people use and the printing house has to have their own copy for their presses.
-- Who are you? The new #2 Who is #1? You are #617565. I am not a number, I am a free man! Muhahaha.
Correction: The first two sentences should read:
That is possibly correct. Fonts (the files) themselves can be copyrighted but I do not know if the ones that ship with the OS are. Depending on the license, they may be limited to a particular OS.
I swear I previewed it twice and made corrections both times. I guess that should have made me preview it a third...
I am still hung over from stumbling around Cambridge last night. You have got to love the Cellar!
-- Who are you? The new #2 Who is #1? You are #617565. I am not a number, I am a free man! Muhahaha.
Not working in Mandrake 9.0. Someone plz help ...
by
vivek7006
·
· Score: 1
Now it's time to make them available. Re-start X, and then open the KDE
Control Center as root. Go to System, Font Installer. Click the tab 'Anti-Alias'
and tick 'Use sub-pixel hinting'. Now click the 'Fonts' tab
I am using Mandrake 9.0 and cannot find Font Installer under system
in KDE control center. Has someone tried this in Mandrake 9.0 (KDE 3.0) ?
Pfft, why go with a software solution
by
Xenph
·
· Score: 1
When all I need to do is put a lighter on my GeForce2 MX GPU for a few seconds and the whole screen AA's font, OS, Window manager and program independently!!
-- #include <Xenph Yan>
should have read the comments first
by
bkeeps
·
· Score: 1
After reading this article, I thought I might give it a try. However, I am using RH8 and didn't realize that I wasn't gaining anything. So I installed freetype and used Ctr+Alt+Backspace to restart X. Well, it never came back. I seem to be the only one with this problem, and I'm still a youngen in the Linux world.
What happens is X actually starts, but sits with the blue background before I get to the login screen.
A screenshot would work fine for your screen.
why not just stick it on your website? I'll do the same.
The problem I see is that I'm using Cleartype on a 1600x1200 LCD.. and if I take a screenshot, you won't really see what I see unless you are using an LCD with the exact same physical structure as mine... it will actually look fuzzy on your screen. What I see has absolutely no fuzz whatsoever, it looks razor sharp.
I will dig up the highest resolution camera I can find here and take a shot of a portion of the screen.. that should get the point across.
I'll send a screenshot too.. but you'll really want to view it on a 1600x1200 LCD with a digital interface to get the effect (and preferably the same model LCD as I have.. as the settings are tuned to it)
I'm using a Toshiba Satellite 5100 (The Canadian model)
Screenshot is at http://www.tesla.cx/screenshots/screenshot_fonts.T IF
Working on a photo...
Printers do anti-alias
by
wytcld
·
· Score: 4, Informative
... or something damn close to it. For an old HP LJIIIp that looks a lot better than an LJII, even though both are 300 dpi. It's because the IIIp uses smaller dots where appropriate at the edges. Many ink jet printers do the same thing. Not sure if anything at 1200 dpi bothers with this trick, but the trick's good enough that the quality difference between the IIIp at 300 dpi and a 600 dpi printer is very hard to see.
-- "with their freedom lost all virtue lose" - Milton
Re:Maybe you should use those purty fonts...
by
NortWind
·
· Score: 1
Please provide spacific examples of how my freedoms are being abridged and limited, and how Microsoft owns my computer(s). Please, be specific and don't rely on what you've "heard" here in Slashdot...
I guess that I am used to controlling the software on my computer. I pay for the computer, I own it. I pay for the software, I own it. I bought my music, I own it.
If you accept the EULA, you grant Microsoft the right to change the software on your computer. Please check with this InfoWorld article, not Slashdot. They can add DRM software, they can encrypt your own MP3's, and they can disable your favorite players for not being "secure". If they feel like it. When they feel like it.
It all makes good sense to them, and it will be good business for them. It just doesn't appeal to me.
Very screen specific
by
Looke
·
· Score: 2, Informative
When this patch recently was included in Debian's freetype package, TrueType fonts became significantly more blurred on my 1024×768 LCD screen. Rebuilding with the patch disabled (and the bytecode interpreter turned on again) restored my fonts to normal.
My point is that what looks good on my LCD monitor may look totally different on a hi-res 1600×1200 LCD or a normal CRT monitor. These things should be configurable, since there are different compile-time settings which give the best results on different screens.
Sub-pixel aliasing - is configurable, which is good.
Bytecode interpreter - is determined at compile-time, because of patent issues? That's not good:( (It does make a great difference, especially on small font sizes.)
"Ft slight" hack - is applied at compile-time, but should be made configurable when (if) included in the main freetype sources.
Anti-aliasing in general is very configurable, down to deciding which fonts in which sizes and variants should be anti-aliased. Great!
What we need is a very configurable freetype, with good configuration/preview tools; and a general understanding of the highly different effects on different displays.
Hmmm... isn't this a little dated now?
by
dabneyd
·
· Score: 2, Informative
This is good if you're using KDE = 2 or Gnome 1, but if you're using the latest versions, it's find of obsolete. Actually, KDE has had font smoothing since sometime in v2. What I'm saying is, if you want really nice fonts, download the newest version of Gnome or KDE, whichever you prefer.
Michael
You have explained why the fonts are RENDERED badly. But none of this explains the needlessly complex methods that are used for installing and using fonts under Linux. As usual, it's a bunch of excuses and no action.:(
Hey, if I had the l33t c0d3z0r1ng 5k1llz to fix this, I would have done it by now. Chastising me for failing to fix xfree's font handling is like complaining that your cat hasn't finished overhauling the car's engine yet!
A screenshot would work fine for your screen.
why not just stick it on your website? I'll do the same.
D'oh! Now, why didn't I think of that first...:-) I can't just put a screenshot up by itself, though, I have to put it inside a web page: my apache is set up so that you can't browse the contents of a folder...I'm sure I can change that for a specific folder, but I really don't feel like touching the configuration right now - my motto is: it works, leave it alone!
The problem I see is that I'm using Cleartype on a 1600x1200 LCD.. and if I take a screenshot, you won't really see what I see unless you are using an LCD with the exact same physical structure as mine... it will actually look fuzzy on your screen.
Actually, considering that the screen shot should be seen on a LCD, I must admit it looks pretty good. I can mentally compensate for the visual artifacts, of which there aren't that much (they don't look "fuzzy" as much as discolored). Pretty slick...
Now, I don't how my screenshot (from a CRT) will look on your display...I've tried to include a couple of windows to show how the fonts behave under a variety of apps...mind you, KDE does a great job when it comes to font consistency (not to start a flame war...I haven't really tried Gnome2 yet).
Well, looks like a draw to me...
--
Reminder: find a new sig
Re:Not working in Mandrake 9.0. Someone plz help .
by
cyberb0b
·
· Score: 1
In Mandrake 9.0 I used the Configuration -> Mandrake Control Center (which runs drakconf) and in the System -> Fonts section (which runs drakfont) to import my windows fonts automatically. I'm not sure where 'Use sub-pixel hinting' is, but my fonts seem to work fine with anti-aliasing on and off (checkbox in KDE Control Center -> Look and Feel -> Fonts).
Xfthack looks inferior to RH8 stock Xft2
by
tau_
·
· Score: 1
To me, the xfthack results (based on the posted screenshots) look clearly inferior to RH8's stock Xft2 functionality (set to slight hinting, subpixel RGB rendering, to match my LCD panel).
Why? Look at the vertical lines of the fonts: they're not sharp. In fact, the results look more like hinting completely disabled! That I can do myself with a click in the font prefs.
I don't think Xft2 is quite there yet either - some diagonal lines, such as the drop line in 'y' at some sizes of Times New Roman, gets rendered so thinly that it's difficult to see at all. Perhaps that's because I haven't rebuilt Freetype with the bytecode hinter enabled.
Hinting is a difficult issue, and very much related to the resolution of your display. Single words or short phrases (such as titles) always look better without hinting, because (especially with subpixel rendering enabled) the character shapes and spacing is more correct. However, large bodies of text become difficult to read because individual characters are blurred. That's where hinting helps: it subtly changes character spacing and shapes to reduce blur (improve contrast). Text becomes more readable - unless the uneven spacing bugs you more than blurry shapes.
A few years back, I was on Babble, the Cure mailing list. One day someone posted that they were recently in a car accident, and had been listening to the Cure at the time: not on tape, but on the radio. Suddenly, out of the wood work came a bunch of "Me-too"'s: people that had been in auto accidents or similar, and had been listening to the Cure at the time. Some started to think that this was some kind of omen, mentioning how disconcerting it was and the like, until one guy posted a response along the lines of: "Everyone on this list is a Cure fan. Because of that, everyone will have a tendancy to either listen to Cure tapes in their car, or tune to radio stations that play the Cure." That shut everyone up fast.
The point here is that you're a Linux user. You read/. because it has a lot of stories about Linux and tweaking Linux. The fact that you were tweaking some aspect of your Linux system, went over to/. and saw a story about exactly what you were doing is not coincidential. It's a very basic statistical correlation.
Now then, had you gone over to MSN and found an artical about tweaking fonts in Linux while in the midst of doing such, I'd say it's time to pull out the tin-foil hats, pack up the kids and head for the hills.
Celestial navigation is based on the premise that the Earth is the center of the universe. The premise is wrong, but the navigation works. An incorrect model can be a useful tool.
-- Kelvin Throop III
- this post brought to you by the Automated Last Post Generator...
I was in this prematurely air conditioned supermarket and there were all these aisles and there were these bathing caps you could buy that had these kind of Fourth of July plumes on them that were red and yellow and blue and I wasn't tempted to buy one but I was reminded of the fact that I had been avoiding the beach.
-- Lucinda Childs "Einstein On The Beach"
- this post brought to you by the Automated Last Post Generator...
Isn't it strange that this gets posted as I'm futzing with my fonts? I open konqueror to test them and I see this!! Just confirms my fears that THEY are watching my every move...
Does that mean they'll look like they were sprayed with Rust-Oleum? That's how my grandfather makes everything purdy.
---
DRM is like antifreeze, to the MPAA/RIAA it's sweet, to the consumers it's poison.
1. Install a distro that actually cares about fonts. Eg, Red Hat 8.
Congratulations, you're finished.
I know someone will get on here saying (or at least think it), can't we concentrate on making the 2.5 kernel as stable as 2.2.x. Fonts are just for making things look 'purdy' which doesn't help if you are crashing, blah blah blah
Fonts are very important.
Fonts are one of the last barriers to a linux migration. That is also one of the first (negative) differences people notice on my monitor.
Never underestimate the lure of a goodlooking UI on the average user!
--Joey
Maybe it's just me, but the after picture looks worse than the before picture. Or, maybe it's just a case of "Oops, I named the files wrong."
Overrated / Underrated : Moderation
The author recommends you install the fonts in 2 or 3 different places. Whatever happened to installing them in one spot and symlinking to the others? Also removes the need to go thru the whole copy to the other directories rigamorale everytime you reinstall/upgrade.
Why not fork?
Licensing issues with apple
GTA3 is like the Sims to me - MC Hawking
http://www.bradenton.com/mld/bradenton/news/nation /3876857.htm
Chicago2600.net more than a lifestyle, its a survival trait.
I want fonts to be antialiased on paper, not on the screen.
If you don't have ClearType or font smoothing, you can approximate the effect.
Just smear Vaseline evenly over your screen - voila! Antialiased fonts!
It worked for Cybil Shepard on 'Moonlighting'.
Well, personally, I prefer to read text without AA, because anti-aliased text is too blurry. Sure it looks pretty on screenshots and you can impress al your friends, but really, when I have to read large amounts of text from a pc screen my eyes get tired twice as wuickly with AA switched on. Sharp edges help.
Now, merely having TTFs or anti-aliasing isn't enough. Take a look at this screen shot of TTFs in an OpenOffice.org document. They're clunky and blocky and basically impossible to distinguish from each other. However, with a bit of tweaking we can make them look distinct, slick and refined, as you can see in this screen shot.
I think everyone agrees that the first one is horrible. And the second... well maybe it's just me, but I can't see a difference between their tweaked AA and my own no-tweaked non-AA...
Join the elite! Post at score:2! Ghostwheel is online.
Red Hat 8 appears to have most of this set up from the factory, with the exception of the MS fonts.
There is an unbelievably irritating aspect of anti-alised fonts I've found with RH8 (and in previous experiences with Gnome2): GTK+2 apps will insist on using Anti-alised fonts for EVERYTHING, and there seems to be no way to turn it off. While I think anti-aliased fonts are wonderful most of the time, I believe most developers will agree they are not so great in terminal windows or when viewing source code.
If you change your font preferences to "monochrome", you can then set source code editor/terminal fonts to non-anti-aliasable ones, like LucidaTypewriter. Then switch the font prefs back to your previous anti-aliased setting, and the modified programs will retain the non-antialiased font setting.
I don't know whose fault it is that this workaround is required (GTK, Red Hat, the apps themselves, etc), but it would be most appreciated if non-antialiasable fonts appeared in the font-selection dialogs even when antialiasing is enabled.
...can be found here. It's really easy to follow his instructions to get true type fonts working right.
That HOWTO seems to ignore the best option for getting pretty fonts on X, Xft.
I am currently running Redhat 8.0 with an XFT version of Mozilla, and I must may my screenies are much prettier.
With Xft, FreeType, and some good TrueType fonts, I finally have a Linux desktop with fonts prettier than WinXP.
With the recent sendmail trojan (which trojaned your system when you ran make), I would assume people would be more careful of this. The howto author compiles as root, just a warning...
I'm sorry to say that these people obviously haven't messed with the fonts stuff other than the top layer of complexity. I suggest if you are really interested in font antialiasing and configuration you look at Fontconfig and Xft2. Keith Packard has done an excellent job with these products along many other cool things within X (ie. Render Extension, RandR, the new XCursor system). Compiling everything with Fontconfig/Xft2 support is a little daunting at first, but when you're done it looks great.
Step 1) Install Redhat 8.0 (If you can, f*cking .0 releases)
Step 2) Install MS core font package from http://corefonts.sourceforge.net/
Enjoy.
No really Redhat 8.0 has terrific looking fonts with the exception of Mozilla, but I'll wait a little longer for a 1.2 build with Xft support.
Anyhow KDE has had AA for a while and I'll admit I've been envy and now that Gnome has too, and Mozilla will have it soon, I don't suspect I'll even have to think about it again. Expect all distros to have this setup by default.
Who the fuck cares.
For those saying that ClearType style subpixel hinting is "too blurry", you should be aware that it only really works on TFT screens as the way it works requires a set pixel layout, which traditional CRTs don't have. Steve Gibson has a fairly good explanation of how it works on his website (if you can put up with his infuriating self-congratulatory writing style).
:D
So yes - regular antialiasing should be all that's needed on a CRT.
And... I'm currently typing this from Konqueror 3, which renders subpixel antialiased Truetype and Type1 fonts absolutely beautifully, along with the rest of KDE 3, in fact I would say it looks a lot nicer than Cleartype. Especially on a 1600x1200 TFT. Mmm, shiny
He goes through all the hassle of rebuilding Freetype, and then the screenshots at the end aren't even antialiased...
So what was the point of this article again?
Everybody cares about fonts not being perfect.
Nobody cares grep's -o option doesn't work with -i (well, it's actually already fixed in RawHide, but that's another matter).
After half a year we can expect articles about screensaver settings in Linux while RedHat will stop distributing xterm, because of no one using terminal any more.
Is Linux dead?
Life is the slowest way to death.
First off: if you're basing your choice of operaing system on a windowing program's ability to render fonts, then something is seriously wrong. IMHO.
Second: I don't like anti-aliased fonts. I'd rather look at code/text in a non-AA, monospaced font. It gives me fewer headaches. Text in a magazine or on a newpaper is one thing, but when I'm looking at a monitor, I don't want anti-aliasing. "Linux" (those with a clue, just assume that X is Linux for a minute here for the sake of discussion; some people don't know that the GUI and the OS are two different things) displays fonts just fine for me. If I wanted AA fonts, I can have them. If I don't want them, I don't have to get them; nobody has made my choice for me. Being forced to put up with someone else's choices is really what is pathetic. (Although trolling with old Windows bigotry comes close.)
-B
Ash and Hickory, straight-grained and true, make excellent bludgeons, dandy for the cudgeling of vegetarians.
Mostly the same stuff, possibly?
The flag that this article suggests turning on is off by default because the hinting algorithm in question may violate Microsoft and Apple patents. Not the average user really cares about this, but it was irresponsible of The Register to not explain this in the article. On the other hand, this is The Reg we're talking about here...
More info: http://freetype.sourceforge.net/patents.html
I've got to point out this site for improving fonts even more. The difference it made to my fonts was amazing - and I was already using sub-pixel rendering and a laptop display with freetype2-2.1.2 (with the bytecode interpreter compiled in).
I STRONGLY recommend you try it out - he even includes a pre-compiled libfreetype (built for Red Hat, I think, but works great on Mandrake 9.0). You'll need to put it in the right directory, and create the right symbolic links to it.
I don't know how much of the improvement is due to this guy's improvements, and how many are due to the upcoming freetype2-2.1.3, but whatever - Linux fonts are no longer inferior to look at.
Jus' a second thought.
listen here.
you're preaching to the choir.
but your an asshat. take a deep breath and think before you speak.
and whether your OS is gui driven or cli driven is irrelevant. it's the use you make of it that is (or isn't) "mindless".
i for one am sick of typing everything, and sick of the tendonitis i've developed from years of doing so.
only do-nothing IT guys and admins brag about using a command line.
i do however have a problem with linux becoming windows, because noone seems to be able to think of anything better.
I don't need no instructions to know how to rock!!!!
Just mkdir ~/.fonts and copy your TrueType fonts in there. WHAMMO, instant MS fonts. Still though, I'm trying to get Mozilla looking better. Makes my website look like it got up on the wrong side of the bed.
There is nothing inherently safe about liberty. That's why so many people died protecting it.
(look at the pictures)
track7.org has all kinds of interesting stuff!
Well to start. Why shouldn't admins have a nice screen to look at? I use to work with a very very nice monitor (commercial OS) that had such a beautiful screen. Shame I couldn't take it home with me. Now I can have the same experience with my home OS. Two by unified userbase you wouldn't be forgetting all the different varieties of Unix out there would you? Three it is a myth that you have to give up control while having ease of learning as well as use. However the present problem I see with what's coming out is that an interface that "grows" with you as you transit from newbie to power-user is hard to do. Most interfaces commercial or otherwise hit either end, while being weak in the middle. Can an interface be for everyone? Yes, but it may mean more work and looking very hard at what we presently assume.
From the last time I did this:
1-an interface needs to be free of unnecessary elements at all time. In other words (does this contribute to the goal(s) being achieved?).
2-An interface needs to keep it's audiance in mind. Professional? Amateur? Artist? Blue-blood?
3-Organizing devices must leverage common elements while going from general to specific.
4-Make the interface playable by making the consequences of actions as reversable as possible.
5-If an action is unreversable let the user know in a non-threatening, non-insulting way.
6-Choose intelligent defaults.
7-Keep the perception as much as possible that the user is in control of the situation.
8-If control is needed in a situation (a certain sequence needs to be followed) guide the user as gently as possible.
9-As part of transiting from newbie to power-user. Have the interface show you some of the alternative ways to accomplich the same task.
10-User control of variable preferences is one way to accomplish gradual disclosure of the power that lies beneath without intimidating the user.
Anyone else want to add anything?
Much as the work on getting fonts to work on X is to be commended, I don't think we're ready to start showing off just yet.
Get back to me in a few years when something approaching a workable standard is around.
I don't get it. The two screenshots he shows to compare (923.png and 930.png) look identical to me, except that one has anti-aliasing and one doesn't. He claims the second one looks better, but I don't see it.
In fact, I think his screenshots look pretty ugly in general. He's managed to duplicate the blocky, hard-edged look of Windows 9x quite well, but I hardly consider this attractive. Red Hat 8.0's fonts look significantly better than his screenshots.
Mac OS X still has a wide lead on best look fonts, but IMO a modern Linux box has superior fonts to any version of Windows.
Cleartype only really works if you are using an LCD, btw... and it depends on how the LCD screen is constructed.
Also, have you gone to the proper MS site and tuned your cleartype settings?
Tune Cleartype
IF you have a 1600x1200 laptop, I recommend setting XP to 120dpi instead. Yes, the fonts get larger, and some things are a bit out of whack due to bad programming.. but I assure you the increased resolution combined with cleartype makes things look sweeeeeet. Also, if you use Acrobat Reader (which uses it's own font rendering engine), make sure you go into the settings and turn on CoolType to get similar results.
Another trick to getting nice fonts is to insure you've installed any scalable fonts you can get your hands on.
I am posting the same thing here as I posted over at the dot 10 minutes ago. Just a glace at his two Openoffice screenshots showed me this guy is seriously whacked. The second screenshot, which he claimed is "more refined" is clearly much more jagged than the first. A simple look with Xmag sees the only difference between the two is that the second has anti-aliasing turned off. Same with the"results" screenshots at the end.... they look like crap compared to my fonts in KDE, and I did nothing speccial. Just apt-get install msttcorefonts in Debian. There is no anti-aliasing going on at all in these screenshots, they look horrible.
Now, I totally respect people who don;t like anti-aliased fonts. but in KDE (which this article seems to be mainly about) or OpenOffice, disbling anti-aliasing is as easy as unchecking a menu option... if you don't want it, don't use it. What is the point of the whole long process in this article exactly?
I guess stealing fonts from Microsoft so that you can have a decent-looking OS is heroic.
And please don't give me the stupid "M$ is evil" spiel. It's as tired as a hooker at a GeekWorld convention.
I guarantee that if you sat down in front of my windows laptop, you would fall instantly in love with programming on it, simply because of the fonts.
I know what you are saying about AA fonts giving you headaches.. but that's because they aren't properly antialiased.
Proper antialiasing yields fonts that look solid and smooth, and are easier on the eyes, not harder.
Define acceptance? Some of us click "Agree" knowing full well we don't agree to anything, and that we will do what we want in spite of those alleged terms.
I cannot comprehend what is so hard about making fonts work. TrueType is a known format. The OS loads it up and the programs use the OS to interact with the fonts, right? Windows and Mac handle it fine, what exactly is the cause of the difficulty under Linux?
If you're running a high-res screen (currently this would be one of those 133 or 140 DPI LCDs) or if you like your fonts on the softer side, the TrueType hinting algorithm will tend to make your fonts too thin. I'm running a 1600x1200 LCD and the bytecode interpreter, which tends to snap fonts to integral numbers of pixels, distorts the shape and makes fonts too thin to read. A wonderful fix for this is to download and compile the FreeType2-current from FreeType's FTP site (under the unstable directory). Then, get some nice Type1 fonts (currently, a lot of fixes are in the pshinter) and make sure to disable the TrueType bytecode interpreter (it's disabled by default). Turn on AA, and you're treated to some wonderfully rendered fonts. Anti-aliased enough to be smooth, but still sharp enough to be easily readable. I've got a screenshot at: http://home.mindspring.com/~heliosc/fonts.png
A deep unwavering belief is a sure sign you're missing something...
The point of TrueType is not to give you more readable fonts than good manually designed ones, it is to give you complete families of decent fonts at many screen resolutions and sizes; that's needed because it would be way too much work to design all those font instances by hand. Still, if you did, you'd only improve the TrueType output.
Furthermore, anti-aliasing, font smoothing, and similar tricks do make pages appear prettier, but they generally don't enhance readability, and may even degrade it. That's why, among other things, many systems let you turn off font smoothing below a certain size. Cleartype and its equivalents, however, may help with readability, since they really do increase spatial resolution (at the cost of color fidelity).
Ok so here I am with my first moderator points in who knows how
long[0] and I wanted to use them so badly on this thread because I am
really new to this whole X font thing having spent so much time in a
self imposed exile to the command line for two years[1]. So I am back
to using X and this font HOWTO sounded like a great idea. Until I
started reading it. To paraphrase "Just unpack the src RPM". Well
hell I thought HOWTOs were supposed to be distro independent because
the HOWTO might outlive the distro and because not every one uses
Uber_Distro_GNU/Linux. I fit in to that latter category. I run
Slackware and some people run Debian. Now it is possible to unpack
that RPM and futs with it for a little while and hope that it works
no matter what distro you are on but the HOWTOs are supposed to "speak
in a language that everyone can comprehend."[2]
One of the tricks to Linux's success is that is very portable to any
arch. Shouldn't the HOWTOs be written with the same idea?
I really did want to use those mod points here. Oh well better luck
next thread.
[0] remember that 1000 mod pointed post? Well apparently I have
served my time.
[1] to better learn this thing called Linux better than a GUI will
ever allow.
[2] no thats not a Living Color song.
Ascii artist &
Windows 2000/XP: Install a font by dragging it to the fonts folder.
Mac OS X: Install a font by dragging it to the fonts folder.
Linux: Some convoluted thing that involves downloading the Microsoft (!) fonts and putting them in several different places.
Windows XP: Turn antialiasing or ClearType on by checking a box in the display properties. (Note: ClearType is only recommended for digital flat panels.)
Mac OS X: Turn antialiasing/sub-pixel rendering on by checking a box in the display properties.
Linux: Recompile this thing, and oh yeah you have to edit a header file, and then do this, and then it will work, except not in Mozilla, because then you have to do this and the other thing. (A three-page description follows.)
I agree with the first post here. Getting Linux to look good on the desktop is possible. Getting Windows XP or Mac OS X to look good on the desktop is easy. Thanks, but I don't want to f*ck with my computer just to make it look good.
Am I the only one who finds it rediculous all of this isn't in KDE already.
Why do we need to use MS True Type fonts isn't there a way for the community to make their own?
I know nothing about fonts just curious.
I agree, computers are for everyone. Everybody should be able to use one.
What I'm saying is that I'll be damned if I'm going to worry about how granny writes her email. It's not my problem. I don't play the IT game so that you can have a good time, I do it so that I can have a good time. Let's see, I could hack together a console editor in a few days, or I could write an easy to use word processor that isn't going to make me a dime and will take months to complete, but it's for the "greater good". Tough call.
This may be a selfish attitude, but there's at least some of it in every developer.
Apple made OS X so damned sweet because they're selling it. Money, baby. Linux developers are still largely hobbyists and college kids, not the kind of people who really care what their word processor looks like, or if their fonts are nice and smooth. They don't have anybody to please but themselves.
Go ahead and mod it down, I know you're itching to.
--
pants ahoy
I can guarantee you that if you saw my Linux desktop with fonts anti-aliased with David Chester's Xft hack, you'd instantly want to switch. Frankly, I have yet to see TTF fonts this beautiful on any system, Mac OSX included, especially in 1600x1200. I mean, look at this screenshot! Sorry, but I work on a Windows machine all day, with anti-aliased turned on, and it doesn't even come close to this.
The font battle has been won, and the winner is Xft+freetype+Chester's font hack.
Reminder: find a new sig
This is far funnier than my post. hehehehe
Though I don't for one second doubt you... I'm willing to bet your desktop and mine are a close battle.
Mac OSX doesn't hold a candle to what I see here.
If you have something that looks better than this... I'm all for it.
So.. how are we going to compare? The only thing I can think of is ultra high resolution photographs.
What kind of screen are you using?
Honestly, I do NOT see nice fonts displayed any time there is an article about fixing fonts in linux.
There is one place and one place only that I have ever seen a screen loaded with nicely antialiased fonts...my KDE desktop using the longtime antialiasing support from QT. The fonts I have are SMOOTH. Let me reiterate that, they are smooth. No jaggy lines, no stairstep angles, just smooth antialiasing. Beautiful.
I then read an article like that at the Register, look at the screen shots, and all I can do is say "What the fu*K are they talking about?! Those fonts are STILL jaggy and they are NOT aa.
I've recently read a few other articles about fonts, aa, and hinting. I look at the results in screenshots and the fonts are either STILL jaggy or they are horrifically smeared. If hinting means "smear the crap out of the font until it makes you think your glasses are greasy or you are developing cataracts" then that hinting crap is working great! Nice looking aa fonts do NOT have to be blurred out of recognition. AA means NO jaggy lines, just smooth, flowing, SLIGHTLY (EVER so slightly) blurred fonts.
So far, mozilla simply has ugly font rendering no matter how you slice it. Its fonts are jaggy/stairstepped. Period. Butt-ugly. Same with Gnome. I have tried to get fonts to look as nice in Gnome as they look in KDE but it just doesn't happen. I either get the greasy glasses effect or jaggy lines.
I have to come to the conclusion that when people SAY antialiasing, they really don't know what their are talking about. Or they are referring to a different antialiasing than I am aware of. If your fonts have jaggy lines, then you are NOT enjoying the fruit of aa. Sorry, but that is a fact.
In Bushworld, they struggle to keep church and state separate in Iraq as they increasingly merge the two in America.
That's the only explanation. I was puzzled by it too! When I found the first, anti-aliased screen and he says he'll improve it a lot I thought "Wow, let me see the second screen now!".
:)
:)
The second screen shows non-AA fonts!
Weird!
You seem to think that because you have figured out how to have beautiful fonts in Linux then ergo, Windows sucks and is not necessary. That's kind of a stretch, mmm?
Also, the "well, if I want them or not blah blah blah" choice (and I use the term lightly since I can't imagine myself thinking "hey, I want my apps to look crappy!") is pretty fucking irrelevant to the topic. I don't give a shit if you can do something like '#fontometric -i -r00 -l -pr3 -tti -font' or some such weird incantation to reach anti-aliasing Nirvana. If it doesn't do it out of the god damn box then it's pretty much useless.
Being forced to put up with someone else's choices
Spare me the communist claptrap bud.
Trillian runs fine under wine, albiet without *any* alpha blending (not sure tho, it may work on a version of X that supports transparency)
(Just realised I'm using WineX 2.2 - may make a difference, but it works for me)
Two main reasons, both derive from IP issues.
The freetype bytecode interpreter is possibly infringing on an Adobe patent. MS and Apple both shell out big bucks in licensing fees to Adobe for rights to the patented aspects of TrueType rendering, and it shows in the quality of their screen font rendering. Second, the fonts that are available freely (GNU free, not $0 free) are utter shite. They would look bad on any system. Microsoft has great fonts, which are available for free (as in no money) but there are some restrictions on distributing them, so they are never included in a Linux distro.
0 1 - just my two bits
If you accept the EULA, you accept that MS owns your computer, owns any software that you buy from any vendor that you run on that computer, and owns any music or other data that you keep in there. If you are willing to accept that, then I do feel sad for you. Check "pathetic".
I guess stealing fonts from Microsoft so that you can have a decent-looking OS is heroic.
I do not advocate stealing those fonts from Microsoft. Microsoft did make those fonts available for free use, to establish them as a standard for web use, but you what? They decided to change the license. They have that right legally, just as they have the right to change your EULA. Now Linux doesn't have any pretty fonts. Somebody will make some open source fonts someday, I'm not worried. I'll wait.
And please don't give me the stupid "M$ is evil" spiel. It's as tired as a hooker at a GeekWorld convention.I don't think Microsoft is evil. They are a corporation, they are just in the business of making money. They get the most money by controlling their software, your computer, and you. It's efficient. Profits are double what they were same quarter last year! I just don't want to be part of it anymore. I can't imagine why you do.
GNU/Linux does have good defaults, for a server.
However, for the most part, it has very poor defaults for the average home-user desktop-user. I'm speaking as a Debian user here.
Distributions should offer a "desktop" option during setup, which will set things up nicely for the average desktop user: that means anti-aliasing, maximum resolution possible, 16-bit color, a reasonable font-set, and a good default GUI-configuration (this does not mean a aqua-esque theme; this means that, for example, if the WM is WindowMaker, icons for the internet, e-mail, spreadsheets, word processors, etc should be on the dock).
All of the right stuff is there to make GNU/Linux. All that developers need to do is set up good defaults. This is simply a configuration issue; it is not something which is going to prevent you from devoting enough time to core technical issues.
social sciences can never use experience to verify their statemen
I copied over MS TTF fonts and X acknowledged them but looking at a webpage in Moz with Verdana shows huge disproportionate characters. Is this a problem with Mozilla or just a problem with raw TTF/xfs?
It refers to the Microsoft-provided font package, and that's been removed from Debian ever since MS pulled the fonts. The msttcorefonts
Pity, too, because I run Debian, and I've never been able to get decent fonts under any flavor of Linux.
You cannot apply a technological solution to a sociological problem. (Edwards' Law)
Somebody else told me that the MS fonts have been reposted somewhere on sourceforge, and that Debian now downloads them from there. That'd be neat.
I love typesetting, but I hate messing with fonts on my computer. Why the hell can't they look nice out of the box?
You cannot apply a technological solution to a sociological problem. (Edwards' Law)
Well if you look at the font fiascos in recent distributions and desktops (I am speaking of Mandrake 9.0 -- and from what I have heard RedHat), then you end up having about 5000 fonts and each application you run can use about 10 of them. So you end up with some applications able to use some fonts , and other applications able to see others. Depending on what type of app or window manager you are running -- you see a variety of "effects" that may or may not resemble AA. Gtk 1.x apps see some fonts, Gtk 2.x apps see others, QT sees others AND PLEASE don't even get me started on font sizes, most apps just asumme that size 12 is about all they want to use, and some gtk apps occasionally start up with a nice 72 point font staring back at you for some crazy reason or another -- Xfontsel can see a bunch of them but in itself does not do much. (to me it just looks like multiple levels of blur.)
I bet one could write a book with a chapter on each different method for displaying fonts in these new distributions. And if you want to get really confused you can look at the 7 or 8 different font configuration files used to put this clusterfuck together. Whatever happened to the good old days where I could just run XFSTT on a port and get all of my TT fonts pretty much the same as in Windows -- and this was even before XFree 4. With the advent of XFS and XFree 4 we got some primitive looking Jaggy things that "claimed" to be our TT fonts -- but at least where I was standing you could not pick them out from a lineup.
I still don't see how we are any better off in the "font world" than we were 4 years ago -- it seems that each toolkit has just decided to try to invent there own ways to render fonts.. Crazy -- Crazy -- Crazy.
(+1 Funny) only if I laugh out loud.
Making things look purty is always good.
Unless it's the layout and color scheme of Slashdot.
The middle mind speaks!
Not a great screen, but reasonably priced: SyncMaster 955DF from Samsung (500$ canadian for 19"). It does the job!
I can always send you a screenshot (I don't have a digital camera...yet!). My email address at home can be found on my website, under the heading "Courriel" near the bottom of the right hand column (just above the "small type"). The link text is "m'écrire".
But if you say that your display is better than OSX, then I guess that our desktop are pretty close. I'm happy with calling it a draw (though I wouldn't mind a screenshot in any case). Your call.
Reminder: find a new sig
I do understand anti-aliasing, but the parent post is right -- on some screens, at some resolutions, AA'd screen fonts look fuzzy (worst case, they can be almost unreadable). So I think it's good, even necessary, to allow anti-aliasing to be turned off if the user so desires.
BTW, I frequently need to resize image files of various sorts, and have learned that sometimes (depending on content) they look better when I turn off anti-aliasing.
~REZ~ #43301. Who'd fake being me anyway?
"look at what Apple have managed to achieve with MacOS-X.. although they're newbies when it comes to BSD they've managed to design it around the home user rather than the geek.. "
NeXTStep is over 15 years old.
MacOS X is pretty much an enhanced NeXTStep.
The engineers are not "newbies" at it.
Please provide spacific examples of how my freedoms are being abridged and limited, and how Microsoft owns my computer(s). Please, be specific and don't rely on what you've "heard" here in Slashdot since that's about as balanced and valid as sexual guidance from the Vatican.
Breathlessly awaiting your insight.
Sounds like it's time for somebody like RedHat to shell out some of the big bucks they're making.
BTW your reason about not being able to distribute the Microsoft fonts is bogus. If that was the only problem, we could all just download them to the right folder and it would work, right? But it doesn't, and that is the problem, not a few missing fonts.
Your "reason" about the bytecode interpreter is also lame. You have explained why the fonts are RENDERED badly. But none of this explains the needlessly complex methods that are used for installing and using fonts under Linux. As usual, it's a bunch of excuses and no action. :(
I've been using this FreeType hack for a while now and Windows and MacOS look far worse in comparison. Just check out the screenshots on the page if you don't believe me!
Here's a diff of the default unix.js file against my customised one - note that there's a size for minimum aa'ing (which I have set at 1, but you could set at 16 if that's what you want), and that you can change the "bluriness" via dark_text.gain/light_text.gain settings.
Also note that this mod works with any version of mozilla - 1.0 or 1.1, you don't need to get 1.2b and you don't need to recompile - and all you have to do is edit this file. (And yes, I was cursing when I found out just how easy it was to enable aa'ing!)
70,74d69
231c226
---
> pref("font.FreeType2.enable", true);
235c230
---
>
238c233
---
> pref("font.antialias.min", 1);
241c236
---
> pref("font.scale.tt_bitmap.dark_text.gain", "0");
245a241
> pref("font.directory.truetype.1", "/usr/X11R6/lib/X11/fonts/drakfont");
250,251c246,247
---
> pref("font.scale.aa_bitmap.always", true);
> pref("font.scale.aa_bitmap.min", 1);
255c251
---
> pref("font.scale.aa_bitmap.dark_text.gain", "0");
I could swear I recently read a /.'d article about how it's actually "illegal" to extract fonts from one OS (particularly Microsoft) to another OS (particularly Linux).
Am I way off base?
Jerry Fletcher,
Privacy Protection By:
http://www.cotse.net/servicedetails.html
so i don't need no font antialiasing! :)
matula
Now it's time to make them available. Re-start X, and then open the KDE Control Center as root. Go to System, Font Installer. Click the tab 'Anti-Alias' and tick 'Use sub-pixel hinting'. Now click the 'Fonts' tab
I am using Mandrake 9.0 and cannot find Font Installer under system in KDE control center. Has someone tried this in Mandrake 9.0 (KDE 3.0) ?
When all I need to do is put a lighter on my GeForce2 MX GPU for a few seconds and the whole screen AA's font, OS, Window manager and program independently!!
#include <Xenph Yan>
After reading this article, I thought I might give it a try. However, I am using RH8 and didn't realize that I wasn't gaining anything. So I installed freetype and used Ctr+Alt+Backspace to restart X. Well, it never came back. I seem to be the only one with this problem, and I'm still a youngen in the Linux world.
What happens is X actually starts, but sits with the blue background before I get to the login screen.
Anyone have any ideas?
A screenshot would work fine for your screen.
T IF
why not just stick it on your website? I'll do the same.
The problem I see is that I'm using Cleartype on a 1600x1200 LCD.. and if I take a screenshot, you won't really see what I see unless you are using an LCD with the exact same physical structure as mine... it will actually look fuzzy on your screen. What I see has absolutely no fuzz whatsoever, it looks razor sharp.
I will dig up the highest resolution camera I can find here and take a shot of a portion of the screen.. that should get the point across.
I'll send a screenshot too.. but you'll really want to view it on a 1600x1200 LCD with a digital interface to get the effect (and preferably the same model LCD as I have.. as the settings are tuned to it)
I'm using a Toshiba Satellite 5100 (The Canadian model)
Screenshot is at http://www.tesla.cx/screenshots/screenshot_fonts.
Working on a photo...
... or something damn close to it. For an old HP LJIIIp that looks a lot better than an LJII, even though both are 300 dpi. It's because the IIIp uses smaller dots where appropriate at the edges. Many ink jet printers do the same thing. Not sure if anything at 1200 dpi bothers with this trick, but the trick's good enough that the quality difference between the IIIp at 300 dpi and a 600 dpi printer is very hard to see.
"with their freedom lost all virtue lose" - Milton
I guess that I am used to controlling the software on my computer. I pay for the computer, I own it. I pay for the software, I own it. I bought my music, I own it.
If you accept the EULA, you grant Microsoft the right to change the software on your computer. Please check with this InfoWorld article, not Slashdot. They can add DRM software, they can encrypt your own MP3's, and they can disable your favorite players for not being "secure". If they feel like it. When they feel like it.
It all makes good sense to them, and it will be good business for them. It just doesn't appeal to me.
When this patch recently was included in Debian's freetype package, TrueType fonts became significantly more blurred on my 1024×768 LCD screen. Rebuilding with the patch disabled (and the bytecode interpreter turned on again) restored my fonts to normal.
My point is that what looks good on my LCD monitor may look totally different on a hi-res 1600×1200 LCD or a normal CRT monitor. These things should be configurable, since there are different compile-time settings which give the best results on different screens.
What we need is a very configurable freetype, with good configuration/preview tools; and a general understanding of the highly different effects on different displays.
This is good if you're using KDE = 2 or Gnome 1, but if you're using the latest versions, it's find of obsolete. Actually, KDE has had font smoothing since sometime in v2. What I'm saying is, if you want really nice fonts, download the newest version of Gnome or KDE, whichever you prefer. Michael
You're too funny, man... Right on.
-B
Ash and Hickory, straight-grained and true, make excellent bludgeons, dandy for the cudgeling of vegetarians.
-B
Ash and Hickory, straight-grained and true, make excellent bludgeons, dandy for the cudgeling of vegetarians.
You have explained why the fonts are RENDERED badly. But none of this explains the needlessly complex methods that are used for installing and using fonts under Linux. As usual, it's a bunch of excuses and no action. :(
Hey, if I had the l33t c0d3z0r1ng 5k1llz to fix this, I would have done it by now. Chastising me for failing to fix xfree's font handling is like complaining that your cat hasn't finished overhauling the car's engine yet!
0 1 - just my two bits
A screenshot would work fine for your screen. why not just stick it on your website? I'll do the same.
:-) I can't just put a screenshot up by itself, though, I have to put it inside a web page: my apache is set up so that you can't browse the contents of a folder...I'm sure I can change that for a specific folder, but I really don't feel like touching the configuration right now - my motto is: it works, leave it alone!
D'oh! Now, why didn't I think of that first...
Check the screenshot here.
The problem I see is that I'm using Cleartype on a 1600x1200 LCD.. and if I take a screenshot, you won't really see what I see unless you are using an LCD with the exact same physical structure as mine... it will actually look fuzzy on your screen.
Actually, considering that the screen shot should be seen on a LCD, I must admit it looks pretty good. I can mentally compensate for the visual artifacts, of which there aren't that much (they don't look "fuzzy" as much as discolored). Pretty slick...
Now, I don't how my screenshot (from a CRT) will look on your display...I've tried to include a couple of windows to show how the fonts behave under a variety of apps...mind you, KDE does a great job when it comes to font consistency (not to start a flame war...I haven't really tried Gnome2 yet).
Well, looks like a draw to me...
Reminder: find a new sig
In Mandrake 9.0 I used the Configuration -> Mandrake Control Center (which runs drakconf) and in the System -> Fonts section (which runs drakfont) to import my windows fonts automatically. I'm not sure where 'Use sub-pixel hinting' is, but my fonts seem to work fine with anti-aliasing on and off (checkbox in KDE Control Center -> Look and Feel -> Fonts).
To me, the xfthack results (based on the posted screenshots) look clearly inferior to RH8's stock Xft2 functionality (set to slight hinting, subpixel RGB rendering, to match my LCD panel).
Why? Look at the vertical lines of the fonts: they're not sharp. In fact, the results look more like hinting completely disabled! That I can do myself with a click in the font prefs.
I don't think Xft2 is quite there yet either - some diagonal lines, such as the drop line in 'y' at some sizes of Times New Roman, gets rendered so thinly that it's difficult to see at all. Perhaps that's because I haven't rebuilt Freetype with the bytecode hinter enabled.
Hinting is a difficult issue, and very much related to the resolution of your display. Single words or short phrases (such as titles) always look better without hinting, because (especially with subpixel rendering enabled) the character shapes and spacing is more correct. However, large bodies of text become difficult to read because individual characters are blurred. That's where hinting helps: it subtly changes character spacing and shapes to reduce blur (improve contrast). Text becomes more readable - unless the uneven spacing bugs you more than blurry shapes.
Ask a silly person, get a silly answer.
.. now you've insulted all the Yugo fans out there!
I hope you're really proud of yourself.
3 pages of instructions to get decent fonts?
... That's not how to do it.
Download this, unpack that, login as root
Decent on-screen fonts in the default installation: that's the only way to do it. Linux fonts are seriously broken until it's done like that.
A few years back, I was on Babble, the Cure mailing list. One day someone posted that they were recently in a car accident, and had been listening to the Cure at the time: not on tape, but on the radio. Suddenly, out of the wood work came a bunch of "Me-too"'s: people that had been in auto accidents or similar, and had been listening to the Cure at the time. Some started to think that this was some kind of omen, mentioning how disconcerting it was and the like, until one guy posted a response along the lines of: "Everyone on this list is a Cure fan. Because of that, everyone will have a tendancy to either listen to Cure tapes in their car, or tune to radio stations that play the Cure." That shut everyone up fast.
The point here is that you're a Linux user. You read /. because it has a lot of stories about Linux and tweaking Linux. The fact that you were tweaking some aspect of your Linux system, went over to /. and saw a story about exactly what you were doing is not coincidential. It's a very basic statistical correlation.
Now then, had you gone over to MSN and found an artical about tweaking fonts in Linux while in the midst of doing such, I'd say it's time to pull out the tin-foil hats, pack up the kids and head for the hills.
-"Zow"
Celestial navigation is based on the premise that the Earth is the center
of the universe. The premise is wrong, but the navigation works. An
incorrect model can be a useful tool.
-- Kelvin Throop III
- this post brought to you by the Automated Last Post Generator...
I was in this prematurely air conditioned supermarket and there were all
these aisles and there were these bathing caps you could buy that had these
kind of Fourth of July plumes on them that were red and yellow and blue and
I wasn't tempted to buy one but I was reminded of the fact that I had been
avoiding the beach.
-- Lucinda Childs "Einstein On The Beach"
- this post brought to you by the Automated Last Post Generator...