Hi Julien, On Sat, Aug 30, 2008 at 03:14, Julien Kerihuel <[EMAIL PROTECTED]> wrote: > > Hi List, > > This week-end I'll commit an important update to the > mapi-named-properties file which may probably break developer's > applications relying on the existing set of named properties. > > I have basically been mapping properties listed in MS-OXCPROPS ( from > page 31 to 114) which results in around 388 modifications (add + > change). > > I don't yet think the file is complete, but it provides a much more > robust and complete set of named properties than we used to have. > Furthermore this new set is a one-shot process and no further > modification of existing properties will be scheduled.
ATM, I have one concern - the differentiation of PT_STRING8 and PT_UNICODE named properties. From what I've observed, some properties like PidLidLocation (from MS-OXOCAL) do not seem to work correctly if I use PT_STRING8 and have some non-ASCII characters like '€' in the string. Will such properties be updated to PT_UNICODE? Or is there a way to have them both? (The documents seem to use PtypString to indicate PT_UNICODE and PtypString8 to indicate PT_STRING8.. but well, there are inconsistencies in there, its probably not reliable enough yet. :-) ) -Suman _______________________________________________ devel mailing list devel@openchange.org http://mailman.openchange.org/listinfo/devel
