You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -513,7 +509,6 @@ To view the entire output, visit the Azure samples repository on GitHub to view
513
509
**Add the following code sample to the `FormRecognizer.java` file. Make sure you update the key and endpoint variables with values from your Azure portal Document Intelligence instance:**
@@ -641,7 +636,6 @@ Analyze and extract common fields from specific document types using a prebuilt
641
636
**Add the following code sample to the `DocIntelligence.java` file. Make sure you update the key and endpoint variables with values from your Azure portal Document Intelligence instance:**
@@ -1023,7 +1015,6 @@ To view the entire output, visit the Azure samples repository on GitHub to view
1023
1015
**Add the following code sample to the `FormRecognizer.java` file. Make sure you update the key and endpoint variables with values from your Azure portal Document Intelligence instance:**
_See_[**Virtual Network Support**](v3-0-reference.md#virtual-network-support) for Translator service selected network and private endpoint configuration and support.
36
+
For more information, _see_[**Virtual Network Support**](v3-0-reference.md#virtual-network-support) for Translator service selected network and private endpoint configuration and support.
30
37
31
38
## Request parameters
32
39
@@ -43,14 +50,14 @@ Request headers are:
43
50
44
51
|Headers|Description|
45
52
|---|---|
46
-
|Accept-Language|**Optional request header**.<br><br>The language to use for user interface strings. Some of the fields in the response are names of languages or names of regions. Use this parameter to define the language in which these names are returned. The language is specified by providing a well-formed BCP 47 language tag. For instance, use the value `fr` to request names in French or use the value `zh-Hant` to request names in Chinese Traditional.<br/>Names are provided in the English language when a target language isn't specified or when localization isn't available.|
53
+
|Accept-Language|**Optional request header**.<br><br>The language to use for user interface strings. Some of the fields in the response are names of languages or names of regions. Use this parameter to define the language in which these names are returned. The language is specified by providing a well-formed `BCP` 47 language tag. For instance, use the value `fr` to request names in French or use the value `zh-Hant` to request names in Chinese Traditional.<br/>Names are provided in the English language when a target language isn't specified or when localization isn't available.|
47
54
|X-ClientTraceId|**Optional request header**.<br>A client-generated GUID to uniquely identify the request.|
48
55
49
56
Authentication isn't required to get language resources.
50
57
51
58
## Response body
52
59
53
-
A client uses the `scope` query parameter to define which groups of languages it's interested in.
60
+
A client uses the `scope` query parameter to define which groups of languages to list.
54
61
55
62
*`scope=translation` provides languages supported to translate text from one language to another language;
56
63
@@ -80,7 +87,7 @@ The value for each property is as follows.
80
87
81
88
*`translation` property
82
89
83
-
The value of the `translation` property is a dictionary of (key, value) pairs. Each key is a BCP 47 language tag. A key identifies a language for which text can be translated to or translated from. The value associated with the key is a JSON object with properties that describe the language:
90
+
The value of the `translation` property is a dictionary of (key, value) pairs. Each key is a `BCP` 47 language tag. A key identifies a language for which text can be translated to or translated from. The value associated with the key is a JSON object with properties that describe the language:
84
91
85
92
*`name`: Display name of the language in the locale requested via `Accept-Language` header.
86
93
@@ -106,7 +113,7 @@ The value for each property is as follows.
106
113
107
114
*`transliteration` property
108
115
109
-
The value of the `transliteration` property is a dictionary of (key, value) pairs. Each key is a BCP 47 language tag. A key identifies a language for which text can be converted from one script to another script. The value associated with the key is a JSON object with properties that describe the language and its supported scripts:
116
+
The value of the `transliteration` property is a dictionary of (key, value) pairs. Each key is a `BCP` 47 language tag. A key identifies a language for which text can be converted from one script to another script. The value associated with the key is a JSON object with properties that describe the language and its supported scripts:
110
117
111
118
*`name`: Display name of the language in the locale requested via `Accept-Language` header.
112
119
@@ -171,7 +178,7 @@ The value for each property is as follows.
171
178
172
179
*`dictionary` property
173
180
174
-
The value of the `dictionary` property is a dictionary of (key, value) pairs. Each key is a BCP 47 language tag. The key identifies a language for which alternative translations and back-translations are available. The value is a JSON object that describes the source language and the target languages with available translations:
181
+
The value of the `dictionary` property is a dictionary of (key, value) pairs. Each key is a `BCP` 47 language tag. The key identifies a language for which alternative translations and back-translations are available. The value is a JSON object that describes the source language and the target languages with available translations:
175
182
176
183
*`name`: Display name of the source language in the locale requested via `Accept-Language` header.
177
184
@@ -209,7 +216,7 @@ The value for each property is as follows.
209
216
210
217
The structure of the response object doesn't change without a change in the version of the API. For the same version of the API, the list of available languages may change over time because Microsoft Translator continually extends the list of languages supported by its services.
211
218
212
-
The list of supported languages doesn't change frequently. To save network bandwidth and improve responsiveness, a client application should consider caching language resources and the corresponding entity tag (`ETag`). Then, the client application can periodically (for example, once every 24 hours) query the service to fetch the latest set of supported languages. Passing the current `ETag` value in an `If-None-Match` header field allows the service to optimize the response. If the resource hasn't been modified, the service returns status code 304 and an empty response body.
219
+
The list of supported languages doesn't change frequently. To save network bandwidth and improve responsiveness, a client application should consider caching language resources and the corresponding entity tag (`ETag`). Then, the client application can periodically (for example, once every 24 hours) query the service to fetch the latest set of supported languages. Passing the current `ETag` value in an `If-None-Match` header field allows the service to optimize the response. If the resource isn't modified, the service returns status code 304 and an empty response body.
213
220
214
221
## Response headers
215
222
@@ -225,9 +232,9 @@ The following are the possible HTTP status codes that a request returns.
225
232
|Status Code|Description|
226
233
|--- |--- |
227
234
|200|Success.|
228
-
|304|The resource hasn't been modified since the version specified by request headers `If-None-Match`.|
235
+
|304|The resource isn't modified and aligns with the version specified by request headers `If-None-Match`.|
229
236
|400|One of the query parameters is missing or not valid. Correct request parameters before retrying.|
230
-
|429|The server rejected the request because the client has exceeded request limits.|
237
+
|429|The server rejected the request because the client exceeded request limits.|
231
238
|500|An unexpected error occurred. If the error persists, report it with: date and time of the failure, request identifier from response header `X-RequestId`, and client identifier from request header `X-ClientTraceId`.|
232
239
|503|Server temporarily unavailable. Retry the request. If the error persists, report it with: date and time of the failure, request identifier from response header `X-RequestId`, and client identifier from request header `X-ClientTraceId`.|
0 commit comments