import { FC } from 'react';
/**
 * Language, in ONE place.
 *
 * ★★ This replaces two controls that looked identical and lived apart: a globe
 * chip in the composer (the language you SPEAK) and a separate row in this menu
 * (the language the assistant ANSWERS in). Same icon, same kind of list, no
 * visible words telling them apart — so they read as the same setting shown
 * twice, and the person who commissioned the split read them that way too.
 *
 * ★ They are not quite the same, and the difference is worth keeping: reply
 * language also chooses the VOICE, and a farmer may dictate in Tamil but want
 * the answer in English to forward to a buyer. But that is an override, not a
 * peer setting — so it is subordinate here rather than living somewhere else
 * entirely.
 *
 * ★★ The default couples them. `replyLanguage: null` means MATCH THE INPUT, so
 * a user who picks Tamil gets Tamil answers without touching the second row.
 * The second row exists to BREAK that coupling, and announces the language it
 * currently resolves to so "Match my language" is never a mystery.
 *
 * ★ Both stay native `<select>`s. On a phone that opens the OS picker, which
 * already scrolls, searches and localises itself — worth far more across nine
 * Indic languages than a custom dropdown that reimplements all three badly.
 */
export declare const AssistantLanguageMenu: FC;
//# sourceMappingURL=AssistantLanguageMenu.d.ts.map