[missing-sync-palmos-talk] Missing Sync for Palm OS 4.0.1 beta 5 now available

[Scott Gruby]

On Sep 9, 2004, at 2:03 AM, Eugene Bobin wrote:

> 3. Make hack in hotsync manager, which will smart recode byte stream
> between iSync conduit and palm device (reading/writing addresses,todos
> and datebook databases)
>

This is not an option as Missing Sync simply passes the data from the 
device to the conduit without looking at what is in the stream; the 
conduit needs to have the intelligence to deal with character sets. If 
Missing Sync started transcoding the byte stream, conduits wouldn't 
work (what would the effect be on the backup conduit to change the 
character set of the data?). If we special cased each conduit, how 
would we know when to start and stop the transcode? There is some 
information that the conduits read (which we don't control) that would 
be inappropriate for a transcode.

I wish there was a better solution for you, but it seems to be that the 
right solution is 2 fold:

1) Have the companies that make the Cyrillic (and other language) 
modules report the proper encoding to the conduit. In our MemoPad 
conduit, we call SyncReadFeature(sysFtrCreator, sysFtrNumEncoding, 
&encoding); to get the encoding. With the Cyrillic support we've tried, 
they improperly report the encoding as charEncodingPalmLatin when it 
should be charEncodingCP1251, charEncodingKoi8R, or charEncodingKoi8.

2) Have the conduit developers read the encoding from the device and do 
the proper transcoding where they need to do it. In our MemoPad 
conduit, we are trying to do that by reading the encoding and then 
picking a proper OS X encoding that is equivalent.


--
Scott Gruby
Lead Engineer, Missing Sync for Palm OS
Mark/Space, Inc.
<http://www.markspace.com/>

Please contact support at markspace.com for assistance with Mark/Space 
products.