Closed GoogleCodeExporter closed 9 years ago
If you're a Portuguese speaker, set your translation language in the plugin's
config settings to Portuguese. If the person you're talking to is an English
speaker, choose 'Translate to'->'English' in the more menu (I think you might
have it back to front)
Original comment by eionrobb
on 22 Sep 2011 at 3:21
[deleted comment]
No, it's the other way around - I'm an English speaker talking to a Portuguese
speaker.
Currently I've set my global language to English, and in the more menu, I've
selected 'Traslate to' -> 'Portuguese'.
After looking through the code, I seem to be able to reach the servers (both
the Google API and the Microsoft Translator), however no text is displayed in
the chat session when google is selected, and the entire app crashes when I
attempt to send text if Microsoft is selected. :-/
Original comment by cade.cam...@gmail.com
on 22 Sep 2011 at 4:08
Ok, thanks for the clarification.
Can you get a debug log (Help->Debug Window) when using the Google API, and a
backtrace when crashing with the Microsoft Translator?
Original comment by eionrobb
on 22 Sep 2011 at 4:10
Attached is the de-bug info for google - appears it's a proxy issue on my end
(attempts to access the google server on port 11004, which is probably getting
blocked?).
Also attached is the .RPT file from \.purple for the Microsoft Translator
service crashes.
No expert, but looks like a proxy issue as well?
Any suggestions?
Original comment by cade.cam...@gmail.com
on 22 Sep 2011 at 4:36
Attachments:
Ah, no, the 11004 is the Windows socket error number. Looks like it's a DNS
thing? The crash report is also to do with DNS within libpurple/Pidgin
Original comment by eionrobb
on 22 Sep 2011 at 4:49
Solved this issue - I didn't have a global proxy server set (the plugin wasn't
using the proxy settings set for the individual chat protocols). It's actually
quite logical that the plugin should use the global settings, and not
necessarily a per-protocol one. Now have this service working, and it's great!
Wondering if the plugin can fail a tad more gracefully or notify the user
(within the chat session perhaps?) for instances where this error occurs in the
future?
Huge thanks to eionrobb for your quick responses though! You've got a great
plugin going here! As per the Google Translate API site, think their service
might stop around 1 December 2011. Something to think about anyway.
Thanks again!
Original comment by cade.cam...@gmail.com
on 23 Sep 2011 at 12:36
Glad to hear it's all up and running :)
The segfaulting isn't a good thing though... you might want to report that on
Pidgin's trac.
I'm aware of the Google Translate API shutting down soon, but it's good to get
a reminder to get a move on. I've found a couple of other services out there
which might be useful, but none are as good as Google :(
Original comment by eionrobb
on 23 Sep 2011 at 2:53
Original issue reported on code.google.com by
cade.cam...@gmail.com
on 22 Sep 2011 at 2:04