x2v-issues: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
No edit summary
(see also h2vx)
 
(21 intermediate revisions by 8 users not shown)
Line 1: Line 1:
x2v is one of the main microformats implementations.
[[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.
BrianSuda 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...


''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?''
== 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.


__TOC__
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
=== `<section>` is not recognized as a valid vcard container ===


== trailing_slash ==
x2v does not recognize vcards if their containing element is an HTML5  `<section>` element.


X2V failed trailing slash in rel-tag (this is now fixed)
Failing code:


== FN ORG incomplete ==
    <section class='vcard'>
        ...
    </section>


However, if the element is a `<div>`, all is well.
Example: jeffreydking.com[http://jeffreydking.com] has a vcard that validates[http://microformatique.com/optimus/?format=validate&uri=jeffreydking.com], but is not found[http://h2vx.com/vcf/jeffreydking.com/] by x2v.
=== issue2006-12-20content-encoding ===
X2V's php does not correctly check for content-encodings.
<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)
</div>
=== 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====
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.


===Background===
==== Currently ====
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.
<pre>&lt;html lang=en>
  &lt;head>
    &lt;title>My calendar&lt;/title>
  &lt;/head>
  &lt;body class=vcalendar>...&lt;/body>
&lt;/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>
 
=== 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? [[User:Tantek|Tantek]]
 
== resolved issues ==
=== trailing_slash ===
X2V failed trailing slash in rel-tag (this is now fixed).


=== Currently ===
== see also ==
* [[X2V]]
* [[h2vx]]
* [[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.
* [[implementations]]

Latest revision as of 23:07, 28 September 2013

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:

  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

`<section>` is not recognized as a valid vcard container

x2v does not recognize vcards if their containing element is an HTML5 `<section>` element.

Failing code: 

   <section class='vcard'>
       ...
   </section>

However, if the element is a `<div>`, all is well.

Example: jeffreydking.com[1] has a vcard that validates[2], but is not found[3] by x2v.

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

Retrieved from "http://microformats.org/wiki/index.php?title=x2v-issues&oldid=63949"