Timeline for Allow URL with diacritics
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 16, 2015 at 5:36 | comment | added | Nathan Tuggy | @JeremyBanks: Oh how I wish that were true. | |
| May 16, 2015 at 1:30 | comment | added | Jeremy | UTF-8 is the one true encoding. Any claim of the existence of of other encodings is a lie. | |
| May 15, 2015 at 23:38 | comment | added | Rubén | "A lone URL doesn't provide enough context..." Then add something else to the SE platform so its users could add the required context :) | |
| May 15, 2015 at 21:47 | history | edited | Martijn Pieters | CC BY-SA 3.0 |
added 100 characters in body
|
| May 15, 2015 at 21:28 | comment | added | Rubén | A feature request could be a wish, a hope, a desire... Don't you think? | |
| May 15, 2015 at 21:24 | comment | added | Martijn Pieters | @Rubén: the problem there is that not all sites use UTF-8 to encode non-ASCII codepoints. | |
| May 15, 2015 at 21:23 | history | edited | Martijn Pieters | CC BY-SA 3.0 |
added 401 characters in body
|
| May 15, 2015 at 21:21 | comment | added | Rubén | Idea from the answer: where markdown is allowed, the custom URL could be displayed as follow https://plus.google.com/+RubénRivera. Use custom URL between [ and ] and encoded / valid URL between ( and ). | |
| May 15, 2015 at 21:18 | comment | added | Rubén | Using your words, the feature-request is that SE profile be more tolerant so the custom URL links could be "human readable". | |
| May 15, 2015 at 20:48 | history | answered | Martijn Pieters | CC BY-SA 3.0 |