Timeline for Enqueue Google Web Fonts Without Messing Up Symbols In URL
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 21, 2013 at 18:55 | vote | accept | its_me | ||
| Jan 1, 2013 at 5:04 | history | bounty ended | its_me | ||
| Dec 30, 2012 at 21:47 | comment | added | Andrew Nacin | I spoke about both in my answer, and comment. You were worried about both in your original question. | |
| Dec 30, 2012 at 8:47 | comment | added | webaware | @AndrewNacin: just a nitput, but: that URL to blooberry.com is actually about URL-encoding characters, not HTML-encoding characters. The issue you are addressing is the latter, not the former. | |
| Dec 30, 2012 at 8:16 | comment | added | Andrew Nacin |
Correct. I edited my answer slightly to make it a bit more clear. In this case, the ampersand is an escaped HTML entity, not URL encoded. It should not be encoded (which would be %38) because it is being used in its special URL role. URL encoding a reserved or unsafe character like |, :, or spaces are separate, and also encouraged.
|
|
| Dec 30, 2012 at 8:14 | history | edited | Andrew Nacin | CC BY-SA 3.0 |
added 12 characters in body
|
| Dec 30, 2012 at 7:58 | comment | added | its_me |
So, you are saying... when you have a properly encoded URL in an HTML src or href attribute (i.e. http://fonts.googleapis.com/css?family=Ubuntu+Condensed&subset=latin,latin-ext), the way the browser treats it is equivalent to the user entering http://fonts.googleapis.com/css?family=Ubuntu+Condensed&subset=latin,latin-ext (i.e. with the actual & and not the HTML entity) in the address bar. Is that correct? If so, thanks for the clear explanation. :)
|
|
| Dec 30, 2012 at 7:23 | comment | added | webaware | A very fine explanation, thanks for taking the time Andrew! | |
| Dec 30, 2012 at 7:17 | history | answered | Andrew Nacin | CC BY-SA 3.0 |