[Pidgin] #15120: Contacts using GTalk on Android don't show up as capable of audio/video.

[Pidgin]

#15120: Contacts using GTalk on Android don't show up as capable of audio/video.
--------------------------+-------------------------------------------------
 Reporter:  malu          |     Owner:  rekkanoryo
     Type:  defect        |    Status:  new       
Component:  unclassified  |   Version:  2.10.3    
 Keywords:                |  
--------------------------+-------------------------------------------------
 Contacts using the Android GTalk application don't show up with a webcam
 icon.

 Looking at the contents of ~/.purple/xmpp-caps.xml
 we can see this regarding the gmail web plugin:


         <client node='http://mail.google.com/xmpp/client/caps' ver='1.1'>
                 <identity category='client' type='pc'/>
                 <feature var='http://jabber.org/protocol/disco#info'/>
                 <ext identifier='voice-v1'>
                         <feature
 var='http://www.google.com/xmpp/protocol/voice/v1'/>
                 </ext>
                 <ext identifier='video-v1'>
                         <feature
 var='http://www.google.com/xmpp/protocol/video/v1'/>
                 </ext>
                 <ext identifier='sms-v1'>
                         <feature
 var='http://www.google.com/xmpp/protocol/sms/v1'/>
                 </ext>
                 <ext identifier='pmuc-v1'>
                         <feature
 var='http://www.google.com/xmpp/protocol/pmuc/v1'/>
                 </ext>
                 <ext identifier='vavinvite-v1'>
                         <feature
 var='http://www.google.com/xmpp/protocol/vavinvite/v1'/>
                 </ext>
         </client>

 and for the GTalk client on Android 4.0 (ICS) on an Asus Eeepad
 Transformer:

         <client node='http://www.android.com/gtalk/client/caps2'
 ver='1.1'>
                 <identity category='account' type='registered'
 name='Google Talk User Account'/>
                 <feature var='http://jabber.org/protocol/disco#items'/>
                 <feature var='http://jabber.org/protocol/disco#info'/>
                 <ext identifier='voice-v1'>
                         <feature
 var='http://jabber.org/protocol/disco#items'/>
                         <feature
 var='http://jabber.org/protocol/disco#info'/>
                 </ext>
                 <ext identifier='camera-v1'>
                         <feature
 var='http://jabber.org/protocol/disco#items'/>
                         <feature
 var='http://jabber.org/protocol/disco#info'/>
                 </ext>
                 <ext identifier='video-v1'>
                         <feature
 var='http://jabber.org/protocol/disco#items'/>
                         <feature
 var='http://jabber.org/protocol/disco#info'/>
                 </ext>
                 <ext identifier='pmuc-v1'>
                         <feature
 var='http://jabber.org/protocol/disco#items'/>
                         <feature
 var='http://jabber.org/protocol/disco#info'/>
                 </ext>
         </client>

 one solution, although hacky, could be to assume a feature of the
 corresponding type for each of those <ext/> tags.
 This might be acceptable, since we already do some special hacks for the
 Google stuff to work, as far as I remember.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/15120>
Pidgin <http://pidgin.im>
Pidgin