Re: [Gnu-arch-users] URL Encoding

[Yannick Gingras]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On March 20, 2004 04:30 pm, Jan Hudec wrote:
> Unfortunately it's a problem, because you can't tell, algorithmicaly,
> whether a certain URL is encoded (there are cases you know it isn't and
> cases where you don't know). So one must be chosen. Tla chooses
> unencoded form. It should be documented, but tla shouln't guess what it
> just got.

I'm never really good at parsing RFCs but I read in 2396 that

  "Because the percent "%" character always has the reserved purpose of
   being the escape indicator, it must be escaped as "%25" in order to
   be used as data within a URI."

Isn't it possible to guess by looking at what follows the "%" ?

I may be totally wrong (which is usually what happens when I read
RFCs) but it seems to be possible.

If I'm totally wrong, just a "--encoded" option for "tla register-archive" 
would have gave me an instant hint about the encoded representation.

Regards, 

- -- 
Yannick Gingras                       "Thinking is the hardest work there is"
Coder for OBB : One-man Blest Blonde                            -- Henry Ford
http://OpenBeatBox.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAXMJMZJ8/OobqizMRAuu2AJ41IDPJ8YUJfNkukNHaS663XVp6LgCg8Ldd
8At1qV5qsTXfiiJAM4DDtMk=
=eiNS
-----END PGP SIGNATURE-----