W3C home > Mailing lists > Public > www-validator-cvs@w3.org > May 2009

[Bug 6915] Encoded unicode chars errors as "broken URI fragments"

From: <bugzilla@wiggum.w3.org>
Date: Mon, 18 May 2009 20:58:46 +0000
To: www-validator-cvs@w3.org
Message-Id: <E1M69v4-0001E9-SP@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6915


Ville Skyttä <ville.skytta@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|4.4                         |4.5




--- Comment #1 from Ville Skyttä <ville.skytta@iki.fi>  2009-05-18 20:58:46 ---
The set of allowed characters depends on the type of the document where the
target of the fragment identifier (not the link) is, and what the target is. 
For example, if it's an "id" attribute, the set of characters is quite
restricted and for example for <a name="..."> there are differences between
HTML 4.x and XHTML 1.x what the allowed characters are:
http://www.w3.org/TR/xhtml1/#C_8

No working, real URL to check was provided so it isn't possible to dig deeper
into your particular case, but for compatibility I would suggest sticking with
the allowable characters for ID and NAME types from HTML 4:
http://www.w3.org/TR/html4/types.html#type-name

It is quite possible that the link checker indeed has issues with some things
that should be allowed though, so I'm leaving this bug open for now.  A working
link to real, public document with which such issues can be reproduced would be
nice though.

(Version 4.5 is in the drop down menu now, thanks for noting its absence.)


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 18 May 2009 20:58:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:02:35 UTC