Re: IRIs and bidirectional formatting characters

On Wed, Aug 26, 2015 at 8:36 PM, Phillips, Addison <addison@lab126.com> wrote:
> I think that's a good start, although it doesn't clarify what the problem is. I understand why you don't want to pollute the standard with extravagant illustrations. If I18N WG published a suitable reference (a Note or the update to [1] which we need to do anyway at some point) would that help?

Yeah, I think that would be great. I'm not opposed to including
background material if it's light, though. See e.g.,
https://fetch.spec.whatwg.org/#background-reading for some examples.


> You have a suggestion for presentation in the browser address bar. Since that *is* a special environment, perhaps a bit more could be added to the suggestion. For example, you might recommend to make the display (as if) each of the path, query, and fragment start with FSI (U+2068) and then surround sequences made up of 'userinfo encode set' with PDI (U+2069) before and FSI (U+2068) after (bidi experts: do I have that right? Or would we want LSI?). Although the display would differ from the plain text presentation, it would not be confusable.

Currently the bit of text in rendering aimed at browsers suggests to
just display the "host" since that is used for security decisions and
we wouldn't want part of the host to end up in the path and vice
versa. Userinfo we definitely don't want to render as it's easily
confused with the host.



> I think the note is a little weak. Currently says: ...  Suggest: ...

Thank you, I have tweaked the note along the lines of your suggestion.


> Adding the Latin/Cyrillic 'a' is good, but maybe add a reference to UTR#36?

Done. I also added you to the acknowledgments as it seems that had not
happened yet!


Commit:

  https://github.com/whatwg/url/commit/e67f9dd7a1106d867862d3b5d9f044388f84909e


-- 
https://annevankesteren.nl/

Received on Thursday, 27 August 2015 10:10:18 UTC