Hi Chris,

I did some brief tests with my address book and call logs, and btardump
works very fine. Thanks!

However, with SMS Messages (which is my main concern), as btardump
doesn't support specifying character encoding like btool does, the
output is a mess and cannot be read by a text editor. The strings from
btardump itself (and btool without "-i UTF-8") are ASCII, while for SMS
containing international characters the encoding is UCS-2 which is
ASCII-incompatible.

Therefore I hope inside r_sms.cc the encoding of the message should be
converted to UTF-8 even if no IConverter parameter is passed. Most
modern *NIX systems are running on UTF-8 now, and it could also make
using the library easier since program output are expected to be UTF-8
with international characters.


Keep up the great work,
Ryan

On Tue, 2010-11-30 at 22:30 -0500, Chris Frey wrote:
> Hi list!
> 
> The above desired feature now exists, in the form of tools/btardump.cc
> and the accompanying parser classes and builder classes which have been
> added to Barry's git tree today.
> 
> The idea is that you can have multiple builders, which provide raw
> binary record data from various sources, which can feed into parsers
> which provide Record classes (Contact, Calendar, etc) that hold the
> fields of usable data.  Alternately, parsers can just store the data
> whatever format they need.
> 
> There is also a Pipe class that hooks them together.  So we now have:
> 
>       Builders                                Parsers
>       ========                                =======
>       Restore                                 Backup
>       DeviceBuilder        (Pipe)             HexDumpParser
>                                               RecordParser<>
>                                               MultiRecordParser
>                                               AllRecordParser
>                                               TeeParser
>                                               NullParser
> 
> Restore reads from backup tarballs, Backup writes them.
> DeviceBuilder reads from devices.
> 
> The RecordParser<> template takes a storage functor class, and there
> are three built-in storage classes available:
> 
>       NullStore
>       DumpStore
>       AllRecordDumpStore : public AllRecordStore
> 
> See examples/pipedump.cc and tools/btardump.cc for examples of how
> to connect these classes to do work for you.
> 
> Enjoy, and let me know if you find any bugs!
> - Chris



------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to