Re: [openscreenprotocol] [SSDP] Ensure that advertised friendly names are i18n capable

I did some tracking of this.  The short answer for SSDP is "not simply."

SSDP adopts the RFC 2616 message format from HTTP 1.0 [1] which *technically* allows ISO-8859-1 in header values (although only ASCII is guaranteed to work across implementations.)  Non-ASCII values (i.e., UTF-8) should use MIME encoding [2], basically quoted-printable or base64.

[1] https://www.ietf.org/rfc/rfc2616
[2] https://www.ietf.org/rfc/rfc2047

base64 is simpler and universally supported.  So if we want to include the friendly name in the SSDP response, it should be base64 encoded.










 



-- 
GitHub Notification of comment by mfoltzgoogle
Please view or discuss this issue at https://github.com/webscreens/openscreenprotocol/issues/22#issuecomment-334882640 using your GitHub account

Received on Friday, 6 October 2017 22:13:21 UTC