Converting from WP 2.02beta to Current WP 2.3.1-6

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

These Are The Steps I Followed – Part 6

To Do List – Fonts

Safari displays very small font sizes, while Firefox displays very large sizes in Neo-Classical – Pearson uses numerous typographical tricks (setting body font to 62.5%) to display the fonts, but it does not work correctly across Mac browsers, so one can only wonder what it looks like on windows!

Pearson included no actual font declaration for the post_body, so text was rendered as some default.

These are the fonts I’m working with: Caflish Script Pro, Park Avenue, Slimbach, Copperplate, Verdana, Georgia, Trebuchet MS, Times, Lucida Sans Unicode, Lucida, Times New Roman, sans-serif.

These are the browsers I’m using: Mozila 1.8a4; Firefox 2.0010; Opera 8.54. Navigator 9.02b, and Safari 1.0.

h1 font rendered as Copperplate in Safari, and Opera. Safari seems one size larger than Opera.

h1 font rendered as Caflish Script Pro in Netscape, Mozila, and Firefox. Size seems the same.

h2 is rendered as Copperplate in Safari.

h2 is rendered as Slimbach in Firefox, Opera, Netscape, and Mozila.

h3 is rendered as Copperplate in Safari.

h3 is rendered as Slimbach in Firefox, Opera, Netscape, and Mozila.

Removing the ‘Caflish Script Pro, Park Avenue’ declarations everywhere: result in all font renderings: Safari and Opera refuse to see Slimbach and skip to Copperplate.

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

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.