google-cloud-translate 2.3.0 → 3.0.0

data/CHANGELOG.md

@@ -1,164 +0,0 @@
-# Release History
-
-### 2.3.0 / 2020-03-28
-
-#### Features
-
-* send quota project header in the V2 client
-
-### 2.2.0 / 2020-03-11
-
-#### Features
-
-* Support separate project setting for quota/billing
-
-### 2.1.2 / 2020-03-02
-
-#### Bug Fixes
-
-* support faraday 1.x
-
-### 2.1.1 / 2020-01-23
-
-#### Documentation
-
-* Update copyright year
-* Update Status documentation
-
-### 2.1.0 / 2019-11-06
-
-#### Bug Fixes
-
-* Update minimum runtime dependencies
-  * Fixes an issue where required dependencies may not be used.
-
-### 2.0.0 / 2019-10-28
-
-#### ⚠ BREAKING CHANGES
-
-* Add Translate V3 client
-  * Update google-cloud-translate to contain a generated v3 client
-    as well as the legacy hand-written v2 client.
-  * The following methods now return an instance of
-    Google::Cloud::Translate::V3::TranslationServiceClient:
-    * Google::Cloud#translate
-    * Google::Cloud.translate
-    * Google::Cloud::Translate.new
-  * To use the legacy v2 client specify the version when creating:
-    * v2_client = Google::Cloud::Translate.new version: :v2
-
-#### Features
-
-* Add Translate V3 client
-  * The v3 client includes several new features and updates:
-  * Glossaries - Create a custom dictionary to correctly and
-    consistently translate terms that are customer-specific.
-  * Batch requests - Make an asynchronous request to translate
-    large amounts of text.
-  * AutoML models - Cloud Translation adds support for translating
-    text with custom models that you create using AutoML Translation.
-  * Labels - The Cloud Translation API supports adding user-defined
-    labels (key-value pairs) to requests.
-* Now requires Ruby 2.4 or later.
-
-#### Documentation
-
-* Update the list of GCP environments for automatic authentication
-
-### 1.4.0 / 2019-10-01
-
-#### Features
-
-* Support overriding of service endpoint
-
-### 1.3.1 / 2019-08-23
-
-#### Documentation
-
-* Update documentation
-
-### 1.3.0 / 2019-02-01
-
-* Make use of Credentials#project_id
-  * Use Credentials#project_id
-    If a project_id is not provided, use the value on the Credentials object.
-    This value was added in googleauth 0.7.0.
-  * Loosen googleauth dependency
-    Allow for new releases up to 0.10.
-    The googleauth devs have committed to maintaining the current API
-    and will not make backwards compatible changes before 0.10.
-
-### 1.2.4 / 2018-09-20
-
-* Update documentation.
-  * Change documentation URL to googleapis GitHub org.
-* Fix circular require warning.
-
-### 1.2.3 / 2018-09-12
-
-* Add missing documentation files to package.
-
-### 1.2.2 / 2018-09-10
-
-* Update documentation.
-
-### 1.2.1 / 2018-08-21
-
-* Update documentation.
-
-### 1.2.0 / 2018-02-27
-
-* Support Shared Configuration.
-
-### 1.1.0 / 2017-11-14
-
-* Add `Google::Cloud::Translate::Credentials` class.
-* Rename constructor arguments to `project_id` and `credentials`.
-  (The previous arguments `project` and `keyfile` are still supported.)
-* Document `Google::Auth::Credentials` as `credentials` value.
-* Updated `faraday`, `googleauth` dependencies.
-
-### 1.0.1 / 2017-07-11
-
-* Remove mention of discontinued Premium Edition billing from documentation.
-
-### 1.0.0 / 2017-06-28
-
-* Release 1.0
-
-### 0.23.1 / 2017-05-23
-
-* Fix error handling (adrian-gomez)
-
-### 0.23.0 / 2017-03-31
-
-* No changes
-
-### 0.22.2 / 2016-12-22
-
-* Change product name to Google Cloud Translation API in docs.
-
-### 0.22.1 / 2016-11-16
-
-* Add missing googleauth dependency (frankyn)
-
-### 0.22.0 / 2016-11-14
-
-* Support authentication with service accounts
-* Add `model` parameter to translate method
-* Add `model` attribute to Translation objects
-
-### 0.21.0 / 2016-10-20
-
-* New service constructor Google::Cloud::Translate.new
-
-### 0.20.1 / 2016-09-02
-
-* Fix for timeout on uploads.
-
-### 0.20.0 / 2016-08-26
-
-This gem contains the Google Cloud Translate service implementation for the `google-cloud` gem. The `google-cloud` gem replaces the old `gcloud` gem. Legacy code can continue to use the `gcloud` gem.
-
-* Namespace is now `Google::Cloud`
-* The `google-cloud` gem is now an umbrella package for individual gems

data/CODE_OF_CONDUCT.md

@@ -1,40 +0,0 @@
-# Contributor Code of Conduct
-
-As contributors and maintainers of this project, and in the interest of
-fostering an open and welcoming community, we pledge to respect all people who
-contribute through reporting issues, posting feature requests, updating
-documentation, submitting pull requests or patches, and other activities.
-
-We are committed to making participation in this project a harassment-free
-experience for everyone, regardless of level of experience, gender, gender
-identity and expression, sexual orientation, disability, personal appearance,
-body size, race, ethnicity, age, religion, or nationality.
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery
-* Personal attacks
-* Trolling or insulting/derogatory comments
-* Public or private harassment
-* Publishing other's private information, such as physical or electronic
-  addresses, without explicit permission
-* Other unethical or unprofessional conduct.
-
-Project maintainers have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct. By adopting this Code of Conduct, project
-maintainers commit themselves to fairly and consistently applying these
-principles to every aspect of managing this project. Project maintainers who do
-not follow or enforce the Code of Conduct may be permanently removed from the
-project team.
-
-This code of conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community.
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by opening an issue or contacting one or more of the project
-maintainers.
-
-This Code of Conduct is adapted from the [Contributor
-Covenant](http://contributor-covenant.org), version 1.2.0, available at
-[http://contributor-covenant.org/version/1/2/0/](http://contributor-covenant.org/version/1/2/0/)

data/CONTRIBUTING.md

@@ -1,188 +0,0 @@
-# Contributing to Google Cloud Translation
-
-1. **Sign one of the contributor license agreements below.**
-2. Fork the repo, develop and test your code changes.
-3. Send a pull request.
-
-## Contributor License Agreements
-
-Before we can accept your pull requests you'll need to sign a Contributor
-License Agreement (CLA):
-
-- **If you are an individual writing original source code** and **you own the
-  intellectual property**, then you'll need to sign an [individual
-  CLA](https://developers.google.com/open-source/cla/individual).
-- **If you work for a company that wants to allow you to contribute your work**,
-  then you'll need to sign a [corporate
-  CLA](https://developers.google.com/open-source/cla/corporate).
-
-You can sign these electronically (just scroll to the bottom). After that, we'll
-be able to accept your pull requests.
-
-## Setup
-
-In order to use the google-cloud-translate console and run the project's tests,
-there is a small amount of setup:
-
-1. Install Ruby. google-cloud-translate requires Ruby 2.4+. You may choose to
-   manage your Ruby and gem installations with [RVM](https://rvm.io/),
-   [rbenv](https://github.com/rbenv/rbenv), or
-   [chruby](https://github.com/postmodern/chruby).
-
-2. Install [Bundler](http://bundler.io/).
-
-   ```sh
-   $ gem install bundler
-   ```
-
-3. Install the top-level project dependencies.
-
-   ```sh
-   $ bundle install
-   ```
-
-4. Install the Translation dependencies.
-
-   ```sh
-   $ cd google-cloud-translate/
-   $ bundle exec rake bundleupdate
-   ```
-
-## Console
-
-In order to run code interactively, you can automatically load
-google-cloud-translate and its dependencies in IRB. This requires that your
-developer environment has already been configured by following the steps
-described in the {file:AUTHENTICATION.md Authentication Guide}. An IRB console
-can be created with:
-
-```sh
-$ cd google-cloud-translate/
-$ bundle exec rake console
-```
-
-## Translation Tests
-
-Tests are very important part of google-cloud-translate. All contributions
-should include tests that ensure the contributed code behaves as expected.
-
-To run the unit tests, documentation tests, and code style checks together for a
-package:
-
-``` sh
-$ cd google-cloud-translate/
-$ bundle exec rake ci
-```
-
-To run the command above, plus all acceptance tests, use `rake ci:acceptance` or
-its handy alias, `rake ci:a`.
-
-### Translation Unit Tests
-
-
-The project uses the [minitest](https://github.com/seattlerb/minitest) library,
-including [specs](https://github.com/seattlerb/minitest#specs),
-[mocks](https://github.com/seattlerb/minitest#mocks) and
-[minitest-autotest](https://github.com/seattlerb/minitest-autotest).
-
-To run the Translation unit tests:
-
-``` sh
-$ cd google-cloud-translate/
-$ bundle exec rake test
-```
-
-### Translation Documentation Tests
-
-The project tests the code examples in the gem's
-[YARD](https://github.com/lsegal/yard)-based documentation.
-
-The example testing functions in a way that is very similar to unit testing, and
-in fact the library providing it,
-[yard-doctest](https://github.com/p0deje/yard-doctest), is based on the
-project's unit test library, [minitest](https://github.com/seattlerb/minitest).
-
-To run the Translation documentation tests:
-
-``` sh
-$ cd google-cloud-translate/
-$ bundle exec rake doctest
-```
-
-If you add, remove or modify documentation examples when working on a pull
-request, you may need to update the setup for the tests. The stubs and mocks
-required to run the tests are located in `support/doctest_helper.rb`. Please
-note that much of the setup is matched by the title of the
-[`@example`](http://www.rubydoc.info/gems/yard/file/docs/Tags.md#example) tag.
-If you alter an example's title, you may encounter breaking tests.
-
-### Translation Acceptance Tests
-
-The Translation acceptance tests interact with the live service API. Follow the
-instructions in the {file:AUTHENTICATION.md Authentication guide} for enabling
-the Translation API. Occasionally, some API features may not yet be generally
-available, making it difficult for some contributors to successfully run the
-entire acceptance test suite. However, please ensure that you do successfully
-run acceptance tests for any code areas covered by your pull request.
-
-To run the acceptance tests, first create and configure a project in the Google
-Developers Console, as described in the {file:AUTHENTICATION.md Authentication
-guide}. Be sure to download the JSON KEY file. Make note of the PROJECT_ID and
-the KEYFILE location on your system.
-
-Before you can run the Translation acceptance tests, you must first create indexes
-used in the tests.
-
-#### Running the Translation acceptance tests
-
-To run the Translation acceptance tests:
-
-``` sh
-$ cd google-cloud-translate/
-$ bundle exec rake acceptance[\\{my-project-id},\\{/path/to/keyfile.json}]
-```
-
-Or, if you prefer you can store the values in the `GCLOUD_TEST_PROJECT` and
-`GCLOUD_TEST_KEYFILE` environment variables:
-
-``` sh
-$ cd google-cloud-translate/
-$ export GCLOUD_TEST_PROJECT=\\{my-project-id}
-$ export GCLOUD_TEST_KEYFILE=\\{/path/to/keyfile.json}
-$ bundle exec rake acceptance
-```
-
-If you want to use a different project and credentials for acceptance tests, you
-can use the more specific `TRANSLATE_TEST_PROJECT`  and `TRANSLATE_TEST_KEYFILE`
-environment variables:
-
-``` sh
-$ cd google-cloud-translate/
-$ export TRANSLATE_TEST_PROJECT=\\{my-project-id}
-$ export TRANSLATE_TEST_KEYFILE=\\{/path/to/keyfile.json}
-$ bundle exec rake acceptance
-```
-
-## Coding Style
-
-Please follow the established coding style in the library. The style is is
-largely based on [The Ruby Style
-Guide](https://github.com/bbatsov/ruby-style-guide) with a few exceptions based
-on seattle-style:
-
-* Avoid parenthesis when possible, including in method definitions.
-* Always use double quotes strings. ([Option
-  B](https://github.com/bbatsov/ruby-style-guide#strings))
-
-You can check your code against these rules by running Rubocop like so:
-
-```sh
-$ cd google-cloud-translate/
-$ bundle exec rake rubocop
-```
-
-## Code of Conduct
-
-Please note that this project is released with a Contributor Code of Conduct. By
-participating in this project you agree to abide by its terms. See
-{file:CODE_OF_CONDUCT.md Code of Conduct} for more information.

data/LICENSE

@@ -1,201 +0,0 @@
-                            Apache License
-                           Version 2.0, January 2004
-                        https://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       https://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.