ISSUE-106: When the character cannot be encoded into the target encoding

When the character cannot be encoded into the target encoding

State:
CLOSED
Product:
html
Raised by:
Addison Phillips
Opened on:
2011-07-22
Description:
Please add comments to bugzilla:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=16971

2.6.3 Resolving URLs
http://www.w3.org/TR/html5/urls.html#resolving-urls

Deals with processing URLs. The steps here result in defining the "character encoding" of the URL, which is applies to the query portion of the URL. I put character encoding in quotes, because what it really is the character encoding of the document or script containing the URL as a string. Step 8.2 contains an implicit encoding conversion (to the document character encoding). A health warning should be supplied about what to do when the character cannot be encoded into the target encoding.
Related Actions Items:
No related actions
Related emails:
  1. Review of tracker issues for best practices (Part IV) (from addison@lab126.com on 2015-03-31)
  2. [Bug 16971] i18n-ISSUE-106: When the character cannot be encoded into the target encoding (from bugzilla@jessica.w3.org on 2014-02-28)
  3. Re: [I18N-ACTION-150] Review of HTML open issues (from ishida@w3.org on 2014-02-21)
  4. [I18N-ACTION-150] Review of HTML open issues (from addison@lab126.com on 2014-02-18)
  5. RE: ISSUE-106: I18N-ISSUE-246: Storage Size (from ysavourel@enlaso.com on 2013-04-07)
  6. Re: ISSUE-106: I18N-ISSUE-246: Storage Size (from fsasaki@w3.org on 2013-04-07)
  7. RE: ISSUE-106: I18N-ISSUE-246: Storage Size (from ysavourel@enlaso.com on 2013-04-06)
  8. Re: ISSUE-106: I18N-ISSUE-246: Storage Size (from asmusf@ix.netcom.com on 2013-04-06)
  9. RE: ISSUE-106: I18N-ISSUE-246: Storage Size (from ysavourel@enlaso.com on 2013-04-06)
  10. RE: ISSUE-106: I18N-ISSUE-246: Storage Size (from pablo.nieto@linguaserve.com on 2013-04-03)
  11. ISSUE-106: I18N-ISSUE-246: Storage Size (from ysavourel@enlaso.com on 2013-04-03)
  12. AW: [ISSUE-106][I18N-ISSUE-246] Storage Size - unit (from stephan.walter@cocomore.com on 2013-04-02)
  13. RE: [ISSUE-106][I18N-ISSUE-246] Storage Size - unit (from pablo.nieto@linguaserve.com on 2013-04-02)
  14. [ISSUE-106][I18N-ISSUE-246] Storage Size - unit (from ysavourel@enlaso.com on 2013-04-01)
  15. [Bug 16971] i18n-ISSUE-106: When the character cannot be encoded into the target encoding (from bugzilla@jessica.w3.org on 2012-05-10)
  16. [Bug 16971] i18n-ISSUE-106: When the character cannot be encoded into the target encoding (from bugzilla@jessica.w3.org on 2012-05-08)
  17. [Bug 16971] i18n-ISSUE-106: When the character cannot be encoded into the target encoding (from bugzilla@jessica.w3.org on 2012-05-08)
  18. Re: HTML5 Comment disposition (from w3@norbertlindenberg.com on 2012-03-20)
  19. [minutes] i18n telecon 2012-03-07 (from ishida@w3.org on 2012-03-12)
  20. I18N-ISSUE-106: When the character cannot be encoded into the target encoding [HTML5-prep] (from sysbot+tracker@w3.org on 2011-07-22)

Related notes:

[aphillip]: When the character cannot be encoded into the target encoding

7 Mar 2012, 16:39:16

bug 16971

Addison Phillips, 7 May 2012, 17:44:39

The comment is no longer relevant, since the text here:

http://www.w3.org/html/wg/drafts/html/CR/infrastructure.html#resolving-urls

... has changed significantly and I don't see a reason to add health warnings in the new text.

Addison Phillips, 28 Feb 2014, 21:36:49

Display change log ATOM feed


Addison Phillips <addison@amazon.com>, Chair, Richard Ishida <ishida@w3.org>, Fuqiao Xue <xfq@w3.org>, Atsushi Shimono <atsushi@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $