Client For Google Translate Pro
Shay Silvertooth
For now though I'm stumped because the only example given uses Buzz and from my experiments, the Google Translate (v2) api must behave quite differently to Buzz in the google-api-ruby-client.
I'd love to hear of Ruby command line and desktop applications using this: google-api-ruby-client for services other than Buzz and in particular the Translate api (I'm less interested in the existing Ruby gems using the translate service at this point).
This is to get server access to the google api and bypass all the oauth stuff. THE MOST IMPORTANT BIT was the :authorization param when constructing he client.... this ensures the api key is used when calling, in preference to oauth. Without it you will get 401 Unauthorized response status everytime.
More progress. I put a bug report for Google-API-Ruby-client for part of this problem. The short version is that for Translate (at least) the Google-API-Ruby-client fails under SSL::VERIFY_PEER and succeeds when SSL::VERIFY_NONE is used.
The client can also send requests using v2 compatible style.However, it results in a bigger bundle size and may be dropped in next major version. More details in the blog poston modular packages in AWS SDK for JavaScript
This client code is generated automatically. Any modifications will be overwritten the next time the @aws-sdk/client-translate package is updated.To contribute to client you can check our generate clients scripts.
Interaction with the Translator service using the client library begins with creating an instance of the TextTranslationClientclass. You need your API key and region to instantiate a client object.The Text Translation API key is found in the Azure portal:
Create a client object to interact with the Text Translation SDK, and then call methods on that client object to interact with the service. The SDKs provide both synchronous and asynchronous methods. For more insight, see the Text Translation sample repository for .NET/C#.
Create a client object to interact with the Text Translation SDK, and then call methods on that client object to interact with the service. The SDKs provide both synchronous and asynchronous methods. For more insight, see the Text Translation sample repository for Java.
Create a client object to interact with the Text Translation SDK, and then call methods on that client object to interact with the service. The SDKs provide both synchronous and asynchronous methods. For more insight, see the Text Translation sample repository for JavaScript or TypeScript.
Create a client object to interact with the Text Translation SDK, and then call methods on that client object to interact with the service. The SDKs provide both synchronous and asynchronous methods. For more insight, see the Text Translation sample repository for Python.
The quality of a product is completely dependent on the process of how it's built. Product development starts when a client specifies their requirements, and developing software requires the entire team to precisely define what that application is supposed to do.
Dealing with unknown or unclear requirements is one of the greatest challenges when it comes to managing a product. If the client is dissatisfied with the poor quality of the product or unmet expectations, this could force you to increase the cost of production to correct the product's deficiencies. This often a result of not properly understanding a client's requirements from the start.
It can be difficult to translate a client's "voice" into user requirements for a product they are seeking help with. It often starts with an interview with the client in which you discuss problems and seek solutions for them. Scheduling an informal, candid conversation is a good way to get some initial thoughts and ideas about their needs.
When clients provide their requirements, it's common for those requirements to lack a focus on technical specifications. In this case, the risk is that the client's expectations are not in sync with their own requirements.
Without complete knowledge of the process of product development and the architecture that goes into building it, clients often assume that complicated features will be trivial or forget to include key features entirely. You need to be sure that you are precise when having technical discussions with non-technical clients.
Lack of communication is really the biggest mistake that any business in any sector can make these days. Sometimes, poor development outcomes can be attributed to a failure of communication between a product manager and a client.
A product's requirements are based on understanding the difference between what is really required and what is a simple "nice to have." A client's ability to understand the difference between the two is not always reliable. It is important to explain these two types of requirements for the success of both the client and the product development team working on it.
A client's vision for a product may be beyond the scope of their budget or even the capabilities of existing technology. As a product manager, it is essential to flag pie-in-the-sky ideas early on and make sure that all the requirements of the product are deciphered into clear, achievable goals.
Sometimes, in an effort to win a client's business, development teams may rush the scoping process without conducting due diligence on the exact project the client is trying to build. This is rarely a worthwhile sacrifice, as disagreements over project scope will come back to spoil the relationship later on in the development cycle.
A product manager or a team of developers presented with this story may think that the user story consists of simply saving a list. However, this would be a misinterpretation because the user story is made up of many pieces. A developer is likely to miss the point that the client wants to email the story and not just save a list of items in the application.
The above format of multiple user stories is clear for any product manager or a developer to understand. They can now easily see that the client's requirement does not stop just at saving the list of items, but also that the app's user can reuse the saved list of items. With these user stories, they can work on extending the functionality to provide a complete set of features within the app.
We've established how important it is to have a clear set of product requirements. At the same time, it's important to understand that clients come from a wide range of background, so you may need to help them flesh out their product requirements properly.
Helping a client to specify exactly what they are looking for from their product should be the initial step of any product development process. There are some practices that you can follow to capture their product requirements.
Checklists are versatile in nature. Utilizing a checklist before a product's development process begins could eliminate complicated pipeline steps later on. It also enables the interaction of different teams and departments to sustain proper coordination and communication as well as with the client. Here are some of the most important things to keep in mind before the process itself gets initiated in order to capture the client's requirements.
Get in touch with us today to learn about the technologies we use, the process of building an app, our expertise in your industry, and what other clients have to say about development services with Crowdbotics.
Save the script as 'Translate to English' or whatever
Now, right clicking on any highlighted text and selecting 'Translate to English' will open up a new Google Translate page with the highlighted text translated into English.
Hmm, that's weird. And you're working on a widget client script?
Can you try using c.getMessage and see if that works? I usually do translation on server side, so if client side doesn't work you could just use data.prompt = gs.getMessage("messagekey"); since that should be available on the client side then as "c.data.prompt".
My basic understanding is that I would need to save the various website pages from Chrome (or Microsoft Edge) in a HTML format, import these pages in Trados Studio, figure out how many words there are in order to provide a quote, then create a dedicated project, translate and send the output files to the client. Or, politely ask the client the provide the HTML pages they need to translate.
Well... the normal approach doesn't seem very helpful as your client would have to take these strings and recreate the html pages by copy pasting the translations which seems a bit of a waste of time.
Surely if your client is asking you for translated versions of their website they must have some mechanism for putting them somewhere so they get used? Given this they would surely prefer it if they gave you their html pages, you translated these and then sent them back? Seems a lot less work to me.
But if you want to download the entire website... and this means you may actually end up translating work your client didn't even ask for (another good reason to ask them for the files)... the this site seems to have some useful tools:
Once you've downloaded just create a project in Studio, drop all the files and folders into the project, and Studio will manage this for you. When you're done and you save the target project you'll have the same structure but fully translated.
If I got it right, you suggest me that I should receive the HTML pages from the client, save them into a folder, load them in Trados Studio, proceed with the translation as I would normally do with word or excel files, and save the outuput files in HTML format: the client then has just to upload those output files in their website and the job is done?
You got it right... although keep in mind you can have the folder structure the client gives you, no need to separate the files out and put them in a folder. Just making sure you got that right. For example;
aa06259810