"Using Saved Location: foo"
bulb at ucw.cz
Thu Apr 27 19:03:06 BST 2006
On Thu, Apr 27, 2006 at 12:33:44 -0500, John Arbash Meinel wrote:
> Jan Hudec wrote:
> > On Thu, Apr 27, 2006 at 09:55:09 -0500, John Arbash Meinel wrote:
> >> Aaron Bentley wrote:
> >> So I think we should display unescaped "urls" as much as possible. (Yes
> >> they are not real urls, but they are close).
> >> Now, doing so violates the "support urls that aren't unicode" principle
> >> that we have been talking about. But I think the violation is worth it
> >> for the user.
> > Well, it mostly supports them. If the sequence makes sense in utf-8, then
> > decode it, else leave it as is. Also codes for things like %, ,, ;, ? and
> > & would have to remain undecoded, since they have special meaning in URLs.
> > It is pretty rare that non-utf8 sequence is valid utf-8 due to the redundancy
> > in utf8.
> Are there any others which we need to be careful of? I can just write a
> "safe_decode_url" which is just a helper for displaying URLs in a nice
> form to the user.
I can't quickly find the right place to look into right now, but I think the
list of characters to never decode would be:
Note, that those characters are not auto-encoded either, so if they are
encoded, they were specified as such (+ because it means ' ' in
query-strings, so it may be significant whether it is encoded).
Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060427/213358a0/attachment.pgp
More information about the bazaar