You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, as I'm working on the manual, I'm noticing something about the speak label.
So, the options for the language dropdown are either automatic or any of the other languages the grid has been translated into. That means an element in an English grid set that is labeled in English could instead speak the word in Hindi, if the grid set has been translated to Hindi. I can't think of a real life use at the moment. Was this made because the change language/voice wasn't available at first? The only useful life usage I can think of right now is if the collection element could speak in another language (something like two collection elements, one speaks "normal" and the other speaks in another language or a separate button to make the content of the collection element speak in another language, so basically to "translate" what the user has said into another language) but that's not what this action can do. (Edit: Just realised that AG automatically translates after switching the language, so ignore that last part.)
If that option wasn't created because there were users who requested it for specific situations, I wonder if it would make sense to hide it, so people don't get confused with this and the change language/voice action and the voice/language option in the grid set settings.
Edit: Similar for speak custom text, could it make sense to hide the language option?
The text was updated successfully, but these errors were encountered:
Yes, I think I've added it before there was the option to change the content language by action, or even before there was the possibility to translate grid sets at all.
So I also think that it probably could be hidden or removed. @arasaac-dga: what do you think?
So, as I'm working on the manual, I'm noticing something about the
speak label
.So, the options for the
language
dropdown are eitherautomatic
or any of the other languages the grid has been translated into. That means an element in an English grid set that is labeled in English could instead speak the word in Hindi, if the grid set has been translated to Hindi. I can't think of a real life use at the moment. Was this made because thechange language/voice
wasn't available at first?The only useful life usage I can think of right now is if the collection element could speak in another language (something like two collection elements, one speaks "normal" and the other speaks in another language or a separate button to make the content of the collection element speak in another language, so basically to "translate" what the user has said into another language) but that's not what this action can do.(Edit: Just realised that AG automatically translates after switching the language, so ignore that last part.)If that option wasn't created because there were users who requested it for specific situations, I wonder if it would make sense to hide it, so people don't get confused with this and the
change language/voice
action and the voice/language option in the grid set settings.Edit: Similar for
speak custom text
, could it make sense to hide the language option?The text was updated successfully, but these errors were encountered: