x2v-issues: Difference between revisions
(see also vcard-implementations for problems with vcard implementations, same with iCalendar) |
(Doesn't support AGENT.) |
||
| Line 47: | Line 47: | ||
=== Proposal === | === Proposal === | ||
The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code> | The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code> | ||
== No support for AGENT == | |||
Doesn't seem to support agent at all -- either as a human-readable string nor as a nested hCard. E-mail addresses, phone numbers, etc which are part of the agent's vcard are treated as belonging to the main contact. | |||
Test: http://examples.tobyinkster.co.uk/hcard | |||
== See also == | == See also == | ||
* [[vcard-implementations]] for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values. | * [[vcard-implementations]] for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values. | ||
* [[icalendar-implementations]] for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values. | * [[icalendar-implementations]] for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values. | ||
Revision as of 08:40, 26 March 2008
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...
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
No support for AGENT
Doesn't seem to support agent at all -- either as a human-readable string nor as a nested hCard. E-mail addresses, phone numbers, etc which are part of the agent's vcard are treated as belonging to the main contact.
Test: http://examples.tobyinkster.co.uk/hcard
See also
- vcard-implementations for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values.
- icalendar-implementations for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values.