x2v-issues: Difference between revisions
Singpolyma (talk | contribs) (I'm a fool and that issue isn't there...) |
(added tips for reporting X2V issues to help encourage more reproducible bug reports and real world examples that are easier to narrow down) |
||
| Line 1: | Line 1: | ||
[[X2V ]] is one of the main [[microformats]] [[implementations]]. | |||
The code is managed in an | The code is managed in an [http://hg.microformats.org/x2v/ x2v hg repository]. | ||
[http://hg.microformats.org/x2v/ x2v hg repository]. | [[User:Brian|Brian Suda]] and DanC are starting to track issues here. | ||
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec]. | See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec]. | ||
See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom... | See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom... | ||
== tips for reporting X2V issues == | |||
Please provide: | |||
# The URL of the page you are attempting to convert with X2V | |||
# An X2V conversion URL that takes that URL in (1) and escapes it and attempts to convert it | |||
# The problematic line(s) of .vcf or .ics code | |||
# The expected line(s) of .vcf or .ics code | |||
# A link/citation to the respective [[hCard]] or [[hCalendar]] spec (or other related document like [[hcard-parsing]] or [[icalendar-implementations]]) which documents the expected behavior. | |||
If you can provide all five of these items in your issue/bug report then it will greatly accelerate the X2V developer(s) tracking down (reproducing) the problem, and hopefully fixing it. | |||
== issue2006-12-20content-encoding == | == issue2006-12-20content-encoding == | ||
X2V's php does not correctly check for content-encodings | X2V's php does not correctly check for content-encodings | ||
| Line 55: | Line 61: | ||
== See also == | == See also == | ||
* [[X2V]] | |||
* [[hCard]] | |||
* [[hcard-implementations]] | |||
* [[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. | ||
* [[hCalendar]] | |||
* [[hcalendar-implementations]] | |||
* [[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 07:40, 25 June 2009
X2V is one of the main microformats implementations. The code is managed in an x2v hg repository. Brian Suda and DanC are starting to track issues here. See #microformats discussion 20 Dec.
See also: hcard-tests, hcard-issues, @@likewise for hCalendar, hAtom...
tips for reporting X2V issues
Please provide:
- The URL of the page you are attempting to convert with X2V
- An X2V conversion URL that takes that URL in (1) and escapes it and attempts to convert it
- The problematic line(s) of .vcf or .ics code
- The expected line(s) of .vcf or .ics code
- A link/citation to the respective hCard or hCalendar spec (or other related document like hcard-parsing or icalendar-implementations) which documents the expected behavior.
If you can provide all five of these items in your issue/bug report then it will greatly accelerate the X2V developer(s) tracking down (reproducing) the problem, and hopefully fixing it.
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
- X2V
- hCard
- hcard-implementations
- vcard-implementations for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values.
- hCalendar
- hcalendar-implementations
- icalendar-implementations for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values.