Re: [Fwd: Re: DSV replacement with csv]

> Unicode is outside of the scope of csv. As recently discussed on clp, 
> csv deals exclusively with bytes. However IIRC Unicode inside "" passes.
> I have to do some extra tests.

We definitely need unicode handled correctly.  Programs on Mac in particular
like to spew out unicode text files.
 
> Same for csv.

Cool.  I had looked originally when the csv module was first introduced
but obviously wasn't paying enough attention.  Other than potential 
unicode issues, dropping DSV will be a really nice gain.

> Currently I can use only Windows and yes, I am in that order.

On the algorithms side, we desperately need to be able to do syncing.
In theory this is simple - record the state of information before and
after on a data source (Outlook, the phone etc) and then apply the diffs
to the data elsewhere (eg in BitPim).  If smart enough you can allow for
updates in multiple sources and still get the results right.

The problem we have in BitPim is that the phones are lousy.  They munge the
data, have restricted fields, lose information etc.  Heck even Outlook has
arbitrary limitiations (eg only 3 email addresses).  So the question is how
do you do syncing despite all the sources of data messing with it?  NB the
BitPim internal format is very strong and doesn't lose data (much).

Roger


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click