Languages

Input profiles

An input profile binds language behavior (IME, prediction, fonts) to a keyboard layout (key topology):

Bundled defaults define one profile per layout (56 total). Profile id combines languageTag and layout variant (for example en-qwerty, de-qwertz, zh-Hans-pinyin, ja-12key).

Defaults ship in layouts.lnlay under share/lnvirtualkeyboard/dictionaries/ (always deployed with the plugin). Omit inputProfiles in QML to use bundled profiles; set only activeProfileIds and currentProfileId.

Activating bundled profiles

VirtualKeyboard {
    width: parent.width
    activeProfileIds: ["en-qwerty", "fr-azerty", "de-qwertz", "ja-romaji"]
    currentProfileId: "en-qwerty"
}

Or at runtime via the singleton (mutating calls return bool; check Lnvk.lastError on failure):

Component.onCompleted: {
    if (!Lnvk.setActiveProfileIds(["en-qwerty", "fr-azerty", "de-qwertz", "ja-romaji"]))
        console.warn(Lnvk.lastError.code, Lnvk.lastError.message)
    Lnvk.setCurrentProfileId("en-qwerty")
}

Japanese has two bundled profiles (ja-romaji, ja-12key). Hindi has transliteration (hi-transliteration) and Devanagari (hi-Deva-deva).

Custom profiles

Override or extend the bundled set by supplying inputProfiles (each object needs id, languageTag, layoutId, displayName, imeEngineId):

VirtualKeyboard {
    inputProfiles: [
        {
            id: "en-qwerty",
            languageTag: "en",
            layoutId: "en",
            displayName: "English",
            imeEngineId: "none"
        },
        {
            id: "es-qwerty",
            languageTag: "es",
            layoutId: "es",
            displayName: "Español",
            imeEngineId: "none"
        }
    ]
    activeProfileIds: ["en-qwerty", "es-qwerty"]
    currentProfileId: "en-qwerty"
}

Switching at runtime

Users switch via the globe key (when ≥ 2 profiles are active) or long-press on the space bar.

Lnvk.selectProfile("fr-azerty")   // by profile id — returns false if not found
Lnvk.selectLanguage("fr")         // first active profile with this languageTag

currentProfileId, currentLanguage, and currentDisplayName on the singleton reflect the active profile:

Text { text: Lnvk.currentDisplayName }  // e.g. "English"

Finding profiles

Discovery helpers return objects from the full inputProfiles catalog (not only activeProfileIds). Each entry has id, languageTag, layoutId, displayName, and imeEngineId. Use Lnvk.activeProfiles for the enabled subset (same shape; used by the language popup).

// Two Japanese layouts share languageTag "ja"
const japanese = Lnvk.profilesForLanguageTag("ja")

if (japanese.length > 0)
    Lnvk.selectProfile(japanese[0].id)

// Enabled profiles for the language popup
languageList.model = Lnvk.activeProfiles

selectLanguage(bcp47) switches among active profiles only (first exact languageTag match). Prefer selectProfile(id) when you know the profile id.

Available bundled profiles

Use profile id values in activeProfileIds, currentProfileId, and Lnvk.selectProfile(). Profile ids encode language and layout variant (for example ja-romaji, zh-Hans-pinyin, hi-Deva-deva). Full input methods (IME with candidate selection) are provided for Chinese, Japanese and Korean.