Links and properties

[Michael Strey via mobileorg-android]

Hello,

I'm using a contact data base inspired by org-contacts, where contact
details are stored in the properties drawer.

First question: Are there any plans to show drawer content in the MobileOrg
read view (not only in the edit view)?

The contact details contain phone numbers as well. Recently we had some
discussion about phone links in the Org-Mode mailing list. This inspired
me to make a little test with various forms of links and phone numbers.

I synchronised the following contact with MobileOrg.

#+BEGIN_SRC org
** Surname, Name
:PROPERTIES:
:EMAIL: test2-***@public.gmane.org; name-***@public.gmane.org
:PHONE: [phone]
:END:

Visible as link and working:
[[tel:[phone]][[phone]]]
[[tel:[phone]][[phone]]]

Visible as link but not working:
[[phone:[phone]][[phone]]]

Not recognized as links by MobileOrg:
[[tel:[phone]]]
[[tel:[phone]]]
[[phone:[phone]]]
[[phone:[phone]]]
[[phone:[phone]]]

Not working:
[phone]
[phone]
[phone]
[phone]
#+END_SRC

In MobileOrg some of the above links are displayed as links and some not.
The links with the key "tel:" lead me to the phone application on my
smartphone, those with the key "phone" don't. Pure numbers sometimes lead
to the phone app but only parts of the complete number are transmitted.

What is the reason for the tel: links working and the phone: links not?
AFAIK non of them is supported yet by Org-Mode.

Regards
Michael Strey
--
I'm sorry for the HTML. I'm writing from Google Groups and didn't find a
setting to switch it off.

[mobileorg-android on behalf of Matthew Jones]

note that "tel:" is a common uri for indicating that something is a
telephone number (http://tools.ietf.org/html/rfc3966)

We allow Android's controls to realize any linkable text that it finds and
I'm not sure how well that works for your locale (it does a pretty good job
of identifying US phone numbers.

We don't have a problem necessarily implementing viewable drawers with
information like that but we don't want to just show all drawer content as
a lot of it is just metadata that is meant to be parsed a certain way. If
this is something you'd like to see handled in a particular way can you
open an issue in our issue tracker so that we can prioritize it?


On Wed, Apr 10, 2013 at 10:02 AM, Michael Strey via mobileorg-android <

Post by Michael Strey via mobileorg-android
Hello,
I'm using a contact data base inspired by org-contacts, where contact
details are stored in the properties drawer.
First question: Are there any plans to show drawer content in the
MobileOrg read view (not only in the edit view)?
The contact details contain phone numbers as well. Recently we had some
discussion about phone links in the Org-Mode mailing list. This inspired
me to make a little test with various forms of links and phone numbers.
I synchronised the following contact with MobileOrg.
#+BEGIN_SRC org
** Surname, Name
:PHONE: [phone]
[[tel:[phone]][[phone]]]
[[tel:[phone]][[phone]]]
[[phone:[phone]][[phone]]]
[[tel:[phone]]]
[[tel:[phone]]]
[[phone:[phone]]]
[[phone:[phone]]]
[[phone:[phone]]]
[phone]
[phone]
[phone]
[phone]
#+END_SRC
In MobileOrg some of the above links are displayed as links and some not.
The links with the key "tel:" lead me to the phone application on my
smartphone, those with the key "phone" don't. Pure numbers sometimes lead
to the phone app but only parts of the complete number are transmitted.
What is the reason for the tel: links working and the phone: links not?
AFAIK non of them is supported yet by Org-Mode.
Regards
Michael Strey
--
I'm sorry for the HTML. I'm writing from Google Groups and didn't find a
setting to switch it off.
--
You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en
.
For more options, visit https://groups.google.com/groups/opt_out.

[mobileorg-android]

X-Received: by 10.50.170.68 with SMTP id ak4mr2607676igc.1.1365608751844;
Wed, 10 Apr 2013 08:45:51 -0700 (PDT)
X-BeenThere: mobileorg-android-/***@public.gmane.org
Received: by 10.50.29.1 with SMTP id f1ls1861103igh.40.canary; Wed, 10 Apr
2013 08:45:51 -0700 (PDT)
X-Received: by 10.43.45.130 with SMTP id uk2mr2023162icb.28.1365608751409;
Wed, 10 Apr 2013 08:45:51 -0700 (PDT)
Received: from mx2.supremebox.com (mx2.supremebox.com. [198.23.53.42])
by gmr-mx.google.com with ESMTPS id mk7si2636862igc.0.2013.04.10.08.45.51
(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
Wed, 10 Apr 2013 08:45:51 -0700 (PDT)
Received-SPF: pass (google.com: domain of mobileorg-android-/***@public.gmane.org
designates 198.23.53.42 as permitted sender) client-ip=198.23.53.42;
Received: from [77.189.144.177] (helo=localhost) by mx2.supremebox.com with
esmtpa (Exim 4.80) (envelope-from <mobileorg-android-/***@public.gmane.org>) id
1UPxDa-0004eP-Mu for mobileorg-android-/***@public.gmane.org; Wed, 10 Apr 2013
15:45:51 +0000
In-Reply-To: <CABSYn2jf=DT0iL3ft_oPWu1C-zw452NcFF3Ax93f832smY8QyQ-JsoAwUIsXosN+***@public.gmane.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Sender-Ident: mobileorg-android-/***@public.gmane.org
Precedence: list
Mailing-list: list mobileorg-android-/***@public.gmane.org; contact mobileorg-android+owners-/***@public.gmane.org
List-ID: <mobileorg-android.googlegroups.com>
X-Google-Group-Id: 690670325022
List-Post: <http://groups.google.com/group/mobileorg-android/post?hl=en>, <mailto:mobileorg-android-/***@public.gmane.org>
List-Help: <http://groups.google.com/support/?hl=en>, <mailto:mobileorg-android+help-/***@public.gmane.org>
List-Archive: <http://groups.google.com/group/mobileorg-android?hl=en>
Sender: mobileorg-android <mobileorg-android-/***@public.gmane.org>
List-Subscribe: <http://groups.google.com/group/mobileorg-android/subscribe?hl=en>,
<mailto:mobileorg-android+subscribe-/***@public.gmane.org>
List-Unsubscribe: <http://groups.google.com/group/mobileorg-android/subscribe?hl=en>,
<mailto:googlegroups-manage+690670325022+unsubscribe-/***@public.gmane.org>
Content-Disposition: inline
Archived-At: <http://permalink.gmane.org/gmane.comp.handhelds.android.mobileorg/207>

Thanks, Matthew, for your fast reply.

Post by mobileorg-android on behalf of Matthew Jones
note that "tel:" is a common uri for indicating that something is a
telephone number (http://tools.ietf.org/html/rfc3966)

I see! But why is "[[tel:[phone]]]" not detected as linkable
text? It is valid org-mode link syntax and moreover contains linkable
text.

Post by mobileorg-android on behalf of Matthew Jones
We allow Android's controls to realize any linkable text that it finds and
I'm not sure how well that works for your locale (it does a pretty good job
of identifying US phone numbers.

It works quite well for German phone numbers too. The standard here is

[phone]

But we find the following forms as well

[phone]
(0351) 412 95-35
0351/412 95 35
[phone]

The last form does not work but I did not expect that either.

Post by mobileorg-android on behalf of Matthew Jones
We don't have a problem necessarily implementing viewable drawers with
information like that but we don't want to just show all drawer content as
a lot of it is just metadata that is meant to be parsed a certain way. If
this is something you'd like to see handled in a particular way can you
open an issue in our issue tracker so that we can prioritize it?

Thank you. I will open an issue.

Regards