Reference documentation and code samples for the Cloud Translation V3 Client class ListGlossariesRequest.
Request message for ListGlossaries.
Generated from protobuf messagegoogle.cloud.translation.v3.ListGlossariesRequest
Namespace
Google \ Cloud \ Translate \ V3
Methods
__construct
Constructor.
Parameters
Name
Description
data
array
Optional. Data for populating the Message object.
↳ parent
string
Required. The name of the project from which to list all of the glossaries.
↳ page_size
int
Optional. Requested page size. The server may return fewer glossaries than requested. If unspecified, the server picks an appropriate default.
↳ page_token
string
Optional. A token identifying a page of results the server should return. Typically, this is the value of [ListGlossariesResponse.next_page_token] returned from the previous call toListGlossariesmethod. The first page is returned ifpage_tokenis empty or missing.
↳ filter
string
Optional. Filter specifying constraints of a list operation. Specify the constraint by the format of "key=value", where key must be "src" or "tgt", and the value must be a valid language code. For multiple restrictions, concatenate them by "AND" (uppercase only), such as: "src=en-US AND tgt=zh-CN". Notice that the exact match is used here, which means using 'en-US' and 'en' can lead to different results, which depends on the language code you used when you create the glossary. For the unidirectional glossaries, the "src" and "tgt" add restrictions on the source and target language code separately. For the equivalent term set glossaries, the "src" and/or "tgt" add restrictions on the term set. For example: "src=en-US AND tgt=zh-CN" will only pick the unidirectional glossaries which exactly match the source language code as "en-US" and the target language code "zh-CN", but all equivalent term set glossaries which contain "en-US" and "zh-CN" in their language set will be picked. If missing, no filtering is performed.
getParent
Required. The name of the project from which to list all of the glossaries.
Returns
Type
Description
string
setParent
Required. The name of the project from which to list all of the glossaries.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getPageSize
Optional. Requested page size. The server may return fewer glossaries than
requested. If unspecified, the server picks an appropriate default.
Returns
Type
Description
int
setPageSize
Optional. Requested page size. The server may return fewer glossaries than
requested. If unspecified, the server picks an appropriate default.
Parameter
Name
Description
var
int
Returns
Type
Description
$this
getPageToken
Optional. A token identifying a page of results the server should return.
Typically, this is the value of [ListGlossariesResponse.next_page_token]
returned from the previous call toListGlossariesmethod.
The first page is returned ifpage_tokenis empty or missing.
Returns
Type
Description
string
setPageToken
Optional. A token identifying a page of results the server should return.
Typically, this is the value of [ListGlossariesResponse.next_page_token]
returned from the previous call toListGlossariesmethod.
The first page is returned ifpage_tokenis empty or missing.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getFilter
Optional. Filter specifying constraints of a list operation.
Specify the constraint by the format of "key=value", where key must be
"src" or "tgt", and the value must be a valid language code.
For multiple restrictions, concatenate them by "AND" (uppercase only),
such as: "src=en-US AND tgt=zh-CN". Notice that the exact match is used
here, which means using 'en-US' and 'en' can lead to different results,
which depends on the language code you used when you create the glossary.
For the unidirectional glossaries, the "src" and "tgt" add restrictions
on the source and target language code separately.
For the equivalent term set glossaries, the "src" and/or "tgt" add
restrictions on the term set.
For example: "src=en-US AND tgt=zh-CN" will only pick the unidirectional
glossaries which exactly match the source language code as "en-US" and the
target language code "zh-CN", but all equivalent term set glossaries which
contain "en-US" and "zh-CN" in their language set will be picked.
If missing, no filtering is performed.
Returns
Type
Description
string
setFilter
Optional. Filter specifying constraints of a list operation.
Specify the constraint by the format of "key=value", where key must be
"src" or "tgt", and the value must be a valid language code.
For multiple restrictions, concatenate them by "AND" (uppercase only),
such as: "src=en-US AND tgt=zh-CN". Notice that the exact match is used
here, which means using 'en-US' and 'en' can lead to different results,
which depends on the language code you used when you create the glossary.
For the unidirectional glossaries, the "src" and "tgt" add restrictions
on the source and target language code separately.
For the equivalent term set glossaries, the "src" and/or "tgt" add
restrictions on the term set.
For example: "src=en-US AND tgt=zh-CN" will only pick the unidirectional
glossaries which exactly match the source language code as "en-US" and the
target language code "zh-CN", but all equivalent term set glossaries which
contain "en-US" and "zh-CN" in their language set will be picked.
If missing, no filtering is performed.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
static::build
Parameter
Name
Description
parent
string
Required. The name of the project from which to list all of the glossaries. Please seeTranslationServiceClient::locationName()for help formatting this field.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Cloud Translation V3 Client - Class ListGlossariesRequest (2.0.3)\n\nVersion latestkeyboard_arrow_down\n\n- [2.0.3 (latest)](/php/docs/reference/cloud-translate/latest/V3.ListGlossariesRequest)\n- [2.0.2](/php/docs/reference/cloud-translate/2.0.2/V3.ListGlossariesRequest)\n- [1.21.0](/php/docs/reference/cloud-translate/1.21.0/V3.ListGlossariesRequest)\n- [1.20.2](/php/docs/reference/cloud-translate/1.20.2/V3.ListGlossariesRequest)\n- [1.19.0](/php/docs/reference/cloud-translate/1.19.0/V3.ListGlossariesRequest)\n- [1.18.1](/php/docs/reference/cloud-translate/1.18.1/V3.ListGlossariesRequest)\n- [1.17.7](/php/docs/reference/cloud-translate/1.17.7/V3.ListGlossariesRequest)\n- [1.16.0](/php/docs/reference/cloud-translate/1.16.0/V3.ListGlossariesRequest)\n- [1.15.4](/php/docs/reference/cloud-translate/1.15.4/V3.ListGlossariesRequest)\n- [1.14.3](/php/docs/reference/cloud-translate/1.14.3/V3.ListGlossariesRequest)\n- [1.13.3](/php/docs/reference/cloud-translate/1.13.3/V3.ListGlossariesRequest)\n- [1.12.12](/php/docs/reference/cloud-translate/1.12.12/V3.ListGlossariesRequest) \nReference documentation and code samples for the Cloud Translation V3 Client class ListGlossariesRequest.\n\nRequest message for ListGlossaries.\n\nGenerated from protobuf message `google.cloud.translation.v3.ListGlossariesRequest`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Translate \\\\ V3\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getParent\n\nRequired. The name of the project from which to list all of the glossaries.\n\n### setParent\n\nRequired. The name of the project from which to list all of the glossaries.\n\n### getPageSize\n\nOptional. Requested page size. The server may return fewer glossaries than\nrequested. If unspecified, the server picks an appropriate default.\n\n### setPageSize\n\nOptional. Requested page size. The server may return fewer glossaries than\nrequested. If unspecified, the server picks an appropriate default.\n\n### getPageToken\n\nOptional. A token identifying a page of results the server should return.\n\nTypically, this is the value of \\[ListGlossariesResponse.next_page_token\\]\nreturned from the previous call to `ListGlossaries` method.\nThe first page is returned if `page_token`is empty or missing.\n\n### setPageToken\n\nOptional. A token identifying a page of results the server should return.\n\nTypically, this is the value of \\[ListGlossariesResponse.next_page_token\\]\nreturned from the previous call to `ListGlossaries` method.\nThe first page is returned if `page_token`is empty or missing.\n\n### getFilter\n\nOptional. Filter specifying constraints of a list operation.\n\nSpecify the constraint by the format of \"key=value\", where key must be\n\"src\" or \"tgt\", and the value must be a valid language code.\nFor multiple restrictions, concatenate them by \"AND\" (uppercase only),\nsuch as: \"src=en-US AND tgt=zh-CN\". Notice that the exact match is used\nhere, which means using 'en-US' and 'en' can lead to different results,\nwhich depends on the language code you used when you create the glossary.\nFor the unidirectional glossaries, the \"src\" and \"tgt\" add restrictions\non the source and target language code separately.\nFor the equivalent term set glossaries, the \"src\" and/or \"tgt\" add\nrestrictions on the term set.\nFor example: \"src=en-US AND tgt=zh-CN\" will only pick the unidirectional\nglossaries which exactly match the source language code as \"en-US\" and the\ntarget language code \"zh-CN\", but all equivalent term set glossaries which\ncontain \"en-US\" and \"zh-CN\" in their language set will be picked.\nIf missing, no filtering is performed.\n\n### setFilter\n\nOptional. Filter specifying constraints of a list operation.\n\nSpecify the constraint by the format of \"key=value\", where key must be\n\"src\" or \"tgt\", and the value must be a valid language code.\nFor multiple restrictions, concatenate them by \"AND\" (uppercase only),\nsuch as: \"src=en-US AND tgt=zh-CN\". Notice that the exact match is used\nhere, which means using 'en-US' and 'en' can lead to different results,\nwhich depends on the language code you used when you create the glossary.\nFor the unidirectional glossaries, the \"src\" and \"tgt\" add restrictions\non the source and target language code separately.\nFor the equivalent term set glossaries, the \"src\" and/or \"tgt\" add\nrestrictions on the term set.\nFor example: \"src=en-US AND tgt=zh-CN\" will only pick the unidirectional\nglossaries which exactly match the source language code as \"en-US\" and the\ntarget language code \"zh-CN\", but all equivalent term set glossaries which\ncontain \"en-US\" and \"zh-CN\" in their language set will be picked.\nIf missing, no filtering is performed.\n\n### static::build"]]
