시작
Kore.ai 대화형 플랫폼
챗봇 개요
자연어 처리(NLP)
봇 개념 및 용어들
빠른 시작 가이드
봇 빌더 접근 방법
사용 고지 사항 (영어)
Kore.ai 봇 빌더로 작업하기
봇 구축 시작하기
릴리스 정보
현재 버전 (영어)
이전 버전 (영어)

개념
디자인
스토리보드
대화 작업
개요
Using the Dialog Builder Tool
노드 유형
사용자 의도 노드
대화 노드
엔티티 노드
양식 노드
확인 노드
서비스 노드
봇 조치 노드
Service Node
WebHook 노드
스크립트 노드
노드 그룹화하기
Agent Transfer Node
사용자 프롬프트
음성 통화 속성
대화 관리
노드 및 전환
구성 요소 전환
컨텍스트 개체
이벤트 기반 봇 조치
지식 그래프
소개
지식 추출
지식 그래프 생성
봇에 지식 그래프 추가
그래프 생성
지식 그래프 작성
FAQ 추가
작업 실행
기존 소스에서 FAQ 구축
특성, 동의어 및 불용어
변수 네임스페이스 관리
수정
용어 편집 및 삭제
용어 편집 및 삭제
질문과 응답 편집
Knowledge Graph Training
지식 그래프 분석
봇 온톨로지 가져오기 및 내보내기
지식 그래프 가져오기
지식 그래프 내보내기
지식 그래프 생성
CSV 파일에서
JSON 파일
지식 그래프 생성
경고 작업
스몰 토크
Digital Skills
디지털 양식
Views
Digital Views
Panels
Widgets
기차
봇 성능 향상 – NLP 최적화
기계 학습
소개
모델 검증
기초 의미
지식 그래프 학습
특성
순위 및 해결
고급 NLP 설정
NLP 설정 및 지침
봇 인텔리전스
소개
컨텍스트 관리
컨텍스트 관리
대화 관리
다중 – 의도 탐지
엔티티 수정
기본 대화
정서 관리
어조 분석
Test & Debug
봇과 대화
발화 테스트
배치 테스트하기
대화 테스트
배포
채널 활성화
봇 게시
분석
봇 분석하기
Conversations Dashboard
Performance Dashboard
사용자 정의 대시보드
소개
맞춤형 메타 태그
사용자 정의 대시보드 생성 방법
Conversation Flows
NLP 지표
Containment Metrics
사용량 지표
스마트 봇
소개
범용 봇
소개
범용 봇 정의
범용 봇 생성
범용 봇 학습
범용 봇 커스터마이징
범용 봇용 추가 언어 활성화
스토어
Manage Assistant
플랜 및 사용량
Overview
Usage Plans
Support Plans
플랜 관리
봇 인증
다국어 봇
개인 식별 정보 삭제하기
봇 변수 사용
IVR 통합
일반 설정
봇 관리

방법
간단한 봇 생성하기
Design Conversation Skills
뱅킹 봇 생성
뱅킹 봇 – 자금 이체
뱅킹 봇 – 잔액 업데이트
Knowledge Graph (KG) 구축
스마트 경고를 예약하는 방법
Design Digital Skills
디지털 양식 설정 방법
디지털 보기 설정 방법
데이터 테이블에 데이터를 추가하는 방법
데이터 테이블 내 데이터 업데이트 방법
UI 양식에서 데이터 테이블에 데이터를 추가하는 방법
Train the Assistant
특성 사용 방법
의도와 엔티티에 대한 패턴 사용 방법
컨텍스트 전환 관리 방법
Deploy the Assistant
상담사 전환을 설정하는 방법
봇 기능 사용 방법
콘텐츠 변수 사용 방법
전역 변수 사용 방법
Kore.ai 웹 SDK 튜토리얼
Kore.ai 위젯 SDK 튜토리얼
Analyze the Assistant
사용자 정의 대시보드 생성 방법
사용자 지정 태그를 사용하여 봇 메트릭을 필터링하는 방법

API 및 SDK
API 참조
Kore.ai API 사용
API 목록
API 컬렉션
koreUtil Libraries
SDK 참조
상담사 전환을 설정하는 방법
봇 기능 사용 방법
콘텐츠 변수 사용 방법
전역 변수 사용 방법
소개
Kore.ai 웹 SDK 튜토리얼
Kore.ai 위젯 SDK 튜토리얼

관리
소개
봇 관리자 콘솔
대시보드
사용자 관리
사용자 관리
그룹 관리
역할 관리
봇 관리 모듈
등록
사용자 초대
사용자 등록을 위한 대량 초대 보내기
사용자 및 사용자 데이터 가져오기
Active Directory에서 사용자 동기화
보안 및 준수
싱글 사인 온 사용
보안 설정
Kore.ai 커넥터
봇 관리자용 분석
Billing (지원하지 않음)
  1. Docs
  2. Virtual Assistants
  3. Advanced Topics
  4. Language Management
  5. Multilingual VAs: Components & Feature Support

Multilingual VAs: Components & Feature Support

In the case of multilingual VAs, while much of the assistant’s behavior does not change with the language, the semantics does impose some restrictions. In this document we will list out the different behaviors that would be language-dependent, so you can cater for such scenarios.

This article discusses language-specific components for multilingual VAs, as well as feature support and behavior, as compared to single language assistants. 

This article lists the VA elements for which you can provide language-specific values. You need not translate Standard Responses as the Platform automatically translates them when you enable a language.

Metadata

JSON object consisting of the following translatable elements

FIELD NAME TYPE DESCRIPTION
Bot Name String Name of the assistant
Bot Description String Description of the assistant
Bot Synonyms Object Arrays of important words in the task names and their corresponding synonyms. Enter translation of the words as well as their synonyms. Refer to Managing Synonyms to learn more about bot synonyms.
Bot Error Codes Object Arrays of error codes and their corresponding messages. Enter translations of the error message. Refer to Customizing Error Messages to learn more about error messages.

Dialog Tasks

JSON object consisting of the following translatable components of your VA’s Dialog Tasks.

FIELD NAME TYPE DESCRIPTION
Dialog Task Name String Name of the dialog task
Dialog Task Desc String Description of the dialog task
Dialog Task Upgrade Message String Message displayed to the developer on the History page for the upgraded task

Dialog Components

JSON object consisting of the following translatable components related to the NLP settings of a dialog task.

FIELD NAME TYPE DESCRIPTION
Dialog Component Intent String Name of the User Intent node
Dialog Component Description String Description of the User Intent node
Dialog Component Synonyms Object Synonyms for the words in the entity node names. Refer to Managing Synonyms to learn more.
Dialog Component Patterns Object Patterns for the User Intent and Entity nodes in the dialog task. Refer to Managing Patterns to learn more.

Message Templates

JSON object with arrays of Message Template IDs and Message Template Text values. They correspond to the User Responses field in the Message node and the Bot Prompts and Error Prompts fields in the Entity node of the dialog tasks.

FIELD NAME TYPE DESCRIPTION
Message Template Text String The text entered in User Responses, Bot Prompts, or Error Prompts fields in any Message or Entity node of a dialog task.

Alert Task

JSON object consisting of the following translatable components of your assistant’s Alert Tasks.

FIELD NAME TYPE DESCRIPTION
Alert Name String Name of the alert task
Alert Short Desc String Description of the alert task
Alert Keywords Array The search keywords entered for the alert task
Alert Patterns Array Array of patterns related to the alert task’s name. Replace the pattern text with the translated text. Refer to Managing Patterns to learn more.
Alert Field Synonyms Object Arrays consisting of synonyms for each task field. Replace the field name and the synonyms with the translated text. Refer to Managing Synonyms to learn more.
Alert Field Patterns Object Arrays consisting of patterns for each task field. Replace the pattern text with the translated text. Refer to Managing Patterns to learn more.
Alert Ignore Words Array Arrays of ignore words related to the alert task. Replace the words with the translated text. Refer to Managing Ignore Words and Field Memory to learn more.
Alert Upgrade Short Message String Upgrade short message related to the alert task.
Alert Upgrade Long Message String Upgrade long message related to the alert task.
Alert Query Fields Object Arrays consisting of key-value pairs of Alert Field Help and Alert Field Title. Replace the text with the translated text.
Alert Payload Fields Object Arrays consisting of key-value pairs of Alert Payload fields. Replace the text with the translated text.

Alert Fields

JSON object consisting of the following translatable components in the API Request tab of the Alert task.

FIELD NAME TYPE DESCRIPTION
Alert Field Title String The title of the user input field related to the alert task, for example, Choose city
Alert Field Help String The help text displayed below the field title to describe the task, for example, Which city would you like to get weather alerts for?
Alert Field Placeholder String The placeholder text displayed inside the field.

Bot Filters

JSON object consisting of the following translatable components related to Bot filters

FIELD NAME TYPE DESCRIPTION
Filter Name String Name of the task filter

IDP Config Form Fields

JSON object consisting of the following translatable components related to IDP configuration form

Field Name Type Description
IDP Form Field String Name of the IDP Form Field displayed to the end-user in the authentication dialog

Pattern Support

We have seen in this document, how Patterns can be used for Intent detection and Entity extraction. These rules are for VAs in the English language. In other languages, there may be differences. 

Patterns can be used in Small Talk (while defining queries), Knowledge Graph (using alternate question fields), and Trait identification but their behavior might differ slightly. The table below provides an overview of how this may occur.

PATTERN SYNTAX INTENT DETECTION AND ENTITY EXTRACTION SMALL

TALK

TRAITS KNOWLEDGE

GRAPH

SUPPORTED IN LANGUAGES NOT SUPPORTED IN LANGUAGES
word1 word2 … wordn

This mandates all the words defined to be available in the user utterance in the same consecutive order with additional words allowed in between, before and after

All languages Yes Yes Yes
word1_word2

Enforce phrase, no additional words allowed in between word1 and word2.

All languages Yes Yes Yes
word1 * word2

0 to infinite number of additional words between the specified words/phrases

All languages Yes Yes Yes
word1 *n word2

Exactly n number of additional words between the specified words/phrases

All languages Yes Yes Yes
word1 *0 word2

To disable wildcards between two tokens.

All languages Yes Yes Yes
word1 < word2

Indicates the match for word2 should start from the beginning of a sentence.

All languages Yes Yes Yes
word1 > word2

Indicates the end of the sentence and no words are allowed after it.

All languages Yes Yes Yes
!abc

Indicates the word/concept “abc” should not exist anywhere in the user utterance after this token

All languages Yes Yes Yes
!!abc

The very next word/concept should not be “abc”

All languages Yes Yes Yes
[ … ]

Used to define a group of words/concepts and the match should be against exactly one of the group declared in [ ].

All languages Yes Yes Yes
{ … }

Used to define an optional group or words/concepts and the match would be against zero or one of the words/patterns declared in { }.

All languages Yes Yes Yes
( … )

contain a pattern i.e when a pattern or part of a pattern is enclosed in these parentheses, we treat it as a pattern unlike [ ] and { }.

All languages Yes Yes Yes
<< … >>

Used to find words in any order

All languages Yes Yes Yes
‘word1

If you quote words or use words that are not in canonical form, the system will restrict itself to what you used in the pattern

All languages No No No
System Concepts

Support for built-in concepts

English,

German,

Spanish,

French

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional,

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian,

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi,

Telugu,

Tamil,

Marathi,

Catalan,

Tagalog,

Portuguese (European)

No No No
Developer concepts

Support for developer-defined concepts

English,

German,

Spanish,

French,

Portuguese (Brazilian)*,

Italian*,

Chinese simplified*,

Chinese traditional*,

Indonesian*,

Korean*,

Dutch*,

Japanese*,

Arabic*,

Finnish*,

Russian*,

Polish*,

Ukrainian*,

Swedish*,

Kazakh*,

Norwegian*,

Hindi*,

Telugu*,

Tamil*,

Marathi*,

Catalan*

Yes Yes Yes*
Two-letter identifiers for Dates

Like Mo for Monday, Tu for Tuesday, etc

English,

German,

Spanish,

Portuguese (Brazilian),

Portuguese (European),

Italian,

Chinese simplified,

Chinese traditional,

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian,

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi

French,

Telugu,

Tamil,

Marathi,

Catalan,

Tagalog

No

* in these cases, developer concepts are not supported in entity extraction

NLP Support

Here are the NLP features supported by Multilingual VAs:

NLP FEATURE SUPPORTED IN LANGUAGES NOT SUPPORTED IN LANGUAGES SMALL TALK TRAITS KNOWLEDGE GRAPH
List of Values
Full Match All languages No
Partial Match All languages No
Exact Match All languages No
Ambiguity behavior All languages No
Ambiguity with multi-item selection English Not supported in any language except English No
Spell Correction English,

German,

Spanish,

French,

Portuguese (Brazilian),

Italian,

Indonesian,

Korean (from ver7.3),

Dutch,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Portuguese (European)

Chinese simplified,

Chinese traditional,

Japanese,

Hindi,

Telugu,

Tamil,

Marathi

Yes
Amend Entities English Not supported in any language except English Yes
Sentiment Analysis English,

German,

Spanish,

French,

Dutch,

Korean (from ver7.3),

Japanese (from ver8.0),

Russian (from ver8.0),

Kazakh (from ver8.0),

Norwegian,

Tagalog,

Portuguese (European)

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional

Indonesian,

Arabic,

Finnish,

Polish,

Ukrainian,

Swedish,

Hindi,

Telugu,

Tamil,

Marathi,

Catalan

Yes
Bot Synonyms (default) English,

German,

Spanish,

French,

Tagalog

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh

Yes
Knowledge Graph
Patterns All Languages Yes
Search in Answer English,

German (from ver7.3),

Spanish (from ver7.3),

French (from ver7.3),

Portuguese (Brazilian) (from ver7.3),

Italian (from ver7.3),

Indonesian (from ver7.3),

Dutch (from ver7.3),

Finnish (from ver7.3),

Polish (from ver7.3),

Swedish (from ver7.3),

Tagalog,

Portuguese (European)

Chinese simplified,

Chinese traditional,

Korean,

Japanese,

Arabic,

Russian,

Ukrainian,

Kazakh

Yes
Spell Correction English,

German,

Spanish,

French,

Portuguese (Brazilian),

Italian,

Indonesian,

Korean,

Dutch,

Arabic,

Finnish,

Polish,

Swedish,

Ukrainian

Russian (from ver8.0),

Kazakh (from ver8.0),

Japanese (from ver8.0),

Portuguese (European)

Chinese simplified,

Chinese traditional,

Catalan,

Tagalog

Yes
Special Character support All languages except English English Yes
NL Engines
Dependency Parser Model German (from ver7.3),

French (from ver7.3),

Italian (from ver8.0)

English,

Spanish,

Portuguese (Brazilian),

Chinese simplified,

Chinese traditional

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi

Multilingual VAs: Components & Feature Support

In the case of multilingual VAs, while much of the assistant’s behavior does not change with the language, the semantics does impose some restrictions. In this document we will list out the different behaviors that would be language-dependent, so you can cater for such scenarios.

This article discusses language-specific components for multilingual VAs, as well as feature support and behavior, as compared to single language assistants. 

This article lists the VA elements for which you can provide language-specific values. You need not translate Standard Responses as the Platform automatically translates them when you enable a language.

Metadata

JSON object consisting of the following translatable elements

FIELD NAME TYPE DESCRIPTION
Bot Name String Name of the assistant
Bot Description String Description of the assistant
Bot Synonyms Object Arrays of important words in the task names and their corresponding synonyms. Enter translation of the words as well as their synonyms. Refer to Managing Synonyms to learn more about bot synonyms.
Bot Error Codes Object Arrays of error codes and their corresponding messages. Enter translations of the error message. Refer to Customizing Error Messages to learn more about error messages.

Dialog Tasks

JSON object consisting of the following translatable components of your VA’s Dialog Tasks.

FIELD NAME TYPE DESCRIPTION
Dialog Task Name String Name of the dialog task
Dialog Task Desc String Description of the dialog task
Dialog Task Upgrade Message String Message displayed to the developer on the History page for the upgraded task

Dialog Components

JSON object consisting of the following translatable components related to the NLP settings of a dialog task.

FIELD NAME TYPE DESCRIPTION
Dialog Component Intent String Name of the User Intent node
Dialog Component Description String Description of the User Intent node
Dialog Component Synonyms Object Synonyms for the words in the entity node names. Refer to Managing Synonyms to learn more.
Dialog Component Patterns Object Patterns for the User Intent and Entity nodes in the dialog task. Refer to Managing Patterns to learn more.

Message Templates

JSON object with arrays of Message Template IDs and Message Template Text values. They correspond to the User Responses field in the Message node and the Bot Prompts and Error Prompts fields in the Entity node of the dialog tasks.

FIELD NAME TYPE DESCRIPTION
Message Template Text String The text entered in User Responses, Bot Prompts, or Error Prompts fields in any Message or Entity node of a dialog task.

Alert Task

JSON object consisting of the following translatable components of your assistant’s Alert Tasks.

FIELD NAME TYPE DESCRIPTION
Alert Name String Name of the alert task
Alert Short Desc String Description of the alert task
Alert Keywords Array The search keywords entered for the alert task
Alert Patterns Array Array of patterns related to the alert task’s name. Replace the pattern text with the translated text. Refer to Managing Patterns to learn more.
Alert Field Synonyms Object Arrays consisting of synonyms for each task field. Replace the field name and the synonyms with the translated text. Refer to Managing Synonyms to learn more.
Alert Field Patterns Object Arrays consisting of patterns for each task field. Replace the pattern text with the translated text. Refer to Managing Patterns to learn more.
Alert Ignore Words Array Arrays of ignore words related to the alert task. Replace the words with the translated text. Refer to Managing Ignore Words and Field Memory to learn more.
Alert Upgrade Short Message String Upgrade short message related to the alert task.
Alert Upgrade Long Message String Upgrade long message related to the alert task.
Alert Query Fields Object Arrays consisting of key-value pairs of Alert Field Help and Alert Field Title. Replace the text with the translated text.
Alert Payload Fields Object Arrays consisting of key-value pairs of Alert Payload fields. Replace the text with the translated text.

Alert Fields

JSON object consisting of the following translatable components in the API Request tab of the Alert task.

FIELD NAME TYPE DESCRIPTION
Alert Field Title String The title of the user input field related to the alert task, for example, Choose city
Alert Field Help String The help text displayed below the field title to describe the task, for example, Which city would you like to get weather alerts for?
Alert Field Placeholder String The placeholder text displayed inside the field.

Bot Filters

JSON object consisting of the following translatable components related to Bot filters

FIELD NAME TYPE DESCRIPTION
Filter Name String Name of the task filter

IDP Config Form Fields

JSON object consisting of the following translatable components related to IDP configuration form

Field Name Type Description
IDP Form Field String Name of the IDP Form Field displayed to the end-user in the authentication dialog

Pattern Support

We have seen in this document, how Patterns can be used for Intent detection and Entity extraction. These rules are for VAs in the English language. In other languages, there may be differences. 

Patterns can be used in Small Talk (while defining queries), Knowledge Graph (using alternate question fields), and Trait identification but their behavior might differ slightly. The table below provides an overview of how this may occur.

PATTERN SYNTAX INTENT DETECTION AND ENTITY EXTRACTION SMALL

TALK

TRAITS KNOWLEDGE

GRAPH

SUPPORTED IN LANGUAGES NOT SUPPORTED IN LANGUAGES
word1 word2 … wordn

This mandates all the words defined to be available in the user utterance in the same consecutive order with additional words allowed in between, before and after

All languages Yes Yes Yes
word1_word2

Enforce phrase, no additional words allowed in between word1 and word2.

All languages Yes Yes Yes
word1 * word2

0 to infinite number of additional words between the specified words/phrases

All languages Yes Yes Yes
word1 *n word2

Exactly n number of additional words between the specified words/phrases

All languages Yes Yes Yes
word1 *0 word2

To disable wildcards between two tokens.

All languages Yes Yes Yes
word1 < word2

Indicates the match for word2 should start from the beginning of a sentence.

All languages Yes Yes Yes
word1 > word2

Indicates the end of the sentence and no words are allowed after it.

All languages Yes Yes Yes
!abc

Indicates the word/concept “abc” should not exist anywhere in the user utterance after this token

All languages Yes Yes Yes
!!abc

The very next word/concept should not be “abc”

All languages Yes Yes Yes
[ … ]

Used to define a group of words/concepts and the match should be against exactly one of the group declared in [ ].

All languages Yes Yes Yes
{ … }

Used to define an optional group or words/concepts and the match would be against zero or one of the words/patterns declared in { }.

All languages Yes Yes Yes
( … )

contain a pattern i.e when a pattern or part of a pattern is enclosed in these parentheses, we treat it as a pattern unlike [ ] and { }.

All languages Yes Yes Yes
<< … >>

Used to find words in any order

All languages Yes Yes Yes
‘word1

If you quote words or use words that are not in canonical form, the system will restrict itself to what you used in the pattern

All languages No No No
System Concepts

Support for built-in concepts

English,

German,

Spanish,

French

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional,

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian,

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi,

Telugu,

Tamil,

Marathi,

Catalan,

Tagalog,

Portuguese (European)

No No No
Developer concepts

Support for developer-defined concepts

English,

German,

Spanish,

French,

Portuguese (Brazilian)*,

Italian*,

Chinese simplified*,

Chinese traditional*,

Indonesian*,

Korean*,

Dutch*,

Japanese*,

Arabic*,

Finnish*,

Russian*,

Polish*,

Ukrainian*,

Swedish*,

Kazakh*,

Norwegian*,

Hindi*,

Telugu*,

Tamil*,

Marathi*,

Catalan*

Yes Yes Yes*
Two-letter identifiers for Dates

Like Mo for Monday, Tu for Tuesday, etc

English,

German,

Spanish,

Portuguese (Brazilian),

Portuguese (European),

Italian,

Chinese simplified,

Chinese traditional,

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian,

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi

French,

Telugu,

Tamil,

Marathi,

Catalan,

Tagalog

No

* in these cases, developer concepts are not supported in entity extraction

NLP Support

Here are the NLP features supported by Multilingual VAs:

NLP FEATURE SUPPORTED IN LANGUAGES NOT SUPPORTED IN LANGUAGES SMALL TALK TRAITS KNOWLEDGE GRAPH
List of Values
Full Match All languages No
Partial Match All languages No
Exact Match All languages No
Ambiguity behavior All languages No
Ambiguity with multi-item selection English Not supported in any language except English No
Spell Correction English,

German,

Spanish,

French,

Portuguese (Brazilian),

Italian,

Indonesian,

Korean (from ver7.3),

Dutch,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Portuguese (European)

Chinese simplified,

Chinese traditional,

Japanese,

Hindi,

Telugu,

Tamil,

Marathi

Yes
Amend Entities English Not supported in any language except English Yes
Sentiment Analysis English,

German,

Spanish,

French,

Dutch,

Korean (from ver7.3),

Japanese (from ver8.0),

Russian (from ver8.0),

Kazakh (from ver8.0),

Norwegian,

Tagalog,

Portuguese (European)

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional

Indonesian,

Arabic,

Finnish,

Polish,

Ukrainian,

Swedish,

Hindi,

Telugu,

Tamil,

Marathi,

Catalan

Yes
Bot Synonyms (default) English,

German,

Spanish,

French,

Tagalog

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh

Yes
Knowledge Graph
Patterns All Languages Yes
Search in Answer English,

German (from ver7.3),

Spanish (from ver7.3),

French (from ver7.3),

Portuguese (Brazilian) (from ver7.3),

Italian (from ver7.3),

Indonesian (from ver7.3),

Dutch (from ver7.3),

Finnish (from ver7.3),

Polish (from ver7.3),

Swedish (from ver7.3),

Tagalog,

Portuguese (European)

Chinese simplified,

Chinese traditional,

Korean,

Japanese,

Arabic,

Russian,

Ukrainian,

Kazakh

Yes
Spell Correction English,

German,

Spanish,

French,

Portuguese (Brazilian),

Italian,

Indonesian,

Korean,

Dutch,

Arabic,

Finnish,

Polish,

Swedish,

Ukrainian

Russian (from ver8.0),

Kazakh (from ver8.0),

Japanese (from ver8.0),

Portuguese (European)

Chinese simplified,

Chinese traditional,

Catalan,

Tagalog

Yes
Special Character support All languages except English English Yes
NL Engines
Dependency Parser Model German (from ver7.3),

French (from ver7.3),

Italian (from ver8.0)

English,

Spanish,

Portuguese (Brazilian),

Chinese simplified,

Chinese traditional

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi

메뉴