Cómo especificar textos localizados
Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Se recomienda admitir la localización en la integración de Acciones de reservas de extremo a extremo. A los usuarios se les muestra una experiencia localizada según su configuración de idioma. Si no se establece ninguna localización, es posible que se le muestre al usuario el texto predeterminado. Puedes proporcionar texto localizado para muchos campos de la integración, como los nombres y las descripciones de los servicios. Consulta nuestras especificaciones del feed para obtener la lista completa de los campos que se pueden localizar con el mensaje Text.
Implementa la localización
// A possibly-localized text payload. Some Text fields may contain marked-up
// content.
message Text {
// Required. Text value in an unknown locale, which will be displayed if
// `localized_value` for the user locale is empty or missing. The locale for
// this value may depend on the partner or service provider, and it should not
// be assumed to be any specific language.
string value = 1;
// Per-locale text values. Required.
repeated LocalizedString localized_value = 2;
}
Cualquier campo de los feeds que use un mensaje Text se puede localizar proporcionando un localized_value para cada idioma admitido.
Es obligatorio especificar value y
localized_value.
- Mostraremos el
localized_value según la configuración regional del usuario (que se establece en la configuración de idioma del navegador del usuario).
- El valor se usará de forma predeterminada cuando la configuración regional del usuario no esté en tu lista de localizaciones admitidas.
- Si no defines el valor y la configuración regional del usuario no está en tu lista de localizaciones admitidas, usaremos el primer valor presente en localized_value. Si bien este resguardo está disponible, te recomendamos que especifiques el valor predeterminado de forma explícita.
Si no admites la localización en tu sistema, configura localized_value y locale con el único idioma que admites. También establece value, que se puede usar como valor predeterminado.
Ejemplo de fragmento de feed de servicios
"localized_service_name": {
"value": "Chocolate Tasting",
"localized_value": [
{
"locale": "en",
"value": "Chocolate Tasting"
},
{
"locale": "fr",
"value": "Dégustation de chocolats"
}
]
}
Salvo que se indique lo contrario, el contenido de esta página está sujeto a la licencia Atribución 4.0 de Creative Commons, y los ejemplos de código están sujetos a la licencia Apache 2.0. Para obtener más información, consulta las políticas del sitio de Google Developers. Java es una marca registrada de Oracle o sus afiliados.
Última actualización: 2025-07-26 (UTC)
[null,null,["Última actualización: 2025-07-26 (UTC)"],[[["\u003cp\u003eLocalization in Actions Center Reservations is highly recommended to provide users with a tailored experience based on their language settings.\u003c/p\u003e\n"],["\u003cp\u003eLocalizable fields, such as service names and descriptions, can be found in the feed specification, and are identified by utilizing the \u003ccode\u003eText\u003c/code\u003e message type.\u003c/p\u003e\n"],["\u003cp\u003eImplementing localization involves providing both a default \u003ccode\u003evalue\u003c/code\u003e and \u003ccode\u003elocalized_value\u003c/code\u003e entries within the \u003ccode\u003eText\u003c/code\u003e message, enabling the system to display the appropriate text based on the user's locale.\u003c/p\u003e\n"],["\u003cp\u003eIf localization is not supported, it's crucial to specify the \u003ccode\u003elocalized_value\u003c/code\u003e and \u003ccode\u003elocale\u003c/code\u003e with the supported language, while also setting the default \u003ccode\u003evalue\u003c/code\u003e for fallback purposes.\u003c/p\u003e\n"]]],["Localization is strongly recommended in the Actions Center Reservations integration. Fields using the `Text` message can be localized by specifying a `localized_value` for each supported language and a default `value`. The user's locale, from their browser settings, determines which `localized_value` is displayed. If the user's locale isn't found, the provided `value` is the default. If `value` is not set, the first value from `localized_value` is used. Even for single-language support, set both `value` and `localized_value`.\n"],null,["# Specify localized texts\n\nIt is highly recommended to support localization in the Actions Center Reservations End-to-End\nintegration. Users are shown a localized experience based on their language\nsettings. If no localization is set, the default text may be shown to the\nuser. You are able to provide localized text for many fields in the\nintegration, such as service names and descriptions. Please refer to our\n[feed\nspecification](/actions-center/verticals/reservations/e2e/integration-steps/feeds) for the full list of fields that can be localized by using the\n`Text` message.\n\nImplementing localization\n-------------------------\n\n```mysql\n// A possibly-localized text payload. Some Text fields may contain marked-up\n// content.\nmessage Text {\n // Required. Text value in an unknown locale, which will be displayed if\n // `localized_value` for the user locale is empty or missing. The locale for\n // this value may depend on the partner or service provider, and it should not\n // be assumed to be any specific language.\n string value = 1;\n\n // Per-locale text values. Required.\n repeated LocalizedString localized_value = 2;\n}\n```\n\nAny field in the feeds that uses a `Text` message can be localized by providing\na `localized_value` for each supported language.\n\nIt is required to specify both the `value` and\n`localized_value`.\n\n- We will show the `localized_value` based on the user's locale (which is set in the user's language browser settings).\n- Value will be used as a default when the user's locale is not in your list of supported localizations\n - Should you not define value and the users locale is not in your list of supported localizations we will use the first value present in localized_value. While this fallback is available it is strongly recommend for you to specify the default value explicitly.\n\nIf you do not support localization in your system, please set\n`localized_value` and set `locale` with the only\nlanguage you support. Set `value` as well which may be used as a\ndefault.\n\nExample Services Feed Snippet\n-----------------------------\n\n```scdoc\n \"localized_service_name\": {\n \"value\": \"Chocolate Tasting\",\n \"localized_value\": [\n {\n \"locale\": \"en\",\n \"value\": \"Chocolate Tasting\"\n },\n {\n \"locale\": \"fr\",\n \"value\": \"Dégustation de chocolats\"\n }\n ]\n }\n```"]]
