From: Jesper Harder <harder@myrealbox.com>
Subject: Re: gnus-url-mailto broken on foo+bar@somewhere.invalid
Date: Wed, 27 Aug 2003 16:53:11 +0200 [thread overview]
Message-ID: <m3ptirxico.fsf@defun.localdomain> (raw)
In-Reply-To: <v91xv75hjv.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>> Jesper Harder <harder@myrealbox.com> writes:
>
>>> I'm wondering if the "+" -> " " substitution is bogus not just for
>>> mailto: but for all URI types. I can't find anything in RFC 2396
>>> stating that this substitution should be performed.
>
> For mailto it's not useful, AFAICS. See also my reply to Karl
>
>>> I guess that code should just be removed from
>>> `gnus-url-unhex-string'.
>
> This would break info links like <info://gnus/Starting+Up>.
Yes, but that notation is our own invention, I think.
Instead of introducing yet another syntax for info URL's, wouldn't it
be nicer to support the two (incompatible, *sigh* [1]) forms that are
already used elsewhere -- from url(7)
info - Info page documentation
info:virtual-filename
info:virtual-filename#nodename
info:(virtual-filename)
info:(virtual-filename)nodename
This scheme refers to online info reference pages (generated
from texinfo files), a documentation format used by programs
such as the GNU tools. This URI scheme is unique to Unix-like
systems (such as Linux) and is not currently registered by the
IETF. As of this writing, GNOME and KDE differ in their URI
syntax and do not accept the other's syntax. The first two
formats are the GNOME format; in nodenames all spaces are
written as underscores. The second two formats are the KDE
format; spaces in nodenames must be written as spaces, even
though this is forbidden by the URI standards. It's hoped that
in the future most tools will understand all of these formats
and will always accept underscores for spaces in nodenames. In
both GNOME and KDE, if the form without the nodename is used
the nodename is assumed to be "Top". Examples of the GNOME
format are <info:gcc> and <info:gcc#G++_and_GCC>. Examples of
the KDE format are <info:(gcc)> and <info:(gcc)G++ and GCC>.
[1] Someone should write an infomational RFC about the info: scheme.
next prev parent reply other threads:[~2003-08-27 14:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 16:52 Reiner Steib
2003-08-26 18:05 ` Karl Pflästerer
2003-08-27 13:22 ` Reiner Steib
2003-08-27 14:43 ` Karl Pflästerer
2003-08-26 21:37 ` Jesper Harder
2003-08-27 11:42 ` Benjamin Riefenstahl
2003-08-27 13:57 ` Reiner Steib
2003-08-27 14:53 ` Jesper Harder [this message]
2003-08-27 17:37 ` Kai Großjohann
2003-08-27 18:33 ` Jesper Harder
2003-09-04 1:59 ` Jesper Harder
2003-09-04 13:15 ` Reiner Steib
2003-09-04 15:32 ` Jesper Harder
2003-09-04 16:10 ` Simon Josefsson
2003-09-04 16:53 ` Reloading info files (was: gnus-url-mailto broken on foo+bar@somewhere.invalid) Reiner Steib
2003-09-05 21:58 ` Reloading info files Kevin Ryde
2003-09-04 17:43 ` gnus-url-mailto broken on foo+bar@somewhere.invalid Jesper Harder
2003-09-04 22:42 ` Simon Josefsson
2003-09-04 21:46 ` Frank Schmitt
2003-09-05 1:34 ` Jesper Harder
2003-09-05 7:33 ` Frank Schmitt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ptirxico.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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 NNTP newsgroup(s).