From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Is there something like `file-name-concat', but for urls?
Date: Wed, 26 Jul 2023 06:34:07 +0200 [thread overview]
Message-ID: <ZMCiP6pvpFLPOcn2@tuxteam.de> (raw)
In-Reply-To: <87v8e7yh7b.fsf@dataswamp.org>
[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]
On Tue, Jul 25, 2023 at 08:33:12PM +0200, Emanuel Berg wrote:
> tomas wrote:
>
> >> BTW thanks for letting me realize I should modernize that,
> >> it is so old https isn't even included [...]
> >
> > Plus URL encoding. Plus deciding in fringe cases whether
> > encoding is in order or not [...]
>
> How the URL can look is defined by a grammar
Have you read RFC 3986?
> this is
> Computer Science theory of Compiler Design. Because, if we get
> the standard definition, expressed as a grammar, we can not
> only use the correct terminology from there, we can also
> verify if the result URL is valid or not.
No. This is, alas, Computer Tinkering Practice, where RFCs try
as well as they can, to codify existing practice. Some try to
even set up a grammar, often in some EBNF dialect -- but practice
and existing implementations often emerge long before that
grammar was written, shaped by negligence, inexperience, not
seldomly by economical or political interests.
When people, at last, meet at a table to hammer out an RFC,
often they are sent in by companies trying to defend the stakes
they have rammed in the ground.
Once the RFC is out, if, say, Microsoft or Google is doing
something not according to it, you can shout at them until you
are blue in the face. It won't help, anyway.
Sometimes, standards bodies just give up and declare something
as a "living standard", which means "whatever we come up with
this week", as happens to HTML5.
This is, alas, reality, where our "industry" is dominated by
a handful of actors.
Enjoy, nevertheless.
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-07-26 4:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 5:14 Is there something like `file-name-concat', but for urls? Marcin Borkowski
2023-07-24 11:58 ` Eli Zaretskii
2023-07-24 15:26 ` Marcin Borkowski
2023-07-25 16:21 ` Emanuel Berg
2023-07-25 17:24 ` tomas
2023-07-25 18:33 ` Emanuel Berg
2023-07-26 4:34 ` tomas [this message]
2023-07-26 12:13 ` Emanuel Berg
2023-07-25 19:00 ` Marcin Borkowski
2023-07-25 19:07 ` Emanuel Berg
2023-07-25 19:38 ` Emanuel Berg
2023-07-25 17:35 ` Yuri Khan
2023-07-25 18:23 ` Emanuel Berg
2023-07-25 20:01 ` Yuri Khan
2023-07-25 21:51 ` Emanuel Berg
2023-07-26 12:44 ` Emanuel Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZMCiP6pvpFLPOcn2@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).