x2v-issues

(Difference between revisions)

Jump to: navigation, search
(added tips for reporting X2V issues to help encourage more reproducible bug reports and real world examples that are easier to narrow down)
(added some suggeste rejections, separated open issues and resolved issues)
Line 16: Line 16:
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.
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 ==
+
== open issues ==
-
X2V's php does not correctly check for content-encodings
+
=== issue2006-12-20content-encoding ===
-
 
+
X2V's php does not correctly check for content-encodings.
-
== trailing_slash ==
+
<div class="discussion">
-
 
+
* Please provide URL to example with content-encoding that X2V supposedly does not correctly check. Suggest REJECT NO EXAMPLE GIVEN. [[User:Tantek|Tantek]] 07:56, 25 June 2009 (UTC)
-
X2V failed trailing slash in rel-tag (this is now fixed)
+
</div>
-
 
+
-
== FN ORG incomplete ==
+
 +
=== FN ORG incomplete ===
FN == ORG (i don't think) is complete
FN == ORG (i don't think) is complete
 +
<div class="discussion">
 +
* Please provide URL to example that shows X2V's implementation of FN == ORG is incomplete. Suggest REJECT NO EXAMPLE GIVEN. [[User:Tantek|Tantek]] 07:56, 25 June 2009 (UTC)
 +
</div>
-
== XSLT case-conversion on Nodes  ==
+
=== 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::
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.
The downside is that then it will not extract the node name from ANY namespace, but a specific one.
-
== language for X-WR-CALNAME ==
+
=== language for X-WR-CALNAME ===
-
 
+
====Background====
-
===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.
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 ===
+
==== Currently ====
<pre>&lt;html lang=en>
<pre>&lt;html lang=en>
   &lt;head>
   &lt;head>
Line 51: Line 51:
END:VCALENDAR</pre>
END:VCALENDAR</pre>
-
=== 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 ==
+
=== 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.
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
Test: http://examples.tobyinkster.co.uk/hcard
-
== See also ==
+
What is the expected .vcf output? [[User:Tantek|Tantek]]
 +
 
 +
== resolved issues ==
 +
=== trailing_slash ===
 +
X2V failed trailing slash in rel-tag (this is now fixed).
 +
 
 +
== see also ==
* [[X2V]]
* [[X2V]]
* [[hCard]]
* [[hCard]]
Line 68: Line 73:
* [[hcalendar-implementations]]
* [[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.
 +
* [[implementations]]

Revision as of 07:56, 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...

Contents

tips for reporting X2V issues

Please provide:

  1. The URL of the page you are attempting to convert with X2V
  2. An X2V conversion URL that takes that URL in (1) and escapes it and attempts to convert it
  3. The problematic line(s) of .vcf or .ics code
  4. The expected line(s) of .vcf or .ics code
  5. 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.

open issues

issue2006-12-20content-encoding

X2V's php does not correctly check for content-encodings.

  • Please provide URL to example with content-encoding that X2V supposedly does not correctly check. Suggest REJECT NO EXAMPLE GIVEN. Tantek 07:56, 25 June 2009 (UTC)

FN ORG incomplete

FN == ORG (i don't think) is complete

  • Please provide URL to example that shows X2V's implementation of FN == ORG is incomplete. Suggest REJECT NO EXAMPLE GIVEN. Tantek 07:56, 25 June 2009 (UTC)

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

What is the expected .vcf output? Tantek

resolved issues

trailing_slash

X2V failed trailing slash in rel-tag (this is now fixed).

see also

x2v-issues was last modified: Wednesday, December 31st, 1969

Views