Skip to content

Think about pulling this in for the translate API? #970

Closed

Description

@jgeewax

Activity

  1. dhermes commented on Jul 6, 2015

    @dhermes
    Contributor

    Neat!

    As far as calling a discovery-based API, we have all the mechanics in the JSONConnection base class.

  2. added
    type: questionRequest for information or clarification. Not an issue.
    on Dec 31, 2015
  3. dhermes commented on Apr 11, 2016

    @dhermes
    Contributor

    @jgeewax Did you want us to try to pull this in? Or emulate it?

    AFAICT there are only three methods (two of which will be used by a user):

    • language.detections.list: Detect the language of text.
    • language.languages.list: Just list languages supported by the API
    • language.translations.list: Returns text translations from one language to another.

    This should be do-able in a very short amount of work. Maybe @daspecster could get his feet wet here?

    /cc @tseaver

  4. daspecster commented on Apr 11, 2016

    @daspecster
    Contributor

    Looks like it's kind of in disrepair these days.
    https://app.wercker.com/#applications/559a14a31154bc641a014c59

    Could be a good starting point though. I'm game either way!

  5. dhermes commented on Apr 11, 2016

    @dhermes
    Contributor

    I don't think we should pull in that library just start fresh with a new client / connection and maybe a class or two for the relevant nouns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

type: questionRequest for information or clarification. Not an issue.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions