On 10/03/11 10:30, Brad Hards wrote:
On Monday 03 October 2011 19:13:30 Alois Schloegl wrote:
(*) patch_unicode+keywords.diff: the function function mapidump_contact
in libmapi/mapidump.c is actually patched, it incorporates a field
separator 0x1e, in order to avoid escaping of special characters within
each field.
Maybe someone else can make more sense of this, but I'm more confused than
before. Possibly it doesn't help that I can't read the perl script.
The purpose of this script is to test whether the number in the first
line matches the number of data records, if not it reports a warning.
Of course, one could use a number of other tools, for testing this
issue. Pick any, you feel comfortable with.
Is the problem that you just don't like the formatting of mapidump_contact? I
think you're possibly expecting too much of openchangeclient...
I've included the patch because I use a number of additional fields in
mapidump_contact and I'm not sure whether this might affect the issue.
The reason for using a different line separator is, that some field
values can have multiple lines, this easily confuses my parser of the
dump file. Escaping of special characters (like <line feed>, <new line>,
etc) seemed to be more complicated than the present solution.
Ideally, there would be an interface to SQL, or at least a CSV export.
Why are you reverting changes to the version of samba? Which part of the patch
relates the problem you're trying to describe?
I installed openchange from the SVN repository shortly after 0.11 has
been released, and I had difficulties installing openchange. It seemed
the installer did not upgrade the version number of samba in an
appropriate way. Changing the version number fixed the issue for me.
Alois
Brad
_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel
