> To be honest, the more and more I think about this, the more my
> conclusion is to not support phonebook export. It is a bad idea. It is
> highly complex and it is not a feature that will be used anyway.
Ok, got it. Do you have any insight if MeeGo still wants this
(http://bugs.meego.com/show_b
> no index number. We will never use them. It is either the full
> phonebook
> at once or nothing. The write function has to empty out left over
> entries.
...
> Actually I prefer we use proper Dict field names. We never use anything
> literally from the specifications in this area. So why start no
> > > > To support this feature then first we need to convert the current
> > > > feature into returning a dict. And then have this feature using a
> > dict
> > > > as input.
> > >
> > > Is there already a specification/draft of the format of this dict?
> If
> > not, I would be tempted to use the 2
> > > To support this feature then first we need to convert the current
> > > feature into returning a dict. And then have this feature using a
> dict
> > > as input.
> >
> > Is there already a specification/draft of the format of this dict? If
> not, I would be tempted to use the 27.007 +CPBR/W fi
> > diff --git a/TODO b/TODO
> > index bf2305b..9dcb43f 100644
> > --- a/TODO
> > +++ b/TODO
> > @@ -496,3 +496,14 @@ Miscellaneous
> >
> >Priority: Low
> >Complexity: C4
> > +
> > +- Enable exporting contact information from vCard data to SM and ME
> stores.
> > + Need to implement a robu
