. . "1057686284"^^ . "Unicode and email"@en . "Many email clients now offer some support for Unicode. Some clients will automatically choose between a legacy encoding and Unicode depending on the mail's content, either automatically or when the user requests it. Technical requirements for sending of messages containing non-ASCII characters by email include \n* encoding of certain header fields (subject, sender's and recipient's names, sender's organization and reply-to name) and, optionally, body in a content-transfer encoding \n* encoding of non-ASCII characters in one of the Unicode transforms \n* negotiating the use of UTF-8 encoding in email addresses and reply codes (SMTPUTF8) \n* sending the information about the content-transfer encoding and the Unicode transform used so that the message can be correctly displayed by the recipient (see Mojibake). If the sender's or recipient's email address contains non-ASCII characters, sending of a message requires also encoding of these to a format that can be understood by mail servers."@en . . . . "5364"^^ . "2008884"^^ . . . . . "Many email clients now offer some support for Unicode. Some clients will automatically choose between a legacy encoding and Unicode depending on the mail's content, either automatically or when the user requests it. Technical requirements for sending of messages containing non-ASCII characters by email include If the sender's or recipient's email address contains non-ASCII characters, sending of a message requires also encoding of these to a format that can be understood by mail servers."@en . .