Provide "Copy to (locale)" option in the developer console
Right now the process of adding a new language to an existing skill in the developer console is tedious, especially when the data for those languages is exactly identical.
For example, right now, the process for manually copying things on the Publishing Information tab (Launch tab on the new console) alone involves tabbing back and forth 12 different times between the two languages to copy the text from the six different fields. For an English language skill being released worldwide, that process has to be done 4 times (and that's only going to grow).
Making things worse, in the new console, each time you tab you also get forced into a "save" dialog even if you didn't change anything (as described here: https://alexa.uservoice.com/forums/906892-alexa-skills-developer-voice-and-vote/suggestions/33345916--unsaved-data-flow-doesn-t-work-properly) which further multiplies the number of manual clicks you have to make just to have a new language with identical configuration.
A "copy to (select locale)" option would be much preferrable.
Acknowledging that there are minor differences in the available intents between locales (US first name intent not available in India, etc), it would be reasonable to still do the copy but just notify the developer that their intent model needs fixing.
Eric Olson
shared this idea
Thanks for submitting this suggestion Eric. We’ll get this routed over to the appropriate internal team for review.
2 comments
-
MoMA
commented
Correction. This can be done in the JSON Editor.
-
MoMA
commented
AND...the default English is en-AU so I just added 15 utterances to en-AU and there does not seem to be a way to copy those to en-US (or en-UK).