- From: Kevin R. Phillips <kevin@audiodesigns.com>
- Date: Wed, 22 Mar 2000 14:31:53 -0500 (EST)
- To: L.Wood@eim.surrey.ac.uk
- Cc: www-validator@w3.org, gerald@w3.org
Hi Lloyd, We did read the FAQ. In fact, we have filled 2 - 4" thick binders with accessibility guidelines, specifications, and the FAQs so familiarity with the basic '&' is not the issue. Here's the response I sent to Christian and David who were very helpful and brought up the same concern with '&' : ********* I thought that might be the case but unfortunately these links are for ordering the product assigned to that link. The link is created by the ecommerce software when it is entered into the database (and cannot be customized). We won't be able to change it to '&' or else the link won't function. Thanks for the quick response! Kevin *********************************************** >I thought the problem might have been with the '&' character in the >parameter strings. To be compatible, the actual link needs to contain >'&' instead of just '&': > >Good: <a href="http://www.test.com/script.asp?Parm1=ABC&Parm2=DEF"> > >Bad: <a href="http://www.test.com/script.asp?Parm1=ABC&Parm2=DEF"> >(Results in 'general entity "Parm2" not defined' etc.) ******************** At 10:17 AM 3/22/2000, Lloyd Wood wrote: >On Wed, 22 Mar 2000, Kevin Phillips wrote: > >> I've noticed that certain links created by shopping cart ecommerce >> software has a syntax that's not compatible according to the Validator. >> Here's the errors: >> >> Line 56, column 82: >> >> ... >> /www.upbeats.com/Merchant/merchant.mv?Screen=BASK&Store_Code=up1" onMo >> ... >> ^ >> >> Error: general entity "Store_Code" not defined and no default >> entity > > >You should be escaping and replacing & with & > >Read the FAQ. > >L. > ><L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>
Received on Wednesday, 22 March 2000 16:05:41 UTC