Bj?rn W?rmedal <bjorn.warmedal at gmail.com> writes: >> How is this better than agreeing that link paths in gemtext are always >> completely percent-encoded? In that case, clients can percent-decode the >> path and display that. Authors could use a tool that 'fully' (as in, it >> also turns every "%" into "%25") percent-encodes a link for them. >> >> Counterintuitively, in this way I think mandating completely >> percent-encoded paths in gemtext link lines might actually result in >> easier linking for authors. > > This is -- as I read it -- what the spec requires now. I think that's > the best solution. The wording in the spec can (and maybe should) be > clarified, though. I don't think this is going to be acceptable for authors. It's unreasonable to ask authors to use a tool other than their favorite text editor to write gemtext. Why is it reasonable for the client to have to punycode the domain (an uncommon encoding for which not every common language has a library), but unreasonable for it to have to urlencode the path (a common encoding for which libraries are ubiquitous)? Why is it so hard to convince people to just do the right thing? ??? -- +-----------------------------------------------------------+ | Jason F. McBrayer jmcbray at carcosa.net | | A flower falls, even though we love it; and a weed grows, | | even though we do not love it. -- Dogen |
---
Previous in thread (12 of 34): 🗣️ Björn Wärmedal (bjorn.warmedal (a) gmail.com)
Next in thread (14 of 34): 🗣️ PJ vM (pjvm742 (a) disroot.org)