Existing language strings for an application can be customized for any language in the Geocortex Web Designer. To provide a complete translation in an entirely new locale for Geocortex Web, please contact us.
Geocortex Web was designed to be fully internationalizable on all levels of the product, from app config to custom code. A major component of this is language strings. Language strings provide a couple advantages over hardcoding plain text in a component.
- Language strings can be easily translated or modified without having to change component code.
- Language strings can be shared across components.
- Language strings consolidate user facing text throughout the application, making it easy to review and find.
It is recommended you use language strings for all user facing text in your application.
Language strings are defined as properties in a plain JSON file. It's convention to define language strings with the format
If you define a language string that Geocortex Web has already defined, it will override the existing language string with your custom string.
By convention, these files are named after the locale they represent. For example, a file of german language strings would be named
All language resource files need to be registered with the SDK before they can be used.
Geocortex Web has full language tag support as specified in the WC3 spec. The casing of a language tag determines what is it parsed as.
- All lowercase tags like
deare parsed as a language code.
- Region codes, like
- Script codes like
ru-Latnare pascal cased.
Regional locales will not be used as fallback locales for a language. This means that if a browser is configured in the
de locale, but language strings are registered with the
de-AT locale in Geocortex Web, the fallback translation, not
de-AT, will be shown.
Internationalization in App Config
Learn how to use language strings in the app config
Learn how to use language strings for user facing text in components