x2v-issues: Difference between revisions
No edit summary |
m (Reverted edit of EikUc2, changed back to last version by Tantek) |
||
| Line 35: | Line 35: | ||
=== Currently === | === Currently === | ||
<pre><html lang=en> | |||
<head> | |||
<title>My calendar</title> | |||
</head> | |||
<body class=vcalendar>...</body> | |||
</html></pre> | |||
yields something like | |||
<pre>BEGIN:VCALENDAR | |||
X-WR-CALNAME:My calendar | |||
... | |||
END:VCALENDAR</pre> | |||
=== Proposal === | |||
The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code> | |||
Revision as of 05:15, 9 June 2007
x2v is one of the main microformats implementations. The code is managed in an x2v hg repository. BrianSuda and DanC are starting to track issues here. See #microformats discussion 20 Dec.
See also: hcard-tests, hcard-issues, @@likewise for hCalendar, hAtom...
Hmm... we'd like to give each issue a URI; how about using mediawiki's TOC support? What sort of issue names strike the best balance between convenience and durability?
issue2006-12-20content-encoding
X2V's php does not correctly check for content-encodings
trailing_slash
X2V failed trailing slash in rel-tag (this is now fixed)
FN ORG incomplete
FN == ORG (i don't think) is complete
XSLT case-conversion on Nodes
Firefox seems to convert nodes to uppercase when using local-name(.) and name(.). This can be solved by switching to self::
The downside is that then it will not extract the node name from ANY namespace, but a specific one.
language for X-WR-CALNAME
Background
The X-WR-CALNAME is a widely supported extension property of VCALENDAR that stores the calendar title. It does not currently have a LANGUAGE attribute. It's value is meant to be human readable, so maybe it should.
Currently
<html lang=en>
<head>
<title>My calendar</title>
</head>
<body class=vcalendar>...</body>
</html>
yields something like
BEGIN:VCALENDAR X-WR-CALNAME:My calendar ... END:VCALENDAR
Proposal
The second line should read X-WR-CALNAME;LANGUAGE=en:My calendar