opensync-users

[Opensync-users] Character coding problem

[Patryk C. <li...@pr...>]

Hi,

I'm using multisync 0.90 with 2 OpenSync plugins: syncml-obex-client (for my 
Nokia 6650) and kdepim-sync.
Config for syncml-obex-client is:
<?xml version="1.0"?>
<config>
  <bluetooth_address></bluetooth_address>
  <bluetooth_channel></bluetooth_channel>
  <interface>0</interface>
  <identifier>PC Suite</identifier>
  <version>1</version>
  <wbxml>1</wbxml>
  <username></username>
  <password></password>
  <type>5</type>
  <usestringtable>1</usestringtable>
  <onlyreplace>0</onlyreplace>
  <onlyLocaltime>0</onlyLocaltime>
  <recvLimit>10000</recvLimit>
  <maxObjSize>0</maxObjSize>
  <contact_db>Contacts</contact_db>
  <calendar_db>Calendar</calendar_db>
  <note_db>Notes</note_db>
</config>

And it works almost nice. :) The only problem is wrong handling of Polish 
diacritics. When I synced, all contacts from the phone were copied to KDE 
PIM. But in KDE PIM Polish diacritics are screwed up. I assume that it is 
some kind of character encoding problem. How can I check what encoding is 
used by my phone?

Can I somehow make proper character mappings for syncml plugin?

Is there some kind very verbose (diagnostic) mode for multisync? Or maybe I 
can use some USB sniffer? What USB sniffer do OpenSync Devs use for 
debugging?

Thanks
-- 
Patryk Cisek

Re: [Opensync-users] Character coding problem

[Chris F. <cd...@fo...>]

On Wed, May 13, 2009 at 02:22:51PM +0200, Patryk Cisek wrote:
> Can I somehow make proper character mappings for syncml plugin?
> 
> Is there some kind very verbose (diagnostic) mode for multisync? Or maybe I 
> can use some USB sniffer? What USB sniffer do OpenSync Devs use for 
> debugging?

I don't know the answer to your charset question, but if you are interested
in USB sniffing, this document may be useful as general information:

http://repo.or.cz/w/barry.git?a=blob;f=doc/USB-capture.txt;h=3e39632bd92b7d51106ddd3e9ab5caad37a87e27;hb=e3324779769a01894f86d9c16f55c82f9493dda8

See also usbmon:

http://www.mjmwired.net/kernel/Documentation/usb/usbmon.txt

Opensync also supports very verbose logging of its internal behaviour
if you set the following environment variables;

	export OSYNC_TRACE=/path/to/some/empty/directory
	export OSYNC_NOPRIVACY=1

These logs don't go to the USB level though.  But you may be able to see
the flow of data through the plugins and engine, and see where the charset
problem occurs.  I'd start here.

- Chris

Re: [Opensync-users] Character coding problem

[Patryk C. <li...@pr...>]

On Thursday 14 of May 2009 00:51:02 Chris Frey wrote:
> I don't know the answer to your charset question, but if you are interested
> in USB sniffing, this document may be useful as general information:
>
> http://repo.or.cz/w/barry.git?a=blob;f=doc/USB-capture.txt;h=3e39632bd92b7d
>51106ddd3e9ab5caad37a87e27;hb=e3324779769a01894f86d9c16f55c82f9493dda8
>
> See also usbmon:
>
> http://www.mjmwired.net/kernel/Documentation/usb/usbmon.txt
>
> Opensync also supports very verbose logging of its internal behaviour
> if you set the following environment variables;
>
> 	export OSYNC_TRACE=/path/to/some/empty/directory
> 	export OSYNC_NOPRIVACY=1
>
> These logs don't go to the USB level though.  But you may be able to see
> the flow of data through the plugins and engine, and see where the charset
> problem occurs.  I'd start here.
Thanks, I'll take a look at this.

-- 
Patryk Cisek