Re: [presentation-api] list of displays: should it address display name, language, etc.?

For background, there are a couple of reasonable ways a friendly 
display name can be passed through mDNS:
 
1. Via the instance name in the DNS SRV record advertised by a service
 instance.  The spec [1] says that this must be up to 63 Net-Unicode 
characters, but doesn't have any place to pass locale information that
 might be used to customize the display of the name.

2. Via a DNS-TXT record [2].  The TXT record is a list of key=value 
strings up to 255 bytes in length.  However it is completely up to the
 implementation how to populate this record.  An implementation could 
use one string to pass the name (as unicode) and another string to 
pass the locale.

What I propose is implementation guidance along the lines of @tidoust:

* That the receiving user agent advertise the locale (language, 
direction) to be used to interpret the display name.
* That the controlling user agent take that into consideration when 
rendering that name, when available.

[1] https://tools.ietf.org/html/rfc6763#section-4.1
[2] https://tools.ietf.org/html/rfc6763#section-6

-- 
GitHub Notification of comment by mfoltzgoogle
Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/315#issuecomment-240864179
 using your GitHub account

Received on Thursday, 18 August 2016 21:33:54 UTC