I have webspace I'm not yet using, because I'm lazy and haven't shifted my site to it. I think I've got 200 megs and a fair amount of bandwidth.

I stand corrected. Dammit.

Re: tagline-character-counting scripts:

we need to have it count hard returns as two characters, not one.

But I fixed that ages ago.

I put a version up for testing at [link] a few days ago.

It gives annoying messages, but just for debugging purposes. It finds the length, then checks for returns and adds one to the length variable for each one it finds.

I just would like it tested on Windows and *NIX computers because I'm not quite sure what "\\r" means on other platforms. We might need to use ("\\r" or "\\n") for instance.

Did you tell me you'd done that? Last I heard, you said you were going to do it. I'll check it out.

It's not working on my Windows ME machine. It's still treating returns as one character.

Correction: It's doing something in IE, but not in Mozilla.

Sorry about the confusion. From memory, I said something ambiguous like "want to check it out?".

It's not working on my Windows ME machine. It's still treating returns as one character.

OK so if you put in text with returns, it says "original length x", and then the next dialog that appears says "adjusted length x"?

OK I'm looking at it in Mozilla too and you're right, it doesn't see any linebreaks.

I'll tweak it.

OK tweaks completed. It adds one to the length for either a CR or an LF, as much as I understand those terms. It's the kind of stuff that baffles me.

As long as there isn't a platform/browser which puts CR and LF into a TEXTAREA when you hit return, then we're rocking and rolling.

OK, this is what I get for not checking things thoroughly beforehand -

Ignoring your tweaks, John, IE always counts a forced return as two characters whereas Mozilla (which I normally use) counts it as one. I'm sorry that I didn't notice this before.

So, now, with your tweaks, the script works in Mozilla, but overcounts in IE.