hmm...
1) I'll look into the UTF-8 issue, Your server is NOT sending any
language encoding:
HTTP/1.1 200 OK
Date: Tue, 26 Sep 2006 12:02:13 GMT
Server: Apache
Transfer-Encoding: chunked
Content-Type: text/html
so i might be assuming it as UTF-8? when i run your code through the
W3C tidy, they
On 9/26/06, Yoan BLANC [EMAIL PROTECTED] wrote:
Do you prefer if I send a Content-Type: text/html; charset=iso-8859-1
It's much a matter of your tool. Technorati deals with this page
correctly (except with the dates) so why x2v cannot, strange no?
I'll look into this now that i know you want
Brian Suda wrote:
On 9/26/06, Yoan BLANC [EMAIL PROTECTED] wrote:
Do you prefer if I send a Content-Type: text/html; charset=iso-8859-1
It's much a matter of your tool. Technorati deals with this page
correctly (except with the dates) so why x2v cannot, strange no?
I'll look into this now
On Sep 26, 2006, at 5:44 AM, Brian Suda wrote:
On 9/26/06, Yoan BLANC [EMAIL PROTECTED] wrote:
Do you prefer if I send a Content-Type: text/html; charset=iso-8859-1
It's much a matter of your tool. Technorati deals with this page
correctly (except with the dates) so why x2v cannot, strange no?
On Sep 25, 2006, at 6:48 AM, Brian Suda wrote:
This has been corrected[1]. I have committed the changes to HG, so
anyone at technorati can pull them down
done.
-ryan
___
microformats-discuss mailing list
microformats-discuss@microformats.org
On Sep 26, 2006, at 5:44 AM, Brian Suda wrote:
I won't go too much technical detail on the discuss list, you can
email me off list for a complete explaination and how the W3C defines
the order of where to look for language encodings, etc.
Our own Mark Pilgrim wrote a good explanation of
Good catch! i had a look at the issue and the problem was that all our
test cases added the time from the timezone up to 24, in your
case you were subtracting to get '0' which was not being checked for
so things were going padded then that '0' was being added so we got
'7' instead of '6'.
