Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: url fontification fails with `{'
Date: Fri, 10 May 2002 17:50:04 +0200	[thread overview]
Message-ID: <m3pu04kno3.fsf@defun.localdomain> (raw)
In-Reply-To: <ruolmayz23a.fsf@billwlx.wolfram.com> (billw@wolfram.com's message of "Sun, 5 May 2002 22:02:07 +0000 (UTC)")

billw@wolfram.com (Bill White) writes:

> In my gnus, url fontification stops at the `=' character.  Oort Gnus
>
> http://canada.com/news/story.asp?id={7157C231-B4AF-441E-993F-6D902B45ED6B}

The problem is that { and } have to be encoded in URLs.  RFC 1738 says:

   Other characters are unsafe because gateways and other transport
   agents are known to sometimes modify such characters. These
   characters are "{", "}", "|", "\", "^", "~", "[", "]", and "`".

   All unsafe characters must always be encoded within a URL.

If you want to allow them, you can add them to `gnus-button-url-regexp'.

-- 
Cheers,
Jesper Harder




      parent reply	other threads:[~2002-05-10 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-05 22:01 Bill White
2002-05-05 22:16 ` Bill White
2002-05-06 10:05 ` Kai Großjohann
2002-05-10 15:50 ` Jesper Harder [this message]

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=m3pu04kno3.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /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).