Skip to main content
New Idea

Ability to add custom Localization Language attributes

Related products:PX Admin & Security

  • Helper ⭐️⭐️
  • 64 replies

We have the requirement to support language for Spanish-Latin America (es-419) within GainsightPX (as we do in our product). Is it possible to add custom language attributes within GainsightPX to be used across the product suite?

2 replies

JPKelliher
Forum|alt.badge.img
  • Contributor ⭐️⭐️⭐️⭐️⭐️
  • 59 replies
  • May 1, 2023

@lpicone , could you please provide a bit more detail on your use case? Is it that you need to use the locale “419” so that your translations do not default to “es”? 

 

We have worked with the localization features quite a bit and have found some workarounds. If your default version of Spanish is Latin American Spanish, you can load your XLIFF files into the “es” default and any locale should default to the parent language (in this case “es”).

 

Example: all xliff files are loaded with <target> equal to “es”. 

 

If you must differentiate between only two locales, Castellano Spanish and Latin American Spanish, you can try sending a specific locale code for all Latin American Spanish and a specific locale for all Castellano Spanish.

 

Example: Latin American Spanish = es-CR 

                   Castellano Spanish = es-ES

 


  • Author
  • Helper ⭐️⭐️
  • 64 replies
  • September 25, 2023

@JPKelliher 

Sorry! Just seeing this now. ‘es-419’ is the value used by the localisation team. I would like to go the other way, attempting to standardize using just the language value and not the country (except for specific cases). 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings