Actually, HTML5 returned a number of the inline formatting tags that 4.01 had claimed obsolete, including [small] (but not [big>]). I only used "4.01 Transitional", which the W3C verifier was happy to approve with all the inline tags.

As far as CSS is concerned, since I've never used it at all, it might as well be CSS3, which may be final because there is no ongoing effort to produce CSS4. Of course, I'm ignoring all the fancy stuff in CSS3, so I'm probably effectively using CSS1 or CSS2.

Actually, I'm getting along pretty well with HTML5/CSS3, having learned to preserve the appearance of my pages almost perfectly. HTML5 declared a lot of entities "block", and I couldn't live with that, but display:inline in the style sheet fixes that.

One thing that annoys me, is that when I started, I used the [h1], [h2], [h3] tags, but the W3C verifier rejected them as obsolete. Now I'm told their use is critical to good SEO performance. Oh well, I can't use [big] any more, and conversion to [h1,2,3] isn't hard, so I can live with that.

Now that I have constructed examples and .css files it is no more difficult for me to make pages to the new standards than the old.

The problem is 4565 pages to update. Fortunately, I can do a lot by cut, paste and edit from my examples, but it is still a hassle and will take years. I've done a bunch of the most important pages, which tend to be long ones. Updating the three recipe indexes was tedious, but they're done.

Fortunately, Web browsers will continue to display the old format pages correctly for years, but search engines are starting to get a bit picky.

I was thinking perhaps the enlarged picture pages could be automated, but even there there are some that are somewhat different and some that are radically different.

The rest of the pages need extensive work, and their consistency is more an illusion than a fact. While they descend one from another, each is changed in subtle or radical ways to serve an exact purpose.

Besides, I've found it very useful to edit by hand, as it forces me to systematically revisit pages that haven't been touched for 10 to 12 years, and bring them up to standards, mine and the W3C's.

Fortunately, this is a chronic problem, not an acute problem, as Web browsers will correctly interpret the pages probably for around 8 years. Anything new or modified I submit to the W3C Validator will be updated.

In any case, I appreciate the offers, and will keep them in mind. Thanks.