Gosh, the new google fonts can be pretty

[andrewducker]

You can do stuff like this!

Or this!

See here for how it works.
(At least, I get two cool fonts in Firefox, dunno how well it works in IE)
EDIT: Gah! LJ is turning the "quote marks" into 39's - it's escaping them.
Any idea how to work around that in LJ?

Comments

[interactiveleaf.livejournal.com]

I'm in Chrome, and the two fonts look exactly alike.

[matgb]

Same for me in Firefox. I wonder if the fonts themselves are cached on Andrew's machine but we're not picking them up?

[tamaranth.livejournal.com]

Snap (Chrome) and snap (exactly alike) --- also, the two exactly-alike fonts are not cool fonts, they are mundane and dull (sorry A!)

[andrewhickey.livejournal.com]

Yeah - on Chromium on Debian they're just a standard serif font.

[interactiveleaf.livejournal.com]

Right! It's some sort of boring serif font; nothing special.

[matgb]

You can do stuff like this!

Test

[andrewducker]

Gah! It's turning the "quote marks" into 39's - it's escaping them.

Any idea how to work around that in LJ?

[interactiveleaf.livejournal.com]

I don't see any quote marks, so I suspect it's not strictly an LJ issue.

[andrewducker]

In the source.....

[interactiveleaf.livejournal.com]

Oooohhhh. I see.

[interactiveleaf.livejournal.com]

I see the same font that is used in the OP.

[matgb]

Yup, LJ is stripping the important bit of code:
[link href='http://fonts.googleapis.com/css?family=Tangerine' rel='stylesheet' type='text/css']

I'm assuming it needs to be in the header of the page, not inline, and LJ doesn't like stuff that embeds off site stuff. I have no idea how to work around it on a post by post basis, but suspect it could be hacked into S2 layers.

It's a nice idea, but...

[interactiveleaf.livejournal.com]

Well, I think Tangerine is technically a serif font, so at least they got that right.

[momentsmusicaux.livejournal.com]

Can you maybe do it with an @embed instead of a link?

[matgb]

Pretty sure embeds are stripped completely by the CSS cleaner, LJ tend to the paranoid on CSS and security stuff, so might need to poke them to allow whatever Google are doing.

Will play on my DW later, I can access my code there, free account on LJ, no code access.

[nameandnature]

Any idea how to work around that in LJ?

There should be no way to work around it in LJ: wasn't the last XSS attack because they'd left a JS hole in their CSS stuff?

[marrog.livejournal.com]

Times New Roman, mmmm...

[matgb]

Heh, see, I see Verdana. Which means its going to browser default, never could stand TNR.

[marrog.livejournal.com]

I actually find that I like TNR and Arial better the older I get. I dunno what that's a sign of.

[0olong.livejournal.com]

It means They're winning.