- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Nov 2015 13:52:40 +0000
- To: public-secondscreen@w3.org
@tkanai OK, now I see what you meant, many thanks for the concrete examples! I pointed out the issue to @r12a who created an issue for the Internationalization Working Group, which should eventually get back to us: http://www.w3.org/International/track/issues/506 The two examples are different. My understanding is that things work "as planned" for the first set of characters, meaning that they are indeed rendered slightly differently depending on the underlying language context. The backslash character is definitely a weird example. I suppose that there is some sort of legacy involved, as one would expect the character to be rendered as a backslash no matter what. FWIW, on my computer, MS Edge renders it properly as a backslash character in all three cases, while Chrome renders it as a backslash for the default and Japanese language and as a Won sign for the Korean language. Anyway, these examples provide good additional rationale to recommend that the receiving browsing context uses the locale of the requesting side when possible, as discussed during the F2F. -- GitHub Notif of comment by tidoust See https://github.com/w3c/presentation-api/issues/218#issuecomment-155425091
Received on Tuesday, 10 November 2015 13:52:42 UTC