Hi Davide,

I’ve been checking your website. The problem is relatively simple to solve. The thing is that if you don’t specify the from parameter, then it’ll have the default value, which is en, so the text will be in Italian, but the API is trying to translate from English to English.

So you’ll have to set this fromparameter to it whenever the text is in Italian. I think that wouldn’t be too complicated for you since I can see you have some good knowledge

Let me know…

Cheers, Fred

Hi Iamheaddown,

I don’t know your website URL , but doesn’t matter. This problem seems like is not going away. That’s why I made a modification to the script, so please go ahead and download the package again, and it’ll work just fine.

If after you updated the files, the problem is still there, then the reason is that your browser is taking the files from its cache. So please make sure you’re clearing it. Or even better, when you load the js file, add a dummy parameter, for instance, instead of:

<script type="text/javascript" src="/translator/javascript/jquery.translator.min.js"></script>

Use:

<script type="text/javascript" src="/translator/javascript/jquery.translator.min.js?rev=1.6"></script>

Let me know…

Cheers, Fred

Works again, thanks for the update. I didn’t see the update listed on the Version log on the page? Thanks again.

Glad to know it works fine Can’t believe I forgot to update the main page, we’ll do it soon! Thanks for the comment!

Hi Businessbroker,

thanks for buying! I can modify the current script to work with the Google Translate API v2, other people have asked me that too, so I guess I could do it. But you’ll have to use the new version of the plugin, because both Google and Microsoft APIs use a way to connect to the translation service different than the Google Translate API v1.

Since you have a key already, I assume you’ve seen the admin panels and all the things you have to set to prevent your key being stolen, right?

What I’m offering you is to update the script to work with the Google Translate API v2, nothing less nothing more. As you might know, when the usage gets over the limit, the translation service won’t be available. So, in the case your key goes over the limit, the translator will be displayed but it won’t work.

If you accept the above, of course feel free to comment , please send me a message using the form on the lower right side of this page: http://codecanyon.net/user/SurStudio so I’ll have your email. I’ll also need the API key to make a couple of tests, I promise I’ll be translating only “hellos”.

Cheers, Fred

Hi DSchragg,

sorry, the script doesn’t support the Google Translate API v2. Make sure that you really want to use it, you can sign up for the API for free so you can see the admin panels.

You will have to set limits per IP address, max costs per day, and referrer checks so you will be protected if someone steals your api key (which is something extremely easy to do) or if there are too many of your visitors using the translation service.

Also, you should know that once the usage of the api key is above of any limit, then the service won’t be available until the next day or until you pay the bill.

Cheers, Fred

Glad you like it Thanks for the comment!

Hi Mac,

sorry to hear about your bad luck with the other script :/

Is it possible to predefine the target-language?

Is possible, but you need to make a little trick. Let me give you a brief explanation. You have to specify the source language, so, instead of saying, from: “en”, or from: “de”, you should call a function that depending on the current url it’ll return the source language.

In short, the function should check for self.location.href to retrieve the source language:

from: (function() {
  // test self.location.href and return en, de or it
})()

or instead of creating an adhoc function, call a predefined one:

function getLanguage() {
  // test self.location.href and return en, de or it
}
...
from: getLanguage()

I can do it for you if you want, it’ll take 2 minutes.

Cheers, Fred

thank you for your fast react, this will make my choice easier

rgds
mac

No problem Let me know if you have some other question.

Cheers, Fred

Hi Seoranch,

when you buy the plugin, you’re buying a license to use it in one website, see http://codecanyon.net/wiki/support/legal-terms/licensing-terms/ in Regular License:

(a) Your use of the Work is limited to a single application.

So if you want to use the plugin in, lets say, 3 websites, then you should buy it 3 times.

Cheers, Fred

Cool, glad to hear that I think you’re the first person using it!!

Hi Edgemu,

if the installation is “basic”, then there’s no fee. You might be wondering how or when a installation is “not basic”, well, it depends on the website, if it requires modifications, CSS adjustments, then I’ll have to charge you depending on the spent time. But if is only editing a file and make the translator works, then that costs nothing because it takes no time.

I think is easy enough if you follow these steps: http://surstudio.com.ar/translator-lite-installation.html#index-3

To be honest, I have no idea about XARA Designer Pro 7, I’d guess is some kind of graphical tool to make HTML ?

Cheers, Fred

Sure:

$(".translator").translator({
  apiKey: "", // place your API Key here
  onComplete: function(filtered_elements, translation, source, from, to, options, restore) {
    console.log([filtered_elements, translation, source, from, to, options, restore]);
  }
});

See the console.log statement, if you run this on Chrome for instance, you’ll be able to explore all the data. Anyway. I can tell you what the variables have:

filtered_elements: an array with the DOM nodes selected to translate.
translation: an array with the translated text for each DOM node.
souce: an array with the text to be translated, for each DOM node too.
from: the source language code (en, es, etc)
to: the destination language (en, es, etc)
options: an object with all the internal options
restore: true or false, depending if the visitor has clicked on the Restore button

Would be better if you can define your function instead of using an adhoc function as above. For instance:

function my_on_complete_function(_nodes, _translation, _source, _from, _to, _options, _restore) {
  // do something
}

$(".translator").translator({
  apiKey: "", // place your API Key here
  onComplete: my_on_complete_function
});

Let me know if you have some other question.

Cheers, Fred

Hi, yes, the Microsoft API isn’t as good as Google. I’ve fixed the issue already, but it takes about a day until the Envato staff approves the change. Please send me an email using the form on the right side of this page: http://codecanyon.net/user/SurStudio and then I’ll send you the update right away.

Sorry for the problem.

Cheers, Fred

Hi there,

thanks for buying!

This problem should be caused because of a non well formed HTML . Can you please send me the URL so I can take a deeper look?

You can send me an email using the form in this page http://codecanyon.net/user/SurStudio which I recommend you because CodeCanyon doesn’t warn me whenever you post a message here, so you’ll get a quicker answer

If your page isn’t on the internet, please attach the HTML code.

Don’t worry, we’ll find the issue and fix it.

Cheers, Fred

Thanks Fred, sending to that URL

Hi Renata,

I’ve done the update already, I’m testing it and make it little adjustments. I think I’ll submit it tomorrow or the day after tomorrow. Then, it might take another day or two to get it approved by the Envato staff.

Cheers, Fred

Hi again Renata,

just wanted to tell you that the new version is ready.

Cheers, Fred

Hi IntMilkBrilliant,

that’s correct, this script uses a 3rd party API to make the translations. So you won’t be able to use your own set of translations.

I’ll be releasing an update next week, and the script will support the Microsoft Translate API , which allows you to add custom translations. However, if you have your content translated in, lets say, a database, I recommend you to look not for an AJAX Translator, because that translated content won’t be indexed by search engines, and that would be a shame.

Cheers, Fred

Fred,

Many thanks for your honesty. Best of luck with your sales…

Thanks and good luck to you too

Hi Jack,

currently, the script works with the Google Translate API , which, as you said, is going to be deprecated on December 1st.

In about a week, I’ll be releasing an update to handle new translation APIs:

• Google TranslateElement API
• Microsoft Translate API

The TranslateElement API is free, while the MS API is free until you hit the 2.000.000 characters per month limit.

I’ll be supporting both because I don’t trust Google right now, they have made a lot of changes in their APIs, so the MS API is more like a backup plan.

Cheers, Fred

Hi k8thegrrr8,

thanks for buying

I think the main issue for you was a little of a misunderstanding, because this is a jQuery plugin and not a Wordpress plugin but don’t worry, it can be installed on Wordpress.

Telling you all the steps is kind of long and might be kind of hard for you to follow them up, so we have 2 options:

1) I guide you through the steps one by one, so we can actually see progress on the installation.

2) You give me temporary ftp access to your site and I install it for you.

Lets assume you chose 1), so the first thing I’m going to ask you is to upload the files located in the translator folder to somewhere in your site, doesn’t really matter where. Then send me an email with the following information:

• Your website’s URL
• The location where you uploaded the translator’s files
• Attach the header.php file (which is located in the wp-content/themes/your_theme_name)

In order to send me the email, please use the form on the lower right side of this page: http://codecanyon.net/user/SurStudio

Cheers, Fred

Hi there,

yes, it’s possible to set an option (which name is cookie) to make the translator behave as you described. You can try it by yourself on the demo page: http://surstudio.com.ar/translator-lite-examples.html example number 2.

Cheers, Fred

Hi anaaiza,

both scripts Lite and Pro versions will continue working based on the Google TranslateElement API http://translate.google.com/translate_tools , it will be free and the translators will continue working as they are now.

Also, Microsoft has released a Translate API too, which is free until you hit 2.000.000 characters within a month. This is not so good, because a simple page has more than 2.000 characters, so you’ll have about 1.000 translations per month. Plus, the Microsoft promotion might end at any time. I’ll wait a little on the Microsoft API to see what the people say about it.

Cheers, Fred

Great, glad to know that everything is working fine

I see this error in your page now, it says it is located in jquery.min.js.

As I see, you can try 2 things:

1.- load the latest jquery library and not 1.5.1

2.- your language setting is wrong, it has an extra comma:

languages: ["en", "es", "de", "ar", "tl", "id", "ko", "zh", "ja", "it", "hi", "tr",],

should be:

languages: ["en", "es", "de", "ar", "tl", "id", "ko", "zh", "ja", "it", "hi", "tr"],