Microformats Wiki - User contributions [en]

x2v-issues

2010-10-29T22:20:37Z

Kingjeffrey: /* `<section>` is not recognized as a valid vcard container */

[[X2V ]] is one of the main [[microformats]] [[implementations]].
The code is managed in an [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 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.

== 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[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
<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 ===
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 ====
<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>

=== 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).

== 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.
* [[implementations]]

x2v-issues

2010-10-29T22:19:55Z

Kingjeffrey: /* `<section>` is not recognized as a valid vcard container */

[[X2V ]] is one of the main [[microformats]] [[implementations]].
The code is managed in an [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 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.

== 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[http://jeffreydking.com] has a vcard that validates[http://microformatique.com/optimus/?format=validate&uri=jeffreydking.com], but is not found by x2v[http://h2vx.com/vcf/jeffreydking.com/].

=== 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
<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 ===
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 ====
<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>

=== 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).

== 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.
* [[implementations]]

x2v-issues

2010-10-29T22:19:15Z

Kingjeffrey: /* `<section>` is not recognized as a valid vcard container */

[[X2V ]] is one of the main [[microformats]] [[implementations]].
The code is managed in an [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 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.

== 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: [[http://jeffreydking.com]] has a vcard that (validates)[http://microformatique.com/optimus/?format=validate&uri=jeffreydking.com], but (is not found by x2v)[http://h2vx.com/vcf/jeffreydking.com/].

=== 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
<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 ===
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 ====
<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>

=== 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).

== 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.
* [[implementations]]

x2v-issues

2010-10-29T22:18:26Z

Kingjeffrey: /* `<section>` is not recognized as a valid vcard container */

[[X2V ]] is one of the main [[microformats]] [[implementations]].
The code is managed in an [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 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.

== 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: [http://jeffreydking.com][] has a vcard that (validates)[http://microformatique.com/optimus/?format=validate&uri=jeffreydking.com], but (is not found by x2v)[http://h2vx.com/vcf/jeffreydking.com/].

=== 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
<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 ===
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 ====
<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>

=== 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).

== 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.
* [[implementations]]

x2v-issues

2010-10-29T22:16:54Z

Kingjeffrey: /* open issues */

[[X2V ]] is one of the main [[microformats]] [[implementations]].
The code is managed in an [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 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.

== 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)[http://jeffreydking.com] has a vcard that (validates)[http://microformatique.com/optimus/?format=validate&uri=jeffreydking.com], but (is not found by x2v)[http://h2vx.com/vcf/jeffreydking.com/].

=== 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
<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 ===
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 ====
<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>

=== 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).

== 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.
* [[implementations]]

x2v-issues

2010-10-29T22:14:31Z

Kingjeffrey: /* `<section>` is not recognized as a valid vcard container */

[[X2V ]] is one of the main [[microformats]] [[implementations]].
The code is managed in an [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 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.

== open issues ==
=== 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>

=== `<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)[http://jeffreydking.com] has a vcard that (validates)[http://microformatique.com/optimus/?format=validate&uri=jeffreydking.com], but (is not found by x2v)[http://h2vx.com/vcf/jeffreydking.com/].

=== FN ORG incomplete ===
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 ===
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 ====
<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>

=== 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).

== 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.
* [[implementations]]

x2v-issues

2010-10-29T22:13:18Z

Kingjeffrey: /* issue2006-12-20content-encoding */

[[X2V ]] is one of the main [[microformats]] [[implementations]].
The code is managed in an [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 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.

== open issues ==
=== 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>

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

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

Failing code:

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

However, if the element is a `lt;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 by x2v)[http://h2vx.com/vcf/jeffreydking.com/].

=== FN ORG incomplete ===
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 ===
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 ====
<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>

=== 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).

== 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.
* [[implementations]]