That would be a great idea (a "propername" or "notranslate" tag), but I've never heard of such a thing. Ideally it should be supported by multiple translation engines, not just Babelfish.

The best workaround I can think of would be to write the word/phrase out using Javascript, but of course that would screw up your search engine listings.

The only real solution would be to detect the Babelfish UA and modify your pages on the fly per some form of script.

Presumably you're having the translations checked by qualified speakers of the target languages?

Please don't even bother using machine translation for your website. It's a complete waste of your time. If you're doing a multi-language site you need human translators who are fluent in the target language.

Here are a few threads that touch on the topic:

• Multiple langagues on your website [webmasterworld.com]
  
• Multiple language sites [webmasterworld.com]
  
• Creating HTML mark-up for languages you don't know [webmasterworld.com]

I interpreted the question to mean that the OP links to Babelfish, so that users can translate the current page if they wish. I implemented something like this, and it's quite reasonable if properly labeled. I also see lots of people translating my site on their own, using other translaters.

Anyway I do agree that using one of these tools in order to publish a translation of one's website is a rather shoddy practice.

Since my site features mainly guides and articles, most text consists on simple instructions and short phrases. As long as the text has a correct grammar, syntax and punctuation, most of the contents are very easy to understand on the translated version.

Now, I show a small warning at the top of all pages when they are auto translated, to inform the user the fact that the translation might not be totally accurate.

The serious problem is with nouns and software names, that should NEVER try be translated. AltaVista says that to prevent a name from being translated, a period must be put in front of it. For example:

"The program .Microsoft .FrontPage is obsolete nowadays."

But this method involves inserting absurd periods all around the original english version, this is simply unpracticable.