On Monday, Dec 8, 2003, at 21:00 America/New_York, Tanya Mayer Photography wrote:
Omg, sorry guys i know that this is totally OT, BUT I was just chatting with
#7 via AIM, and we were looking at my website, when I realised that all of
my text has shrivelled up! No kidding! Usually, it is large, and easily
readable, but now on some pages it is barely recognisable!
I just browsed a few pages and there doesn't seem to be a problem. Check your browser preferences and set your default font typeface and size to something reasonable and see if that improves anything.
I notice that in some of your CSS styles, the font size is specified in pixels. This could cause a problem on some displays: e.g. a font size of 10px is going to look smaller on a 96ppi display than a 72ppi display. I suggest that you specify font size in points rather than pixels. The font sizing is also inconsistent across pages. e.g. text on about.html appears smaller than on fairmaidens.html.
You mentioned that you're hand-coding the site, which is an admirable endeavor. However parts of it look messy, most likely because of the original code generated by Adobe Go-Live. I think you'll find it much easier to maintain if you clean up the code. Two simple things you can do is to put the CSS and JavaScript into separate files. That way, you don't have to repeat the scripts and styles on every single page (unless you're already using server-side includes). If you make any modifications to the styles or scripts, you do it once in the external .css and .js files instead of having to make the same changes on each page. Also, remove any code that you don't use. e.g. I noticed a rather useless script that appears to trap right-mouseclicks. Something to do with copying/saving images? If I want to save an image on a web page into my disk, I just drag it into my Finder window and it's saved! The script does nothing to prevent this. Finally, format and indent your code neatly. It'll improve the maintainability of your code.
There were a few places where you used both CSS styles as well as the deprecated <font> tag. I think it'll be helpful if you choose to adopt one or the other. If you use both, then you get into a situation where the appearance properties are set both in the font tag as well as in the CSS style. I don't remember if one overrides the other or if both sets of properties are used and what's the precedence. But you can see that conflicting settings could easily occur.
btw, when using proportionally-spaced fonts you only need one space after a period (full-stop), not two.
--jc
