Note:The Free and Commercial hyperlinks above will take you directly to DWfaq.com's store where you can read about my extensions. The Cartweaver links below will take you to their website. If you'd rather stay on this site, be sure to read my message where you'll find links to brief descriptions for your convenience.
Note: I only wrote the extensions for Cartweaver 3 for Application Dynamics Inc., not the application itself.
Note: The links below are only the most recent titles that I've been involved with. Follow the links below to visit the official book website.
Warning: Some of the images in the Medical section section are very graphic in nature. If you cannot stand the sight of blood, it is advised that you skip these images.
All ImagesOsteochondromaCurrent Filter:
Category: (X)HTML
Date Range: 7/1/2004 - 7/31/2004
(clear
filters)
Earlier today I received this anonymous comment under my previous post:
Name: praetorian
Email: laughing@liber.als
Date Added: 7/2/2004 8:21:30 PM
Content: this really has nothing to do with your birthday, but your source code claims to be xhtml 1.1 yet it's not even close
http://validator.w3.org/check?verbose=1&uri=http%3A//www.dwmommy.com/
happy belated birthday, regardless
Well whoever you are, you were right. I'd neglected to encode the ampersands in the some URLs... such a horrible offense that one was. I forgot to add an alt attribute to the Macromedia affiliate ad image too. Other than that, it was a bunch of encoded characters that weren't recognized within blog comments. (My guess is someone wrote the comment in Word then pasted to the form.) Dreamweaver also converted some onclick events to onClick in my navigation include file -- Dreamweaver bug which I was aware of but always forget to fix.
In any case they were all silly little mistakes, and if I had a transitional doctype it probably would have passed (except for maybe the blog comments). It only took a couple minutes to fix. Whoever you are, thanks for pointing it out to me. You didn't need to hide your identity either. I wouldn't have been offended.
I know there's a chance that the pages won't validate due to comments in posts or a lack of an encoded ampersand in a URL (which I have to say is a really stupid rule). I just need to be better about checking regularly. Thanks for the reminder...
Posted by ~Angela | Comments (1) | Add Comment | Permalink
Comment from Luke Shingles on 9/22/2004
Actually unencoded ampersands are invalid even in HTML4.
Like I said, it is a stupid rule. (I never said it was an XHTML rule only either ;-)) ~Angela