Correct European mail documentation #1142
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These functions are used for converting European Mail to a "safe" representation by mapping conflicting characters to unused values in the English font, avoiding most cases of mojibake.
Language-aware clients (FIGS Gold/Silver, EFIGS Crystal) send all Mail over the wire in this "safe" format so that language-unaware clients (English Gold/Silver) will display them reasonably correctly, just with some spaces in place of the proper characters. When the Mail returns to a language-aware client, it gets converted back to the proper character set for use with the appropriate font based on the stored nationality value. For trades between two language-aware clients, this effectively means it just gets encoded and decoded again immediately.