thoughts on this issue?
http://code.google.com/p/thinktankforums/issues/detail?id=37
-----
(1)
i need to change the anchors for specific posts. right now, we use this format to link to a post:
http://www.thinktankforums.com/thread.php?thread_id=265#1435
but beginning an id with a numeral isn't allowed per the xhtml 1.1 dtd.
so i need to remove these ids, but it will break tons of links. :(
i guess i just have to bite the bullet and change it over?
-----
(2)
we've been using blockquote tags in posts for a while. unfortunately, we've been using them incorrectly. as the xhtml 1.1 dtd requires, there needs to be a nested block-level element (e.g., p, div) inside of a blockquote.
should i edit all of the posts that have blockquotes? or should i do some kind of additional on-the-fly formatting when output?
-----
asemisldkfj
the law is no protection
1. that seems kind of silly that IDs aren't allowed to begin with a numeral. any idea why? what is the alternative for linking to posts? using like "one", "two", "three", etc. to identify where a post is in a thread? that seems kind of dumb. and doing something like "username#numerical_post_id#" just seems like a hackish way to comply with XHTML.
2. I think you should create your own set of tags for ttf. there is already a hyperlinking shortcut and a href doesn't work, so why not change the blockquote thing too? you can still keep very basic html stuff like b, i, u, etc.
(1) instead of this:
thread.php?thread_id=265#1435
we'll probably use anchors like this:
thread.php?thread_id=265#post_1435
(2) but what should i do with all of the old, invalid posts?
asemisldkfj
the law is no protection
I am going to take a look at the code right now.
asemisldkfj
the law is no protection
can't you just change thread.php from this:
<div class="userbar" id="<?php echo $post["post_id"]; ?>">
to this:
<div class="userbar" id="<?php echo 'post_' . $post["post_id"]; ?>">
?
asemisldkfj
the law is no protection
oh wait I misread your question.
asemisldkfj
the law is no protection
I guess reformatting all of the old posts with a new markup would take forever and might be really complicated depending on how different the new markup is. hmm. good question! start ttf fresh and have an archive with old posts? that would kind of suck though.
i don't want to start ttf fresh.
383 posts contain blockquotes.
36 posts link to specific posts.
i can update those 36 posts by hand, so that they link to the posts correctly.
then if we migrate to textile, i'll make a script that will find and replace all of the blockquote tags.
okay, those posts are updated, and the ID format is now "post\-[0-9]+".
:D
one step away from xhtml 1.1! woo
using blockquote tags should produce both a blockquote and a p tag for xhtml 1.1 compliance.
check
this
out!
hello, my name is pman
i do pman things
i'm in a pman world
wait a minute..
whut, will it stay open?
maybe?
ooh, it still blockquotes without closing! ha
all posts and profiles have been reformatted with the new code, which puts <p> tags inside the blockquotes.
yeah, no i was just saying that < blockquote > doesn't need a closing tag -- ttf is smarter than anyone posting.
and we're fully xhtml 1.1 compliant, as far as i can tell!
asemisldkfj
the law is no protection
or maybe not!
http://validator.w3.org/check?uri=http%3A%2F%2Fthinktankforums.com%2Fthread.php%3Fthread_id%3D1822&charset=%28detect+automatically%29&doctype=Inline&group=0
ciew is :D
http://validator.w3.org/check?uri=http://ciew.org&charset=(detect+automatically)&doctype=Inline&group=0
> or maybe not!
i can't be held responsible for users not closing their tags, can i?
asemisldkfj
the law is no protection
good point. I didn't realize all those errors stemmed from that.
with textile that won't be a problem though, right?
yeah, i don't think so. :)