19524 2012-10-13 15:15:04 +0000 Validator.w3.org flagging required characters within URL's 2012-10-23 16:05:17 +0000 1 1 1 Unclassified Validator check HEAD PC Windows NT RESOLVED INVALID P2 normal --- 1 paulandrewanderson dave.null www-validator-cvs oldest_to_newest 76213 0 paulandrewanderson 2012-10-13 15:15:04 +0000 There are many characters within URLs (& = etc.) that cannot altered, encoded or eliminated. It would be a staggering effort to encode every ampersand within every URL on the web. Line 128, Column 110: general entity "m" not defined and no default entity …/B0082PM7QA/ref=tmm_kin_title_0?ie=UTF8&m=AG56TWVU5XWC2" title="Amazon eBooks"> ✉ This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. Line 128, Column 111: reference not terminated by REFC delimiter …/B0082PM7QA/ref=tmm_kin_title_0?ie=UTF8&m=AG56TWVU5XWC2" title="Amazon eBooks"> ✉ If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. Line 128, Column 111: reference to external entity in attribute value …/B0082PM7QA/ref=tmm_kin_title_0?ie=UTF8&m=AG56TWVU5XWC2" title="Amazon eBooks"> ✉ This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'. Line 128, Column 111: reference to entity "m" for which no system identifier could be generated …/B0082PM7QA/ref=tmm_kin_title_0?ie=UTF8&m=AG56TWVU5XWC2" title="Amazon eBooks"> ✉ This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. Line 128, Column 109: entity was defined here …/B0082PM7QA/ref=tmm_kin_title_0?ie=UTF8&m=AG56TWVU5XWC2" title="Amazon eBooks"> 76965 1 ville.skytta 2012-10-23 16:05:17 +0000 Ampersands can and need to be encoded as & in URLs embedded in valid HTML documents, no matter how much work that might be.