To view parent comment, click here.
To read all comments associated with this story, please click here.
Verdana is an MS font, but Arial and Helvetica are both industry standards. If none are on your machine, it defaults out to however sans-serif is configured on your machine.
A) Suse should include Arial and/or Helvetica, as they are required for any remotely serious work in anything even related to type.
B) Suse should configure its system to use a sans-serif font that doesn't look like complete and total garbage something in between point sizes
The full css rules for the text is
font-family:Verdana,Arial,Helvetica,sans-serif;
font-size:70%;
line-height:140%;
margin:0px;
padding:0px 0px 1em;
That is very standard stuff, and should both look nice and be readable on any os set up even remotely well. The worst thing you can say is that they put verdana as the first choice on the list, but I don't think that is really worth complaining about.
The reason it looks like ass on your computer is freetype and/or your sans-serif font is dying painfully trying to rendor in between points (as it is set to 70% rather then a specific size) I don't think MS should have to take this into account, it is like complaining that a website sucks because you have a hard time using it as your browser doesn't support images, or javascript, or css.
Edited 2008-06-18 22:19 UTC
I can see what the guy is talking about, the site looks like pants on this setup too, it is Vectorlinux running on Firefox 2.
Can you not see his point ? Should I also have to change my default font setup just to accommodate Microsoft, or any other website that assumes they can dictate how I view webpages ?
It looks to me like some muppet designed a webpage in MSWord and saved it to web.






Member since:
2005-07-06
You prove my point exactly. I was using a default Firefox install on a Suse Linux system. Normally there is no problem on websites, but yet, you think I need to add/change fonts on my machine just so that I can look at it the same way someone else can on a different setup ?
This is another example of Microsoft and standards, and another example of someone not blaming Microsoft, but assuming the problem was caused by HOW they used the computer.....