We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The RFC: http://www.faqs.org/rfcs/rfc2368.html
Specifies about encoding in Section 5: "Also note that line breaks in the body of a message MUST be encoded with "%0D%0A".
Currently pcs only uses %0A ( 0A == \n ).
The text was updated successfully, but these errors were encountered:
[pelican_comment_system] Fix mailto link: use '\r\n' instead of '\n'; F…
6a17f90
…ixes getpelican#719
89faff9
No branches or pull requests
The RFC: http://www.faqs.org/rfcs/rfc2368.html
Specifies about encoding in Section 5:
"Also note that line breaks in the body of a message MUST be encoded with "%0D%0A".
Currently pcs only uses %0A ( 0A == \n ).
The text was updated successfully, but these errors were encountered: