Content Server 6.3
Language Pack
Configuration Instructions

Dec 2, 2005

Copyright © 2003, 2004, 2005 FatWire Software All rights reserved.

Language packs for Content Server version 6.3 are available in the following languages:

You install the language packs after you have installed the Content Server suite of products.

NOTE: Content Server must be configured with the appropriate internationalization settings to support the language packs. Consult the installation guide for your particular system configuration to ensure compliance.

For the latest release notes, check the e-docs web site.

Table of Contents 

About This Document

After you install a localized version of Content Server, you will still see English in the user interface. The English that appears is a result, for the most part, of installing the sample sites and their data, which have not been translated. The purpose of this document is to offer guidance and suggestions on how to leverage the sample sites to create localized sites. Typically, you do the additional localizaton on your development system to prepare the management system for your editorial staff.

When you create a site, you must create (from "scratch") the templates, pages, and other underlying elements of the site design. Other aspects of your site design, however, can be shared from site to site. Asset types are the most prevalent example. This document identifies areas of the sample sites that you might want to include in your own site, and describes how you can localize these areas. Note that what you localize directly in the sample site will then appear in the local language.

TOP

 

Installing the Language Pack

The following contents are part of a language pack:

To install the language pack that you downloaded, complete the following steps:

  1. Untar or unzip the file, as appropriate to your platform, to a temporary directory.
  2. Change to the temporary directory and start the installer using the appropriate installer file:  langpackinstall.bat or langpackinstall.sh
  3. Enter the appropriate information regarding your CS installation
  4. The license agreement appears. Click Yes to accept the agreement.
  5. The product selection window appears. Select Language Pack Installation v6.3.0 and click Next.
  6. At the next installation window, select Single Server and click Next.
  7. The next window identifies what you are installing and recommends that you read the installation guide. Click Next.
  8. At the next window, confirm that you want to continue. Click Install.
  9. The program begins importing language-specific elements and then displays a warning message that instructs you to start (or restart) the application server. After you do as instructed, click OK.
  10. The program resumes importing language-specific elements. When the system displays the "installation successful" message, click OK.
  11. Click Exit, then click OK to confirm that you want to exit.

The language pack installation is complete.

After you install the language pack, you must set the language default for your locale. The default is English. To change the default language:

  1. Log in to Content Server and select the Admin tab.
  2. Double-click Locale.
  3. On the Locale Manager form, click the pencil icon next to the language that you installed.
  4. Select that language as the default.
  5. Click Save.

You can also set a language preference for individual users that overrides the default setting, as follows:

  1. Select the Admin tab and double-click User Profiles.
  2. On the User Profile Management form, enter a user name and click Select.
  3. Click the pencil icon to open the Edit form and select a language from the Locale Preference drop-down list.
  4. Click Save.
  5. Repeat the procedure for each user for whom you want to set a language preference.

Note that, while users themselves can select their language preference in the browser, the language that you set in the user profile takes precedence.

TOP

 

Localization Notes

You can localize the following general areas of your site design:

This document makes specific recommendations for what you can translate into the local language and how to do it. In some cases, you will translate directly in the CS user interface; in others, you will translate in a database table, using Content Server Explorer. This document also advises on what not to translate. For example, to ensure that the sample sites work correctly, this document may advise you to not translate certain entities. Instead, this document will recommend that you create new versions of these entities in the local language, based on the existing English versions.

Asset Types

Asset types appear throughout the user interface in lists and drop-down menus.

To localize asset type names that appear in the user interface:

  1. Open Content Server Explorer and expand Tables.
  2. Scroll to and click the AssetType table.
  3. For each asset type, translate the text in the description and plural columns. Do not change the values in the assettype column.
  4. Save your changes.

If you are unsure how to change column values, see Editing in Content Server Explorer.

NOTE:Assets created with AssetMaker require that the asset descriptor file DESCRIPTION and INSTRUCTION tags (but nothing else) for all properties be localized. The sample sites include four AssetMaker assets (HelloArticle, HelloImage, ImageFile, and StyleSheet). You must localize these tags in the respective descriptor file if you are going to use these asset types in your site. Database column names are not be localizable

Because assets are associated with sites, you can now enable localized assets for your site:

  1. Log in to Content Server and select the Admin tab.
  2. Select Site > your site > Asset Types > Enable.
  3. On the form that appears, select the assets that you want to enable for your site. Note that the Name column lists the assets by their internal names; these internal names cannot be localized. The Description column displays the localized names.
  4. Click Enable Asset Types.

The localized names will also appear in the sample sites for which they are enabled. After you enable the localized assets for your site, you can proceed with asset configuration.

Asset Configuration

Asset configuration involves setting some or all of the following values, depending on the asset type definition:

Categories

Categories appear in drop-down menus on asset forms that support categories. The categories that currently appear in the user interface are specific to the sample sites. You can create new, localized categories.

  1. In the CS user interface, select the Admin tab and expand Asset Types.
  2. For the assets (enabled for your site) that support categories, expand the asset, then expand Categories and double-click Add New.
  3. On the form that appears, enter a localized description and appropriate code.
  4. Click Add New Category.

The categories that you add will be available on asset forms that support categories.

If the asset type that you are working on supports subtypes, continue with subtype setup.

NOTE: Because category descriptions affect only the user interface, you can optionally choose to localize the sample site categories. Using Content Server Explorer, localize the description column in the Category table for all assets that support categories.

Subtypes

Subtypes appear in drop-down menus on asset forms that support subtypes. The subtypes that currently appear in the user interface are specific to the sample sites. If you change their values, the sample sites will not work correctly. Rather, you should create new, localized subtypes.

  1. For the assets (enabled for your site) that support subtypes, expand the asset and double-click Subtypes.
  2. In the right frame, click Add New Subtype.
  3. On the form that appears, enter a localized subtype name and select your site from the list of sites.
  4. Click Add New Subtype.

The subtypes that you add will be available on asset forms that support subtypes.

If the asset type that you are working on supports associations, continue with association setup.

NOTE: If you do not need to preserve sample subtypes, you can localize the subtype column in the AssetSubtypes table for all assets that support subtypes, using Content Server Explorer.

Associations

Associations appear in drop-down menus on asset forms that support associations. The associations that currently appear in the user interface are specific to the sample sites. You can create new, localized associations.

  1. For the assets (enabled for your site) that support associations, expand the asset, then expand Asset Associations and double-click Add New.
  2. On the form that appears, enter a localized name and description.
  3. Select your site and then complete the rest of the form.
  4. Click Add New Association.

The associations that you add will be available on asset forms that support associations.

Continue with start menu setup for the asset.

NOTE: Because association descriptions affect only the user interface, you can optionally choose to localize the sample site associations. Using Content Server Explorer, localize the description column in the AssocNamed table for all assets that support associations.

Start Menu Setup

Each asset type can have up to four start menu settings, so that users can do the following:

To configure start menu settings for the assets that are enabled for your site:

  1. Expand the asset, then expand Start Menu and double-click Add New.
  2. On the form that appears, enter a localized name and description.
  3. Select New from the Type drop-down menu.
  4. Select your site and then complete the rest of the form.
  5. Click Save.
  6. Perform setup for the other start menu types for this asset, as appropriate for your site.
  7. Repeat the procedure for the other assets that are enabled for your site.

The fields that appear in the Default Values drop-down menu on the form derive from column headings in the database table for the asset type. These values cannot be translated.

Assigning roles to a start menu item is part of start menu setup. If you are localizing roles, you should complete role localization before doing the start menu setup.

NOTE: If you do not need to preserve sample start menus, you can localize the sample menus for all assets from the Start Menu selection on the Admin tab.

Miscellaneous Configuration Items

These are other aspects of configuration that display English in the language packs:

Sources

Sources appear in drop-down menus on asset forms that support sources. The sources that currently appear in the user interface are specific to the sample sites. You can create new, localized sources.

  1. In the CS user interface, select the Admin tab and expand Sources.
  2. Double-click Add New.
  3. On the form that appears, enter a localized source and description.
  4. Click Add New Source.

The sources that you add will be available on asset forms that support sources.

NOTE: Because source descriptions affect only the user interface, you can optionally choose to localize the sample site sources by editing the listed sources under the Source selection on the Admin tab.

Publishing

Publishing choices on the Admin tab include Destinations and Delivery Types. The default destinations (Static and Dynamic) appear in English, as do the three available delivery types. These values appear on forms in the user interface.

Because destinations are associated with specific sites, you can define your own localized destinations and choose not to enable Static and Dynamic for your site.

If you want to localize delivery types:

  1. In the CS user interface, select the Admin tab.
  2. Expand Publishing then Delivery Types.
  3. Double-click Export to Disk.
  4. On the form that appears, enter a localized name and description. Do not change the Delivery Elements Path.
  5. Click Save.
  6. Repeat the procedure for the other delivery types, as appropriate for your site.

Tree Tabs

Tree tabs appear in the left frame of the CS user interface. Users rely on these tree tabs to navigate the site and use most of the CS functions. The tabs that currently appear are specific to the sample sites. If you change their values, the sample sites will not work correctly. Rather, you should create new, localized tree tabs.

  1. On the Admin tab, double-click Tree.
  2. In the right frame, click Add New Tree Tab.
  3. On the form that appears, enter a localized title and tooltip.
  4. Select your site and then complete the rest of the form.
  5. Click Save.

Assigning roles to a tree tab is part of adding a new tree tab. If you are localizing roles, you should complete role localization before adding new tree tabs.

The tabs that you add will appear in the left frame of the CS user interface for your site.

NOTE: If you do not need to preserve sample sample tree tabs, you can localize them by editing the title and tooltop for each tab that appears in the tabs list in the left frame.

Locale

There is a configuration entry for each language pack that you installed. You can localize each language/country pair.

  1. On the Admin tab, double-click Locale.
  2. Click the pencil icon next to each language to localize the text.
  3. Click Save.

Workflow-related Items

The following are workflow-related items that you may want to localize for use on your site.

Roles

Sample site roles appear throughout the CS user interface. The roles that currently appear in the user interface are specific to the sample sites. If you change their values, the sample sites will not work correctly. Rather, you should create new, localized roles.

  1. In the CS user interface, select the Admin tab and expand Roles.
  2. Double-click Add New.
  3. On the form that appears, enter a localized name and description.
  4. Click Add New Role.

The roles that you add will be available wherever you are required to assign roles.

Workflow Actions

The actions available under Workflow Actions on the Admin tab are used by the sample workflow processes. You can localize these actions by translating their descriptions. Do not, however, translate the element names and arguments.

E-Mail Messages

The workflow e-mail messages available under Email on the Admin tab are used by the sample workflow processes. You can localize these e-mail messages by translating their descriptions, subjects, and message bodies. Do not, however, translate the names and variables.

Workflow Functions

The workflow functions available under Functions on the Admin tab are used by the sample workflow processes. They appear only to administrators. If you want to localize functions as they appear to administrators, open the Edit form for each function and translate its description, but do not translate anything else.

Sample Workflow Processes

Workflow processes are associated with specific sites. If you want to adapt the sample workflow processes to a localized site:

  1. In the CS user interface, select the Workflow tab and expand States.
  2. Re-create the states used by the process that you want to adapt. You can do either of the following:
  3. On the Workflow tab, expand Processes.
  4. Adapt the selected process to use the localized states that you just created. You can either localize the sample process and its steps; or create a new, localized process that mirrors the sample.
  5. Be sure to click Save when you are done.

Sample Data

Sample data consists of the following items:

None of these is a candidate for localization. Rather, you can use them as examples of how to design a site, code pages, build a flex family, and so forth. If you choose to adapt existing queries, remember that the queries are composed in their own language and must not be translated.

Editing in Content Server Explorer

To edit a database table column using Content Server Explorer:

  1. Click the column value that you want to edit.
    A border appears around the value. (If the border appears, but the background remains gray, the column cannot be edited.)
  2. Edit the value (delete, insert, type over, as appropriate).
  3. When you are done, press Return, or select another column value.
    A red asterisk appears next to the ID of the item in the right pane, and next to the containing table in the left pane, to indicate that changes are pending.
  4. Continue with additional edits.
  5. When you are done, select File Save or click the Save icon to record your changes. There is also a File Save All menu selection and icon, if you want to save multiple tables that you changed.

TOP

 

 Contacting FatWire Software 

To contact FatWire Software about technical support for your product:

Web: http://www.fatwire.com/Support/index.html

TOP

 

 

FatWire
Documentation

Copyright © 2003, 2004, 2005 FatWire Software All rights reserved.