[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 53751] Whitespaces in URL's are not expanded to %20
From:       Philippe Rigault <prigault () pacbell ! net>
Date:       2003-11-09 22:25:12
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=53751     




------- Additional Comments From prigault@pacbell.net  2003-11-09 23:25 -------
I suggest helping the user by:
  1. Giving a visual clue in the location bar (background color --tricky--, warning \
icon, font ?) all cases where prettyURL is different from fully encoded URL and could \
cause problems (e.g with cut-and-paste into konsole).  2. Adding an action (and \
keyboard shortcut) to switch between prettyUTL and fully encoded name.

This way, having prettyURL as the default would be perfectly acceptable, since there \
would be a way around its limitations. An option for the default (prettyURL or fully \
encoded URL) may also be added.

Example: in the case of IRI-containing URL:
- The user sees http://www.domain.com/r�um�pdf AND a graphical clue that this is \
                not encoding-safe as plain text.
- The user wants to cut-and-paste the URL to an application (e.g wget). He knows \
                (graphical clue) that this would cause problem. 
- He then switches to fully encoded URL, then sees \
http://www.domain.com/r%C2%A9sum%C2%A9.pdf in the location bar, together with a \
                graphical clue that this is encoding safe.
- He can then cut-and-paste the correct URL into what he wants.

Does this make sense ?


[prev in list] [next in list] [prev in thread] [next in thread]