Migrator for Notes to Exchange 4.15.2 - Program Parameters Reference Guide

About language sections

The Global Defaults, Task Parameters, and (for the SSDM) notesdtapp.ini file contain parameter sections that specify the names Migrator for Notes to Exchange will assign to migrated Outlook mail folders in various languages. For example, the section for the Japanese language [JPN] looks like this:

By default, Migrator for Notes to Exchange's Data Migration Wizard and SSDM read the Windows locale to determine the appropriate language for new Outlook folders, and then refer to that language section of parameters when naming the new Outlook folders they create. However, a different language section can be specified (see below).

The Global Defaults and notesdtapp.ini contain sections for several common languages, and common variants of the world’s primary languages—for example, French as spoken in France vs. Canada vs. Belgium vs. Monaco, etc. But the default program parameters do not include sections for many less common language variants. The Global Defaults and notesdtapp.ini file do, however, contain sections for more generic forms of the world’s primary languages, so if the wizard can’t find a section for a language variant associated with a particular locale, the wizard will instead consult the more generic section. In Quebec, for example, if the wizard can't find a section for [FRC] (Canadian French), it will instead use the folder names specified in [FR] (generic French).

If the default program parameters do not contain a section for the language variant associated with your locale, and if you don't want to use the more generic language alternative, you can create a new section for the language variant you want, in the Global Defaults or notesdtapp.ini, or both.

You can create a local language section with a three-letter section name, such as ARY (Arabic Yemen). A table of Language three-letter acronyms (TLA) is shown below. You can also create a generic language section with a two-letter section name that supports any local language that is identified by a TLA that starts with the same two letters. For example, you can create a new section for Arabic, with an [AR] language section name. This section would support local languages such as ARY (Arabic Yemen) or ARQ (Arabic Qatar).

To enable MNE to use your new language section, you must specify the LanguageCode parameter. (See [General] LanguageCode=<SECTIONNAME> for the Admin version of this parameter.) The value specified in the LanguageCode Admin or SSDM parameter must identify a section defined in the Global Defaults or notesdtapp.ini, respectively. To use a language section with a TLA section name, the value of the LanguageCode parameter must be the same TLA. To use a generic language section, the value of the LanguageCode parameter can be the two-letter section name or a TLA that begins with the two-letter section name. So if you have defined a generic language section with the section name [AR], the LanguageCode values AR, ARY, ARQ, etc. would use this section.

Multiple target mail-folder names

The Global Defaults, Task Parameters, and (for the SSDM) notesdtapp.ini file contain parameter sections that specify the names Migrator for Notes to Exchange will assign to migrated Outlook mail folders in various languages. For example, the section for the Japanese language [JPN] looks like this:

By default, Migrator for Notes to Exchange's Data Migration Wizard and SSDM read the Windows locale to determine the appropriate language for new Outlook folders, and then refer to that language section of parameters when naming the new Outlook folders they create. However, a different language section can be specified (see below).

The Global Defaults and notesdtapp.ini contain sections for several common languages, and common variants of the world’s primary languages—for example, French as spoken in France vs. Canada vs. Belgium vs. Monaco, etc. But the default program parameters do not include sections for many less common language variants. The Global Defaults and notesdtapp.ini file do, however, contain sections for more generic forms of the world’s primary languages, so if the wizard can’t find a section for a language variant associated with a particular locale, the wizard will instead consult the more generic section. In Quebec, for example, if the wizard can't find a section for [FRC] (Canadian French), it will instead use the folder names specified in [FR] (generic French).

If the default program parameters do not contain a section for the language variant associated with your locale, and if you don't want to use the more generic language alternative, you can create a new section for the language variant you want, in the Global Defaults or notesdtapp.ini, or both.

You can create a local language section with a three-letter section name, such as ARY (Arabic Yemen). A table of Language three-letter acronyms (TLA) is shown below. You can also create a generic language section with a two-letter section name that supports any local language that is identified by a TLA that starts with the same two letters. For example, you can create a new section for Arabic, with an [AR] language section name. This section would support local languages such as ARY (Arabic Yemen) or ARQ (Arabic Qatar).

To enable MNE to use your new language section, you must specify the LanguageCode parameter. (See [General] LanguageCode=<SECTIONNAME> for the Admin version of this parameter.) The value specified in the LanguageCode Admin or SSDM parameter must identify a section defined in the Global Defaults or notesdtapp.ini, respectively. To use a language section with a TLA section name, the value of the LanguageCode parameter must be the same TLA. To use a generic language section, the value of the LanguageCode parameter can be the two-letter section name or a TLA that begins with the two-letter section name. So if you have defined a generic language section with the section name [AR], the LanguageCode values AR, ARY, ARQ, etc. would use this section.

Multiple target mail-folder names

Migrator for Notes to Exchange also supports multiple target mail-folder names to accommodate name differences introduced by Microsoft between different Exchange versions. Between Exchange 2010 and 2013, for example, Microsoft changed the English-language name of the junk mail folder from Junk E-mail to Junk Email. To define an additional folder name, you can append “_<version>” (e.g., _2010 or _2013) to the original folder name to create a new parameter key name (the portion of the parameter that precedes the “=” symbol). For example, since the English 2013 version has a different junk mail folder name, you could use these parameters to define an additional English junk mail folder for 2013:

The Wizard will then create a Junk Email target mail folder in an Exchange 2013 target server, or otherwise (for any other target) create a Junk E-mail target mail folder.

Note: The additional values supported in the current Migrator for Notes to Exchange release are:

These language sections to define Outlook folder names are not included with the other Migrator for Notes to Exchange INI parameters that follow the TLAs table below.

Custom folder mapping

Migrator for Notes to Exchange's Data Migration Wizard and SSDM support the migration of Notes custom folders and views to renamed target folders within one or more designated parent folders in Outlook. Custom naming of custom folders and views is accomplished by adding one or more custom-folder parameters to the language section of Migrator for Notes to Exchange Global Defaults, Task Parameters and/or notesdtapp.ini.

The key-name portion of a custom-folder parameter must begin with the Outlook target folder name (as specified by the [Notes] UserFolderPrefix value for custom folders or the [Notes] UserViewPrefix values for custom views), followed by a backslash, and then the name of the custom folder or view in the Notes source. The key name is followed by the "=" symbol and then the parameter value: the path you want Migrator for Notes to Exchange to assign to the target custom folder in Outlook. For example:

... tells Migrator for Notes to Exchange to create a new Outlook folder named OutlookFolderName within the Folders parent folder, and then migrate the contents of the Notes folder NotesFolderName to the new Outlook folder. Custom views are remapped in a similar fashion using the UserViewPrefix setting. However, unlike custom folders, the custom view folder is only created in Outlook if content is migrated for the view (see the MigrateViews setting for details). If no content is migrated for the view, no view will be created in Outlook.