Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
E-Mail - Ask For Help / Re: Email subject wrong codepage problem after upgrading (NT10->NT14)
« on: November 21, 2023, 10:22:06 PM »
I figure it out: setCodePage input parameter is charset, not codepage (strange, I don't know what is the reason for that?)... so setCodePage(st:CP_WINDOWS_1250) is wrong (and do nothing).. and setCodePage(CHARSET:EASTEUROPE) changed codePage...
MaybeEncodeString procedure still bothers me because I can't bypass the re-encoding (I have to change the code in a lot of places, delete my encoding to utf8 and add the code page change), while with the textMessageST field nothing changet, I still have to do that (?)
MaybeEncodeString procedure still bothers me because I can't bypass the re-encoding (I have to change the code in a lot of places, delete my encoding to utf8 and add the code page change), while with the textMessageST field nothing changet, I still have to do that (?)
2
E-Mail - Ask For Help / Email subject wrong codepage problem after upgrading (NT10->NT14)
« on: November 21, 2023, 06:10:55 AM »
Greetings,
I have a problem with subject field (and also organization and filename (attachment)..).
in the previous version (NT 10) I filled the subject field with a string (codepage 1250) converted to utf8 (same as the messageText field), and everything was fine.
After upgrading to NT14, sending emails created in the same way does not bring correct characters in the subject field (messageText is still OK).
Example, subject: "TEST ?đčć??ĐČĆ?" now I get as "TEST
?".
The problem is obviously in the MaybeEncodeString procedure (NetEmail.clw). Whatever I tried, after calling MaybeEncodeString codepage is wrong (western europe 1252, and not Central/Eastern Europe 1250)... It seems to me that setCodePage doesn't work as expected?!
Everything seems to be fine when I change line
str.ToUnicode(st:EncodeUtf8,self.codepage)
To
str.ToUnicode(st:EncodeUtf8,st:CP_WINDOWS_1250).
Regards, QiQo
I have a problem with subject field (and also organization and filename (attachment)..).
in the previous version (NT 10) I filled the subject field with a string (codepage 1250) converted to utf8 (same as the messageText field), and everything was fine.
After upgrading to NT14, sending emails created in the same way does not bring correct characters in the subject field (messageText is still OK).
Example, subject: "TEST ?đčć??ĐČĆ?" now I get as "TEST
?". The problem is obviously in the MaybeEncodeString procedure (NetEmail.clw). Whatever I tried, after calling MaybeEncodeString codepage is wrong (western europe 1252, and not Central/Eastern Europe 1250)... It seems to me that setCodePage doesn't work as expected?!
Everything seems to be fine when I change line
str.ToUnicode(st:EncodeUtf8,self.codepage)
To
str.ToUnicode(st:EncodeUtf8,st:CP_WINDOWS_1250).
Regards, QiQo
3
E-Mail - Ask For Help / Re: Gmail send issue after upgrading to Nettalk 14
« on: October 30, 2023, 10:41:04 PM »
>>NetTalk Version History:
>>14.10 - 25 October 2023
>>Desktop
>>Fix: Emails to smtp.gmail.com would fail to connect.
Is this connected to our problems? Is it fixed now?
>>14.10 - 25 October 2023
>>Desktop
>>Fix: Emails to smtp.gmail.com would fail to connect.
Is this connected to our problems? Is it fixed now?
4
E-Mail - Ask For Help / Re: Gmail send issue after upgrading to Nettalk 14
« on: September 27, 2023, 04:25:07 AM »Did you note the updated SSL DLL's?
https://www.capesoft.com/docs/NetTalk14/NetTalk.htm#DeployingAtlsClientOrServer
I have exactly the same problem as willieb.
Version of libcrypto-3.dll and libssl-3.dll is 3.1.1 (date of DLLs is 2023-05-30).. Problem is also duplicated in the latest nettalk version (14.04), demo app.
Pages: [1]