I searched for an API which takes a document as an input and translates that document into a specified language but I'm unable able to find such an API.
I know Google provides an API to translate text but here I need to translate a whole document and return it translated. Please let me know if any API like this is available.
You might want to look into the Pairaphrase translation API.
It will translate documents (and other files) from one language into another.
Just note that Pairaphrase is really meant to be used as a translation productivity tool for businesses. It won't give you perfect translation.
Instead, it facilitates secure, high-quality translation by doing the following.
It uses machine translation and translation memory to translate your files quickly (as a 1st draft).
Then, it's up to the user to share (using the "share" feature inside Pairaphrase) the translated files with bilingual users inside and/or outside their organizations to edit the translations within Pairaphrase.
When this is done correctly, Pairaphrase learns human-translated words and phrases so that you never need to translate the same phrases or sentences twice.
All translation data is encrypted and two-factor authentication is available to provide data security.
They have a demo video that you can check out. This will give you a feel for the functionality and if this translation API is right for you.
Related
I feel like this is a simple enough thing to do and can't believe how hard of a time I'm having finding the example I need so alas, human help please! You failed me Google :)
FYI I've written a bit of code in my life (Java, C, ASM, PHP), new to APIs.
As the title lays bare, I want to retrieve info (tickets out of our ticketing system meeting certain conditions) via a GET request, loop through each ticket, and update each one (PUT) based on certain conditions.
If there's a tutorial you know of that covers that, please point me to it! If not, if you could please fill in some of these holes?
I wound up in Postman, is this an appropriate environment to accomplish such? Of course you can make individual API calls here but I got lost trying to string the aforementioned sequence together. Is it possible via "Create API?" This makes it sound like I'm creating my own API server for other users to access data from. If it is possible via "Create API," where's the dang run code button?! If not Postman, what tool should I be using to write code in? And again, if you have any code samples/videos closely resembling said scenario for that tool.
Thank you for any assistance you can offer.
Cheers,
Jay
You want to interact with your ticketing system: read existing tickets, and update them. Correct?
To do this, your TICKETING SYSTEM must have an "api" (possibly - but not necessarily - a REST API).
If it does, you might be in luck. But you need to learn the API first, possibly from product documentation. If it doesn't, there's probably not much you can do except to interact with the system as a "normal user".
If it has an API, and if it's a relatively simple API (like REST), you can use the API manually (e.g. through POSTMAN), or you can use it programmatically (using Python, C#, Java or just about any programming language you feel comfortable with).
In summary, you need to:
Determine if your ticketing system provides any kind of web api
If so, get the API details
If at that point you want proceed, determine what programming language or framework you'd like to use.
Hopefully that gives you a bit of "direction".
Just as one is able to use various speech-to-text 'dictation' tools to convert spoken word into its corresponding text, I would like to know if there are similar such tools for converting spoken word into its corresponding SSML. That is, it will provide the text in addition to the relevant SSML tags associated with any intonation, prosody, pauses/breaks, inflection, etc... present in the speaker's voice.
I work on building Voice apps. In a recent project I was working on, we needed the text to sound exactly right, with all the associated intonations, prosody, pauses/breaks, inflection, etc.
On extensive research, we found that the only way to make the text sound like being spoken by a real person is either to use SSML (still not perfect) or a recorded mp3.
If you're trying to get the real person feel for a project, the best way to execute it is to utilize a human. I would suggest you record the mp3 (/get it recorded by a professional) instead of trying to get SSML from voice.
The reason we use SSML is exactly that computers cannot understand the associated intonations, prosody, pauses/breaks, inflection, etc. of human speech.
If your goal is to get SSML, then the best way would be to convert text to SSML. For this, I'd suggest taking a peek here:
W3C SSML
Google SSML
Amazon SSML
This is to the best of our knowledge # mid July 2018.
If anyone has more info please feel to add to this answer.
Hope this helps :3
When I use the Google Translate web tool it breaks the translated result into short phrases and offers alternate translations for each phrase. When I read the Translate API Reference it appears that if I use the API I can only get a single translation. I want a lot of alternate translation information. Is there any way I can do this? I am willing to pay for the API, I just need this functionality.
No, in this moment there is no way to get an alternate translation through Google Translation API.
When should one develop HATEOAS server RESTful API instead of using HTML (resource links, forms, etc.)?
Isn't HTML and a browser good enough as hypermedia engine?
Isn't HTML and a browser good enough as hypermedia engine?
HTML + HTTP + URI + Browser === The world wide web. So it's pretty good, no joke.
It's not without fault.
HTML's understanding of links is disappointingly limited. No support for idempotent writes. Uri Template support for GET only. I'm not super keen on how many different spellings there are for "link".
It's kind of verbose for a hypermedia format; don't get me wrong - built in text markup is brilliant when you are trying to document what is going on for a human being. But my impression thus far is that same structure starts to get in the way when as a human being you want to quickly review the semantic content that your automated agent is consuming.
I call your attention to this quote from RFC-4287
The primary use case that Atom addresses is the syndication of Web content such as weblogs and news headlines to Web sites as well as directly to user agents.
So a bunch of really smart guys, specifically trying to address use cases directly related to the web, decided to invest a bunch of effort into standardizing a new hypermedia format rather than using the one that was already ubiquitous in their problem domain.
And over the past 10+ years, that format has been widely adopted.
Without adoption, I'm not sure that HATEOAS has much benefit. You don't need a hypermedia api if you are controlling both sides of the conversation (example: javascript on the web -- hypermedia with code on demand capability downloading a client that has learned the protocol of a web api via some out of band channel).
Evidence would seem to suggest that HTML is not nearly as convenient a format as, for example, any of the JSON based hypermedia formats.
In conclusion: no, it's not good enough. It might be an acceptable place holder for the moment; but the JSON hypermedia tool sets are soon going to be sufficiently mature that HTML will be seen as a giant step in the wrong direction.
Everyone. Recently Google Translate Is Integrated Into My Project, Which Plays The Role Of Translating Some Product Names, Product Descriptions, Product Related Category Names. But Cause There Are Plenty Of Products In My Database(And Increased Quickly), Google Translate Api Would Cost Considerable Money.
I Want To Translate By Google As Less As Possible. In The Translation, Many Words Are Same Among Many Products, For Example : 阿迪达斯 - Adidas, 苹果 - iphone, 篮球 - Basketball, Bla Bla..... I Wanna Do Some Tricks, But Find No Idea.
Did Anyone Encounter Such Questions?
Any Help Would Be Appreciated.
It sounds like what you need is actually the ability to reuse translation at the string or substring level (in other words, per database entry). You can't really do that with Google, that I know of. You've got a few options, as I see it:
You could switch over to Microsoft Translator and use their methods
that allow you to place translations yourself, such as their
Collaborative Translation feature that lets you override the MT with
a preferred translation and even to vote translations up/down. Quality here will be broadly comparable to Google (I often find it better), and you have methods at your disposal that allow this override. Also, unlike Google, the Microsoft API is free up to a certain volume. Take a look:
http://www.microsoft.com/en-us/translator/developers.aspx
Microsoft also has a unique feature called the Microsoft Translator Hub, which can use your terminology, for example, for translations. However,depending on how you implemented any solution with Microsoft, you might still have the problem that you are making more calls out to Microsoft than you'd like, and, moreover, that "matching" only takes place at the level of a whole record or string, so it would not hit the case of shared linguistic elements being concatenated into one string.
There's a commercial offering called GeoFluent (full disclosure--I am the product manager for this product, so I'm clearly biased :)) that works with Microsoft Translator but provides pre and post translation processing that can deal with sub-segment and may reduce the volume you are therefore putting through translation each time. It could make sense if, as you mention, you are rapidly adding to your database. Of course, this is a commercial offering too, so you'd have to balance the costs.
Let me know if this helps, and happy to answer any other questions you have.
Marcus
There is a PHP sample here : http://weblite.ca/svn/dataface/modules/tm/trunk/lib/googleTranslatePlugin.php
That allows you to send and array and return an array.
array(source=>target) getTranslations()
translates all of the user provided strings into the target language using the Google Translate API and returns an array of source=>target
strings.