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

MultiMail has limited, archaic character set support #9

Open
wmcbrine opened this issue Mar 20, 2018 · 3 comments
Open

MultiMail has limited, archaic character set support #9

wmcbrine opened this issue Mar 20, 2018 · 3 comments

Comments

@wmcbrine
Copy link
Owner

Modern terminals speak Unicode. So should MultiMail.

@andy5995
Copy link
Contributor

andy5995 commented Aug 8, 2019

I'd be interested in working on this, but I'm not sure how to begin. Would you be willing to give me some starting tips?

@andy5995
Copy link
Contributor

andy5995 commented Aug 8, 2019

I'll back out of this, better to let someone work on it who knows what they're doing ;)

@rswindell
Copy link
Contributor

Synchronet-created QWK packets can contain CP437 or UTF-8 encoded message body text and header fields (e.g. to/from/subject), though CP437 is the default. The HEADERS.DAT includes an indicator ("utf8=true") to indicate to the reader that any non-ASCII characters for a particular message (body text and header fields) are indeed UTF-8 and not CP437.

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

No branches or pull requests

3 participants