https://microformats.org/wiki/api.php?action=feedcontributions&user=Kingjeffrey&feedformat=atomMicroformats Wiki - User contributions [en]2024-03-19T02:02:02ZUser contributionsMediaWiki 1.38.4https://microformats.org/wiki/index.php?title=x2v-issues&diff=43204x2v-issues2010-10-29T22:20:37Z<p>Kingjeffrey: /* `&lt;section>` is not recognized as a valid vcard container */</p>
<hr />
<div>[[X2V ]] is one of the main [[microformats]] [[implementations]].<br />
The code is managed in an [http://hg.microformats.org/x2v/ x2v hg repository]. <br />
[[User:Brian|Brian Suda]] and DanC are starting to track issues here.<br />
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec].<br />
<br />
See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom...<br />
<br />
== tips for reporting X2V issues ==<br />
Please provide:<br />
# The URL of the page you are attempting to convert with X2V<br />
# An X2V conversion URL that takes that URL in (1) and escapes it and attempts to convert it<br />
# The problematic line(s) of .vcf or .ics code<br />
# The expected line(s) of .vcf or .ics code<br />
# 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.<br />
<br />
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.<br />
<br />
== open issues ==<br />
<br />
=== `&lt;section>` is not recognized as a valid vcard container ===<br />
<br />
x2v does not recognize vcards if their containing element is an HTML5 `&lt;section>` element.<br />
<br />
Failing code:<br />
<br />
&lt;section class='vcard'><br />
...<br />
&lt;/section><br />
<br />
However, if the element is a `&lt;div>`, all is well.<br />
<br />
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.<br />
<br />
=== issue2006-12-20content-encoding ===<br />
X2V's php does not correctly check for content-encodings.<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== FN ORG incomplete ===<br />
FN == ORG (i don't think) is complete<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== XSLT case-conversion on Nodes ===<br />
Firefox seems to convert nodes to uppercase when using local-name(.) and name(.). This can be solved by switching to self::<br />
<br />
The downside is that then it will not extract the node name from ANY namespace, but a specific one.<br />
<br />
=== language for X-WR-CALNAME ===<br />
====Background====<br />
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.<br />
<br />
==== Currently ====<br />
<pre>&lt;html lang=en><br />
&lt;head><br />
&lt;title>My calendar&lt;/title><br />
&lt;/head><br />
&lt;body class=vcalendar>...&lt;/body><br />
&lt;/html></pre><br />
yields something like<br />
<pre>BEGIN:VCALENDAR<br />
X-WR-CALNAME:My calendar<br />
...<br />
END:VCALENDAR</pre><br />
<br />
==== Proposal ====<br />
The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code><br />
<br />
=== No support for AGENT ===<br />
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.<br />
<br />
Test: http://examples.tobyinkster.co.uk/hcard<br />
<br />
What is the expected .vcf output? [[User:Tantek|Tantek]]<br />
<br />
== resolved issues ==<br />
=== trailing_slash ===<br />
X2V failed trailing slash in rel-tag (this is now fixed).<br />
<br />
== see also ==<br />
* [[X2V]]<br />
* [[hCard]]<br />
* [[hcard-implementations]]<br />
* [[vcard-implementations]] for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values.<br />
* [[hCalendar]]<br />
* [[hcalendar-implementations]]<br />
* [[icalendar-implementations]] for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values.<br />
* [[implementations]]</div>Kingjeffreyhttps://microformats.org/wiki/index.php?title=x2v-issues&diff=43203x2v-issues2010-10-29T22:19:55Z<p>Kingjeffrey: /* `&lt;section>` is not recognized as a valid vcard container */</p>
<hr />
<div>[[X2V ]] is one of the main [[microformats]] [[implementations]].<br />
The code is managed in an [http://hg.microformats.org/x2v/ x2v hg repository]. <br />
[[User:Brian|Brian Suda]] and DanC are starting to track issues here.<br />
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec].<br />
<br />
See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom...<br />
<br />
== tips for reporting X2V issues ==<br />
Please provide:<br />
# The URL of the page you are attempting to convert with X2V<br />
# An X2V conversion URL that takes that URL in (1) and escapes it and attempts to convert it<br />
# The problematic line(s) of .vcf or .ics code<br />
# The expected line(s) of .vcf or .ics code<br />
# 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.<br />
<br />
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.<br />
<br />
== open issues ==<br />
<br />
=== `&lt;section>` is not recognized as a valid vcard container ===<br />
<br />
x2v does not recognize vcards if their containing element is an HTML5 `&lt;section>` element.<br />
<br />
Failing code:<br />
<br />
&lt;section class='vcard'><br />
...<br />
&lt;/section><br />
<br />
However, if the element is a `&lt;div>`, all is well.<br />
<br />
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/].<br />
<br />
=== issue2006-12-20content-encoding ===<br />
X2V's php does not correctly check for content-encodings.<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== FN ORG incomplete ===<br />
FN == ORG (i don't think) is complete<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== XSLT case-conversion on Nodes ===<br />
Firefox seems to convert nodes to uppercase when using local-name(.) and name(.). This can be solved by switching to self::<br />
<br />
The downside is that then it will not extract the node name from ANY namespace, but a specific one.<br />
<br />
=== language for X-WR-CALNAME ===<br />
====Background====<br />
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.<br />
<br />
==== Currently ====<br />
<pre>&lt;html lang=en><br />
&lt;head><br />
&lt;title>My calendar&lt;/title><br />
&lt;/head><br />
&lt;body class=vcalendar>...&lt;/body><br />
&lt;/html></pre><br />
yields something like<br />
<pre>BEGIN:VCALENDAR<br />
X-WR-CALNAME:My calendar<br />
...<br />
END:VCALENDAR</pre><br />
<br />
==== Proposal ====<br />
The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code><br />
<br />
=== No support for AGENT ===<br />
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.<br />
<br />
Test: http://examples.tobyinkster.co.uk/hcard<br />
<br />
What is the expected .vcf output? [[User:Tantek|Tantek]]<br />
<br />
== resolved issues ==<br />
=== trailing_slash ===<br />
X2V failed trailing slash in rel-tag (this is now fixed).<br />
<br />
== see also ==<br />
* [[X2V]]<br />
* [[hCard]]<br />
* [[hcard-implementations]]<br />
* [[vcard-implementations]] for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values.<br />
* [[hCalendar]]<br />
* [[hcalendar-implementations]]<br />
* [[icalendar-implementations]] for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values.<br />
* [[implementations]]</div>Kingjeffreyhttps://microformats.org/wiki/index.php?title=x2v-issues&diff=43202x2v-issues2010-10-29T22:19:15Z<p>Kingjeffrey: /* `&lt;section>` is not recognized as a valid vcard container */</p>
<hr />
<div>[[X2V ]] is one of the main [[microformats]] [[implementations]].<br />
The code is managed in an [http://hg.microformats.org/x2v/ x2v hg repository]. <br />
[[User:Brian|Brian Suda]] and DanC are starting to track issues here.<br />
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec].<br />
<br />
See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom...<br />
<br />
== tips for reporting X2V issues ==<br />
Please provide:<br />
# The URL of the page you are attempting to convert with X2V<br />
# An X2V conversion URL that takes that URL in (1) and escapes it and attempts to convert it<br />
# The problematic line(s) of .vcf or .ics code<br />
# The expected line(s) of .vcf or .ics code<br />
# 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.<br />
<br />
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.<br />
<br />
== open issues ==<br />
<br />
=== `&lt;section>` is not recognized as a valid vcard container ===<br />
<br />
x2v does not recognize vcards if their containing element is an HTML5 `&lt;section>` element.<br />
<br />
Failing code:<br />
<br />
&lt;section class='vcard'><br />
...<br />
&lt;/section><br />
<br />
However, if the element is a `&lt;div>`, all is well.<br />
<br />
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/].<br />
<br />
=== issue2006-12-20content-encoding ===<br />
X2V's php does not correctly check for content-encodings.<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== FN ORG incomplete ===<br />
FN == ORG (i don't think) is complete<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== XSLT case-conversion on Nodes ===<br />
Firefox seems to convert nodes to uppercase when using local-name(.) and name(.). This can be solved by switching to self::<br />
<br />
The downside is that then it will not extract the node name from ANY namespace, but a specific one.<br />
<br />
=== language for X-WR-CALNAME ===<br />
====Background====<br />
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.<br />
<br />
==== Currently ====<br />
<pre>&lt;html lang=en><br />
&lt;head><br />
&lt;title>My calendar&lt;/title><br />
&lt;/head><br />
&lt;body class=vcalendar>...&lt;/body><br />
&lt;/html></pre><br />
yields something like<br />
<pre>BEGIN:VCALENDAR<br />
X-WR-CALNAME:My calendar<br />
...<br />
END:VCALENDAR</pre><br />
<br />
==== Proposal ====<br />
The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code><br />
<br />
=== No support for AGENT ===<br />
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.<br />
<br />
Test: http://examples.tobyinkster.co.uk/hcard<br />
<br />
What is the expected .vcf output? [[User:Tantek|Tantek]]<br />
<br />
== resolved issues ==<br />
=== trailing_slash ===<br />
X2V failed trailing slash in rel-tag (this is now fixed).<br />
<br />
== see also ==<br />
* [[X2V]]<br />
* [[hCard]]<br />
* [[hcard-implementations]]<br />
* [[vcard-implementations]] for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values.<br />
* [[hCalendar]]<br />
* [[hcalendar-implementations]]<br />
* [[icalendar-implementations]] for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values.<br />
* [[implementations]]</div>Kingjeffreyhttps://microformats.org/wiki/index.php?title=x2v-issues&diff=43201x2v-issues2010-10-29T22:18:26Z<p>Kingjeffrey: /* `&lt;section>` is not recognized as a valid vcard container */</p>
<hr />
<div>[[X2V ]] is one of the main [[microformats]] [[implementations]].<br />
The code is managed in an [http://hg.microformats.org/x2v/ x2v hg repository]. <br />
[[User:Brian|Brian Suda]] and DanC are starting to track issues here.<br />
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec].<br />
<br />
See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom...<br />
<br />
== tips for reporting X2V issues ==<br />
Please provide:<br />
# The URL of the page you are attempting to convert with X2V<br />
# An X2V conversion URL that takes that URL in (1) and escapes it and attempts to convert it<br />
# The problematic line(s) of .vcf or .ics code<br />
# The expected line(s) of .vcf or .ics code<br />
# 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.<br />
<br />
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.<br />
<br />
== open issues ==<br />
<br />
=== `&lt;section>` is not recognized as a valid vcard container ===<br />
<br />
x2v does not recognize vcards if their containing element is an HTML5 `&lt;section>` element.<br />
<br />
Failing code:<br />
<br />
&lt;section class='vcard'><br />
...<br />
&lt;/section><br />
<br />
However, if the element is a `&lt;div>`, all is well.<br />
<br />
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/].<br />
<br />
=== issue2006-12-20content-encoding ===<br />
X2V's php does not correctly check for content-encodings.<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== FN ORG incomplete ===<br />
FN == ORG (i don't think) is complete<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== XSLT case-conversion on Nodes ===<br />
Firefox seems to convert nodes to uppercase when using local-name(.) and name(.). This can be solved by switching to self::<br />
<br />
The downside is that then it will not extract the node name from ANY namespace, but a specific one.<br />
<br />
=== language for X-WR-CALNAME ===<br />
====Background====<br />
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.<br />
<br />
==== Currently ====<br />
<pre>&lt;html lang=en><br />
&lt;head><br />
&lt;title>My calendar&lt;/title><br />
&lt;/head><br />
&lt;body class=vcalendar>...&lt;/body><br />
&lt;/html></pre><br />
yields something like<br />
<pre>BEGIN:VCALENDAR<br />
X-WR-CALNAME:My calendar<br />
...<br />
END:VCALENDAR</pre><br />
<br />
==== Proposal ====<br />
The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code><br />
<br />
=== No support for AGENT ===<br />
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.<br />
<br />
Test: http://examples.tobyinkster.co.uk/hcard<br />
<br />
What is the expected .vcf output? [[User:Tantek|Tantek]]<br />
<br />
== resolved issues ==<br />
=== trailing_slash ===<br />
X2V failed trailing slash in rel-tag (this is now fixed).<br />
<br />
== see also ==<br />
* [[X2V]]<br />
* [[hCard]]<br />
* [[hcard-implementations]]<br />
* [[vcard-implementations]] for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values.<br />
* [[hCalendar]]<br />
* [[hcalendar-implementations]]<br />
* [[icalendar-implementations]] for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values.<br />
* [[implementations]]</div>Kingjeffreyhttps://microformats.org/wiki/index.php?title=x2v-issues&diff=43200x2v-issues2010-10-29T22:16:54Z<p>Kingjeffrey: /* open issues */</p>
<hr />
<div>[[X2V ]] is one of the main [[microformats]] [[implementations]].<br />
The code is managed in an [http://hg.microformats.org/x2v/ x2v hg repository]. <br />
[[User:Brian|Brian Suda]] and DanC are starting to track issues here.<br />
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec].<br />
<br />
See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom...<br />
<br />
== tips for reporting X2V issues ==<br />
Please provide:<br />
# The URL of the page you are attempting to convert with X2V<br />
# An X2V conversion URL that takes that URL in (1) and escapes it and attempts to convert it<br />
# The problematic line(s) of .vcf or .ics code<br />
# The expected line(s) of .vcf or .ics code<br />
# 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.<br />
<br />
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.<br />
<br />
== open issues ==<br />
<br />
=== `&lt;section>` is not recognized as a valid vcard container ===<br />
<br />
x2v does not recognize vcards if their containing element is an HTML5 `&lt;section>` element.<br />
<br />
Failing code:<br />
<br />
&lt;section class='vcard'><br />
...<br />
&lt;/section><br />
<br />
However, if the element is a `&lt;div>`, all is well.<br />
<br />
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/].<br />
<br />
=== issue2006-12-20content-encoding ===<br />
X2V's php does not correctly check for content-encodings.<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== FN ORG incomplete ===<br />
FN == ORG (i don't think) is complete<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== XSLT case-conversion on Nodes ===<br />
Firefox seems to convert nodes to uppercase when using local-name(.) and name(.). This can be solved by switching to self::<br />
<br />
The downside is that then it will not extract the node name from ANY namespace, but a specific one.<br />
<br />
=== language for X-WR-CALNAME ===<br />
====Background====<br />
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.<br />
<br />
==== Currently ====<br />
<pre>&lt;html lang=en><br />
&lt;head><br />
&lt;title>My calendar&lt;/title><br />
&lt;/head><br />
&lt;body class=vcalendar>...&lt;/body><br />
&lt;/html></pre><br />
yields something like<br />
<pre>BEGIN:VCALENDAR<br />
X-WR-CALNAME:My calendar<br />
...<br />
END:VCALENDAR</pre><br />
<br />
==== Proposal ====<br />
The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code><br />
<br />
=== No support for AGENT ===<br />
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.<br />
<br />
Test: http://examples.tobyinkster.co.uk/hcard<br />
<br />
What is the expected .vcf output? [[User:Tantek|Tantek]]<br />
<br />
== resolved issues ==<br />
=== trailing_slash ===<br />
X2V failed trailing slash in rel-tag (this is now fixed).<br />
<br />
== see also ==<br />
* [[X2V]]<br />
* [[hCard]]<br />
* [[hcard-implementations]]<br />
* [[vcard-implementations]] for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values.<br />
* [[hCalendar]]<br />
* [[hcalendar-implementations]]<br />
* [[icalendar-implementations]] for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values.<br />
* [[implementations]]</div>Kingjeffreyhttps://microformats.org/wiki/index.php?title=x2v-issues&diff=43199x2v-issues2010-10-29T22:14:31Z<p>Kingjeffrey: /* `&lt;section>` is not recognized as a valid vcard container */</p>
<hr />
<div>[[X2V ]] is one of the main [[microformats]] [[implementations]].<br />
The code is managed in an [http://hg.microformats.org/x2v/ x2v hg repository]. <br />
[[User:Brian|Brian Suda]] and DanC are starting to track issues here.<br />
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec].<br />
<br />
See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom...<br />
<br />
== tips for reporting X2V issues ==<br />
Please provide:<br />
# The URL of the page you are attempting to convert with X2V<br />
# An X2V conversion URL that takes that URL in (1) and escapes it and attempts to convert it<br />
# The problematic line(s) of .vcf or .ics code<br />
# The expected line(s) of .vcf or .ics code<br />
# 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.<br />
<br />
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.<br />
<br />
== open issues ==<br />
=== issue2006-12-20content-encoding ===<br />
X2V's php does not correctly check for content-encodings.<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== `&lt;section>` is not recognized as a valid vcard container ===<br />
<br />
x2v does not recognize vcards if their containing element is an HTML5 `&lt;section>` element.<br />
<br />
Failing code:<br />
<br />
&lt;section class='vcard'><br />
...<br />
&lt;/section><br />
<br />
However, if the element is a `&lt;div>`, all is well.<br />
<br />
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/].<br />
<br />
=== FN ORG incomplete ===<br />
FN == ORG (i don't think) is complete<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== XSLT case-conversion on Nodes ===<br />
Firefox seems to convert nodes to uppercase when using local-name(.) and name(.). This can be solved by switching to self::<br />
<br />
The downside is that then it will not extract the node name from ANY namespace, but a specific one.<br />
<br />
=== language for X-WR-CALNAME ===<br />
====Background====<br />
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.<br />
<br />
==== Currently ====<br />
<pre>&lt;html lang=en><br />
&lt;head><br />
&lt;title>My calendar&lt;/title><br />
&lt;/head><br />
&lt;body class=vcalendar>...&lt;/body><br />
&lt;/html></pre><br />
yields something like<br />
<pre>BEGIN:VCALENDAR<br />
X-WR-CALNAME:My calendar<br />
...<br />
END:VCALENDAR</pre><br />
<br />
==== Proposal ====<br />
The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code><br />
<br />
=== No support for AGENT ===<br />
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.<br />
<br />
Test: http://examples.tobyinkster.co.uk/hcard<br />
<br />
What is the expected .vcf output? [[User:Tantek|Tantek]]<br />
<br />
== resolved issues ==<br />
=== trailing_slash ===<br />
X2V failed trailing slash in rel-tag (this is now fixed).<br />
<br />
== see also ==<br />
* [[X2V]]<br />
* [[hCard]]<br />
* [[hcard-implementations]]<br />
* [[vcard-implementations]] for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values.<br />
* [[hCalendar]]<br />
* [[hcalendar-implementations]]<br />
* [[icalendar-implementations]] for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values.<br />
* [[implementations]]</div>Kingjeffreyhttps://microformats.org/wiki/index.php?title=x2v-issues&diff=43198x2v-issues2010-10-29T22:13:18Z<p>Kingjeffrey: /* issue2006-12-20content-encoding */</p>
<hr />
<div>[[X2V ]] is one of the main [[microformats]] [[implementations]].<br />
The code is managed in an [http://hg.microformats.org/x2v/ x2v hg repository]. <br />
[[User:Brian|Brian Suda]] and DanC are starting to track issues here.<br />
See [http://rbach.priv.at/Microformats-IRC/2006-12-20#T154234 #microformats discussion 20 Dec].<br />
<br />
See also: [[hcard-tests]], [[hcard-issues]], @@likewise for hCalendar, hAtom...<br />
<br />
== tips for reporting X2V issues ==<br />
Please provide:<br />
# The URL of the page you are attempting to convert with X2V<br />
# An X2V conversion URL that takes that URL in (1) and escapes it and attempts to convert it<br />
# The problematic line(s) of .vcf or .ics code<br />
# The expected line(s) of .vcf or .ics code<br />
# 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.<br />
<br />
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.<br />
<br />
== open issues ==<br />
=== issue2006-12-20content-encoding ===<br />
X2V's php does not correctly check for content-encodings.<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== `&lt;section>` is not recognized as a valid vcard container ===<br />
<br />
x2v does not recognize vcards if their containing element is an HTML5 &`lt;section>` element.<br />
<br />
Failing code:<br />
<br />
lt;section class='vcard'><br />
...<br />
&lt;/section><br />
<br />
However, if the element is a `lt;div>`, all is well.<br />
<br />
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/].<br />
<br />
=== FN ORG incomplete ===<br />
FN == ORG (i don't think) is complete<br />
<div class="discussion"><br />
* 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)<br />
</div><br />
<br />
=== XSLT case-conversion on Nodes ===<br />
Firefox seems to convert nodes to uppercase when using local-name(.) and name(.). This can be solved by switching to self::<br />
<br />
The downside is that then it will not extract the node name from ANY namespace, but a specific one.<br />
<br />
=== language for X-WR-CALNAME ===<br />
====Background====<br />
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.<br />
<br />
==== Currently ====<br />
<pre>&lt;html lang=en><br />
&lt;head><br />
&lt;title>My calendar&lt;/title><br />
&lt;/head><br />
&lt;body class=vcalendar>...&lt;/body><br />
&lt;/html></pre><br />
yields something like<br />
<pre>BEGIN:VCALENDAR<br />
X-WR-CALNAME:My calendar<br />
...<br />
END:VCALENDAR</pre><br />
<br />
==== Proposal ====<br />
The second line should read <code>X-WR-CALNAME;LANGUAGE=en:My calendar</code><br />
<br />
=== No support for AGENT ===<br />
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.<br />
<br />
Test: http://examples.tobyinkster.co.uk/hcard<br />
<br />
What is the expected .vcf output? [[User:Tantek|Tantek]]<br />
<br />
== resolved issues ==<br />
=== trailing_slash ===<br />
X2V failed trailing slash in rel-tag (this is now fixed).<br />
<br />
== see also ==<br />
* [[X2V]]<br />
* [[hCard]]<br />
* [[hcard-implementations]]<br />
* [[vcard-implementations]] for how particular vCard implementations (e.g. clients) have problems with any standard vCard properties or values.<br />
* [[hCalendar]]<br />
* [[hcalendar-implementations]]<br />
* [[icalendar-implementations]] for how particular iCalendar implementations (e.g. clients) have problems with any standard iCalendar properties or values.<br />
* [[implementations]]</div>Kingjeffrey