egghelp/eggheads community

GTranslate is not working because of TCL issues

2012-04-04T15:12:17-04:00

A small message to say that gTranslator doesn't work anymore and will not be released again.
Google choosed to block the API v1 and the v2 is a commercial one, I refuse to make a script which use commercial services.

@slennox: could you please remove Google Translator from the tcl archive ?

Regards,
CrazyCat

Statistics: Posted by CrazyCat — Wed Apr 04, 2012 3:12 pm

GTranslate is not working because of TCL issues

2011-10-08T18:17:24-04:00

I have new code, it works perfectly and is extremely light-weight and simple.

Code:

administrator@artemis:~$ cat /home/administrator/eggdrop/scripts/gtranslate.tclnamespace eval gTranslator {# Factor this out into a helperproc getJson url {  set tok [http::geturl $url]  set res [json::json2dict [http::data $tok]]  http::cleanup $tok  return $res}# How to decode _decimal_ entities; WARNING: high magic factor within!proc decodeEntities str {  set str [string map {\[ {\[} \] {\]} \$ {\$} \\ \\\\} $str]  subst [regsub -all {&#(\d+);} $str {[format %c \1]}]}bind pub - !tr gTranslator::translateproc translate { nick uhost handle chan text } {  package require http  package require json  set lngto [string tolower [lindex [split $text] 0]]  set text [http::formatQuery q [join [lrange [split $text] 1 end]]]  set dturl "http://ajax.googleapis.com/ajax/services/language/detect?v=1.0&q=$text"  set lng [dict get [getJson $dturl] responseData language]  if { $lng == $lngto } {    putserv "PRIVMSG $chan :\002Error\002 translating $lng to $lngto."    return 0  }  set trurl "http://ajax.googleapis.com/ajax/services/language/translate?v=1.0&langpair=$lng%7c$lngto&$text"  putlog $trurl  set res [getJson $trurl]  putlog $res  #putserv "PRIVMSG $chan :Language detected: $lng"  set translated [decodeEntities [dict get $res responseData translatedText]]  putserv "PRIVMSG $chan :$translated"#  putserv "PRIVMSG $chan :[encoding convertto utf-8 $translated]"}}

Statistics: Posted by ujjain — Sat Oct 08, 2011 6:17 pm

GTranslate is not working because of TCL issues

2011-10-08T11:52:04-04:00

ah cool - thanks
ill wait until its on egghelp as.. i need a translator to go on that site

Statistics: Posted by rayvtirx — Sat Oct 08, 2011 11:52 am

GTranslate is not working because of TCL issues

2011-10-08T11:34:00-04:00

Oh ! I didn't notice the version on egghelp wasn't the last one I did.

The official download is http://www.eggdrop.fr/board/downloads.p ... ew&did=209

I'll send the good version to slennox in a few hours.

Statistics: Posted by CrazyCat — Sat Oct 08, 2011 11:34 am

GTranslate is not working because of TCL issues

2011-10-08T10:44:35-04:00

just happened to find a different version of the same script while googling and this one works http://heartbroken.bshellz.net/gtranslate.tcl

Statistics: Posted by rayvtirx — Sat Oct 08, 2011 10:44 am

GTranslate is not working because of TCL issues

2011-10-08T09:03:04-04:00

ok got tcl 8.5
now getting
Tcl error [gTranslator::translate]: Illegal characters in URL path

Statistics: Posted by rayvtirx — Sat Oct 08, 2011 9:03 am

GTranslate is not working because of TCL issues

2011-10-08T08:13:19-04:00

You need tcl 8.5.

Statistics: Posted by CrazyCat — Sat Oct 08, 2011 8:13 am

GTranslate is not working because of TCL issues

2011-10-08T02:22:39-04:00

i get this error
Tcl error [gTranslator::translate]: can't find package dict
any ideas?

Statistics: Posted by rayvtirx — Sat Oct 08, 2011 2:22 am

GTranslate is not working because of TCL issues

2010-11-25T10:31:45-04:00

@speechies: I know my tcl isn't efficient, it was just an exercice to use the Google Translate API, and I didn't work alot about the language detection / translation.

BTW, I think I'll do a wonderfull version soon Ok, let's say a better one

Do you have any idea how I can solve the Tcl error?

Statistics: Posted by ujjain — Thu Nov 25, 2010 10:31 am

GTranslate is not working because of TCL issues

2010-11-23T16:24:15-04:00

@speechies: I know my tcl isn't efficient, it was just an exercice to use the Google Translate API, and I didn't work alot about the language detection / translation.

BTW, I think I'll do a wonderfull version soon Ok, let's say a better one

Statistics: Posted by CrazyCat — Tue Nov 23, 2010 4:24 pm

GTranslate is not working because of TCL issues

2010-11-20T15:27:50-04:00

You might have a point, although it might take me much time to scrap the other features from that script. I have another script that does almost all Google functions, but it is was used spamishly in our language channel. Our channel is about learning languages and I prefer a bot with little functionality, Google Translate. Converting the syntax from !tr fr|to text might also be hard to do for me.

The current script is working fine and as long as there are no security issues, I am fine with the functionality. Replacing the translate-script by a fully functional Google script is not an option, we have a language channel with 50 users and having them use locate, wikipedia, whois, news functions in our channel will reduce the quality of our channel.

I appreciate your suggestion and will consider taking the translate part of that script as it might work.

Statistics: Posted by ujjain — Sat Nov 20, 2010 3:27 pm

GTranslate is not working because of TCL issues

2010-11-20T14:06:06-04:00

There is no language limitation in place. I changed the comparization in source code to -10, effectively killing the language limit:
Code:
if { [lsearch $::gTranslator::lngs $lngto] == -10 } { 
This effectively ends any relevance of lngs. I will rewrite the entire TCL-script when I have time, but it works perfectly fine as lngs is no longer used. I am aware I can remove both set lngs... including the entire if-statement.

I have been looking for 2 weeks for a way to get the tcl-script working on the eggdrop installed on the CentOS-VM. Do you have any idea's how to achieve this?

Not to hi-jack this thead, but at the moment this script has the functionality your looking for and works if patched for utf-8 support both input and output. Uses the same !tr trigger as well. It is a full featured script with functionality far beyond translations. Some features presently are broken, this is due to the nature of it being based on html rather than api. These will be fixed eventually, but the core functions are solid themselves it's merely the parsers that break.

Now about this script, it has potential easily to rival my mere scraping attempt as it uses pure API. It will not require maintenance for parsing as it is fed a json reply which can be easily machine read. My html parsing version its meant to be read by humans, and it's context and style will change as humans evolve. So my script will break over time. But for the moment, see if perhaps it works for you. It may not, it will likely suffer same error. It may not, can't know without trying. Hopefully CrazyCat evolves this script into something closely resembling mine, but with the added benefit of the API wrapping.

Statistics: Posted by speechles — Sat Nov 20, 2010 2:06 pm

GTranslate is not working because of TCL issues

2010-11-20T13:40:31-04:00

There is no language limitation in place. I changed the comparization in source code to -10, effectively killing the language limit:

Code:

if { [lsearch $::gTranslator::lngs $lngto] == -10 } {

This effectively ends any relevance of lngs. I will rewrite the entire TCL-script when I have time, but it works perfectly fine as lngs is no longer used. I am aware I can remove both set lngs... including the entire if-statement.

I have been looking for 2 weeks for a way to get the tcl-script working on the eggdrop installed on the CentOS-VM. Do you have any idea's how to achieve this?

Statistics: Posted by ujjain — Sat Nov 20, 2010 1:40 pm

GTranslate is not working because of TCL issues

2010-11-20T12:03:44-04:00

@CrazyCat ... Why is this line there at all:

Code:

set lngs { "fr" "en" "es" "de" "it" "nl" "tr" }

Your Google translate script converts between a massive 7 language pairs? Wow, very not impressed at all. To add languages people need to constantly tamper with that variable.. Why?

The Google translate script I have which is part of Incith:Google doesn't limit you, want to translate Serbian to Japanese it will.

# auto detect serbian to japanese
!tr @ja

# auto detect japanese back to serbian
!tr @sr

# force chinese detection and return japanese
!tr zh-cn@ja

# force french detection and return default english reply
!tr fr@

# auto-detect and return default english reply
# fully auto, no languages required.
!tr

Google will auto-detect you've used Serbian and convert it properly to Japanese. There is no limit to the languages you can use in mine as evidenced above. If Google supports it, you will be given the translation. If Google doesn't support it _yet_, you will be given that message. If it isn't a valid language, you will get back your original text. Yours doesn't work like this and limits itself for no reason. You should check out of the translate portion of the Google script and COPY the way I do it exactly. Otherwise, your script will always be inferior even though it should be superior using the API rather than web-scraping.

Statistics: Posted by speechles — Sat Nov 20, 2010 12:03 pm

GTranslate is not working because of TCL issues

2010-11-20T11:47:11-04:00

Well, I'll have a look on this trouble.
I'm using Debian, so it might be hard to reproduce the trouble, but I'll find the solution

Thank you. If you wish to access my CentOS VM, that's no problem.

Code:
set text [::http::formatQuery q [join [lrange [split $text] 1 end]]]set dturl "http://ajax.googleapis.com/ajax/services/language/detect?v=1.0&q=$text"
This looks wrong. q= is .. already going to be part of $text when that first line runs. This is what using [::http::formatQuery] does. It will be "q=text user put minus first word" ... then you add q= agan to it within your "set dturl" line. Why? Google has a very forgiving API if it works like that.

There is nothing wrong as far as that users error goes. [::http::formatQuery] .. or simply [http::formatQuery] should both work exactly the same and not cause that issue. The problem more than likely is ( I replaced http.tcl (renamed old version) and restarted the entire VM to be completely certain it would not do anything with the http.tcl )

So wait, its an eggdrop running inside a virtual machine? was it compiled on that virtual machine so paths and everything work that way. It won't out of the box, it will fail to load packages (or use the wrong path and the wrong http.tcl) just as your seeing now.

Not sure I understand what you mean regarding the setting of variables, but it works on the Ubuntu desktop.

Code:

[16:38:43] http://ajax.googleapis.com/ajax/services/language/translate?v=1.0&langpair=fr%7cnl&q=Je%20deteste%20de%20la%20fromage.[16:38:44] responseData {translatedText {Ik haat de kaas.}} responseDetails null responseStatus 200[16:38:44] http://ajax.googleapis.com/ajax/services/language/translate?v=1.0&langpair=fr%7cnl&q=Je%20deteste%20fromage.[16:38:44] responseData {translatedText {Ik haat kaas.}} responseDetails null responseStatus 200[16:38:44] http://ajax.googleapis.com/ajax/services/language/translate?v=1.0&langpair=fr%7cnl&q=J%c2%b4aime%20bien%20fromage.[16:38:44] responseData {translatedText {Ik hou van kaas.}} responseDetails null responseStatus 200

Eggdrop has been installed on both a CentOS- and Ubuntu-VM and compiling went perfectly fine. Installing Eggdrop on a physical machine or virtual machine should make no difference.

Statistics: Posted by ujjain — Sat Nov 20, 2010 11:47 am