This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://www.whatwg.org/specs/web-apps/current-work/#overlong-form The spec talks about "overlong form". However, "non-shortest form" is more established Unicode jargon: http://www.google.com/search?q=UTF-8+overlong+form http://www.google.com/search?q=UTF-8+non-shortest+form It would make sense to use the term "non-shortest form" in the spec.
# [11:45] <zcorpan> "utf-8 overlong" - 12600 results. "utf-8 "overlong"" - 80900 results # [11:46] <zcorpan> "utf-8 non-shortest" - 25000. "utf-8 "non-shortest"" - 5690 # [11:46] <zcorpan> conclusion: ??? # [11:47] <Philip`> Google's result counts are extremely rough approximations and should not be taken seriously?
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: "overlong" is the term that the UTF-8 spec (RFC3629) uses. Also, "non-shortest form" is really stilted and reads poorly.
mass-move component to LC1