Skip to content

Commit 37b6bb2

Browse files
committed
july freshness
1 parent 74f1996 commit 37b6bb2

26 files changed

+201
-199
lines changed

articles/ai-services/translator/connector/document-translation-flow.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: nitinme
77
ms.service: azure-ai-translator
88
ms.custom: build-2023, build-2023-dataai
99
ms.topic: tutorial
10-
ms.date: 07/18/2023
10+
ms.date: 07/09/2024
1111
ms.author: lajanuar
1212
---
1313

@@ -133,7 +133,7 @@ Next, assign a **`Storage Blob Data Contributor`** role to the managed identity
133133

134134
### Configure a Document Translation flow
135135

136-
Now that you've completed the prerequisites and initial setup, let's get started using the Translator V3 connector to create your document translation flow:
136+
Now that you completed the prerequisites and initial setup, let's get started using the Translator V3 connector to create your document translation flow:
137137

138138
1. Sign in to [Power Automate](https://powerautomate.microsoft.com/).
139139

@@ -181,7 +181,7 @@ Here are the steps to translate a file in Azure Blob Storage using the Translato
181181

182182
* **Translator resource name**. Enter the name of your Translator resource found at the top of your resource page in the Azure portal. Select **Create**.
183183

184-
:::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the add connection window.":::
184+
:::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the how-to-add connection window.":::
185185

186186
> [!NOTE]
187187
> After you've set up your connection, you won't be required to reenter your credentials for subsequent flows.
@@ -190,7 +190,7 @@ Here are the steps to translate a file in Azure Blob Storage using the Translato
190190

191191
* For **Storage type of the input documents**. Select **File** or **Folder**.
192192
* Select a **Source Language** from the dropdown menu or keep the default **Auto-detect** option.
193-
* **Location of the source documents**. Enter the URL for your document(s) in your Azure storage source document container.
193+
* **Location of the source documents**. Enter the URL for your documents in your Azure storage source document container.
194194
* **Location of the translated documents**. Enter the URL for your Azure storage target document container.
195195

196196
To find your source and target URLs:
@@ -209,7 +209,7 @@ Here are the steps to translate a file in Azure Blob Storage using the Translato
209209

210210
## Get documents status
211211

212-
Now that you've submitted your document(s) for translation, let's check the status of the operation.
212+
Now that you submitted your documents for translation, let's check the status of the operation.
213213

214214
1. Select **New step**.
215215

@@ -278,13 +278,13 @@ Here are the steps to upload a file from your SharePoint site to Azure Blob Stor
278278
279279
##### Get file content
280280

281-
1. In the Choose an operation pop-up window, enter **SharePoint**, then select the **Get file content** content. Power Automate automatically signs you into your SharePoint account(s).
281+
1. In the Choose an operation pop-up window, enter **SharePoint**, then select the **Get file content** content. Power Automate automatically signs you into your SharePoint accounts.
282282

283283
:::image type="content" source="../media/connectors/get-file-content.png" alt-text="Screenshot of the SharePoint Get file content action.":::
284284

285285
1. On the **Get file content** step window, complete the following fields:
286286
* **Site Address**. Select the SharePoint site URL where your file is located from the dropdown list.
287-
* **File Identifier**. Select the folder icon and choose the document(s) for translation.
287+
* **File Identifier**. Select the folder icon and choose the documents for translation.
288288

289289
##### Create a storage blob
290290

@@ -300,7 +300,7 @@ Here are the steps to upload a file from your SharePoint site to Azure Blob Stor
300300

301301
1. Choose the Microsoft Entra account associated with your Azure Blob Storage and Translator resource accounts.
302302

303-
1. After you have completed the **Azure Blob Storage** authentication, the **Create blob** step appears. Complete the fields as follows:
303+
1. After you completed the **Azure Blob Storage** authentication, the **Create blob** step appears. Complete the fields as follows:
304304

305305
* **Storage account name or blob endpoint**. Select **Enter custom value** and enter your storage account name.
306306
* **Folder path**. Select the folder icon and select your source document container.
@@ -324,7 +324,7 @@ Here are the steps to upload a file from your SharePoint site to Azure Blob Stor
324324
* **Translator resource name**. Enter the name of your Translator resource found at the top of your resource page in the Azure portal.
325325
* Select **Create**.
326326

327-
:::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the add connection window.":::
327+
:::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the how-to-add connection window.":::
328328

329329
> [!NOTE]
330330
> After you've setup your connection, you won't be required to reenter your credentials for subsequent Translator flows.
@@ -351,7 +351,7 @@ Here are the steps to upload a file from your SharePoint site to Azure Blob Stor
351351

352352
##### Get documents status
353353

354-
Prior to retrieving the documents status, let's schedule a 30-second delay to ensure that the file has been processed for translation:
354+
Before retrieving the documents status, let's schedule a 30-second delay to ensure that the file is processed for translation:
355355

356356
1. Select **New step**. Enter **Schedule** in the search box and choose **Delay**.
357357
* For **Count**. Enter **30**.
@@ -404,7 +404,7 @@ In this step, you retrieve the translated document from Azure Blob Storage and u
404404

405405
1. Select **Add an action**, enter **Azure Blob Storage** in the search box, and select the **Get blob content using path (V2)** action.
406406
1. In the **Storage account name or blob endpoint** field, select **Enter custom value** and enter your storage account name.
407-
1. Select the **Blob path** field to show the **Dynamic content** window, select **Expression** and enter the following logic in the formula field:
407+
1. Select the **Blob path** field to show the **Dynamic content** window, select **Expression**, and enter the following logic in the formula field:
408408

409409
```powerappsfl
410410
@@ -415,7 +415,7 @@ In this step, you retrieve the translated document from Azure Blob Storage and u
415415
1. Select **Add an action**, enter **Azure Blob Storage** in the search box, and select the **Get Blob Metadata using path (V2)** action.
416416
1. In the **Storage account name or blob endpoint** field, select **Enter custom value** and enter your storage account name.
417417

418-
:::image type="content" source="../media/connectors/enter-custom-value.png" alt-text="Screenshot showing 'enter custom value' from the Create blob (V2) window.":::
418+
:::image type="content" source="../media/connectors/enter-custom-value.png" alt-text="Screenshot showing 'enter custom value' from the create-blob-(V2) window.":::
419419

420420
1. Select the **Blob path** field to show the **Dynamic content** window, select **Expression** and enter the following logic in the formula field:
421421

@@ -461,7 +461,7 @@ Let's check your document translation flow and results.
461461

462462
---
463463

464-
That's it! You've learned to automate document translation processes using the Microsoft Translator V3 connector and Power Automate.
464+
That's it! You learned to automate document translation processes using the Microsoft Translator V3 connector and Power Automate.
465465

466466
## Next steps
467467

articles/ai-services/translator/connector/text-translator-flow.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: nitinme
77
ms.service: azure-ai-translator
88
ms.custom: build-2023
99
ms.topic: how-to
10-
ms.date: 07/18/2023
10+
ms.date: 07/10/2024
1111
ms.author: lajanuar
1212
---
1313

@@ -39,7 +39,7 @@ To get started, you need an active Azure subscription. If you don't have an Azu
3939

4040
## Configure the Translator V3 connector
4141

42-
Now that you've completed the prerequisites, let's get started.
42+
Now that you completed the prerequisites, let's get started.
4343

4444
1. Sign in to [Power Automate](https://powerautomate.microsoft.com/).
4545

@@ -76,7 +76,7 @@ Let's select an action. Choose to translate or transliterate text.
7676
* **Subscription Key**. Enter one of your keys that you copied from the Azure portal.
7777
* **Translator resource name**. Enter the name of your Translator resource found at the top of your resource page in the Azure portal. Select **Create**.
7878

79-
:::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the add connection window.":::
79+
:::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the add-connection window.":::
8080

8181
> [!NOTE]
8282
> After you've setup your connection, you won't be required to reenter your credentials for subsequent Translator flows.
@@ -87,7 +87,7 @@ Let's select an action. Choose to translate or transliterate text.
8787
1. Enter the **Body Text**.
8888
1. Select **Save**.
8989

90-
:::image type="content" source="../media/connectors/translate-text-step.png" alt-text="Screenshot showing the translate text step.":::
90+
:::image type="content" source="../media/connectors/translate-text-step.png" alt-text="Screenshot showing the translate-text step.":::
9191

9292
#### [Transliterate text](#tab/transliterate)
9393

@@ -100,15 +100,15 @@ Let's select an action. Choose to translate or transliterate text.
100100
* **Subscription Key**. Enter one of your keys that you copied from the Azure portal.
101101
* **Translator resource name**. Enter the name of your Translator resource found at the top of your resource page in the Azure portal. Select **Create**.
102102

103-
:::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the add connection window.":::
103+
:::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the add-connection window.":::
104104

105105
1. Next, the **Transliterate** action window appears.
106106
1. **Language**. Select the language of the text that is to be converted.
107107
1. **Source script**. Select the name of the input text script.
108108
1. **Target script**. Select the name of transliterated text script.
109109
1. Select **Save**.
110110

111-
:::image type="content" source="../media/connectors/transliterate-text-step.png" alt-text="Screenshot showing the transliterate text step.":::
111+
:::image type="content" source="../media/connectors/transliterate-text-step.png" alt-text="Screenshot showing the transliterate-text step.":::
112112

113113
---
114114

articles/ai-services/translator/containers/deploy-user-managed-glossary.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: laujan
77
manager: nitinme
88
ms.service: azure-ai-translator
99
ms.topic: how-to
10-
ms.date: 08/15/2023
10+
ms.date: 07/10/2024
1111
ms.author: lajanuar
1212
recommendations: false
1313
---

articles/ai-services/translator/custom-translator/concepts/bleu-score.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: laujan
66
manager: nitinme
77
ms.service: azure-ai-translator
88
ms.topic: conceptual
9-
ms.date: 07/18/2023
9+
ms.date: 07/09/2024
1010
ms.author: lajanuar
1111
ms.custom: cogserv-non-critical-translator
1212
#Customer intent: As a Custom Translator user, I want to understand how BLEU score works so that I understand system test outcome better.
@@ -34,7 +34,7 @@ A more extensive discussion of BLEU scores is [here](https://youtu.be/-UqDljMymM
3434

3535
BLEU results depend strongly on the breadth of your domain; consistency of
3636
test, training and tuning data; and how much data you have
37-
available for training. If your models have been trained on a narrow domain, and
37+
available for training. If your models are trained within a narrow domain, and
3838
your training data is consistent with your test data, you can expect a high
3939
BLEU score.
4040

articles/ai-services/translator/custom-translator/concepts/customization.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: laujan
77
manager: nitinme
88
ms.service: azure-ai-translator
99
ms.topic: conceptual
10-
ms.date: 07/18/2023
10+
ms.date: 07/09/2024
1111
ms.author: lajanuar
1212
---
1313

@@ -19,17 +19,17 @@ The feature can also be used to customize speech translation when used with [Azu
1919

2020
## Custom Translator
2121

22-
With Custom Translator, you can build neural translation systems that understand the terminology used in your own business and industry. The customized translation system will then integrate into existing applications, workflows, and websites.
22+
With Custom Translator, you can build neural translation systems that understand the terminology used in your own business and industry. The customized translation system integrates into existing applications, workflows, and websites.
2323

2424
### How does it work?
2525

26-
Use your previously translated documents (leaflets, webpages, documentation, etc.) to build a translation system that reflects your domain-specific terminology and style, better than a standard translation system. Users can upload TMX, XLIFF, TXT, DOCX, and XLSX documents.
26+
Use your previously translated documents (leaflets, webpages, documentation, etc.) to build a translation system that reflects your domain-specific terminology and style, better than a standard translation system. Users can upload `TMX`,`XLIFF`,`TXT`, `DOCX`, and `XLSX` documents.
2727

28-
The system also accepts data that is parallel at the document level but isn't yet aligned at the sentence level. If users have access to versions of the same content in multiple languages but in separate documents, Custom Translator will be able to automatically match sentences across documents. The system can also use monolingual data in either or both languages to complement the parallel training data to improve the translations.
28+
The system also accepts data that is parallel at the document level but isn't yet aligned at the sentence level. If users have access to versions of the same content in multiple languages but in separate documents, Custom Translator os able to automatically match sentences across documents. The system can also use monolingual data in either or both languages to complement the parallel training data to improve the translations.
2929

3030
The customized system is then available through a regular call to Translator using the category parameter.
3131

32-
Given the appropriate type and amount of training data it isn't uncommon to expect gains between 5 and 10, or even more BLEU points on translation quality by using Custom Translator.
32+
Given the appropriate type and amount of training data it isn't uncommon to expect gains between 5 and 10, or even more `BLEU` points on translation quality by using Custom Translator.
3333

3434
More details about the various levels of customization based on available data can be found in the [Custom Translator User Guide](../overview.md).
3535

articles/ai-services/translator/custom-translator/concepts/dictionaries.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: How to create an aligned document that specifies a list of phrases
55
author: laujan
66
manager: nitinme
77
ms.service: azure-ai-translator
8-
ms.date: 07/18/2023
8+
ms.date: 07/09/2024
99
ms.author: lajanuar
1010
ms.topic: conceptual
1111
ms.custom: cogserv-non-critical-translator
@@ -32,11 +32,11 @@ The [neural phrase dictionary](../../neural-dictionary.md) extends our [dynamic
3232

3333
## Sentence dictionary
3434

35-
A sentence dictionary is case-insensitive. The sentence dictionary allows you to specify an exact target translation for a source sentence. For a sentence dictionary match to occur, the entire submitted sentence must match the source dictionary entry. A source dictionary entry that ends with punctuation is ignored during the match. If only a portion of the sentence matches, the entry isn't matched. When a match is detected, the target entry of the sentence dictionary is returned.
35+
A sentence dictionary is case-insensitive. The sentence dictionary allows you to specify an exact target translation for a source sentence. For a sentence dictionary match to occur, the entire submitted sentence must match the source dictionary entry. A source dictionary entry that ends with punctuation is ignored during the match. If only a portion of the sentence matches, the entry isn't matched. When a match is detected, the target entry of the sentence dictionary is returned.
3636

3737
## Dictionary-only trainings
3838

39-
You can train a model using only dictionary data. To do so, select only the dictionary document (or multiple dictionary documents) that you wish to include and select **Create model**. Since this training is dictionary-only, there's no minimum number of training sentences required. Your model typically completes training faster than a standard training. The resulting models use the Microsoft baseline models for translation with the addition of the dictionaries you add. You don't get a test report.
39+
You can train a model using only dictionary data. To do so, select only the dictionary document (or multiple dictionary documents) that you wish to include and select **Create model**. Since this training is dictionary-only, there's no minimum number of training sentences required. Your model typically completes training faster than a standard training. The resulting models use the Microsoft baseline models for translation with the addition of the dictionaries you add. You don't get a test report.
4040

4141
>[!Note]
4242
>Custom Translator doesn't sentence align dictionary files, so it is important that there are an equal number of source and target phrases/sentences in your dictionary documents and that they are precisely aligned.
@@ -47,14 +47,14 @@ You can train a model using only dictionary data. To do so, select only the dict
4747

4848
- The phrase dictionary should be used sparingly. When a phrase within a sentence is replaced, the context of that sentence is lost or limited for translating the rest of the sentence. The result is that, while the phrase or word within the sentence is translated according to the provided dictionary, the overall translation quality of the sentence often suffers.
4949

50-
- The phrase dictionary works well for compound nouns like product names ("_Microsoft SQL Server_"), proper names ("_City of Hamburg_"), or product features ("_pivot table_"). It doesn't work as well for verbs or adjectives because those words are typically highly contextual within the source or target language. The best practice is to avoid phrase dictionary entries for anything but compound nouns.
50+
- The phrase dictionary works well for compound nouns like product names ("_Microsoft SQL Server_"), proper names ("_City of Hamburg_"), or product features ("_pivot table_"). It doesn't work as well for verbs or adjectives because, typically, those words are highly contextual within the source or target language. The best practice is to avoid phrase dictionary entries for anything but compound nouns.
5151

5252
- If you're using a phrase dictionary, capitalization and punctuation are important. Dictionary entries are case- and punctuation-sensitive. Custom Translator only matches words and phrases in the input sentence that use exactly the same capitalization and punctuation marks as specified in the source dictionary file. Also, translations reflect the capitalization and punctuation provided in the target dictionary file.
5353

5454
**Example**
5555

5656
- If you're training an English-to-Spanish system that uses a phrase dictionary and you specify _SQL server_ in the source file and _Microsoft SQL Server_ in the target file. When you request the translation of a sentence that contains the phrase _SQL server_, Custom Translator matches the dictionary entry and the translation that contains _Microsoft SQL Server_.
57-
- When you request translation of a sentence that includes the same phrase but **doesn't** match what is in your source file, such as _sql server_, _sql Server_ or _SQL Server_, it **won't** return a match from your dictionary.
57+
- When you request translation of a sentence that includes the same phrase but **doesn't** match what is in your source file, such as _sql server_, _sql Server_, or _SQL Server_, it **won't** return a match from your dictionary.
5858
- The translation follows the rules of the target language as specified in your phrase dictionary.
5959

6060
- For more information about neural phrase dictionary, _see_ [neural dictionary guidance and recommendations](../../neural-dictionary.md#guidance-and-recommendations).
@@ -63,7 +63,7 @@ You can train a model using only dictionary data. To do so, select only the dict
6363

6464
**Example**
6565

66-
- If your source dictionary contains "_This sentence ends with punctuation!_", then any translation requests containing "_This sentence ends with punctuation_" matches.
66+
- If your source dictionary contains "_This sentence ends with punctuation!_", then any translation requests that contain "_This sentence ends with punctuation_" matches.
6767

6868
- Your dictionary should contain unique source lines. If a source line (a word, phrase, or sentence) appears more than once in a dictionary file, the system always uses the **last entry** provided and return the target when a match is found.
6969

0 commit comments

Comments
 (0)