import { FC } from 'react';
import { AssistantLanguage } from '../../voice/languages';
interface Props {
    /** The language currently in effect, already resolved (never null) — for display. */
    current: AssistantLanguage;
    /**
     * The RAW stored preference: `null` means "follow the interface".
     *
     * The select must be driven by this rather than by `current`, or the two
     * states collapse: while following an English interface, English is already
     * the shown option, so choosing English fires no change event and the
     * preference can never be pinned — and a later interface switch then moves
     * the assistant language with it, which is exactly what the user was trying
     * to prevent.
     */
    selected: string | null;
    /** `null` restores "follow the interface language". */
    onChange: (code: string | null) => void;
    disabled?: boolean;
}
/**
 * Pick the language you SPEAK to the assistant (BOFF-7108).
 *
 * A native `<select>` on purpose. On a phone — which is where a farmer dictating
 * in Tamil actually is — this opens the OS picker, which is already localised,
 * already scrolls properly, and already handles 17 languages across five scripts
 * without us reimplementing any of it. A custom dropdown would look tidier in a
 * desktop screenshot and be worse everywhere that matters.
 *
 * Each option is labelled with its ENDONYM (`தமிழ்`, not `Tamil`): a user who
 * reads only Tamil cannot find "Tamil" in a list. The visible trigger shows the
 * language code so it stays narrow in a docked panel, with the full name as the
 * accessible label.
 */
export declare const AssistantLanguageSelector: FC<Props>;
/** Not a language code, so it can never collide with one. */
export declare const FOLLOW_APP_LOCALE = "__app__";
export {};
//# sourceMappingURL=AssistantLanguageSelector.d.ts.map