On 05/03/11 22:38, Brad Hards wrote:
On Tue, 3 May 2011 08:13:41 pm Alois Schloegl wrote:
Before discussing the alternatives below, I'd really like to know how
important the support for String8 really is. Are there really still
exchange servers around that support only String8 but not Unicode ?
Unicode is required by the documented protocol (i.e. Exchange 2003->).
However some properties are defined as PtypString8 (0x001E) - see [MS-OXPROPS]
document. That is, if you ask for a property that has the 0x001E data type
using the 0x001F data type, I'm not sure it will work in every case. I assume
it will, but I'm not sure that is promised by the protocol.
Brad
For the mapidump_contacts, the change to
request.WantUnicode = 1;
worked very smoothly without any unexpected issues (only a few values at
calls to find_mapi_SPropValue_data(..,value) had to be modified. My
guess would be that this holds also for the other functions.
As far as I can see it, the change to WantUnicode need only change in a
limited number of values in the functions (mapidump_message,
mapidump_appointment, mapidump_task, mapidump_note,
mapidump_walk_attachment, mapidump_walk_container,
mapidump_walk_content). Or do I miss something?
As long as we keep GetPropsAllUnicode(), each of these functions could
be tested independently, and it might be possible to switch gradually
from String8 to Unicode. If you think this is a viable option, I can try
working on patches for such a transition.
Alois
_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel
