我是否需要将长度超过 72 个字符的电子邮件换行?
有时我会看到代码包装电子邮件以确保单行长度不超过 72 个字符。真的有这个必要吗?这到底是怎么回事?
Occasionally I've seen code wrapping email messages to make sure a single line is no more than 72 characters long. Is there really need for this and what is this all about?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
RFC 2822 包含有关行长度的文本,这可能来自:
RFC 2822 contains this text about line lengths, which is where this likely comes from:
为了扩展 Joe 的响应,72 个字符的限制基本上允许正文被引用,因此它为添加到行中的附加字符提供了空间,例如,
因此给出额外的几个字符允许在 80 上保留段落格式-字符终端,至少两个级别,并且可能更多,具体取决于引号字符的添加/使用方式。
To expand on Joe's response, the 72-char limit basically allows for bodies to then be quoted, so it gives room for the additional chars added to a line, e.g.,
So giving an extra few chars allows the parapgraph formatting to be retained on 80-character terminals, for at least two levels, and potentially more depending on how the quote characters are added/used.