What's different about this than any other ones out there?

* Not only does this include the Traditional Google Translator, I've added an edition to make it actually translate your text to another language of your choice, automatically!

* So, what languages can I use? All 41 available languages to Google Translator:
Detect language, Albanian, Arabic, Bulgarian, Catalan, Chinese, Croatian, Czech, Danish, Dutch, English, Estonian, Filipino, Finnish, French, Galician, German, Greek, Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Latvian, Lithuanian, Maltese, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Thai, Turkish, Ukrainian, Vietnamese, including the addition of Detect Language for your convenience.

* So what kinds of things can I do with this?
In this script, you can do 4 kinds of things for translation:
o Translate text via alias (returns an echo) - Syntax: /translate
o Translate text via bot command (returns a channel message) - Syntax: !translate
o Translate text via dialog (returns translation to the dialog) - Syntax: /trans to open up the dialog
o Last but not least, talk normally in an active channel/query, and let the script translate for you. - Syntax: Open up the dialog or use the menu to turn the switch on/off

* Tabs?
In the dialog, there are two tabs.
o The first tab is a replica of the Traditional Google Translator (located here).
o The second tab is the enhancement. It allows you to adjust what language you are auto-translating to, along with enabling/disabling the whole thing, and adding exception channels (so the translations will not work in that channel).


So why did I make this?

* I mainly wanted to focus on using regular expression identifiers such as $regex and $regsubex, to make scripts shorter, and ultimately, stay away from $htmlfree.
* I wanted to try to find a way to make a script without listing all of the possible languages, and in turn, "download" + "write" each of the languages and its abbreviations to separate text files located on another directory.
* Using only one variable that is "/set" and written to variables.ini.



What else? Some new accomplishments and points:

* I managed to use only 1 variable written to variables.ini, or variable that is actually /set. (I dislike using variables because I have OCD with them)
* You can define multi-line expressions. No need to convert them so that they are all in one line.
* Regex can be very helpful in scripts. They can shorten your scripts significantly.
* Original site is used: http://translate.google.com/. Only one site is used, no PHP parsers or anything.
* Though, surprisingly to me, the socket portion is very small, there are a few checks to see if the text files are there, which slightly bulks the script up, but shouldn't be a problem.



A final note if you will use this:

* Preferably, open up the dialog first, when you are using this script
* If the script gets buggy, use the menu option to "reset" everything
* When you load the script, the Auto Text-Translator and the Bot command are disabled - to turn them on, use the menu functions.
* You can add exception channels to the "Auto Text-Translator" in the second tab of the dialog.
* Please don't delete the text files or the directory that stores them, though the script does check to see if they are there or not, and recovers them.