https://bugzilla.wikimedia.org/show_bug.cgi?id=68372

--- Comment #17 from Tisza GergÅ‘ <[email protected]> ---
Could, but should not, IMO. I'll quote the relevant part from the mail linked
in comment 8:

1. Just put the file name as-is (with spaces replaced by underscores) in
   the URL fragment part.
   Pro: readable file names in URLs, easy to generate.
   Con: technically not a valid URI. [2] (It would be a valid IRI,
        probably, but browser support for that is not so great, so non-ASCII
        bytes might get encoded in unexpected ways.) Creates nasty usability 
        and security issues (injection vulnerabilities, RTL characters, 
        characters which break autolinking). Would make it very hard to
        introduce more complex URL formats later, as file names can contain 
        pretty much any character.

2. Use percent encoding (with underscores for spaces).
   Pro: this is the standard way of encoding fragments. [2][3] Always
        results in a valid URI. Readable file names in Firefox. Easy to 
        generate on-wiki (e.g. with {{urlencode}})
   Con: Non-Latin filenames look horrible in any browser that's not Firefox.


[2] http://tools.ietf.org/html/rfc3986#section-3.5
[3] https://tools.ietf.org/html/rfc3987#section-3.1

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to