API for Contributing to Google Translate [closed] - api

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I want to be able to contribute to Google Translate on my native language (Sinhala).
Although there is an online portal (http://translate.google.com/community/) where we can contribute to the translator by translating new phrases or validating existing translations, I would like to create my own, lightweight portal (maybe an Android app) for the contribution service. However, I was unable to find any public API for the translate contribution platform, despite a thorough Google search and a full search through the Google Translator Toolkit API forum (https://productforums.google.com/forum/m/#!categories/translator-toolkit-api) (which seems to have been closed down since the end of 2012).
Currently my best hope is to mimic the request-response sequence followed by the online portal itself. For example, the following request is used by the online portal to fetch a question list for manual translation:
GET http://translate.google.com/community/question_list?sl=en&tl=si&client=t
However, it requires that all the related cookies are properly initialized and passed with the request, which would probably not be easy to mimic in a non-browser environment (such as an Android app). Hence I believe there's a better approach (maybe a yet undocumented API?) somewhere out there.
Does anyone know of any API for accessing this translation contribution feature?
Thanks in advance.
Please note: I am NOT looking for a way to improve Google Translate itself, but for contributing to the actual translation content as described under "How can I help?" in the Google Translate Community FAQ (https://docs.google.com/document/d/1dwS4CZzgZwmvoB9pAx4A6Yytmv7itk_XE968RMiqpMY/pub#h.e1ahmpftpdum).
P.S. I was initially planning to post this question on the Web Apps Stack Exchange, but after reading this post I decided to first try it here.

I'm one of the engineers behind Translate Community and I'm really excited that you want to see it on more platforms. We're currently under active development of the site and making it more accessible on mobile platforms without having to create dedicated native apps.
For the time being, we don't anticipate releasing a public API as the platform is under active development. Until we do release a public API, please don't use any http commands you find to create a separate app. Instead, just let us know how we can make the app a better experience for you and we'll work on making it better.
Thanks!

Related

centralized API documentation for microservices [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
My team and I are currently building multiple services in parallel. We have the benefit of building all the services from scratch. I would like the ability to automatically display all API endpoints, from all services, in one page/site. This would be helpful because (among other things):
I don't have to go to multiple documentation sites to see what are the available endpoints in my entire "system".
It'll be a good first step to determine if any of the services should be split, combined or simply refactored.
Some of our services are in Django and the rest-swagger module is a great help. But I don't see how I can combine rest-swagger documentation from multiple services into a single documentation page/site.
I'm currently looking through this site and anything related to the Netflix experience but could not find a solution to my problem. Maybe centralized documentation isn't a big deal with 600+ services at Netflix, but that's hard to believe.
Can anyone suggest a tool or method to have a combined API documentation for all services in a microservice architecture?
My ideal scenario of what happens when a service is changed:
I click on the link to see the list of endpoints in my system.
A teammate updates a service and also it's documentation.
I refresh the page I am currently and I see that change made from step #2.
With my exp, you have some paths.
http://readme.io/
Make a wiki with JIRA, Redmine.
In Github create a repo for exclusive docs.
Google Docs.
I don't know about any existing tool rather I'm just putting my thought on where to do it.
From what the OP describe, they are already building a micro services architecture using Netflix stack. There should be a repository to config the name (or URL) for each of the services and the 'config server' or 'service registry' will read from that. To me, that's the perfect place to put the reference to each of the micro-service's documentation under their own entries. This way you get the benefit of maintaining the documentation and code at same place, plus you could potentially also collect run time information like instance/connections count if you hook into the config/registry server.
Being in similar situation I am looking to adopt https://readthedocs.org/ with GIT backed.

How to develop web desktop using ExtJS 4? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I have learned basics of ExtJS and developed some web apps using ExtJS. Now I have to develop web desktop using ExtJS (like desktop app which is present in examples folder) but I am not able to find any documentation or tutorial or book about how to develop it.
Does anyone knows how to develop web desktop application using ExtJS 4? Where can I get any tutorial/ book/ video about developing web desktop?
I doubt you'll find a book or tutorial dedicated to exactly what you're looking for, but you can put together enough resources across the internet to do the trick.
A Google search of "extjs 4 cookbook" turned up a book called "Ext JS 4 Web Application Development Cookbook" that seems to have plenty of information. However, it seems very new and I personally haven't read it, so I can't vouch for it. But it's there.
Other than that, Sencha's own documentation site will have most of what you need. The series of articles on App Architecture may be of some use if you're planning to take the MVC approach, as will the articles on components and layouts.
That will cover the basics, but there's no real definitive guide to making a web desktop app that I'm aware of. It all depends on what your requirements are, how much time you have available, etc. If you're looking for help with a specific component (like creating a Windows-style file browser system) then you'll probably have better luck asking more narrow questions.
You can just use default Web Desktop Sample provided by Sencha and modify it a little bit.
I am also interested in, I did what I advice you, so you can look what I have received now:
http://www.bdovhan.orgfree.com/
Hmmm, these free hosting providers use lot of ads if your site becomes clickable.
I created another mirror, there should be no ads: http://www.julfysoft.16mb.com/index.html
but it can take a while to load it...
We inspired from the desktop sample and we build a full functional web app using Extj 6.7 along with Unigui Framework (Delphi), and the result is awsome:
Just implementing the idea step by step.

Decent Video Chat API? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
Just wondering. I'm looking to build a small web application with a single page. It will essentially be a video chat page so I'm looking for an API I can use or any other solutions?
This would be run on a LAMP stack.
A SO search reveals lots of similar questions which are worth checking/contributing to.
It depends if you want something free or are prepared to pay but some things that come up are (mind I havent used any of these myself):
http://www.tokbox.com/
http://code.google.com/apis/talk/open_communications.html#developer
http://www.process-one.net/en/blogs/article/oneteam_media_server_by_processone
https://sites.google.com/site/webrtc/ (Now at: https://webrtc.org/ )
https://www.skype.com/en/developer/
http://farsight.freedesktop.org/wiki/
https://www.twilio.com/docs/api/video
Some MS libraries are mentioned here: Developing a Video Chat Application with high quality video streaming
Apple had promised to open up FaceTime but so far nothing has happened
To get up and running quickly it seems tokbox would be most suitable.
Look into WebRTC, it's a new technology by Google and doesn't require any plugins! It's still under development but the code is available and working at the moment!
I know it's a bit of advert, but you could try to look into http://www.addlive.com. We offer comprehensive set of APIs allowing you to build RTC apps on the web (JS bindings on top of a plug-in and native WebRTC if available) and native mobile and dekstop SDKs.
Vidyo.io can help with this. (Full disclosure: I work for Vidyo.) It provides a simple JavaScript API that supports WebRTC capable browsers and a plug-in for Safari and IE. We also have sample apps on our github page https://github.com/vidyo to help you create a page simile to what you're looking for.

Text to speech on Quizlet.com [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
How did they implement text to speech (TTS)? Is there an open, free API for TTS synthesis? I know about Google Translate, but the license is not clear to me (another issue is that they block a request if it contains a referrer). Any idea?
Majdron,
I'm a lead developer at Quizlet. We're using a combination of our own technology and licensing/purchasing TTS software from several different companies.
There are some open source TTS engines/voices:
http://www.cstr.ed.ac.uk/projects/festival/
http://www.babelfish.org/tts-free.htm
http://espeak.sourceforge.net/
http://freetts.sourceforge.net/docs/index.php
http://mary.dfki.de/
Good luck!
The voices sound exactly the same as http://www.neospeech.com. Also, their list of languages match exactly.
It's not free, you have to license it.
Google has just introduced browser-based access to its speech engine through HTML5.
http://slides.html5rocks.com/#speech-input
To get this page to work, I launched the Chromium browser as follows in Ubuntu:
$ chromium-browser --enable-speech-input
I'm not sure if this works in other operating systems.
Another interesting project is WAMI from MIT:
http://wami.csail.mit.edu
I don't know which specific engine Quizlet are using, but assuming they are using a free service then it might be TTS-API (http://tts-api.com/) which was recently featured on Hacker News.
From what I know is the only "free-to-use" TTS web-API out there. Please comment below if I'm wrong - I'd love to find similar free services. There are a lot of pay only services out there but very very few truly free ones.
Since finding out about TTS-API on HN I've successfully used it in a recent app project. Since the TTS is only a HTTP fetch away I was able to quickly integrate it in both the iOS and Android versions of my app. The service appears to be very quick, so no complaints so far :-)
Nobody gave the right answer. They have their own TTS engine that is connected to a single file located at http://quizlet.com/tts/en.mp3 the file takes arguments with it so the url http://quizlet.com/tts/en.mp3?v=14&b=QXJlYSBvZiBwYXJhbGxlbG9ncmFt&s=m5dx52Q. says "Area of parallelogram" thanks the first base64 string labeled b. I have not discovered what v or s are used for but I know they are essential for making the file speak. I will do more research and get back to this answer.
jj b is correct. The core engine of Quizlet's speech features is Neospeech, and uses Neospeech's VTML (VoiceText [TM] Markup Language) exactly, as far as I can tell.

Platform Independent Tool for Creating API Documentation / Proposal [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
What tools exist for developing platform indepedent API Documentation?
I'm in the process of designing a proposed API, and want to write documentation in a structured and easily editable way. A lot of the answers I've seen have basically been "Use built in language specific documentation tools", but since I'm designing the API from a 'top-level', rather than implementing it, this isn't so useful. I'm looking for a CMS for API Documentation
I've seen a few suggestions to use PBWiki or Confluence, but I'm not convinced that a plain wiki is the best option, though the version control aspects are nice.
In theory, a Drupal build with CCK for API calls and Views for reading the API, but that's a bit of heavy lifting for what I'm looking for.
Is there a API Documentation Management System out there? What are the best options for writing and managing platform-independent documentation for APIs?
I've seen the related questions for this, but there has yet to be a satisfactory answer.
Any structured text language will do. I'd use latex, and troff is old school.
But you may have missed the point of the suggestion to use doxygen or whatever. If you do that, then writing the documentation is also laying down the scaffold for the eventual implementation. Better still, the example documentation will be in the same format as the eventual real documentation and, you will--of course---use source control on it, won't you? So you'll have a potted history of changes to the spec.