h2g2 The Hitchhiker's Guide to the Galaxy: Earth Edition

Entry: Email Addresses in ASCII Code - A2032589
Author: T.B. Falsename ACE: [Buy one, get one free Tibet!!!]"It is the fate of the weak to die unknown, and the destiny of the strong to rule for eternity. Give me glory, or give me death!" - U170182

Submitting this for the second time, I think I've covered all that was mentioned the last time.

a couple of things:

perhaps you could put & in brackets like this (&amp thus enabling the sentence to flow better.

Secondly,take care with spelling bellow is below in this instance

Done, thanks.

This is quite a useful Entry A few changes:

H2G2 --> h2g2 (in the first sentence)

However this can be a problem. Spammers use software called 'bots'. Bots are small programs which scour the internet for information. Not all are used unscrupulously. Many search engines use them. However spammers use them to collect emails.
-->
However, this can be a problem. Spammers use software called 'bots' - small programs which scour the internet for information. Not all are used unscrupulously, as many search engines use them to determine search rankings. However, spammers use them to collect email addresses contained within the text of websites.


You don't really need the header 'Examples', and your other headers could do with being more capitalised.

Oh and it makes an Entry a lot clearer if you put the blocks of code inside tags.

Alex

Changes done, thanks

Maybe you can put spaces around the single letters in the tables giving the corresponding code? They look a bit squeezed in now, hard to see. And I would probably read the table by columns rather than by rows, though I did figure out how you arranged them.

Also, in the "Clickable Link Type Email Addresses in HTML" you don't need the commas after "changing" and "into" - and either capitalise both or write both lowercase Perhaps all the half-sentences in front of the code blocks should have colons at the end? Not sure about that

And for the page that will create links for you - maybe mention that you can always go over the code with a search & replace later to change the <A HREF= code to <LINK HREF= code?

>>Maybe you can put spaces around the single letters in the tables giving the corresponding code? They look a bit squeezed in now, hard to see. And I would probably read the table by columns rather than by rows, though I did figure out how you arranged them.<<

First bit done.

About the second bit, how do people feel about that, would they rather the letters ran horizontally or vertically?

>>Also, in the "Clickable Link Type Email Addresses in HTML" you don't need the commas after "changing" and "into" - and either capitalise both or write both lowercase Perhaps all the half-sentences in front of the code blocks should have colons at the end? Not sure about that<<

First bit done and not sure about the colons.

>>And for the page that will create links for you - maybe mention that you can always go over the code with a search & replace later to change the <A HREF= code to <LINK HREF= code? <<

I've added a bit to remind people that the html code works on h2g2. Also I have, kind of, covered the difference between html and GuideML links earlier in the article and didn't want to restate too much of it incase it became confusing for some people.

Looking good this one will really come in handy.

In XHTML, "<A HREF= ..." should be "<a href= ...". The lowercase version is valid in all forms of (X)HTML, but the uppercase form is valid only in the older HTML.

Excellent informative entry!

TRiG.

ok I've made it XHTML compatible.

I agree this is excellent, my only quibble is that it's not generally good form to link with the word 'here' as people using text readers don't get the link, they just get 'here'. So I would suggest giving the link in short webstyle

Other than that, very cool

umm, could you just clarify what you mean? Do you mean to use the web address instead of the word here?

That's pretty much it, I'd substitute 'here' for something like;

'can be found via an online Email Obfuscator.'

Or something like that.

Nitpicky I know, and not vital to content and be clarified later, just thought I'd mention it for future reference

Done

I could have sworn there's already an entry explaining all this. But it might just be deja vu.

I think it would be better if the table just gave the codes, and not the full <ENTITY = syntax.

The table would work better if it went down the first column with a, b, c, etc, then continued on to the second column and so on.

Done and done.

I think you commented on this when it was in peer review before.

Was that about five years ago?

This Entry was created in Nov 2003 G, so may well have been ...

Time flies when you're having fun!

here's a post you made in 2003, Gnomon, http://www.bbc.co.uk/dna/h2g2/classic/F1685045?thread=344533#p4400070