Skip to content
New issue

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

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

Already on GitHub? # to your account

Fix unicode parsing #139

Merged
merged 1 commit into from
Sep 27, 2022
Merged

Conversation

ThomasChr
Copy link
Contributor

This should fix #136
(Too) many explanations in the issue

I'm not quite sure if this is the right way to do it, but I think it should be correct.
I have two testmails (can't publish them openly) which are now working.

They have both kinds of RTF-Unicode Strings in them:
No. 1:
(C_UNICODE_STRING)

\u-3929 ?;

No 2:
(C_UNICODE_ESC_STRING)

\u8729\'b7

@ThomasChr ThomasChr closed this Sep 26, 2022
@ThomasChr ThomasChr deleted the fix_unicode_parsing branch September 26, 2022 11:01
@ThomasChr ThomasChr restored the fix_unicode_parsing branch September 26, 2022 11:01
@ThomasChr
Copy link
Contributor Author

The mail did not go through. I sent it again.
And I haven no idea why this is closed. I reopen it :-)

@ThomasChr ThomasChr reopened this Sep 27, 2022
@ThomasChr ThomasChr force-pushed the fix_unicode_parsing branch 3 times, most recently from fa9c7bd to 7809917 Compare September 27, 2022 06:36
@ThomasChr
Copy link
Contributor Author

And that did the trick!
Both my testmails are parsing just fine now!

@lolo101 lolo101 merged commit 07526fb into lolo101:master Sep 27, 2022
@lolo101
Copy link
Owner

lolo101 commented Sep 27, 2022

Very well! Thank you very much for the very details report, the fix, and the test 😉

@ThomasChr ThomasChr deleted the fix_unicode_parsing branch October 4, 2022 06:37
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Exception: Encountered <C_ESC_STRING>, Expected <STRING>
2 participants