1. In the General Admin tree, expand the Admin node, and then double-click Locale.

   The Locale Manager form is displayed.

   Figure 7-1 Locale Manager Form

   
   Description of "Figure 7-1 Locale Manager Form"
2. Click the Edit icon next to the locale.

   A radio button opens on the form in the Default column.

3. Select the Default radio button next to the locale.
4. Click Save.

   The next time users log in to WebCenter Sites, the system displays in the new default language.

Although you can configure a multi-lingual management system, certain parts of the user interface can be displayed in one language only.

For example, the names of tables and columns in the WebCenter Sites database and individual items such as categories and source codes can have one name only. While much of the text on an individual WebCenter Sites form can be displayed in any of the languages that you have installed on your WebCenter Sites system, items such as field names and asset type names can be displayed in one language only.

Following is a list of items in WebCenter Sites that can have one name only, which means that they can be displayed in one language only:

• Asset type names

• Field names

• Asset names

• Categories

• Source codes

• Tree node names

• Site names

• Names of workflow building blocks (actions, email objects, conditions, states, steps, processes)

• Role names

• Start menu items, both Search and New

On a system that provides two or more languages, you must determine which language is going to be used by the majority of content providers and then use that language to name your sites, tabs, asset types, and so on.

When your site developers create asset types (either basic or flex), they can specify the field names for those asset types in whatever language they have available on the WebCenter Sites system. However, there are several core columns and fields that WebCenter Sites creates for all asset types by default:

• id

• name

• description

• status

• createdby

• createddate

• updatedby

• updateddate

• startdate

• enddate

• subtype

• filename

• path

• category

When WebCenter Sites displays them as fields in its interfaces, it uses the language that is set as the system default language. However, there are certain field names that are always displayed in English. See User Interface Fields that are Exceptions to Localization.

See Default Columns in the Basic Asset Type Database Table and Default Columns in the Flex Asset Type Database Table in the Developing with Oracle WebCenter Sites.

If your site developers decided to use the sample site asset type named Article, you must also modify the value for the xcelerate.body.length property in the wcs_properties.json file. This property determines how many characters are stored in the urlbody column of the Article table.

Because urlbody is a URL column, the data entered in it is actually stored as a file outside of the WebCenter Sites database. However, the first n number of characters, where n equals the value specified for the xcelerate.body.length property, is also stored in the urlbody column so that you can search for text in the body of an article asset with the search feature in the administrator's interface.

When this column holds non-ASCII text, the value for this property should be set to 500.

There are certain field names in the interfaces of WebCenter Sites that are always displayed in English irrespective of the system default language.

The Contributor interface enables you to use various keyboard shortcuts to both speed up your content management process and provide a completely accessible interface. To view the current keyboard shortcuts for the Contributor interface, press Ctrl+Alt+L from the Contributor interface to log the current keyboard shortcuts in your browser's web console.

For a list of the default keyboard shortcuts, see Keyboard Shortcuts in Using Oracle WebCenter Sites.

1. Open for editing the <shared-install-location>\elements\UI\Config\GlobalHtml.jsp file.
2. Add the config JavaScript object with a shortcuts property, in proper JSON format (config.properties), to the GlobalHtml.jsp file. In the config object, add a line for each keyboard shortcut you want to reconfigure along with the keys you want to associate with the shortcut, in the following syntax:

   config.shortcuts = {
       "ShortCutName" [Keystrokes]
       "ShortCutName2" [Keystrokes]
   }
   

   For the key command to be valid, one or more modifier keys or special keys must be used.

   • Valid modifier keys:

     • ALT

     • CTRL

     • SHIFT

     • META

   • Valid special keys:

     • ALT

     • BACKSPACE

     • CAPS_LOCK

     • CLEAR

     • CTRL

     • DELETE

     • DOWN_ARROW

     • DOWB_DPAD

     • END

     • ENTER

     • ESCAPE

     • F1 through F15

     • HELP

     • HOME

     • INSERT

     • LEFT_ARROW

     • LEFT_DPAD

     • LEFT_WINDOW

     • META

     • NUMPAD_0 through NUMPAD_9

     • NUMPAD_DIVIDE

     • NUMPAD_ENTER

     • NUMPAD_MINUS

     • NUMPAD_MULTIPLY

     • NUMPAD_PERIOD

     • NUMPAD_PLUS

     • NUM_LOCK

     • PAGE_DOWN

     • PAGE_UP

     • PAUSE

     • RIGHT_ARROW

     • RIGHT_DPAD

     • RIGHT_WINDOW

     • SCROLL_LOCK

     • SELECT

     • SHIFT

     • SPACE

     • TAB

     • UP_ARROW

     • UP_DPAD

   For example, to change the keyboard shortcut for viewing the current shortcut configuration in a browser's web console (logShortcutConfiguration), add the following to the GlobalHtml.jsp file:

   config.shortcuts = {
       "logShortcutConfiguration": ["CTRL", "ALT", "SHIFT", "L"]
   }
   

3. Save and close the GlobalHtml.jsp file.
4. Restart the server for your changes to take effect.