Converting from WP 2.02beta to Current WP 2.3.1-7

How to Convert Yahoo’s WordPress 2.02beta to Current 2.3.1

These Are The Steps I Followed – Part 7

To Do List – Fonts tests

Next Test – for consistent font usage across browsers (Safari 1.32, Firefox, Opera 9.24, Netscape, iCab 3.0.3, Camino 1.5.3 and Mozila 1.8).

Each font statement in the css file will use original declaration such as font-family, em size and so on.

Each statement will test for only one of the following font types in every css declaration in the css file: Slimbach, Copperplate, Verdana, Georgia, Trebuchet MS, Times, Lucida Sans Unicode, Lucida, Times New Roman, sans-serif. Example – font-family: slimbach, sans serif.

I also noticed Pearson’s use of em statements for multiple em sizes – such as font: normal 1.1em/1.3em – this may screw up rendering in some browsers. Will have to test this separately depending on results of first test.

I’ve divided these files into parts because several of them are quite long, as well as following the steps seems easier this way.

Pearson has a font hack which he says is for Safari – to keep consistent font sizes – turned this off and fonts are more consistent with other browsers. His hack may work on later editions of Safari (Tiger/Leopard) and Safari 3.

Font Sizes

Navigator and Opera seem to use the same font (Verdana?) and the same size for each area, EXCEPT the post body, where Netscape is larger than Opera.

iCab seems consistently smaller in each section.

Camino and Netscape seem to be identical in size in all sections.

It seems impossible to get all browsers to display font size identically – some set resolution, some have a larger minimum size, etc.
Firefox has the absolute smallest size – bordering on the unreadable.

Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6 | Part 7

This entry was posted in Exclusive, Technology and tagged , , . Bookmark the permalink.