Having problems with message search?
Whether you set the _A or _W flavor of a given property, the
underlying message store provider must store only once instance of the property
and should be able to return either _A or _W property depending on what the
client requests.
MFCMAPI and OutlookSpy both happen to request the _A flavor.
From:
outlook-dev@yahoogroups.com [mailto:outlook-dev@yahoogroups.com] On Behalf
Of tgoetze
Sent: Friday, June 19, 2009 4:22 PM
To: outlook-dev@yahoogroups.com
Subject: Re: Setting recipients with non-ascii data
That was it (needed to use _W property).
I am not checking for Unicode support, but it is working....meaning now I can
see the values as expected in Outlook.
However, it is interesting that using MFCMAPI does not allow the non-ASCII data
to be shown (it shows ????), and the tag ends in 1E and is listed as a
PT_STRING8. So, this makes sense as to why it shows ????, but it is unpexected
since I set it as 1F and Outlook is happy with it.
-t
--- In outlook-dev@yahoogroups.com,
"Ken Slovak" <kenslovak@...> wrote:
>
> Did you change the property tag you're looking at?
>
> If a string property tag ends with 0x1E it's a PT_STRING8 property, for
> Unicode you'd have a property tag ending with 0x1F (PT_UNICODE). You also
> obviously need a store that supports Unicode (PR_STORE_SUPPORT_MASK on the
> store would have the STORE_UNICODE_OK bit flag set.
>
> Ken Slovak
> Slovak Technical Services, Inc.
Offline 
Send Email