Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix prop type for PidNameKeywords #216

Merged

Conversation

sixstone-qq
Copy link
Contributor

It is PtypMultipleString (0x101F) Unicode and not String 8b
according to [MS-OXPROPS] Section 2.444

It is PtypMultipleString (0x101F) Unicode and not String 8b
according to [MS-OXPROPS] Section 2.444
sixstone-qq pushed a commit to zentyal/sogo that referenced this pull request Feb 15, 2015
See [MS-OXCICAL] Section 2.1.3.1.1.20.3 for details.

It requires openchange/openchange#216 to retrieve
the value from MAPI client
sixstone-qq pushed a commit to zentyal/sogo that referenced this pull request Feb 15, 2015
See [MS-OXCICAL] Section 2.1.3.1.1.20.3 for details.

It requires openchange/openchange#216 to retrieve
the value from MAPI client
jkerihuel added a commit that referenced this pull request Feb 15, 2015
…Keywords

Fix prop type for PidNameKeywords
@jkerihuel jkerihuel merged commit baca39f into openchange:master Feb 15, 2015
sixstone-qq pushed a commit to zentyal/sogo that referenced this pull request Feb 17, 2015
See [MS-OXCICAL] Section 2.1.3.1.1.20.3 for details.

It requires openchange/openchange#216 to retrieve
the value from MAPI client
@sixstone-qq sixstone-qq deleted the ejhernandez/fix-type-PidNameKeywords branch May 4, 2015 12:51
sixstone-qq pushed a commit to sixstone-qq/openchange that referenced this pull request Feb 16, 2016
…int-StringsArray_r-nspi

nspi: Beautify StringsArray_r structure output
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants