Rendering problem with GT Mod 2.0

[Kosse]

Awesome man!

Why didn't you came up earlier with this thing?

Nobody asked me..

you defined in you snippet to repalce alle the h* elements.
So you enter the information normaly within your CMS (e.g. the headline of an article) and the system recognizes, that this will be a h1-formated text and replaces the browser text with the correct formating (defined in sIFR.css) and the swf-font, right?

Right, but you can define also classes with the h pseudo-classes, be carefull with IE though, conditionnal comment sare welcome

So I define all the stuff one time and do not have to think about it (like using RTs for the headline) any more? Just type my headlines normaly and the system does the rest?

Yes, exactly, so if u want to leave h3 out of it just don't put it (sometimes usefull)

Sorry for the bad english, but I am rather excited at the moment...

It's ok, I'm not a teacher and ur english is quite ok
Cheers

[charliespeed]

hi Kosse,

i've done a lot of testing and want to say:

THANK YOU! This awesome thing just works!

[shiny]

Just as a side note on TTF rendering with the GT Mod, it is certainly the case that it simply doesn't work properly on some fonts. It's not the fault of the GT Mod itself, mind you - the blame appears to lay with the GD font rendering subsystem, or at least the one that's built into PHP.

While I wouldn't claim to know a lot about the internals of GD, the fact that font rendering results are distinctly different (especially for small, anti-aliased fonts) under Windows and Unix would imply that there's some OS-specific stuff in there. The server that my site runs on is a Linux one, and the font-rendering under GD on it is demonstrably worse (particularly with Kerning) than on my local machine under Windows. Sadly, there doesn't appear to be much that we can do about it. sIFR is a good alternative for places where you really need the fonts to look consistent. I use both GT Mod and sIFR on my site.