Talk:Percent-encoding

message: The article doesn't mention it, so I assume both upper and lower-case hex digits are valid? So %FF == %ff == %fF == %Ff  — Preceding unsigned comment added by 75.161.222.199 (talk) 19:21, 7 August 2020 (UTC)
thread_title:  Upper- and lower-case hex digits 

message: I note that backslash, "\", 0x5C, is now a reserved character for at least some browsers -- specifically Firefox. It will automatically be changed in the path to forward slash, both on the URI line and when processing AJAX calls, if not escaped as %5C. Please add that the list of reserved characters. Hansonrstolaf (talk)  —Preceding undated comment added 16:45, 29 August 2016 (UTC)
thread_title:  Missing reserved character 

message: The corresponding german article about url encoding mentions the percent sign as a reserved character as well. But here I don't see the percent sign in the list. If one reads RFC 3986, the percent sign is indeed not reserved. So its more a problem of the german article.
Janburse (talk) 15:33, 24 July 2011 (UTC)
thread_title:  Percent Sign 

message: I think, in the character data section, there should be a more thorough explanation of the significance of UTF-8 percent encoding; for instance there is no examples of "higher" characters; how do you encode say a diacritic or a kenji, etc.? At this point, I don't know, and the article as written will not give me that knowledge either... A.R.  — Preceding unsigned comment added by 205.151.118.180 (talk) 20:34, 1 December 2011 (UTC)
thread_title:  Coverage of "extended" characters needed please 

message: The text in the article repeats an ambiguous statement from RFC3986:
"Because the percent ("%") character serves as the indicator for percent-encoded octets, it must be percent-encoded as "%25" for that octet to be used as data within a URI."
The grammar of the sentence makes it unclear whether "that octet" refers back to "%25", or to 
an octet in "percent-encoded octets", or to "it" or furthest back of all to '("%")'.
I'm pretty certain that the sentence means:
"For a percent ("%") character to appear as stand-alone data (octet value 25) in a URI, it must avoid being interpreted as the first character of a percent encoding. Thus a stand-alone "%" must be encoded, as "%25".
If someone has a reference which backs this up, perhaps we could use this clearer sentence, or some better one?  Gwideman (talk) 10:23, 9 February 2012 (UTC)
thread_title:  Percent encoding ambiguity 

message: It's unambiguous in the RFC, because the word "data" is specifically defined there, and octet means byte. But, it's hard to understand on WP, so I'm changing it.
martnik (talk) 11:05, 5 September 2015 (UTC)
thread_title:  RFC 3986 

message: It encodes bytes. A code unit like “%C2” represents a byte, not a character. Revert (or do not make) silly edits like [][], please. Incnis Mrsi (talk) 16:10, 27 May 2013 (UTC)
thread_title:  It is not a character encoding 

message: The most prominent implementation is the set of built-in JavaScript (ECMAScript) functions: encodeURI, encodeURIComponent, decodeURI, decodeURIComponent.  These deserve a more prominent mention in the implementation section.  Currently they are only mentioned in passing in the Non-standard implementations section.  — Preceding unsigned comment added by Erikn2 (talk • contribs) 01:49, 13 September 2016 (UTC)
thread_title:  Built-in JavaScript functions: encodeURI, etc. 

message: shouldn't the space character be in the list titled: 'RFC 3986 section 2.2 Reserved Characters (January 2005)'? 82.71.43.56 (talk) 12:17, 14 February 2023 (UTC)
thread_title:  space not shown in reserved character list 

message: :The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.
The result of the move request was: not moved. (non-admin closure) Mattdaviesfsic (talk) 23:04, 28 December 2023 (UTC)
replies: text: Percent-encoding →  – After going back and forth with , I see what they mean by consensus not established with the previous move request here but also it seems this was done as an uncontroversial page move through WP:RM? 
I do think WP:COMMONNAME applies in this case.
 – The Grid (talk)  15:43, 21 December 2023 (UTC)
thread_title:  Requested move 21 December 2023