View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006417 | JEDI VCL | 00 JVCL Components | public | 2015-07-08 10:31 | 2015-09-14 14:09 |
Reporter | tetardd | Assigned To | obones | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | resolved | Resolution | won't fix | ||
Product Version | Daily / GIT | ||||
Target Version | Fixed in Version | ||||
Summary | 0006417: JvMail and JclMAPI use Anis version of API | ||||
Description | Tested with D. XE2: JvMail that uses JclMAPI use the Ansi version of the API. Microsoft says we should be using the Unicode version (search MAPISendMail and MAPISendMailW for example, see here: https://msdn.microsoft.com/en-us/library/windows/desktop/dd296721(v=vs.85).aspx) as the Ansi may be removed from future version of Windows. Hence, for Delphi versions that have Unicode strings as default, the Unicode API should be used by JclMAPI. JclMAPI uses TMapiMessage defined in Winapi.mapi: MapiMessage = record ... lpszSubject: LPSTR; { Message Subject } lpszNoteText: LPSTR; { Message Text } lpszMessageType: LPSTR; { Message Class } lpszDateReceived: LPSTR; { in YYYY/MM/DD HH:MM format } lpszConversationID: LPSTR; { conversation thread ID } ... end; TMapiMessage = MapiMessage; LPSTR are AnsiStrings. | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2015-07-08 10:31 | tetardd | New Issue | |
2015-09-14 11:25 | obones | Status | new => acknowledged |
2015-09-14 14:09 | obones | Note Added: 0021199 | |
2015-09-14 14:09 | obones | Status | acknowledged => resolved |
2015-09-14 14:09 | obones | Resolution | open => won't fix |
2015-09-14 14:09 | obones | Assigned To | => obones |