First let me say that I have used previous versions with great success.
I've noticed several posts where you have referred people with "unmatched quote characters" errors to the w3c validator. There must be something more going on here. I have 115 of these errors on one site, yet the pages COMPLETELY pass W3C validation. I've spent a couple of hours trying to locate the culprit with no success. So, if W3C can't find it and I can't find it - What next?
Also, is there a way to disable case sensitivity for the user's search? Seems to me results for Rusty and rusty should both display as results regardless of the use of caps. If I can disable this for my audience, it would be prefered.
Thanks for your time.
I've noticed several posts where you have referred people with "unmatched quote characters" errors to the w3c validator. There must be something more going on here. I have 115 of these errors on one site, yet the pages COMPLETELY pass W3C validation. I've spent a couple of hours trying to locate the culprit with no success. So, if W3C can't find it and I can't find it - What next?
Also, is there a way to disable case sensitivity for the user's search? Seems to me results for Rusty and rusty should both display as results regardless of the use of caps. If I can disable this for my audience, it would be prefered.
Thanks for your time.
Comment