[uf-discuss] hCard email type properties

2007-03-11 Thread Kim Franch
Hello, I am working on an AddressBook type module for Drupal using hCard and have run up against a minor quandrum in correctly formatting email ( to a lesser extent url) properties. I've read through hCard information on this mailing list and found a type of answer, but I'd like to pick your

Re: [uf-discuss] hCard email type properties

2007-03-11 Thread Paul Wilkins
Kim Franch wrote: My confusion comes when trying to impliment email types. I used the following markup: a href=FooBarRedirect abbr class=email title=[EMAIL PROTECTED] span class=type title=internet prefEmail FooBar/span /abbr /a The markup appears to be correct, as when your code is

[uf-discuss] An Inconvenient hCard

2007-03-11 Thread Ara Pehlivanian
I've got a bit of a problem with an hCard that I need to mark up and I was wondering if anyone could lend me a hand. I realize the syntax requires that a type be specified for telephone numbers (voice, fax, etc...) and that's where my problem lies. It's inconvenient to have the word voice appear

Re: [uf-discuss] An Inconvenient hCard

2007-03-11 Thread Paul Wilkins
From: Ara Pehlivanian [EMAIL PROTECTED] I've got a bit of a problem with an hCard that I need to mark up and I was wondering if anyone could lend me a hand. I realize the syntax requires that a type be specified for telephone numbers (voice, fax, etc...) and that's where my problem lies. It's

Re: [uf-discuss] An Inconvenient hCard

2007-03-11 Thread Ara Pehlivanian
On 3/11/07, Paul Wilkins [EMAIL PROTECTED] wrote: Good news, the voice type is the default one, so you don't have to specify the voice type at all, and only specify for the fax (in this case). With that, you can have p class=telTel: span class=value(514) 123-4567/p p class=telspan

Re: [uf-discuss] An Inconvenient hCard

2007-03-11 Thread Paul Wilkins
From: Paul Wilkins [EMAIL PROTECTED] With that, you can have p class=telTel: span class=value(514) 123-4567/p p class=telspan class=typeFax/span: span class=value(514) 123-4568/span/p Correction: p class=telTel: span class=value(514) 123-4567/span/p p class=telspan class=typeFax/span: span

Re: [uf-discuss] An Inconvenient hCard

2007-03-11 Thread Ara Pehlivanian
On 3/11/07, Paul Wilkins [EMAIL PROTECTED] wrote: From: Ara Pehlivanian [EMAIL PROTECTED] Any ideas about internationalization? How would I handle fax in French? I doubt that Télécopieur would be a valid type, since RFC 2426 doesn't seem to be geared toward types in other languages. If the

Re: [uf-discuss] hCard email type properties

2007-03-11 Thread Mike Kaply
On 3/11/07, Kim Franch [EMAIL PROTECTED] wrote: a href=FooBarRedirect abbr class=email title=[EMAIL PROTECTED] span class=type title=internet prefEmail FooBar/span /abbr /a This markup is incorrect. title can only be used with an abbr - the title on a span wont work. Why aren't you

Re: [uf-discuss] hCard email type properties

2007-03-11 Thread Scott Reynen
On Mar 11, 2007, at 9:47 PM, Mike Kaply wrote: This markup is incorrect. title can only be used with an abbr - the title on a span wont work. To clarify, the title attribute only acts as a replacement of content on abbr, but the title attribute on span is valid HTML markup for generally

Re: [uf-discuss] hCard email type properties

2007-03-11 Thread Paul Wilkins
From: Mike Kaply [EMAIL PROTECTED] On 3/11/07, Kim Franch [EMAIL PROTECTED] wrote: a href=FooBarRedirect abbr class=email title=[EMAIL PROTECTED] span class=type title=internet prefEmail FooBar/span /abbr /a This markup is incorrect. title can only be used with an abbr - the title on

Re: [uf-discuss] hCard email type properties

2007-03-11 Thread Scott Reynen
On Mar 11, 2007, at 10:21 PM, Paul Wilkins wrote: Why aren't you just using a mailto? I suspect because he wants people to be directed to a page where they can get in touch, instead. Why not just have a anchor that points to the web page? Perhaps he wants to be a sneaky bastard (tm)

Re: [uf-discuss] hCard email type properties

2007-03-11 Thread Paul Wilkins
From: Scott Reynen [EMAIL PROTECTED] The inital problem I encountered with both propeties stemmed from the fact that I hook into another Drupal module for link managment and click-through tracking, the latter using a redirect after logging the click-through. So the goal is to have the href