Text part language
The text part language feature lets you mark the language of text fragments. This way browsers and screen readers can correctly interpret parts written in different languages.
# Demo
In the demo below, select a text fragment. Next, use the language toolbar dropdown to choose from predefined languages.
Language is the human ability to acquire and use complex systems of communication, and language is any specific example of such a system. The scientific study of language is called linguistics.
שפה היא דרך תקשורת המבוססת על מערכת סמלים מורכבת בעלת חוקיות, המאפשרת לקודד ולארגן מידע בעל משמעויות רבות ומגוונות. נהוג להבדיל בין הסמל השפתי המסמן לבין המושג או התוכן המסומן בו, אשר יכול להיות מציאותי או מופשט.
Un lenguaje (del provenzal lenguatge y este del latín lingua) es un sistema de comunicación estructurado para el que existe un contexto de uso y ciertos principios combinatorios formales. Existen contextos tanto naturales como artificiales.
اللغة نسق من الإشارات والرموز، يشكل أداة من أدوات المعرفة، وتعتبر اللغة أهم وسائل التفاهم والاحتكاك بين أفراد المجتمع في جميع ميادين الحياة. وبدون اللغة يتعذر نشاط الناس المعرفي.
Source: Wikipedia
This demo presents a limited set of features. Visit the feature-rich editor example to see more in action.
# Additional feature information
The text part language feature is especially useful when your content includes text sections written in different text directions, for example, when the whole content is in English but includes some citations in Arabic.
The text part language feature implements the WCAG 3.1.2 Language of Parts specification.
# Installation
⚠️ New import paths
Starting with version 42.0.0, we changed the format of import paths. This guide uses the new, shorter format. Refer to the Packages in the legacy setup guide if you use an older version of CKEditor 5.
After installing the editor, add the feature to your plugin list and toolbar configuration:
import { ClassicEditor, TextPartLanguage } from 'ckeditor5';
ClassicEditor
.create( document.querySelector( '#editor' ), {
licenseKey: '<YOUR_LICENSE_KEY>', // Or 'GPL'.
plugins: [ TextPartLanguage, /* ... */ ],
toolbar: [ 'textPartLanguage', /* ... */ ]
language: {
// Configuration.
}
} )
.then( /* ... */ )
.catch( /* ... */ );
# Configuring available languages
To modify the list of available languages displayed in the language dropdown use the config.language.textPartLanguage
configuration option.
The example below shows the configuration used for the demo above:
ClassicEditor
.create( document.querySelector( '#editor' ), {
// ... Other configuration options ...
language: {
textPartLanguage: [
{ title: 'Arabic', languageCode: 'ar' },
{ title: 'French', languageCode: 'fr' },
{ title: 'Hebrew', languageCode: 'he' },
{ title: 'Spanish', languageCode: 'es' }
]
}
} )
.then( /* ... */ )
.catch( /* ... */ );
# Related features
There are other language-related CKEditor 5 features you may want to check:
- UI Language – Set the UI language.
- Spelling and grammar checking – Employ multi-language spell check for flawless content.
# Common API
The TextPartLanguage
plugin registers:
- The
'textPartLanguage'
UI dropdown component implemented by the text part language UI feature. - The
'textPartLanguage'
command implemented by the text part language editing feature.
You can execute the command using the editor.execute()
method:
// Applies the language to the selected text part with the given language code.
editor.execute( 'textPartLanguage', { languageCode: 'es' } );
We recommend using the official CKEditor 5 inspector for development and debugging. It will give you tons of useful information about the state of the editor such as internal data structures, selection, commands, and many more.
# Contribute
The source code of the feature is available on GitHub at https://github.com/ckeditor/ckeditor5/tree/master/packages/ckeditor5-language.
Every day, we work hard to keep our documentation complete. Have you spotted outdated information? Is something missing? Please report it via our issue tracker.
With the release of version 42.0.0, we have rewritten much of our documentation to reflect the new import paths and features. We appreciate your feedback to help us ensure its accuracy and completeness.