Italian
Links on this page to features marked Preview describe designs that are not available yet.
How to get natural Italian out of Syntic models, and what to check before you ship. The general rules for every language are on Work in other languages.
At a glance
| Language tags | it-IT, it-CH |
| Script and direction | Latin script, left to right |
| Token use | Measure with token counting on your own text; non-Latin scripts and long compounds usually take more tokens per sentence than English. |
Register and form of address
Lei (formal) or tu (informal) must be chosen; many consumer brands now use tu. With Lei, the capitalised form in writing is a stylistic choice to decide once.
Numbers, dates and currency
Decimal comma (12,50 €), dot for thousands. Dates: 5 novembre 2026, 05/11/2026.
Common pitfalls
- Gendered agreement for the user (benvenuto/benvenuta): use neutral wording (ti diamo il benvenuto) if gender is unknown.
- English tech terms (login, app, file) are widely used; prefer the form your product UI already uses.
A system prompt line that works
Writing the language instruction in Italian itself is a strong signal:
Rispondi in italiano dando del Lei all'utente, con un tono cortese e conciso.(Answer in Italian addressing the user as Lei, in a courteous and concise tone.)
Keep the rest of your instructions in whichever language your team maintains best; the model follows mixed-language system prompts reliably, and the reply language follows this line.
Test before launch
- Collect 30 or more real Italian messages, including short, misspelt and mixed-language ones.
- Have a fluent speaker grade replies for correctness, register and naturalness; then calibrate a rubric grader on their grades (Evaluate).
- Check rendering in your actual UI: line breaks, truncation and fonts.
- Re-run the set whenever you change the prompt or the model.
Was this page helpful?