i'm trying to use this: https://developers.google.com/transliterate/v1/getting_started , when i'm use this it shows following error:
Loading "elements" other than "inputtools" is unsupported.
and in its top gives following message:
The Google Transliterate API has been officially deprecated as of May 26, 2011. It will continue to work as per our deprecation policy.
any one help me how can i use this?
Related
When using the translation API, I get a different translation (and worse) than if I use translate.google.com.
I am working on a project for a client, and the client was dissatisfied with the translation and noticed the difference.
Do these two service use different engines? I read that the API uses nmt-mode now, and that translate.google.com already uses the same engine.
Both set to translate from Norwegian to English.
Any more information that can clear this up?
Thanks!
The result differences between the translate.google.com and the Translation API calls are considered as an expected behavior that can be generated due to maintenance tasks and the logic used by the internal processes; However, the engines used for each service seems to be private information.
Based on this, it is normal to get some variances when using the API. I think you can use the model parameter option as an available workaround in case you want to specify which of the available models to use, as well as take a look on the Specifying a model official documentation to get detail information about this alternative.
It's almost about 3 years later and the problem still remains!
So I was trying to translate a dataset with the Google Translate API, but in the end it failed to translate some texts to the target language (in my case, Persian/Farsi). So I decided to check them to see if there's a pattern and maybe translate them using the web version of Google Translate.
As I was doing so, I figured that the web version actually could translate some of those untranslated texts, BUT not all. When trying to find a reason for such behaviour, I found out that most of them were names and not sentences. But as we know, names can easily be written with the target language characters as the translation. But why the API doesn't transform those names while the web version does? This photo will explain everything perhaps:
verified translation
As can be seen, some translations have a badge indicating that the translation has been verified, while some others don't.
So to recap, my guess is that maybe the API is set to only use verified translations, but as for the web version, even unverified translations are allowed since you can edit or report them.
The project that I'm working on mandates (by law) the name of the business to be displayed to the users in the regional language.
The best option that I could find was Google Transliterate. I'm aware Google Transliterate API has been officially deprecated as of May 26, 2011 but is still available to be used - which solves by need.
So my question is - How can I use Transliterate API without the need to open a web browser? When a user keys in a Edit Text say for e.g. "Baskin Robbins" I would like to get it transliterated behind the scene. I'm on minSdk 10.
Any pointers to working samples would be very much appreciated. Is LiquidCore as possibility? https://github.com/LiquidPlayer/LiquidCore . Any known implementation of Liquidcore & Transliterate? Please advise.
www.google.com/transliterate/indic?tlqt=1&langpair=en|ta&text=baskin%20robbins
Also see here
Implementing Google transliterate API using REST and C#, facing unicode and parsing issues
Goolge very kindly offer a sample dataset of Google Analytics data in BigQuery, so you can run some tests before setting up the actual export to BigQuery.
This is detailed at the following page https://support.google.com/analytics/answer/3416091?hl=en&ref_topic=3416089
However when you try to add the project google.com:analytics-bigquery as shown in step 5 of the guide. The following error is shown:
Project IDs may contain letters, numbers, and dashes, with an optional
"domain:" prefix.
As you can see the project ID conforms to this, but you are unable to submit the form.
Google is this just a bug?
Does anyone else have the same issue?
I am confirming - just tried and got the same.
Some-when recently - this dialog form was changed (added options to choose from - display in nav vs. make a current project) and looks like the bug was introduced. previous versions didn't have this bug.
At the same time - confirming that nothing wrong with project name itself - with the internal tool that I am using - I was able to add this project successfully
You should report this bug in BigQuery issue tracker.
Thanks for reporting this issue. We actually already have a fix checked in for this, but we are currently waiting for an opportunity to push this to production, hopefully soon.
In the meantime, you can try one of these workarounds:
navigate directly to the project: https://bigquery.cloud.google.com/queries/<project_id>
navigate to a dataset on the project, which will display it in the left nav: https://bigquery.cloud.google.com/dataset/<project_id>:<dataset_id>
checking the heroku logs for my bot is showing messages like:
/app/scripts/tigger.coffee is using deprecated documentation syntax
but I can't seem to find what the undeprecated documentation syntax should be ...
It's normally due to the TomDoc at the top of the files. There's a good example for a correct one here
I used the Google API to translate word from Ar to En I want to translate only one word every time and I want to get all the possible meaning for that word not only one meaning. How can I do that, all the codes I found give only one translation.
Unfortunately it is impossible for the current version of Google Translate API (v.2).
From the FAQ (https://developers.google.com/translate/v2/faq):
Q: Is it possible to get multiple translations of a word?
A: No. This feature is only available via the web interface
at translate.google.com
I have created a npm package that can do exactly what you want - extended google translate api
However, this package uses unofficial google translate API, so you can't use it in any commercial projects.