New top level fields, translations

[jeyrb]

@lollox80 There are some new translations, automated, so not too sure if it's idiomatically good

spoken_message:
name: "Messaggio parlato"
description: "Un'alternativa parlata al Messaggio, usata dai trasporti che lo leggono ad alta voce (ad es. Alexa, TTS)."
extra_data:
description: "Dati passanti e regolazione del trasporto per trasporti/blueprint che qui si aspettano propri campi, ad es. attributi da un blueprint di notifica Frigate."

Sound OK? Is "Dati passanti" good for pass-through and "regolazione del trasporto" for transport tuning.

[lollox80]

@jeyrb Thanks for checking. The gist is understandable, but a few bits read as machine translation. Three points, most important first.

1. transports → "trasporti": please don't translate this one. In Italian "trasporto" means freight or passenger transport — lorries, trains, shipping. It also breaks the link with the YAML key the user actually types (transport: alexa_media_player), so the translated text becomes harder to map onto the config, not easier. In Italian HA translations this kind of domain term is normally left in English. If a native word is really needed, "canale" (channel) works — but "trasporto" does not.

2. "Dati passanti" for pass-through: no. That is a literal calque that isn't used in Italian. Pass-through is rendered as "inoltrati così come sono" (forwarded as-is) or "trasmessi invariati".

3. "regolazione del trasporto" for transport tuning: the concept is right, the wording isn't. "regolazioni specifiche del transport" is the natural phrasing. Also "che qui si aspettano propri campi" is convoluted — "che richiedono campi propri" reads much better.

Minor: "Messaggio parlato" is understandable but "Messaggio vocale" is what an Italian speaker expects in a notification UI. And "blueprint di notifica Frigate" needs the preposition: "blueprint di notifica di Frigate".

Proposed wording:

spoken_message:
  name: "Messaggio vocale"
  description: "Alternativa vocale al campo Messaggio, usata dai transport che leggono la notifica ad alta voce (es. Alexa, TTS)."

extra_data:
  name: "Dati aggiuntivi"
  description: "Dati inoltrati così come sono e regolazioni specifiche del transport, per transport o blueprint che richiedono campi propri, es. gli attributi del blueprint di notifica di Frigate."

General note for the automated Italian pass: blueprint, transport, delivery, scenario and recipient should all stay in English throughout — they are the config keys users type. Happy to review the rest of it.json if that helps.

[jeyrb]

Thanks for that, made the changes, feel free to correct any of the others. At least two languages will be right!