Support for multiple language descriptions in Geodatabase Domains

793
1
05-13-2013 12:04 PM
Status: Open
PaulBrandt
Occasional Contributor
I would like to see support for implementing multiple languages in geodatabase domain descriptions, and the ArcGIS system automatically display the appropriate language configured for the client application, similar to a resource file implementation for UI labels and other items. More and more we are supporting multi-national companies that require this ability, and the workarounds I have seen for this are an obvious hack at best.

Example Domain:
code1 -- English Description -- French Description -- French Canadian Description -- Spanish Description....
code2 -- English Description -- French Description -- French Canadian Description -- Spanish Description....
1 Comment
TomasoBertoli

Considering the current evolution from geometric Network into the Utility Network and the new Multiplatform Service Architecture it should be relatively easy to extent the GeoDataBase Model \ Architecture to support not only Coded Domain Descriptions in multiple languages as suggested in this geonet.esri.com/ideas/7521 [Support for multiple language descriptions in Geodatabase Domains ] but also: 

  • Feature Class Aliases 
  • Field Aliases
  • Code Domains

The new "services" could implement an (optional) parameter LanguageCode such as [List of ISO 639-2 codes - Wikipedia ] to allow the Server to respond with the appropriate encoding for the client, the response of the Service should include a ClassID and the LanguageCode to allow the client customizations to more easily handle the different "descriptions" for "classes" and "fields"  

The new "clients" could (preferably) implement an (optional) language switch selector, using the Locale of the operating System would also be possible but it is probably more complicated across different platforms and shared architectures

A new "adiministration" tool for the Geodatabase could easily allow for the addition and "manual" translation of new languages in one give geodatabase; A simple XML Export \ Import Language tool would allow a very configuration and the use of external translation services (not included)