stevarino

Heh, thanks francey!

Um, podz, just to set the record straight… I never called myself a designer. I’m a developer! ??
As far as bad weblog trends (calling them blogs is a bad weblog trend in my book), I usually attribute them to social-mechanics over bad taste. They are doing those little buttons because they are free, easy, and all their friends are doing them. The strike-out thing is annoying though. I’ll completely agree to that.

This HTML-Tidy idea would work only if it was transparent. But then we have users thinking they have sent valid xhtml, and are stumped why it doesnt work now when it worked in the past.
I guess the conclusion is that WordPress wouldn’t be the correct platform to enforce standards: it starts and ends with what the user types.
Or we could just have wordpress default to sending the mime-type “application/xhtml+xml” to accepting browsers and let the problem take care of itself. ??

The dl tag is what’s being wrapped in p tags. I think WP just doesn’t realize its a block-level element (you can see its list in wpautop()). Maybe I could wrap it all in a div, but I was hoping WP could offer a more semantic solution. ??

anon #1 – this is css, not xhtml. italic is very much a css property.
You might be right about the paragraph tags over-ruling the italics. Try this:
<pre>blockquote p { font-style: italic; }</pre>

could it be mod-rewrite trouble? if so, you could just edit your .htaccess file found in your wp root folder.

It looks like a problem with your index.php file. Maybe a blank line or space before the “<?php”?

Yah, I highly doubt those stats would accurately reflect the rest of the web. As for me on a Win2k box, here are my browsers in order of preferance:

1. Mozilla 1.6
2. IE6 (mainly for testing and compatibility)
3. Opera (love the amazing CSS features it boasts)
4. Firefox
5. IE5.5 (Oddly very similar to IE6, often have a hard time distinguishing them)
6. IE5 (Not a thing like IE 5.5)
7. Firebird
8. lynx

I’m actually suprised how long that list was. I really should use some of them more. ??

Ahhh.. Allusion said that?!? Wish someone told me before I had published that… :\
Oh well, give the people what they want, or else they’ll just go somewhere else. This is very ironic considering my last comment. D’oh!
You should have asked about the parse errors. I foolishly did little testing, but it’s better now. I also included a new feature so that when you do recieve a parse error, it outputs the problem-code to “wp-php.txt.” This will hopefully speed up any debugging in future problems.

I’m also very curious about a roadmap. When I post a hack, I DO have a personal roadmap of where I want WordPress to go. Every hack contributes towards my goals (except for that purple numbers thing, that was just fun).
However when I don’t know the official roadmap I feel guilty because my hacks might be working against that. Just want to be a good WP-citizen. ??

ihad: How about instead of a div, you use a pre? That’s what I use… However that still doesn’t fix the problem of long hyperlinks.

The
solution wouldn’t work for people posting code. Parse errors galore.

The magical paragraph tags, eh?
Ah, found it! Look for a funcion wpautop in your functions.php. How that actually gets into your code is through an add_filter in your vars.php. Tricksy hobbits.

you forgot an anchor… sheesh

Ahhh, I see now… It all comes together. Heh, no problem. Nice site by the way.