Re: [Telepathy] Pictogram support (Montreal Summit)
Hi Cesar, Helping people with language and cognitive disabilities communicate with each other and with folks who don't have those disabilities is one of the tasks under the AEGIS project [http://www.aegis-project.eu]. In particular, AEGIS partners SU-DART and FPD in Sweden (staff of whom are cc-ed: Mats, Lars, Bengt, and Annika) are doing that work. To that end, they are building fonts out of the CCF symbol sets that they developed for helping folks in Sweden with language and communication impairments. Initially these fonts would be used as part of a text editor - displaying symbols alongside the English/Swedish/Spanish/... words representing the same concepts (to be done as a plug-in to OpenOffice.org / LibreOffice). But the intention is that they could be used for direct communication - with any communication application that supported multi-byte characters. I'll let Mats/Lars/Bengt/Annika describe this in further detail. Regards, Peter On 10/25/2011 12:52 PM, Cesar Mauri wrote: Hi all, Recently I suggested to Meg Ford, who was attending the Montreal Summit, to ask Telepathy developers whether it would be possible to add support for pictogram based communication. Here is my suggestion: Thinking in people with language and communication disorders (i.e. people not able to read/write due to cognitive/mental disorders), it would be interesting to have a IM client able to compose, send and display messages made up pictograms + text. So, messages would look like this: http://1.bp.blogspot.com/___h4z60kN9fAk/TBnOIM61kUI/__AQ8/TM0fBXcTvyA/s1600/__cumplea%C3%B1os.png Also, it would be useful to add TTS support in order to hear messages written in plain text (which could be also useful for blind people). There had been some efforts in that way: http://www.fundmaresme.com/messengervisual/ And here Meg's answer: I spoke to one of the developers of Telepathy about this, and here is what he said: Currently Telepathy does not support this type of feature. For example, users cannot send emoticons that they have drawn themselves. Therefore, you would need to write a library for this. If you are willing to write a library, they would be happy to have this feature. Secondly, they recommend that you write a seperate app for this feature, but use the Empathy contact list. They recommend that the feature be accessed through the accessibility menu. Regarding the feasibility of implementing such a library on top of the supported protocols, Meg also told me: Do they all support sending icons? I assume that all of the chat programs do, but you would need to ask the Telepathy developers. I know enough about A.T. to be able to explain what this type of feature does from a user-end perspective, but I am not a programmer. Guillame Desmottes said that you would need to write an API to support this type of program. Again, you can speak to him about it. He said that some chat programs support, for example, sending user-made icons such as these http://emoticonhq.com/ . He said that you would need to write this type of A.P.I. for Telepathy in order to support the feature you are proposing. However, it would be best if you would discuss this with him if you want more details. And so here I am. My questions is: - Do (most commonly used) supported protocols allow for sending arbitrary images along with text? Otherwise it would be pointless to try to write a library for this. Thanks. Csar ___ gnome-accessibility-list mailing list gnome-accessibility-l...@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Peter Korn | Accessibility Principal Phone: +1 650 506 9522 Oracle Corporate Architecture Group 500 Oracle Parkway | Redwood City, CA
[Telepathy] Ang: Re: Pictogram support (Montreal Summit)
Hi Peter, Cesar and all,As Peter points out, and as I mentioned in my post in the gnome-accessibility list, the 'font track' for graphic symbols is a route to wider compatibility with existing protocols and formats. That's why we ended uptransferring the symbol graphics to fonts,to allow symbol display, aligned with text/words, within OO/LO Writer (ODF/ODT),using the existing (but limited) support for Ruby Annotation in there (only allowing 'plain text' within the annotation text). The drawback with fonts is the lacking (as far as we have found) support for colour in fonts. This is no problem for Blissymbols, but for most other pictographic symbol libraries the colour is essential for most users.So support for graphics is still a very relevant question. And what about support for Ruby Annotation in existing protocols for IM - will that be found anywhere? So on the wish list: An IM protocol with full support for Ruby Annotation - including graphics as part of the text - also in the annotation. But until then what?Mats -Peter Korn peter.k...@oracle.com skrev: -Hi Cesar,Helping people with language and cognitive disabilities communicate with each other and with folks who don't have those disabilities is one of the tasks under the AEGIS project [http://www.aegis-project.eu]. In particular, AEGIS partners SU-DART and FPD in Sweden (staff of whom are cc-ed: Mats, Lars, Bengt, and Annika) are doing that work. To that end, they are building fonts out of the CCF symbol sets that they developed for helping folks in Sweden with language and communication impairments. Initially these fonts would be used as part of a text editor - displaying symbols alongside the English/Swedish/Spanish/... words representing the same concepts (to be done as a plug-in to OpenOffice.org / LibreOffice). But the intention is that they could be used for direct communication - with any communication application that supported multi-byte characters.I'll let Mats/Lars/Bengt/Annika describe this in further detail.Regards,PeterOn 10/25/2011 12:52 PM, Cesar Mauri wrote: Hi all, Recently I suggested to Meg Ford, who was attending the Montreal Summit, to ask Telepathy developers whether it would be possible to add support for pictogram based communication. Here is my suggestion: Thinking in people with language and communication disorders (i.e. people not able to read/write due to cognitive/mental disorders), it would be interesting to have a IM client able to compose, send and display messages made up pictograms + text. So, messages would look like this: http://1.bp.blogspot.com/___h4z60kN9fAk/TBnOIM61kUI/__AQ8/TM0fBXcTvyA/s1600/__cumplea%C3%B1os.png Also, it would be useful to add TTS support in order to hear messages written in plain text (which could be also useful for blind people). There had been some efforts in that way: http://www.fundmaresme.com/messengervisual/ And here Meg's answer: I spoke to one of the developers of Telepathy about this, and here is what he said: Currently Telepathy does not support this type of feature. For example, users cannot send emoticons that they have drawn themselves. Therefore, you would need to write a library for this. If you are willing to write a library, they would be happy to have this feature. Secondly, they recommend that you write a seperate app for this feature, but use the Empathy contact list. They recommend that the feature be accessed through the accessibility menu. Regarding the feasibility of implementing such a library on top of the supported protocols, Meg also told me: Do they all support sending icons? I assume that all of the chat programs do, but you would need to ask the Telepathy developers. I know enough about A.T. to be able to explain what this type of feature does from a user-end perspective, but I am not a programmer. Guillame Desmottes said that you would need to write an API to support this type of program. Again, you can speak to him about it. He said that some chat programs support, for example, sending user-made icons such as these http://emoticonhq.com/ . He said that you would need to write this type of A.P.I. for Telepathy in order to support the feature you are proposing. However, it would be best if you would discuss this with him if you want more details. And so here I am. My questions is: - Do (most commonly used) supported protocols allow for sending arbitrary images along with text? Otherwise it would be pointless to try to write a library for this. Thanks. César ___ gnome-accessibility-list mailing list gnome-accessibility-l...@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Peter Korn | Accessibility PrincipalPhone: +1 650 506 9522 Oracle Corporate Architecture Group500 Oracle Parkway | Redwood City, CA 94065 Oracle is committed to developing practices and products that help protect the environment ___ telepathy mailing list
[Telepathy] Pictogram support (Montreal Summit)
Hi all, Recently I suggested to Meg Ford, who was attending the Montreal Summit, to ask Telepathy developers whether it would be possible to add support for pictogram based communication. Here is my suggestion: Thinking in people with language and communication disorders (i.e. people not able to read/write due to cognitive/mental disorders), it would be interesting to have a IM client able to compose, send and display messages made up pictograms + text. So, messages would look like this: http://1.bp.blogspot.com/___h4z60kN9fAk/TBnOIM61kUI/__AQ8/TM0fBXcTvyA/s1600/__cumplea%C3%B1os.png Also, it would be useful to add TTS support in order to hear messages written in plain text (which could be also useful for blind people). There had been some efforts in that way: http://www.fundmaresme.com/messengervisual/ And here Meg's answer: I spoke to one of the developers of Telepathy about this, and here is what he said: Currently Telepathy does not support this type of feature. For example, users cannot send emoticons that they have drawn themselves. Therefore, you would need to write a library for this. If you are willing to write a library, they would be happy to have this feature. Secondly, they recommend that you write a seperate app for this feature, but use the Empathy contact list. They recommend that the feature be accessed through the accessibility menu. Regarding the feasibility of implementing such a library on top of the supported protocols, Meg also told me: Do they all support sending icons? I assume that all of the chat programs do, but you would need to ask the Telepathy developers. I know enough about A.T. to be able to explain what this type of feature does from a user-end perspective, but I am not a programmer. Guillame Desmottes said that you would need to write an API to support this type of program. Again, you can speak to him about it. He said that some chat programs support, for example, sending user-made icons such as these http://emoticonhq.com/ . He said that you would need to write this type of A.P.I. for Telepathy in order to support the feature you are proposing. However, it would be best if you would discuss this with him if you want more details. And so here I am. My questions is: - Do (most commonly used) supported protocols allow for sending arbitrary images along with text? Otherwise it would be pointless to try to write a library for this. Thanks. César ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] ANNOUNCE: telepathy-rakia 0.7.2
Hello, Fedora rawhide now uses telepathy-rakia version 0.7.2 Since the change from sofia to rakia my app has stopped working. It's always offline. It turns out Mission Control is not starting the telepathy- rakia process. Or the process is timing out. Starting the process manually results in the following error. lateef@submission ~/D/teletest /usr/libexec/telepathy-rakia tp-glib-DEBUG: started version 0.7.2 (telepathy-glib version 0.16.0) tp-glib-DEBUG: no connections, and timed out tp-glib-Message: Exiting Any ideas? Thanks On Tuesday, September 6, 2011, Mikhail Zabaluev wrote: A Telepathy-Rakia development release 0.7.2, the Correcting People release, is now available. Tarball: http://telepathy.freedesktop.**org/releases/telepathy-rakia/** telepathy-rakia-0.7.2.tar.gzhttp://telepathy.freedesktop.org/releases/telepathy-rakia/telepathy-rakia-0.7.2.tar.gz Signature: http://telepathy.freedesktop.**org/releases/telepathy-rakia/** telepathy-rakia-0.7.2.tar.gz.**aschttp://telepathy.freedesktop.org/releases/telepathy-rakia/telepathy-rakia-0.7.2.tar.gz.asc News and enhancements: - The project is renamed to Telepathy-Rakia. - Updated Channel.Interface.DTMF implementation to spec 0.21.3. * This means dialstrings! - Improved and slightly optimized logging. - Added Messages properties to immutable properties. This release also includes fixes and enhancements done to the stable telepathy-sofiasip releases up to version 0.6.8. Наздраве! Mikhail __**_ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/**mailman/listinfo/telepathyhttp://lists.freedesktop.org/mailman/listinfo/telepathy ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
[Telepathy] telepathy-rakia not working (Was: ANNOUNCE: telepathy-rakia 0.7.2)
Hi, -Original Message- From: ext Mystilleef [mailto:mystill...@gmail.com] Sent: 26 October, 2011 17:39 To: Zabaluev Mikhail (Nokia-MP/Helsinki) Cc: telepathy@lists.freedesktop.org; ftp-rele...@lists.freedesktop.org Subject: Re: [Telepathy] ANNOUNCE: telepathy-rakia 0.7.2 Fedora rawhide now uses telepathy-rakia version 0.7.2 Since the change from sofia to rakia my app has stopped working. It's always offline. It turns out Mission Control is not starting the telepathy- rakia process. Or the process is timing out. Starting the process manually results in the following error. lateef@submission ~/D/teletest /usr/libexec/telepathy-rakia tp-glib-DEBUG: started version 0.7.2 (telepathy-glib version 0.16.0) tp-glib-DEBUG: no connections, and timed out tp-glib-Message: Exiting You can make it run persistently by exporting RAKIA_PERSIST=1. Also export RAKIA_DEBUG=all for more information in the log. You can also see the logs in the debug window in Empathy, if you select the rakia component (or it might still be listed as sofiasip, I did not check yet). Hope this helps, Mikhail smime.p7s Description: S/MIME cryptographic signature ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] telepathy-rakia not working (Was: ANNOUNCE: telepathy-rakia 0.7.2)
Thanks, with your help, I enabled debugging and got the rakia process to persist. My app is still offline. Here is the pertinent debug information. In particular, the following line looks strange. Any ideas? ** DEBUG: outbound(0x8c20620): FAILED to validate sip:1295977e0@174.109.174.240:43327;transport=udp ** DEBUG: outbound(0x8c20620): FAILED with 200 OK = ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound: 101 NAT detected ** DEBUG: rakia_base_connection_sofia_callback: connection 0x8c1b058, refcount 1 ** DEBUG: rakia_base_connection_sofia_callback: dispatching to target 0x8c1b058 (handle 0x8c20620) ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound for target 0x8c1b058 was not consumed ** DEBUG: rakia_base_connection_sofia_callback: exit ** DEBUG: rakia_base_connection_sofia_callback: event nua_r_register: 401 Unauthorized ** DEBUG: rakia_base_connection_sofia_callback: connection 0x8c1b058, refcount 1 ** DEBUG: rakia_base_connection_sofia_callback: dispatching to target 0x8c1b058 (handle 0x8c20620) ** DEBUG: priv_handle_auth: response presents an authentication challenge ** DEBUG: priv_handle_auth: using the primary auth credentials ** DEBUG: priv_handle_auth_continue: Digest-authenticating user='1295977e0' realm=sipgate.com ** DEBUG: rakia_base_connection_sofia_callback: exit ** DEBUG: rakia_base_connection_sofia_callback: event nua_r_register: 200 OK ** DEBUG: rakia_base_connection_sofia_callback: connection 0x8c1b058, refcount 1 ** DEBUG: rakia_base_connection_sofia_callback: dispatching to target 0x8c1b058 (handle 0x8c20620) ** DEBUG: rakia_connection_nua_r_register_cb: successfully registered to the network tp-glib/connection-DEBUG: tp_base_connection_change_status: was 1, now 0, for reason 1 tp-glib/connection-DEBUG: tp_base_connection_change_status: emitting status-changed to 0, for reason 1 ** DEBUG: rakia_base_connection_sofia_callback: exit ** DEBUG: conn_get_alias: handle 1 got alias 129597...@sipgate.com ** DEBUG: rakia_connection_set_aliases: setting alias for self: 1295977e0 Gtk-WARNING **: Unknown property: GtkGrid.n-rows ** DEBUG: outbound(0x8c20620): FAILED to validate sip:1295977e0@174.109.174.240:43327;transport=udp ** DEBUG: outbound(0x8c20620): FAILED with 200 OK ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound: 200 OK ** DEBUG: rakia_base_connection_sofia_callback: connection 0x8c1b058, refcount 1 ** DEBUG: rakia_base_connection_sofia_callback: dispatching to target 0x8c1b058 (handle 0x8c20620) ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound for target 0x8c1b058 was not consumed ** DEBUG: rakia_base_connection_sofia_callback: exit ** DEBUG: nta_agent: tport: Bad message ** DEBUG: nta_agent: tport: Bad message ** DEBUG: outbound(0x8c20620): FAILED to validate sip:1295977e0@174.109.174.240:43327;transport=udp ** DEBUG: outbound(0x8c20620): FAILED with 200 OK ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound: 200 OK ** DEBUG: rakia_base_connection_sofia_callback: connection 0x8c1b058, refcount 1 ** DEBUG: rakia_base_connection_sofia_callback: dispatching to target 0x8c1b058 (handle 0x8c20620) ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound for target 0x8c1b058 was not consumed ** DEBUG: rakia_base_connection_sofia_callback: exit = On Wednesday, October 26, 2011, wrote: Hi, -Original Message- From: ext Mystilleef [mailto:mystill...@gmail.com javascript:;] Sent: 26 October, 2011 17:39 To: Zabaluev Mikhail (Nokia-MP/Helsinki) Cc: telepathy@lists.freedesktop.org javascript:;; ftp-rele...@lists.freedesktop.org javascript:; Subject: Re: [Telepathy] ANNOUNCE: telepathy-rakia 0.7.2 Fedora rawhide now uses telepathy-rakia version 0.7.2 Since the change from sofia to rakia my app has stopped working. It's always offline. It turns out Mission Control is not starting the telepathy- rakia process. Or the process is timing out. Starting the process manually results in the following error. lateef@submission ~/D/teletest /usr/libexec/telepathy-rakia tp-glib-DEBUG: started version 0.7.2 (telepathy-glib version 0.16.0) tp-glib-DEBUG: no connections, and timed out tp-glib-Message: Exiting You can make it run persistently by exporting RAKIA_PERSIST=1. Also export RAKIA_DEBUG=all for more information in the log. You can also see the logs in the debug window in Empathy, if you select the rakia component (or it might still be listed as sofiasip, I did not check yet). Hope this helps, Mikhail ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] telepathy-rakia not working (Was: ANNOUNCE: telepathy-rakia 0.7.2)
Hi, -Original Message- From: ext Mystilleef [mailto:mystill...@gmail.com] Sent: 26 October, 2011 18:57 To: Zabaluev Mikhail (Nokia-MP/Helsinki) Cc: telepathy@lists.freedesktop.org Subject: Re: [Telepathy] telepathy-rakia not working (Was: ANNOUNCE: telepathy-rakia 0.7.2) Thanks, with your help, I enabled debugging and got the rakia process to persist. My app is still offline. Here is the pertinent debug information. In particular, the following line looks strange. Any ideas? ** DEBUG: outbound(0x8c20620): FAILED to validate sip:1295977e0@174.109.174.240:43327;transport=udp ** DEBUG: outbound(0x8c20620): FAILED with 200 OK This is harmless. In fact this log shows that telepathy-rakia has successfully connected. Can you capture the dbus log with dbus-monitor --session (filtering irrelevant traffic if needed for privacy reasons) and send it to me? Best regards, Mikhail smime.p7s Description: S/MIME cryptographic signature ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] telepathy-rakia not working (Was: ANNOUNCE: telepathy-rakia 0.7.2)
I captured the following dbus events happen when making an sip call with my app. Basically, the call gets disconnected with error reason 2. Don't know why. My internet connection works fine. = signal sender=:1.133 - dest=(null destination) serial=13 path=/org/sourceforge/SoroSIPMissionControl; interface=org.sourceforge.SoroSIPMissionControl; member=outgoing_call string 01113373037751 method call sender=:1.134 - dest=org.freedesktop.DBus serial=48 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string type='signal',sender='org.freedesktop.Telepathy.ChannelDispatcher',path='/org/freedesktop/Telepathy/ChannelDispatcher',interface='org.freedesktop.Telepathy.ChannelDispatcher' method call sender=:1.134 - dest=org.freedesktop.DBus serial=49 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string type='signal',sender='org.freedesktop.DBus',path='/org/freedesktop/DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.freedesktop.Telepathy.ChannelDispatcher' method call sender=:1.134 - dest=org.freedesktop.DBus serial=50 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetNameOwner string org.freedesktop.Telepathy.ChannelDispatcher method call sender=:1.134 - dest=org.freedesktop.Telepathy.ChannelDispatcher serial=51 path=/org/freedesktop/Telepathy/ChannelDispatcher; interface=org.freedesktop.Telepathy.ChannelDispatcher; member=EnsureChannel object path /org/freedesktop/Telepathy/Account/rakia/sip/_31295977e0_40sipgate_2ecom0 array [ dict entry( string org.freedesktop.Telepathy.Channel.TargetID variant string sip:01113373037...@sipgate.com ) dict entry( string org.freedesktop.Telepathy.Channel.TargetHandleType variant int32 1 ) dict entry( string org.freedesktop.Telepathy.Channel.ChannelType variant string org.freedesktop.Telepathy.Channel.Type.StreamedMedia ) dict entry( string org.freedesktop.Telepathy.Channel.Type.StreamedMedia.InitialAudio variant boolean true ) dict entry( string org.freedesktop.Telepathy.Channel.Type.StreamedMedia.InitialVideo variant boolean false ) ] int64 1319648013 string org.freedesktop.Telepathy.Client.SoroSIPStreamedMediaHandlerClient signal sender=:1.133 - dest=(null destination) serial=14 path=/org/sourceforge/SoroSIPMissionControl; interface=org.sourceforge.SoroSIPMissionControl; member=started_phone_call_session string 01113373037751 method return sender=:1.125 - dest=:1.134 reply_serial=51 object path /com/nokia/MissionControl/requests/r1 method call sender=:1.134 - dest=org.freedesktop.DBus serial=52 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetNameOwner string org.freedesktop.Telepathy.ChannelDispatcher method call sender=:1.134 - dest=org.freedesktop.DBus serial=53 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string type='signal',sender=':1.125',path='/com/nokia/MissionControl/requests/r1',interface='org.freedesktop.Telepathy.ChannelRequest' method call sender=:1.134 - dest=org.freedesktop.DBus serial=54 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string type='signal',sender='org.freedesktop.DBus',path='/org/freedesktop/DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0=':1.125' method call sender=:1.134 - dest=:1.125 serial=55 path=/com/nokia/MissionControl/requests/r1; interface=org.freedesktop.Telepathy.ChannelRequest; member=Proceed method return sender=:1.125 - dest=:1.134 reply_serial=55 method call sender=:1.134 - dest=org.freedesktop.DBus serial=56 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch string type='signal',sender='org.freedesktop.Telepathy.ChannelDispatcher',path='/org/freedesktop/Telepathy/ChannelDispatcher',interface='org.freedesktop.Telepathy.ChannelDispatcher' method call sender=:1.134 - dest=org.freedesktop.DBus serial=57 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch string type='signal',sender='org.freedesktop.DBus',path='/org/freedesktop/DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.freedesktop.Telepathy.ChannelDispatcher' signal sender=:1.125 - dest=(null destination) serial=148 path=/org/freedesktop/Telepathy/Account/rakia/sip/_31295977e0_40sipgate_2ecom0; interface=org.freedesktop.Telepathy.Account; member=AccountPropertyChanged array [ dict entry( string Connection variant object path / ) dict entry( string ConnectionStatusReason variant uint32 1 ) dict entry( string ConnectionStatus
