Timothy Gu

I also found Microsoft's [naming conventions](https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/naming-conventions-for-computer-domain-site-ou#netbios-computer-names) for NetBIOS computer names. Unfortunately it doesn't describe exactly whether spaces are allowed (it's not an alphanumeric character which is explicitly allowed, but also...

Interestingly, Chrome actually doesn't treat `file` URLs differently from `http`/`https`. That is, it allows _both_ percent-encoding _and_ IDNs in URLs: ```js new URL('file://félicit ations.fr/test.txt').href // ⇒ file://xn--flicit%20ations-bnb.fr/test.txt new URL('https://exam ple.com').href...

A few options here: 1. Concede that setters may make URLs non-roundtrippable, and be okay with that. 2. In a setter, if the particular component is completely removed, check if...

I think I prefer 2 over 5. With 2, users have more options: if they want to keep the space and the delimiter, then they can explicitly opt into it...

@karwa The ability to percent-encode unusual characters in CBAB paths would be the ideal case. Sadly, I doubt that will be web-compatible. In fact, I think it'll be difficult just...

@alwinb I think we are using different definitions of "valid" here. When I say "setters will keep the URL valid" I don't mean "valid URL string" as defined in the...

@karwa Escaping `\` in non-special paths sounds like a reasonable idea, but I'm not sure about the web compatibility. Browsers are consistent in not escaping `\`, even though RFC 3986...

@achristensen07 Oh interesting! Didn't realize Safari already fixed this in some way. Sounds like we have alignment on 2 then.

@rmisev Indeed! As evident in UTS 46, the _CheckHyphens_ boolean was first introduced to allow YouTube labels of form "r3---sn-apo3qvuoxuxbt-j5pe". (Previously the boolean was effectively always "true".) But I suppose...

Quick WIP with Inkscape:  Would something like this work?