Norman Walsh
Norman Walsh
I thought I checked for path separator but I guess I missed it. I'm really sympathetic to trying to simplify the set of characters but it's tricky because the URI...
The CG agreed to close this PR without further action at [meeting 089](https://qt4cg.org/meeting/minutes/2024/09-10.html)
Yes. The first issue is an implementation bug that I've now fixed. I'll push new tests in a moment. Also, I updated the PR for #1320 to include this fix...
1. That's a typo in the spec; I probably transformed the output to pretty print it or something and accidentally lost the space. You can see the space in the...
I think I fixed both of those issues in an update to #1440 this morning. Thank you!
I'm using the same encoding function for `query-parameters` that we describe for `path-segments`. I expect that's what we should do for the same reasons outlined under `path-segments`. If you agree,...
Yes. I spoke too soon. The rules for query parts have to be slightly different because of `=` and `&`. Not encoding `/` and `?` seems reasonable too.
I think the note about not using the compromise for query parameters is misguided. And we need special rules for fragment identifiers as well. Bah, say it with me, humbug!
I haven't updated the tests. That's on my list for today. I. meant to have the PR ready to go but...life, ya know?
Nice catch. I think the trick here is that the path segments only need to be encoded if the URI is hierarchical. I think something like the following is the...