Pete On Rails

Alright. The Typo 5.x Standard Issue theme (which I really like, so much that I switched from Scribbish) does not account for the styles used by typo:code macros.

After much headache trying to get Typo to include the typocode themes in minimal.css while rendering themes (so that code would render nicely in any theme that I choose to use), I gave up. Really, I’m not sure I want to override typocode styles in every theme anyway, because someone might come up with an even better set of styles.

So instead, I’ve patched themes/standard_issue/stylesheets/application.css to include the typocode styles. As you can see, code is rendering much more bueno now.

Thanks Brent, for beating me up enough to invetigate a better theme.

If you use Standard Issue and want the updated stylesheet, grab it from my site.

Now, I am working on a bug in the ruby formatting that displays line numbers incorrectly, like this:

Code Highlighting in Typo is awful, cumbersome, and a pain. I am currently running this blog on Typo 5.0.3, and when I write an article using typo:code snippets using LivePreview, here is what I see:

But then it RENDERS like this, no matter which theme I am using:

GAH! That’s not what I thought I was getting! No friggin bueno! So I decided to try a third party code highlighter.

I really liked the TextMate Syntax Highlighter, but: it didn’t work either.

My friend and former colleague Brendan pointed me to a javascript-based code highlighter that does the formatting on the browser. That makes good sense to me. I like it. But it didn’t work either.

So, I’ve decided to roll up my sleeves and figure out why none of the included themes in Typo will render the code blocks the way I want. 2 hours later, I hate the CSS mess, so I’m spending my evening ripping the whole set of stylesheets apart to make them work right.

Stay tuned.