gcloud ml language analyze-syntax

gcloud ml language analyze-syntax - use Google Cloud Natural Language API to identify linguistic information

gcloud ml language analyze-syntax (--content =CONTENT | --content-file =CONTENT_FILE) [--content-type =CONTENT_TYPE; default="plain-text"] [--encoding-type =ENCODING_TYPE; default="utf8"] [--language =LANGUAGE] [GCLOUD_WIDE_FLAG …]

Currently English, Spanish, and Japanese are supported.

gcloudmllanguageanalyze-syntax--content='They drink'

To analyze syntax in file 'myfile.txt':

gcloudmllanguageanalyze-syntax--content-file='myfile.txt'

To analyze syntax in a remote file 'gs://bucket_name/mycontent.html' for Japanese language using UTF-8 encoding:

gcloudmllanguageanalyze-syntax--content-file='gs://bucket_name/mycontent.html'--content-type=HTML--encoding-type=utf8--language=ja-JP

Exactly one of these must be specified:

--content=CONTENT

Specify input text on the command line. Useful for experiments, or for extremely short text.

--content-file=CONTENT_FILE

Specify a local file or Google Cloud Storage (format gs://bucket/object) file path containing the text to be analyzed. More useful for longer text or data output from another system.

--content-type=CONTENT_TYPE; default="plain-text"

Specify the format of the input text. CONTENT_TYPE must be one of: html, plain-text.

--encoding-type=ENCODING_TYPE; default="utf8"

The encoding type used by the API to calculate offsets. If set to none, encoding-dependent offsets will be set at -1. This is an optional flag only used for the entity mentions in results, and does not affect how the input is read or analyzed. ENCODING_TYPE must be one of: none, utf16, utf32, utf8.

--language=LANGUAGE

Specify the language of the input text. If omitted, the server will attempt to auto-detect. Both ISO (such as en or es) and BCP-47 (such as en-US or ja-JP) language codes are accepted.

Run $ gcloud help for details.