vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 MQ ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 Messages for RabbitMQ ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) !
Use [this method](https://cloud.ibm.com/apidocs/log-analysisget-v1-config-stream-exclusions) to list existing streaming exclusion rules.

curl --request GET https://api.eu-gb.logging.cloud.ibm.com/v1/config/stream/exclusions
-H "content-type: application/json"
-H "servicekey: <SERVICE_KEY>"

The response will be similar to the following:

[{"hosts":],"apps":],"title":"Exclude Rule 1","query":"host:iam-am (action read)","active":true,"id":"xxxxxxxxxx"}]





 Get details about a streaming exclusion rule 

Use [this method](https://cloud.ibm.com/apidocs/log-analysisget-v1-config-stream-exclusions-rule-id) to get details of an existing streaming exclusion rule.

curl --request GET https://api.eu-gb.logging.cloud.ibm.com/v1/config/stream/exclusions/{ruleId}
-H "content-type: application/json"
-H "servicekey: <SERVICE_KEY>"

The response will be similar to the following:

{"hosts":[],"apps":[],"title":"Exclude Rule 1","query":"host:iam-am (action read)","active":true,"id":"xxxxxxxxxx"}





 Create a streaming exclusion rule 

Use [this method](https://cloud.ibm.com/apidocs/log-analysispost-v1-config-stream-exclusions) to create a streaming exclusion rule.

curl --request POST https://api.eu-gb.logging.cloud.ibm.com/v1/config/stream/exclusions
-H "content-type: application/json"
-H "servicekey: <SERVICE_KEY>"
All mirroring user controls are performed on the target cluster.



 Setting the topic selection 

The mirroring selection is made based on the topic names on the source cluster by using patterns. Choose the names of the topics on your source cluster carefully, by considering the advice from the [Considerations when you share clusters between multiple entities](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-mirroringsharing_clusters) section.

With well-structured topic names, such as adding a prefix to topics that are part of the same group or application, it is easy to control mirroring. With such a naming convention in place, any future topics that match the pattern are automatically mirrored without the need for more changes. The topic selection is in the form of a list of regex patterns. While more complex regex is supported, the following examples show enabling mirroring for all topics whose name has the prefix accounting or hr.

The first example shows enabling by using the CLI.

ibmcloud es mirroring-topic-selection-set --select ^accounting.,^hr.

The second example shows how to make the same selection by using the Administration REST API.

curl -s -X POST -H "Content-Type: application/json" -H "Authorization: <bearer token>" <admin url>/admin/mirroring/topic-selection -d '{"includes":["^accounting.", "^hr."]}'

Some examples of patterns to select topics for mirroring:



Table 5. Example patterns

 Example Patterns Explanation 

 "^aaa.", "^bbb." Match on the prefix of topic names. 
 ^branch_[0-9]{3}_[a-z]$ More complex regex pattern to match topic names. 
 "topic1", "topic2" Full topic names. 
 "." Mirror all source topics. 
 "" (by Administration REST API) --none (by CLI) Mirror no source topics. 



Updating a topic selection replaces the current set of patterns.

You can also disable mirroring on previously enabled topics.
Item Describes what was impacted by the change that was made within the assistant. For more information, see [Items and activity tracked](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-activity-logactivity-items). 
 Details Shows details about the item that was changed. For example, for an action, this column lists the specific action name and provides a link to open it. 
 Activity Describes the change that was made. For more information, see [Items and activity tracked](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-activity-logactivity-items). 
 Environment The environment in which the activity took place or the end destination of an activity. 
 User Email address of the user that made the change. 
 Date/Time Date and time of the activity in the format DD-MM-YYYY hr:min:sec AM/PM 





 Filtering 

Click the Filter icon ![Filter](https://cloud.ibm.com/docs-content/v1/content/icons/filter.svg) to filter the log. You can filter on:



* Item
* Details
* Activity
* Environment
* Environment ID
* User (requires exact match)
* Date range







 Sorting 

To sort the log, click either the Details or Date/Time columns.





 Downloading 

You can download the activity log as a CSV file. You can either download all activity, or filter the activity log by any of [filtering](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-activity-logactivity-log-filter) choices.

To download the activity log, click the Download icon ![Download](https://cloud.ibm.com/docs-content/v1/content/icons/download.svg).







 Items and activity tracked 

For the early access release, here's the current list of items and activity that are tracked. Events are tracked if they complete successfully.



Items and activity

 Item Activity Notes 

 Assistant Created, Dialog activated, Dialog deactivated
Use [this method](https://cloud.ibm.com/apidocs/activity-trackerget-v1-config-stream-exclusions) to list existing streaming exclusion rules.

curl --request GET https://api.eu-gb.logging.cloud.ibm.com/v1/config/stream/exclusions
-H "content-type: application/json"
-H "servicekey: <SERVICE_KEY>"

The response will be similar to the following:

[{"hosts":],"apps":],"title":"Exclude Rule 1","query":"host:iam-am (action read)","active":true,"id":"xxxxxxxxxx"}]





 Get details about a streaming exclusion rule 

Use [this method](https://cloud.ibm.com/apidocs/activity-trackerget-v1-config-stream-exclusions-rule-id) to get details of an existing streaming exclusion rule.

curl --request GET https://api.eu-gb.logging.cloud.ibm.com/v1/config/stream/exclusions/{ruleId}
-H "content-type: application/json"
-H "servicekey: <SERVICE_KEY>"

The response will be similar to the following:

{"hosts":[],"apps":[],"title":"Exclude Rule 1","query":"host:iam-am (action read)","active":true,"id":"xxxxxxxxxx"}





 Create a streaming exclusion rule 

Use [this method](https://cloud.ibm.com/apidocs/activity-trackerpost-v1-config-stream-exclusions) to create a streaming exclusion rule.

curl --request POST https://api.eu-gb.logging.cloud.ibm.com/v1/config/stream/exclusions
-H "content-type: application/json"
-H "servicekey: <SERVICE_KEY>"
The following example specifies rules by passing a JSON file that is named rules_def.json on the --file option:

--file rules_def.json

The rules_def.json file contains:

[
{
"action":"send",
"targets":
{
"id":"11111111-1111-1111-1111-111111111111"
},
{
"id":"22222222-2222-2222-2222-222222222222"
}
],
"inclusion_filters":
{
"operand": "service_name",
"operator": "in",
"values":
"appconnect",
"cloudant",
"containers-kubernetes"
]
},
{
"operand": "location",
"operator": "in",
"values":
"us-south",
"eu-de"
]
}
]
}
]
Show more

In this example, only metrics from appconnect, cloudant, and containers-kubernetes from the us-south and eu-de regions are routed to targets 11111111-1111-1111-1111-111111111111 and 22222222-2222-2222-2222-222222222222.







 Define routing rules by using the API 

Targets and inclusion filters are defined in API calls by using rules. The rules are defined in a JSON structure.

For example, the following example creates a route that is named my-route and sends metrics from atracker, and containers-registry in the us-east region to targets 11111111-1111-1111-1111-111111111111 and 22222222-2222-2222-2222-222222222222.
curl "https://api.us-south.logging.cloud.ibm.com/v1/export?to=$(date +%s)000&from=$(($(date +%s)-86400))000<=vels=info" -u e08c0c759663491880b0d61712346789:

To send an email with the link to download the log lines specified on the export, you can run the following command:

curl "https://api.us-south.logging.cloud.ibm.com/v1/export?to=$(date +%s)000&from=$(($(date +%s)-86400))000<=vels=info&email=xxx@ibm.com" -u e08c0c759663491880b0d61712346789:

To send an email with a custom subject, you can run the following command:

curl "https://api.us-south.logging.cloud.ibm.com/v1/export?to=$(date +%s)000&from=$(($(date +%s)-86400))000<=vels=info&email=xxx@ibm.com&emailSubject=Export%20test" -u e08c0c759663491880b0d61712346789:

To use the query parameter to find all log lines with a level of info, you can run the following command:

curl -s "https://api.us-south.logging.cloud.ibm.com/v1/export?query=test_query<=vels=info" -u :
* Running GET on https://api.softlayer.com/rest/v3.1/SoftLayer_Event_Log/AllObjects.json?resultLimit=0,50 with no body
/
private void recentLogs() {
LocalDate daysAgo = LocalDate.now().minusDays(30);
List<Log> logs=getAllEvents(false);
List<Log> recentLogs = logs.stream()
.filter(log -> log.getEventCreateDate()
.toZonedDateTime()
.toLocalDate()
.compareTo(daysAgo)>0)
.collect(Collectors.toList());
printEventLogs(recentLogs);
}
/
* Running GET on https://api.softlayer.com/rest/v3.1/SoftLayer_Event_Log/AllObjects.json?resultLimit=0,50 with no body
/
private void loginLogs() {
List<Log> logs=getAllEvents(false);
String loginName="login";
List<Log> loginLogs = logs.stream()
.filter(log -> log
.getEventName()
.toLowerCase()
.contains(loginName))
.collect(Collectors.toList());
printEventLogs(loginLogs);
}
/
* Running GET on https://api.softlayer.com/rest/v3.1/SoftLayer_Event_Log/AllObjects.json?resultLimit=0,50 with no body
/
private void allLogs() {
printEventLogs(getAllEvents(false));
}
/
* Pages through all results from the Event_Log. This might take long time.
/
private List<Log> getAllEvents(boolean allEvents) {
Arabic <br>(Modern Standard) ar-MS_BroadbandModel <br>Deprecated Not supported Not supported GA 
 Chinese <br>(Mandarin) zh-CN_NarrowbandModel <br>Deprecated Not supported Not supported GA 
 zh-CN_BroadbandModel <br>Deprecated Not supported Not supported GA 
 Dutch <br>(Netherlands) nl-NL_NarrowbandModel <br>Deprecated GA GA GA 
 nl-NL_BroadbandModel <br>Deprecated GA GA GA 
 English <br>(Australian) en-AU_NarrowbandModel <br>Deprecated GA GA GA 
 en-AU_BroadbandModel <br>Deprecated GA GA GA 
 English <br>(United Kingdom) en-GB_NarrowbandModel <br>Deprecated GA GA GA 
 en-GB_BroadbandModel <br>Deprecated GA GA GA 
 English <br>(United States) en-US_NarrowbandModel <br>Deprecated GA GA GA 
 en-US_BroadbandModel <br>Deprecated GA GA GA 
 en-US_ShortForm_NarrowbandModel <br>Deprecated GA GA GA 
 French <br>(Canadian) fr-CA_NarrowbandModel <br>Deprecated GA GA GA 
 fr-CA_BroadbandModel <br>Deprecated GA GA GA 
 French <br>(France) fr-FR_NarrowbandModel <br>Deprecated GA GA GA 
 fr-FR_BroadbandModel <br>Deprecated GA GA GA 
 German de-DE_NarrowbandModel <br>Deprecated GA GA GA 
 de-DE_BroadbandModel <br>Deprecated GA GA GA 
 Italian it-IT_NarrowbandModel <br>Deprecated GA GA GA 
 it-IT_BroadbandModel <br>Deprecated GA GA GA 
 Japanese ja-JP_NarrowbandModel <br>Deprecated GA GA GA 
 ja-JP_BroadbandModel <br>Deprecated GA GA GA 
 Korean ko-KR_NarrowbandModel <br>Deprecated GA GA GA
Dutch <br>(Belgian) nl-BE_Telephony GA GA 
 Dutch <br>(Netherlands) nl-NL_Telephony GA GA 
 nl-NL_Multimedia GA GA 
 English <br>(Australian) en-AU_Telephony GA <br><br>IBM Cloud<br><br> 27 February 2023 <br><br>IBM Cloud Pak for Data<br><br> 1 May 2023 GA 
 en-AU_Multimedia GA <br><br>IBM Cloud<br><br> 27 February 2023 <br><br>IBM Cloud Pak for Data<br><br> 1 May 2023 GA 
 English <br>(Indian) en-IN_Telephony GA <br><br>IBM Cloud<br><br> 27 February 2023 <br><br>IBM Cloud Pak for Data<br><br> 1 May 2023 GA 
 English <br>(United Kingdom) en-GB_Telephony GA <br><br>IBM Cloud<br><br> 27 February 2023 <br><br>IBM Cloud Pak for Data<br><br> 1 May 2023 GA 
 en-GB_Multimedia GA <br><br>IBM Cloud<br><br> 27 February 2023 <br><br>IBM Cloud Pak for Data<br><br> 1 May 2023 GA 
 English <br>(United States) en-US_Telephony GA <br><br>IBM Cloud<br><br> 27 February 2023 <br><br>IBM Cloud Pak for Data<br><br> 1 May 2023 GA 
 en-US_Multimedia GA <br><br>IBM Cloud<br><br> 27 February 2023 <br><br>IBM Cloud Pak for Data<br><br> 1 May 2023 GA 
 English <br>(all supported dialects) en-WW_Medical_Telephony Beta Beta 
 French <br>(Canadian) fr-CA_Telephony GA GA 
 fr-CA_Multimedia GA GA 
 French <br>(France) fr-FR_Telephony GA GA 
 fr-FR_Multimedia GA GA 
 German de-DE_Telephony GA GA
Korean [Version 1](https://cloud.ibm.com/docs/discovery?topic=discovery-entity-types-version-1) 
 Brazilian Portuguese [Version 1](https://cloud.ibm.com/docs/discovery?topic=discovery-entity-types-version-1) 
 Russian [Version 1](https://cloud.ibm.com/docs/discovery?topic=discovery-entity-types-version-1) 
 Spanish [Version 1](https://cloud.ibm.com/docs/discovery?topic=discovery-entity-types-version-1) 
 Swedish [Version 1](https://cloud.ibm.com/docs/discovery?topic=discovery-entity-types-version-1)
English (United States) en-US_BroadbandModel GA <br>Deprecated en-US_Multimedia 
 French (Canadian) fr-CA_BroadbandModel GA <br>Deprecated fr-CA_Multimedia 
 French (France) fr-FR_BroadbandModel GA <br>Deprecated fr-FR_Multimedia 
 German de-DE_BroadbandModel GA <br>Deprecated de-DE_Multimedia 
 Italian it-IT_BroadbandModel GA <br>Deprecated it-IT_Multimedia 
 Japanese ja-JP_BroadbandModel GA <br>Deprecated ja-JP_Multimedia 
 Korean ko-KR_BroadbandModel GA <br>Deprecated ko-KR_Multimedia 
 Portuguese (Brazilian) pt-BR_BroadbandModel GA <br>Deprecated pt-BR_Multimedia 
 Spanish (Argentinian, Beta) es-AR_BroadbandModel Beta <br>Deprecated es-LA_Telephony 
 Spanish (Castilian) es-ES_BroadbandModel GA <br>Deprecated es-ES_Multimedia 
 Spanish (Chilean, Beta) es-CL_BroadbandModel Beta <br>Deprecated es-LA_Telephony 
 Spanish (Colombian, Beta) es-CO_BroadbandModel Beta <br>Deprecated es-LA_Telephony 
 Spanish (Mexican, Beta) es-MX_BroadbandModel Beta <br>Deprecated es-LA_Telephony 
 Spanish (Peruvian, Beta) es-PE_BroadbandModel Beta <br>Deprecated es-LA_Telephony 









 The US English short-form model (Deprecated) 

The US English short-form model, en-US_ShortForm_NarrowbandModel, can improve speech recognition for Interactive Voice Response (IVR) and Automated Customer Support solutions. The short-form model is trained to recognize the short utterances that are frequently expressed in customer support settings like automated support call centers. In addition to being tuned for short utterances in general, the model is also tuned for precise utterances such as digits, single-character word and name spellings, and yes-no responses.
GA en-US_EmilyV3Voice <br>Female Your browser does not support the audio tag. 
 GA en-US_HenryV3Voice <br>Male Your browser does not support the audio tag. 
 GA en-US_KevinV3Voice <br>Male Your browser does not support the audio tag. 
 GA en-US_LisaV3Voice <br>Female Your browser does not support the audio tag. 
 GA en-US_MichaelV3Voice <br>Male Your browser does not support the audio tag. 
 GA en-US_OliviaV3Voice <br>Female Your browser does not support the audio tag. 
 French <br>(Canadian) GA fr-CA_LouiseV3Voice <br>Female Your browser does not support the audio tag. 
 French <br>(France) GA fr-FR_NicolasV3Voice <br>Male Your browser does not support the audio tag. 
 GA fr-FR_ReneeV3Voice <br>Female Your browser does not support the audio tag. 
 German GA de-DE_BirgitV3Voice <br>Female Your browser does not support the audio tag. 
 GA de-DE_DieterV3Voice <br>Male Your browser does not support the audio tag. 
 GA de-DE_ErikaV3Voice <br>Female Your browser does not support the audio tag. 
 Italian GA it-IT_FrancescaV3Voice <br>Female Your browser does not support the audio tag. 
 Japanese GA ja-JP_EmiV3Voice <br>Female Your browser does not support the audio tag. 
 Korean GA ko-KR_JinV3Voice <br>Female Your browser does not support the audio tag. 
 Portuguese <br>(Brazilian) GA pt-BR_IsabelaV3Voice <br>Female Your browser does not support the audio tag. 
 Spanish <br>(Castilian) GA es-ES_EnriqueV3Voice <br>Male Your browser does not support the audio tag. 
 GA es-ES_LauraV3Voice <br>Female Your browser does not support the audio tag.
The following Russian translation model can be customized.



Table 45. Russian translation model

 Model ID Source Target Domain 

 ru-en Russian (ru) English (en) general 







 Serbian 

The following Serbian translation model can be customized. The service supports translation for Serbian based on the Cyrillic alphabet, not the Latin alphabet.



Table 46. Serbian translation model

 Model ID Source Target Domain 

 sr-en Serbian (sr) English (en) general 







 Sinhala 

The following Sinhala translation model can be customized.



Table 47. Sinhala translation model

 Model ID Source Target Domain 

 si-en Sinhala (si) English (en) general 







 Slovak 

The following Slovak translation model can be customized.



Table 48. Slovak translation model

 Model ID Source Target Domain 

 sk-en Slovak (sk) English (en) general 







 Slovenian 

The following Slovenian translation model can be customized.



Table 49. Slovenian translation model

 Model ID Source Target Domain 

 sl-en Slovenian (sl) English (en) general 







 Spanish 

The following Spanish translation models can be customized.



Table 50. Spanish translation models

 Model ID Source Target Domain 

 es-ca Spanish (es) Catalan (ca) general 
 es-en Spanish (es) English (en) general 
 es-fr Spanish (es) French (fr) general 
 es-eu Spanish (es) Basque (eu) general 







 Swedish 

The following Swedish translation model can be customized.



Table 51. Swedish translation model

 Model ID Source Target Domain 

 sv-en Swedish (sv) English (en) general 







 Tamil 

The following Tamil translation model can be customized.



Table 52. Tamil translation model

 Model ID Source Target Domain 

 ta-en Tamil (ta) English (en) general 







 Telugu 

The following Telugu translation model can be customized.



Table 53. Telugu translation model

 Model ID Source Target Domain 

 te-en Telugu (te) English (en) general 







 Thai 

The following Thai translation model can be customized.



Table 54. Thai translation model

 Model ID Source Target Domain 

 th-en Thai (th) English (en) general
de-DE_BroadbandModel <br>Deprecated GA GA GA 
 Italian it-IT_NarrowbandModel <br>Deprecated GA GA GA 
 it-IT_BroadbandModel <br>Deprecated GA GA GA 
 Japanese ja-JP_NarrowbandModel <br>Deprecated GA GA GA 
 ja-JP_BroadbandModel <br>Deprecated GA GA GA 
 Korean ko-KR_NarrowbandModel <br>Deprecated GA GA GA 
 ko-KR_BroadbandModel <br>Deprecated GA GA GA 
 Portuguese <br>(Brazilian) pt-BR_NarrowbandModel <br>Deprecated GA GA GA 
 pt-BR_BroadbandModel <br>Deprecated GA GA GA 
 Spanish <br>(Argentinian) es-AR_NarrowbandModel <br>Deprecated Beta Beta Beta 
 es-AR_BroadbandModel <br>Deprecated Beta Beta Beta 
 Spanish <br>(Castilian) es-ES_NarrowbandModel <br>Deprecated GA GA GA 
 es-ES_BroadbandModel <br>Deprecated GA GA GA 
 Spanish <br>(Chilean) es-CL_NarrowbandModel <br>Deprecated Beta Beta Beta 
 es-CL_BroadbandModel <br>Deprecated Beta Beta Beta 
 Spanish <br>(Colombian) es-CO_NarrowbandModel <br>Deprecated Beta Beta Beta 
 es-CO_BroadbandModel <br>Deprecated Beta Beta Beta 
 Spanish <br>(Mexican) es-MX_NarrowbandModel <br>Deprecated Beta Beta Beta 
 es-MX_BroadbandModel <br>Deprecated Beta Beta Beta 
 Spanish <br>(Peruvian) es-PE_NarrowbandModel <br>Deprecated Beta Beta Beta 
 es-PE_BroadbandModel <br>Deprecated Beta Beta Beta 







 Customization support for next-generation models 

Table 2 lists the next-generation models that are supported for language model customization and grammars. Next-generation language models do not support acoustic model customization.
Kannada translation model

 Model ID Source Target Domain 

 kn-en Kannada (kn) English (en) general 







 Korean 

The following Korean translation model can be customized.



Table 30. Korean translation model

 Model ID Source Target Domain 

 ko-en Korean (ko) English (en) general 







 Latvian 

The following Latvian translation model can be customized.



Table 31. Latvian translation model

 Model ID Source Target Domain 

 lv-en Latvian (lv) English (en) general 







 Lithuanian 

The following Lithuanian translation model can be customized.



Table 32. Lithuanian translation model

 Model ID Source Target Domain 

 lt-en Lithuanian (lt) English (en) general 







 Malay 

The following Malay translation model can be customized.



Table 33. Malay translation model

 Model ID Source Target Domain 

 ms-en Malay (ms) English (en) general 







 Malayalam 

The following Malayalam translation model can be customized.



Table 34. Malayalam translation model

 Model ID Source Target Domain 

 ml-en Malayalam (ml) English (en) general 







 Maltese 

The following Maltese translation model can be customized.



Table 35. Maltese translation model

 Model ID Source Target Domain 

 mt-en Maltese (mt) English (en) general 







 Marathi 

The following Marathi translation model can be customized.



Table 36. Marathi translation model

 Model ID Source Target Domain 

 mr-en Marathi (mr) English (en) general 







 Montenegrin 

The following Montenegrin translation model cannot be customized.



Table 37. Montenegrin translation model

 Model ID Source Target Domain 

 cnr-en Montenegrin (cnr) English (en) general 



The Montenegrin-to-English translation model (cnr-en) is not customizable at this time. It can be used for translation but cannot be customized.





 Nepali 

The following Nepali translation model can be customized.



Table 38. Nepali translation model

 Model ID Source Target Domain 

 ne-en Nepali (ne) English (en) general 







 Norwegian Bokmål 

The following Norwegian Bokmål translation model can be customized.



Table 39. Norwegian Bokmål translation model
[External link icon](https://cloud.ibm.com/docs-content/v1/content/ded4adc3ea0bd2a81b113c579f2b1183926da211/icons/launch-glyph.svg)](https://watson-developer-cloud.github.io/doc-tutorial-downloads/discovery/custom_stopwords_fr.txt).
* German: [custom_stopwords_de.txt ![External link icon](https://cloud.ibm.com/docs-content/v1/content/ded4adc3ea0bd2a81b113c579f2b1183926da211/icons/launch-glyph.svg)](https://watson-developer-cloud.github.io/doc-tutorial-downloads/discovery/custom_stopwords_de.txt).
* Italian: [custom_stopwords_it.txt ![External link icon](https://cloud.ibm.com/docs-content/v1/content/ded4adc3ea0bd2a81b113c579f2b1183926da211/icons/launch-glyph.svg)](https://watson-developer-cloud.github.io/doc-tutorial-downloads/discovery/custom_stopwords_it.txt).
* Japanese: [custom_stopwords_ja.txt ![External link icon](https://cloud.ibm.com/docs-content/v1/content/ded4adc3ea0bd2a81b113c579f2b1183926da211/icons/launch-glyph.svg)](https://watson-developer-cloud.github.io/doc-tutorial-downloads/discovery/custom_stopwords_ja.txt).
* Spanish: [custom_stopwords_es.txt !