read(STDIN,$temp,$ENV{'CONTENT_LENGTH'});
@pairs=split(/&/,$temp);
foreach $item(@pairs)
{
($key,$content)=split(/=/,$item,2);
$content=~tr/+/
$content =~ s///g;
$content=~s/%(..)/pack("c",hex($1))/ge;
$fields{$key}=$content;
}
$ENV{'QUERY_STRING'}=~s/%(..)/pack("c",hex($1))/ge;
@REFID=split(/-=-/,$ENV{'QUERY_STRING'});
Must
Jason
PS: I saw that new <CITE> tag and got excited, thinking it was like a PRE tag, but no - it just italicizes everything. The CODE tag is merely a TT tag - I still gotta add those <BR>'s in there
PRE (Score:2)
pudge (and presumably others) don't want <pre> in here because it would allow people to fuxor the layout (by entering very long lines). When I get five minutes of contiguous tuits, I'll prolly put a small pre2slash script that'll throw in the <br/> (err, <br>, XHTML doesn't work here), the , and try to take into account limitations in numbers of contiguous chars. No big deal, I just need those five minutes :)
-- Robin Berjon [berjon.com]
Re:PRE (Score:1)
Re:PRE (Score:2)
I haven't looked at the Everything engine code, but they have something that apparently can deal with proper formatting of code based on a given number of columns (it wraps beyond that width, and adds a small symbol at the end to indicate wrapping).
I'm not sure that this would solve the problem completely, but it could help.
-- Robin Berjon [berjon.com]
Re:PRE (Score:1)
Re:PRE (Score:1)
C'mon Pudge, I know you're capable of saying it's wrong. :) I think the filters in both Slash and Everything originally came from Dave DeMaagd a long, long time ago.
I'd like to revise the HTML parsing code anyway, but haven't finished writing tests.
Re:PRE (Score:1)
Others could have it as they like it.
---ict / Spoon
Re:PRE (Score:1)
Re:PRE (Score:1)
---ict / Spoon
Re:PRE (Score:1)
Re:PRE (Score:1)
Hmm.
---ict / Spoon