…rt binary source text MUST support binary source text encoded using the UTF-8 [ RFC3629 ] character encoding scheme. Other character encoding schemes MAY be supported. Use of UTF-8 to encode binary source text is encouraged but not required. 4.1 . Charset Parameter The charset pa…

…3536 ] for internationalization terminology) for vCard is UTF-8 as defined in [ RFC3629 ]. There is no way to override this. It is invalid to specify a value other than "UTF-8" in the "charset" MIME parameter (see Section 10.1 ). 3.2 . Line Delimiting and Folding Individual lines…

…ch lines MUST NOT begin with "SSH-", and SHOULD be encoded in ISO-10646 UTF-8 [ RFC3629 ] (language is not specified). Clients MUST be able to process such lines. Such lines MAY be silently ignored, or MAY be displayed to the client user. If they are displayed, control character …

…9 ] using the POP3 extension mechanism [ RFC2449 ] to permit un-encoded UTF-8 [ RFC3629 ] in headers, as described in "Internationalized Email Headers" [ RFC5335 ]. It also adds a mechanism to support login names and passwords outside the ASCII character set, and a mechanism to s…

…dly speaking, there are types for textual data (which is interpreted as UTF-8 [ RFC3629 ] text), binary data (whose interpretation is left up to the application), and control frames (which are not intended to carry data for the application but instead for protocol-level signaling…

…dly speaking, there are types for textual data (which is interpreted as UTF-8 [ RFC3629 text), binary data (whose interpretation is left up to the application), and control frames (which are not intended to carry data for the application but instead for protocol-level signaling, …

…dly speaking, there are types for textual data (which is interpreted as UTF-8 [ RFC3629 text), binary data (whose interpretation is left up to the application), and control frames (which are not intended to carry data for the application but instead for protocol-level signaling, …

…adly speaking, there are types for textual data, which is interpreted as UTF-8 [RFC3629] text, binary data (whose interpretation is left up to the application), and control frames, which are not intended to carry data for the application, but instead for protocol-level signaling,…

…her a locale-specific encoding such as ISO-8859-1 ([ ISO-8859-1 ]), or UTF-8 ([ RFC3629 ]). For backwards compatibility reasons, this specification continues to leave the default encoding undefined, as long as it is compatible with US-ASCII (mapping any US-ASCII character to a si…

…n a URI reference, a template processor MUST first encode the string as UTF-8 [ RFC3629 ] and then pct-encode any octets that are not allowed in a URI reference. Gregorio, et al. Standards Track [Page 12] RFC 6570 URI Template March 2012 . Syntax A URI Template is a string of pri…

…rt binary source text MUST support binary source text encoded using the UTF-8 [ RFC3629 ] character encoding scheme. Other character encoding schemes MAY be supported. Use of UTF-8 to encode binary source text is encouraged but not required. 4.1 . Charset Parameter The charset pa…

…dly speaking, there are types for textual data (which is interpreted as UTF-8 [ RFC3629 text), binary data (whose interpretation is left up to the application), and control frames (which are not intended to carry data for the application but instead for protocol-level signaling, …

…9 ] using the POP3 extension mechanism [ RFC2449 ] to permit un-encoded UTF-8 [ RFC3629 ] in headers, as described in "Internationalized Email Headers" [ RFC5335 ]. It also adds a mechanism to support login names and passwords outside the ASCII character set, and a mechanism to s…

…3536 ] for internationalization terminology) for vCard is UTF-8 as defined in [ RFC3629 ]. There is no way to override this. It is invalid to specify a value other than "UTF-8" in the "charset" MIME parameter (see Section 10.1 ). 3.2 . Line Delimiting and Folding Individual lines…

…port binary source text MUST support binary source text encoded using the UTF-8 RFC3629 character encoding scheme. Module goal sources MUST be encoded as UTF-8; all other encodings will fail. Source goal sources SHOULD be encoded as UTF-8; other character encoding schemes MAY be …