Skip to content

Commit b02df23

Browse files
authored
Clarification for translation skill behavior
All documents in the source will be processed for translation, even if the document language is the same as the required target language.
1 parent 26f3673 commit b02df23

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/search/cognitive-search-skill-text-translation.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: careyjmac
88
ms.author: chalton
99
ms.service: cognitive-search
1010
ms.topic: reference
11-
ms.date: 08/12/2021
11+
ms.date: 09/16/2022
1212
---
1313

1414
# Text Translation cognitive skill
@@ -21,6 +21,8 @@ The [Translator Text API v3.0](../cognitive-services/translator/reference/v3-0-r
2121

2222
> [!NOTE]
2323
> This skill is bound to Cognitive Services and requires [a billable resource](cognitive-search-attach-cognitive-services.md) for transactions that exceed 20 documents per indexer per day. Execution of built-in skills is charged at the existing [Cognitive Services pay-as-you go price](https://azure.microsoft.com/pricing/details/cognitive-services/).
24+
>
25+
> When using this skill, take into consideration that all documents in the source will be processed for translation, even if the source document language is the same as the required target language. This is useful for multi-language support within the same document. However, keep this in mind when planning for your source location data, to avoid unexpected billing charges from documents that didn't need to be processed for translation.
2426
>
2527
2628
## @odata.type
@@ -146,4 +148,4 @@ If your text is larger than 50,000 characters, only the first 50,000 characters
146148
## See also
147149

148150
+ [Built-in skills](cognitive-search-predefined-skills.md)
149-
+ [How to define a skillset](cognitive-search-defining-skillset.md)
151+
+ [How to define a skillset](cognitive-search-defining-skillset.md)

0 commit comments

Comments
 (0)