Creating New Culture Strings

As needed, follow these steps to create a Culture Strings record that will display localized content for each culture:

1. Add the Localization Administration application to your profile, if necessary.
2. Expand the Localization Administration heading and open a new record for the Culture Strings service.
3. Enter a Name for the culture string.
   • Culture String Names must be unique. This prevents object methods that are associated with multiple Culture Strings records to retrieve the incorrect culture string.
   • Aptify uses the name to identify the type of culture string and the location to which it applies (such as Entities.DisplayName.SalesTargets to identify the culture string that applies to the Sales Targets entity's display name).
      
4. Enter the default text for this string in the Base String field.
   • This is the record's name field; it is the string's representation in the neutral/base culture.
   • This is the string that appears for users are either not assigned a culture or whose culture (or base culture) does not have a Local Strings sub-type record.
      
5. Enter a Description of the string in the field provided.
6. Enter a Category for this string. This field links to the Culture String Categories service.
   • See Creating Culture String Categories for information on Culture String Categories.
     
      
7. Save the record.
8. Click the Local Strings tab.
   • The Local Strings tab displays a grid of available cultures for which you can specify a location translation of the Base String.
   • The available cultures are defined in the Cultures service. See Defining Cultures for details.
      
9. Enter the text that corresponds to the specified culture directly within the grid.
   • This is the text that will appear in Aptify for users who are associated with the culture you entered in the Culture field.
   • For example, if you are localizing the term Attachments for Spanish users, you would enter Adjuntos in the Local String field, as shown below.
   • If you are localizing a menu option that supports a shortcut key combination (for example, an underline appears under one letter of the word and pressing the Alt key plus that letter executes that particular function), you can define which letter in the localized string to use as the shortcut key by placing an ampersand (&) before the desired letter in the Local String definition. See the Culture Strings record for "OK" (ID 470) for an example.  
     
     
10. If you want to record additional comments about a particular local string, double-click within its row or click the Open button in the toolbar to open the corresponding Local Strings record shown below). Click OK to save and close this record if you make any changes.  
    
    

11. Enter local strings for additional cultures as necessary.

     If you have not specified a Local String for a particular sub-culture, users of that sub-culture will use the Local String for their culture's Base Culture. For example, if you created an Attachments local string for the English base culture but not for the United States and United Kingdom sub-cultures, then this string applies to users associated with the en, en-US, and en-GB cultures.

    
     

12. Save and close the Culture Strings record.
13. Add additional Culture Strings records as necessary.
14. Review the set of existing Culture Strings records and add Local Strings for your organization's supported cultures as necessary.
    • The Culture Strings service includes a set of records to localize the standard commands in the user interface (such as the menus and the button bar on each form). An organization only needs to add the applicable Local Strings for the organization's supported cultures to these Culture Strings. See About the Commands Form for more information on the standard commands in Aptify.