Hi James, James Tomasino writes: > On 5/18/20 1:02 AM, Sean Conner wrote: > decision that all your content is going to be in one language. If we > allow it to be set at the document level then we're starting to add > document header. Maybe in the source files held on the server, but this could also be specified on a per-directory or even per-user basis. But this is just server implementation detail, isn't it? The text/gemini response that's actually served doesn't accrue a header. A gopher analogy: none of the "gopher maps" served up for my gopherhole look anything like the source files from which they're generated. But that has nothing to do with RFC-1436. > It would be neat if there's a way. Anyone else see a good option that > doesn't introduce extensibility or complexity? It's just a parameter in the content type string, is it really introducing extensibility when servers are already free to add as many of these as they like (up to the character limit), and clients are free to ignore them? Tim -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 487 bytes Desc: not available URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200518/5ed6 8b0a/attachment.sig>
---
Previous in thread (42 of 67): 🗣️ James Tomasino (tomasino (a) lavabit.com)
Next in thread (44 of 67): 🗣️ defdefred (defdefred (a) protonmail.com)