[null,null,["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003eActions Builder and the Actions SDK enable developers to create Actions that support multiple languages and regions.\u003c/p\u003e\n"],["\u003cp\u003eBy default, Actions support all regions and utilize a Text-to-Speech voice corresponding to the user's locale, but developers can customize the TTS voice.\u003c/p\u003e\n"],["\u003cp\u003eSuccessful localization requires translating all user-facing content, including intent training phrases, into the supported languages.\u003c/p\u003e\n"],["\u003cp\u003eUser's Assistant language and device region settings combine to form a locale that needs to be supported by Actions on Google for the Action to function correctly.\u003c/p\u003e\n"]]],[],null,["# Build localized Actions\n\nActions Builder and the Actions SDK both support localization of your Action.\nWhen you serve your Action in multiple languages, the user-facing content of\nyour Action requires translation. For example, intents should have multilingual\ntraining phrases.\n\nBy default, your Action projects support the following:\n\n- Supports all regions (countries), as long as your users have set their Google\n Assistant device to a geographic region supported by Assistant and a language\n supported by your Actions project.\n\n- Uses a Text-To-Speech voice that corresponds to the user's Assistant locale.\n You can override this behavior and choose a specific TTS voice that doesn't\n change based on the user's Assistant locale.\n\n| **Note:** Locales are constructed using the language set in the Assistant settings and the region set in the device settings. The combination of these needs to form a supported locale. For example, a device set to the Brazil (BR) region and an Assistant device set to en-US results in a en-BR locale, which is not supported by Actions on Google.\nActions Builder Actions SDK"]]
