Test your actual use#
Use a short sentence in the language and speaking style you plan to use. Include a name and an important constraint. If you switch languages within a sentence, evaluate that case separately rather than assuming a single-language success covers it.
Keep the raw transcript and note the model and input mode. Technical terms and names may need manual correction even when ordinary sentences are recognized. Type exact strings when ambiguity matters.
Do not borrow another product’s list#
A competitor’s support for many languages does not establish CueSpec support. The relevant evidence is the model bundled or selected in CueSpec, its configuration, and tests of the complete capture-to-draft route.
Until a verified matrix is published, treat language suitability as something to evaluate on your setup. The editable-draft route remains useful because it lets you repair meaning before delivery. Optional text refinement needs its own language assessment and should not be assumed to translate or preserve every mixed-language instruction correctly.