Chapter 14: Deploying Office 2003 Multilingual Resources | Microsoft Office 2003 Editions Resource Kit (Pro-Resource Kit)

Download CD Content

Deploying Microsoft Office 2003 with the Microsoft Office 2003 Multilingual User Interface Pack (MUI Pack) is typically a straightforward process. You can easily include one or more MUI Packs with your Office deployment by using several methods, including chaining packages to the installation. The topics in this chapter describe the basic customization and installation procedures for different kinds of multilingual installations.

Customizing and Installing Office 2003 MUI Packs

When you customize and install Microsoft Office 2003 Multilingual User Interface Packs (MUI Packs) together with your Office installation, you can include language options in your Office deployment to configure your users’ installations appropriately for the MUI Packs you deploy. You can also chain your MUI Packs together with Office to deploy them together, simplifying the process.

Another option is to install MUI Packs after your Office installation. This scenario may be more appropriate if your language needs change after you have installed Office, or if you want to stage your Office and MUI Pack deployments.

Customization options for a MUI Pack deployment

There are several types of settings you might customize to properly configure your users’ computers to use the MUI Packs you deploy, and to help ensure that a deployment with Office proceeds smoothly.

Language settings, which include the Install Language, User Interface Language, Help Language, and Editing Languages.
Feature installation states to help provide additional support for certain languages.

For example, you could choose to install the Bidirectional Support feature on users’ computers if you are deploying MUI Packs for languages that read right to left.
Setup properties to allow deployment technologies such as Microsoft Systems Management Server (SMS) to work properly with your Office and MUI Pack installation.

For step-by-step information on configuring all of these options, see the section “Customization Methods for a MUI Pack Deployment” later in this chapter.

Language settings you can customize

You can customize the following language settings when you deploy MUI Packs with Office:

Installation language Sets defaults for Office applications and documents. Also called the default version of Office or the installed version of Office.
User interface language Determines language used by menus and dialogs.
Help language Determines language used for user Help.
Editing languages Determines functionality for editing documents in selected languages.

You can only configure these language settings when you use an Office transform; you cannot configure these settings in a MUI Pack transform.

Note

If you want to help prevent your users from changing language settings, you can specify settings for users with Group Policy. In the Office policy template (Office11.adm), specify policies under Language Settings. For more information about using Group Policy with Office 2003, see “Managing Users’ Configurations by Policy” in Chapter 18, “Updating Users’ Office 2003 Configurations.”

For more information about how language settings work and when to configure them, see “Customizing Language Settings” in Chapter 13, “Preparing for an Office Multilingual Deployment.” For details about how language settings affect the behavior of each Office application, see “Effects of Customizing Language Settings on Office Applications” in Chapter 13, “Preparing for an Office Multilingual Deployment.”

Feature installation states you can customize

You can customize feature installation states to help ensure that the required language features are installed for the MUI Packs you are deploying.

You select these language-specific features on the Set Feature Installation States page in the Custom Installation Wizard. For more information about customizing options in the Custom Installation Wizard for deploying Office with MUI Packs, see the section “Use the Office transform to customize your MUI Packs” later in this chapter.

When you customize these features, keep in mind the following:

If your users work with Asian, Georgian, Armenian, Hindi, or Tamil text and they are not running a matching language version of Microsoft Windows , you may need to install the Japanese or Syriac fonts on users’ computers. These features are included under Office Shared Features | International Support on the Set Feature Installation States page.
If your users need a full Unicode font—for example, if they are working with Microsoft Office Access 2003 datasheets that include languages that use more than one code page—install the Universal font on users’ computers.

Setup properties you can customize

There are three Setup properties you may want to customize when you are deploying MUI Packs: CHECKINSTALLORDER, NOFEATURESTATEMIGRATION, and SKIPLANGCHECK. For more information about how to use these properties with Office 2003 Setup, see “Setup Properties” in Appendix B, “Office 2003 Resource Kit Reference.”

Setting the CHECKINSTALLORDER property

The CHECKINSTALLORDER property allows the MUI Pack files to be installed before Office is installed. Set this property to False when the installation order for a chained deployment cannot be determined in advance; for example, with deployments using SMS or Windows Group Policy software installation.

If you use Group Policy software installation or SMS, you cannot guarantee the order in which components are installed. This means that MUI Packs might be installed before Office, which is usually disallowed. However, by setting the CHECKINSTALLORDER property, MUI Packs can be installed on a user’s computer even if Office is not yet installed.

If you are deploying Office with the MUI Packs by using Group Policy software installation, you must include a separate transform for each MUI Pack, in which you set the CHECKINSTALLORDER Setup property to False.

If instead you deploy Office 2003 and MUI Packs with SMS, you can specify the CHECKINSTALLORDER Setup property in a MUI Pack transform. You can customize the property in the Custom Installation Wizard on the Modify Setup Properties page. Alternatively, you can set the property in the Setup.ini file in the [Options] section or specify the property on the Setup command line.

Setting the NOFEATURESTATEMIGRATION property

Office 2003 MUI Pack Setup (Muisetup.exe) automatically matches MUI Pack feature installation states to the corresponding features in the core English version of Office. If you specify different installation states for MUI Pack features in a transform, you must set the NOFEATURESTATEMIGRATION property in the transform to Do not match feature states during installation to override the default matching behavior.

You can customize the NOFEATURESTATEMIGRATION property in the Custom Installation Wizard on the Modify Setup Properties page. Alternatively, you can set the property in the Setup.ini file in the [Options] section or specify the property on the Setup command line.

Setting the SKIPLANGCHECK property

Office 2003 MUI Pack Setup does not install a language version of a MUI Pack on computers where Windows support for the language is not installed. Language groups that require explicit support for a language on the user’s computer include complex script languages, right-to-left languages, and East Asian languages. You can bypass the system language check by setting SKIPLANGCHECK to 1.

Setting SKIPLANGCHECK does not enable language versions of Office to function properly without the necessary operating system support. Bypassing the system language check merely allows you to install Office products and language support in any order.

You can include this option as a property on the Setup command line, or you can set the property in the Setup.ini file by the setting SKIPLANGCHECK=1 in the [Product] section. This option cannot be specified in a transform (MST file).

Customization methods for a MUI Pack deployment

There are several methods you can use to customize a MUI Pack deployment. You can include customized options for MUI Packs (such as language settings) in your Office transform, or you can customize a separate transform for MUI Packs. If you use a separate transform, you can apply that transform to multiple MUI Pack packages (MSI files).

When you customize settings for MUI Pack deployment by using the Office transform, you can specify the language settings in two ways—by specifying language settings in the Custom Installation Wizard directly when customizing Office, or by specifying an Office profile settings file (OPS file) created with the Office Profile Wizard.

If you need to customize only feature installation states or Setup properties, you can include these in a MUI Pack transform.

Use the Office transform to customize your MUI Packs

You can customize language options in the Custom Installation Wizard and save the customizations in a transform (MST file). This method can be used alone or in combination with specifying settings in an OPS file.

Note

You can use the Custom Installation Wizard to configure Setup properties in addition to configuring language settings and feature installation states. However, in a MUI Pack deployment, you only change MUI Pack Setup properties when you create a separate MUI Pack transform. For more information, see the section “Use a MUI Pack transform to customize your MUI Packs” later in this chapter.

To specify language options in the Custom Installation Wizard

In the Custom Installation Wizard, specify the MSI file for Office.

For example: \\server\share\Pro11.msi
On the Set Feature Installation States page, open Office Shared Features.

By opening International Support, you can choose installation states for fonts (for example, for Japanese Font).

By opening Proofing Tools, you can choose installation states for proofing tools available in the MUI Pack.
On the Change Office User Settings page, click the plus sign (+) next to Microsoft Office 2003 (user) to expand the tree.
Click the plus sign next to Language Settings and select the language options that you want for your deployment.

For example, to set the User Interface Language, click User Interface, then double-click Display menus and dialog boxes in Properties. In the Display menus and dialog boxes in Properties dialog, choose Apply Changes, and then choose a language from the drop-down menu.
To include an OPS file in the same transform, on the Customize Default Application Settings page, browse to the OPS file you have created.

Note that the settings you specify in the Change Office User Settings page take precedence over settings in an OPS file included in the same transform.
Make any other customizations required for your deployment, then click Finish to create the transform.

Capture settings in an OPS file

When you run Office to specify language settings and user preferences, you can capture these settings by using the Office Profile Wizard. Then, using the Custom Installation Wizard, you add the OPS file to your transform. Because the choice of editing languages affects the functionality of certain applications, you can create unique OPS files for different groups of users based on the languages they need.

In general, follow these steps to configure and capture language settings by using the Office Profile Wizard.

Install Office on the test computer, and then install any Multilingual User Interface Pack files.
Customize the Office environment and language settings.
Save the settings in an OPS file by using the Office Profile Wizard.

Note

The Office Profile Wizard stores and retrieves Office 2003 customizations. By using the Profile Wizard, you can create and deploy a standard user profile when you deploy Office 2003 so that all of your users start off with the same settings. For more information about the Profile Wizard and OPS files, see “Updating Feature Installation States and Application Settings” in Chapter 18, “Updating Users’ Office 2003 Configurations.”

Install Office and the MUI Pack on a test computer

You install Microsoft Office on a test computer by using Office Setup (Setup.exe) on the Office CD. Then install the MUI Pack files that you want to customize by using the MUI Pack Setup program (Muisetup.exe). The MUI Pack Setup program starts the Multilingual User Interface Pack Setup Wizard, which will step you through installing MUI Pack files.

Configure Office and language settings on your computer

Once you have installed Office and the MUI Pack files, you start the Office applications you want to configure and customize toolbars, settings, templates, custom dictionaries, and any other options you choose. Then you run the Language Settings tool and specify any of the following language settings:

Installation Language (also called the default version of Office)
Enabled Languages (also called Editing Languages)
User Interface Language
Help Language

To update language settings by using the Language Settings tool

On the taskbar, click Start, then point to All Programs (for Windows XP) or Start Programs (for Windows 2000).
Point to Microsoft Office, point to Microsoft Office Tools, and then click Microsoft Office 2003 Language Settings.
On the User Interface and Help tab, choose a language in the Display Office 2003 in drop-down list.

Only languages for which you have installed a MUI Pack are displayed; therefore, the User Interface and Help tab is displayed in the Language Settings tools only when you have at least one MUI Pack installed on your computer.
Choose a language in the Display Help in drop-down list.

Only languages for which you have installed a MUI Pack are displayed.
On the Enabled Languages tab, select a language in the scroll list, then click Add to enable the language for editing.
Change the Installation Language by choosing a language in the Choose the language that defines default behavior in Microsoft Office applications drop-down list.

For instance, you might add a few languages to the list of enabled languages for your users. Typically, most users creating multilingual documents rarely work with more than three languages. Limiting the number of enabled languages results in a user interface that is less cluttered and allows Office applications to run efficiently for particular languages.

Capture settings in an OPS file

Once you have customized Office and the language settings, you save these settings by using the Office Profile Wizard. These settings will be used to customize users’ installations of Office and MUI Pack files. You then include the OPS file in the Custom Installation Wizard when you create a transform that is applied when Office 2003 is installed.

Office profiles and multiple languages

Office user profiles generated by the Profile Wizard are independent of the operating system—including operating systems in other languages. For example, a profile settings file created on Microsoft Windows 2000 (U.S. English version) can be restored to a computer with Windows XP (Japanese version).

However, Office user profiles are specific to a particular Office language version. For example, if you create an OPS file in the U.S. English version of Office 2003, it cannot be restored to a computer with the German version of Office 2003 installed. There is some overlap between language families. For example, you can restore a U.S. English Office profile to an English or Australian version of Office 2003.

This Office language limitation exists because the different Office versions include localized folder names for the folders that contain the Office user profile information. You can find out more information about Office language limitations in Intlimit.xls in “International Information” in Appendix A, “Toolbox.”

Use a MUI Pack transform to customize your MUI Packs

You create a MUI Pack transform when you want to customize the way that MUI Packs are installed—for instance, after Office is installed. Or you may need to customize individual MUI Packs so that they can be deployed with Office by using SMS or Group Policy software installation.

An advantage of deploying MUI Packs with Office is that you can customize language settings in your Office transform, which you cannot do with a MUI Pack transform. You might use the MUI Pack transform to do the following:

Customize feature states, such as choosing to install the Optical Character Recognition Modules for a MUI pack under Office Shared Features.
Customize Setup properties, such as specifying the NOFEATURESTATEMIGRATION property.
Specify an additional (replicated) server for downloading the MUI Pack.

Note

You customize default language settings in your Office deployment. If you have already deployed Office, you can modify language settings by using the Custom Maintenance Wizard. For more information, see “Updating Feature Installation States and Application Settings” in Chapter 18, “Updating Users’ Office 2003 Configurations.”

This procedure provides an example of settings you might customize in a MUI Pack transform.

To customize options in a transform for a MUI Pack

In the Custom Installation Wizard, on the Open MSI File page, enter (or browse to) the name of the MSI file for the MUI Pack you want to customize.
On the Set Feature Installation States page, open Office Shared Features.

By opening International Support, you can choose installation states for fonts (for example, for Japanese Font).

By opening Proofing Tools, you can choose installation states for proofing tools available in the MUI Pack.
On the Identify Additional Servers page, click Add, then type in or browse to a network share with a replicated copy of the administrative installation point.
On the Modify Setup Properties page, choose or add Setup properties that you want to include in the MUI Pack transform.

To modify an existing property, click the property, then click Modify. For example, click NOFEATURESTATEMIGRATION, then click Modify. Select Do not match feature states during installation from the drop-down menu, then click OK.
Click Finish to create the transform.

Install MUI Packs with an Office installation

If you know the language requirements of your organization at the time that you deploy Office, you might choose to install Office and the MUI Packs at the same time—a straightforward process that uses chaining.

Note

For detailed information about chaining packages with Office, see “Deploying Office and Other Products Together” in Chapter 5, “Installing Office 2003.”

Typically, when you chain MUI Packs to an Office installation, you follow these steps:

Install the MUI Packs on your administrative installation point.
Customize an Office transform to include language settings and other options for MUI Pack deployment, as described earlier in this chapter.

You can also create separate MUI Pack transforms, but this limits your customization options.
Edit the Office Setup.ini file to add a section for each MUI Pack that you want to chain with your Office installation.

To customize Setup.ini to chain MUI Pack packages to your Office installation

Open the Office Setup settings file (Setup.ini) in a text editor such as Notepad.
Create a section called [ChainedInstall_1], and in this section specify the name and path of the MUI Pack you want to chain. For example:

PATH=\\server1\share\office\1041\Mui.msi
Add the following entry to this section:

TASKTYPE=msi
Specify other options in this section, such as IgnoreReturnValue or Reboot.
Specify a unique display setting or transform to apply to the MUI Pack installation by setting the Display or MST property.

For example, you can ensure that the MUI Pack installation installs quietly:

DISPLAY=None
Specify additional options by using the Cmdline property. For example, set the NOFEATURESTATEMIGRATION property to True to cancel the custom action that matches installation states for MUI Pack feature states to corresponding Office feature installation states:

CMDLINE=NOFEATURESTATEMIGRATION=TRUE

The completed section in the Setup.ini file looks like this:

[ChainedInstall_1] PATH=\\server\share\Office\1041\Mui.msi TASKTYPE=msi DISPLAY=None CMDLINE=NOFEATURESTATEMIGRATION=True

Install MUI Packs after an Office installation

You can install MUI Pack packages after your Office installation, rather than chaining them to an Office installation. As with a combined Office and MUI Pack deployment, you can configure language settings in your Office transform when you deploy MUI Packs after Office. If you want to change the language settings after you install the MUI Packs, you use the Custom Maintenance Wizard.

Note

You can have users configure their own language settings. Users might choose to do this, for example, if they run the MUI Pack Wizard to install the languages they need from the MUI Pack administrative installation point.

Even if you choose to deploy MUI Packs after Office, you may want to create an Office administrative installation point that includes the MUI Pack files. This helps you simplify and control the deployment process. For example, you can standardize installation of language resources for all the users in your organization.

While you install Office first and later deploy MUI Packs, you can still use the process of chaining MUI Pack packages (if you want to install more than one MUI Pack). However, to install MUI Packs separately from Office, you customize the Setup.ini file in the first MUI Pack folder instead of customizing the Office Setup.ini file. You add a Chained Install section to the Setup.ini file for each additional MUI Pack you are installing. Then you install the MUI Packs by running Setup in the first MUI Pack folder.

The following procedure uses the example of deploying the French, Spanish, and Vietnamese MUI Packs by using a MUI Pack chained installation after your initial deployment of Office.

Note

For detailed information about chaining packages with Office, see “Deploying Office and Other Products Together” in Chapter 5, “Installing Office 2003.”

To use a chained installation to install multiple MUI Packs after an Office deployment

Using a text editor such as Notepad, open the Setup.ini file in the first MUI Pack folder. For example, open the following Setup.ini file in the French MUI Pack folder:

\\server1\share\office\1036\Setup.ini
Create a section called [ChainedInstall_1], and in this section specify the name and path of the first MUI Pack you want to chain with the French MUI Pack. For example, to add the Spanish MUI Pack:

PATH=\\server1\share\office\3082\Mui.msi
Add the following entry to this section:

TASKTYPE=msi
Optionally, specify other options in this section, such as a Display property.
Create a section called [ChainedInstall_2], and in this section specify the name and path of the next MUI Pack you want to chain. For example, to add the Vietnamese MUI Pack:

PATH=\\server1\share\office\1066\Mui.msi
Add the following entry to this section:

TASKTYPE=msi
Optionally, specify other options in this section, such as a Display property.

Users can now install this group of MUI Packs by running the Setup command line in the French MUI Pack folder. For example:

\\server1\share\office\1036\setup.exe /qb-

Resources and related information

Some MUI Packs contain only proofing tools. For more information about installing proofing tools from those MUI Packs, see “Installing Proofing Tools” in the next section.

In addition to specifying language features and providing support for international users, you can customize many other aspects of your Office installation by using the Custom Installation Wizard. You can also use the Office Profile Wizard to save language-related settings to a file you distribute as part of a custom installation of Office. For more information about customizing deployments by using these wizards, see “Customizing Office Features and Shortcuts” in Chapter 4, “Customizing Office 2003.”

After Microsoft Office has been deployed, you might want to change the language settings you originally deployed with Office. In this case, you can modify language settings for your Office installation by using the Custom Maintenance Wizard. The Custom Maintenance Wizard is installed by default when you run the Office Resource Kit Setup program. For more information, see “Updating Feature Installation States and Application Settings” in Chapter 18, “Updating Users’ Office 2003 Configurations.”