From kfm-devel  Mon Jun 11 20:42:58 2001
From: Yves Arrouye <yves () realnames ! com>
Date: Mon, 11 Jun 2001 20:42:58 +0000
To: kfm-devel
Subject: RE: A more flexible solution for internet keywords
X-MARC-Message: https://marc.info/?l=kfm-devel&m=99229499132229

> For now I'll implement the compatibility mode I suggested in=20
> my last mail
> (query definitions with only one single \1 get replaced with \0 =
before
> substitution) and submit another patch. It should work=20
> without problems
> with both, old and new queries, since the case where only the=20
> first query
> argument should be used, is not vere useful.

Please test it by doing something like this: select Google as your =
fallback
search engine, and then put this in Konqueror's address bar: "un =
=E9t=E9 tr=E8s
chaud". After you get to Goggle, the query should not be changed. If it
contains weird symbols, then \2 (charset) broke. There's a chance it =
won't
since you may be modifying the logic only for web shortcuts. Still, it =
makes
the two things work differently which is bad.

About the "$" sign. Since RFC 2396 marks it as reserved, you're right, =
it
could be a dangerous choice. But you could still keep the "\" as a =
lead, and
have a second char that is used for the new meaning, as in \{1} for =
example
(keeping all the chars from the unwise set of RFC 2396).=20

YA