Achieving the Correct Language Display

The following table lists many of the locations where you might want to display a given language for users. It tells you where to configure the system so that the language is displayed or available for selection. For some language displays, there are different steps in Developer than in MicroStrategy Web.

Translation or Language Display that You Want to Achieve	Where to Enable It
Number format (decimal, thousands separator, currency symbol, weight)	In Developer: Regional settings on the Developer user's machine. In Web: Click the MicroStrategy > Preferences. You can create a dynamic currency format that changes according to the locale's default currency symbol. The dynamic format applies to grid reports, graph reports, and documents displayed in MicroStrategy Web, MicroStrategy Mobile, and MicroStrategy Office and exported to PDF. For a graph report, the dynamic currency is applied to the data label.
Currency conversion	Use a Value prompt on a metric. See the Advanced Prompts section of the Advanced Reporting Help.
Date format and separators	In Developer: Regional settings on the Developer user's machine. In Web: Go to MicroStrategy > Preferences > Languages > Show Advanced Options. In Web, if the browser is set to a language unsupported in MicroStrategy and the user's preferences are set to Default, the date/time and number formatting display in English.
Autostyle fonts that support a given language	In Developer, right-click and Format the attribute or metric (column header, value, or subtotal) using the font you prefer (on the Font tab, specify the font.) From the Grid menu, select Save Autostyle As and either overwrite the existing autostyle or create a new one.
Fonts that support all languages	Few fonts support all languages. One that does is Arial Unicode MS, which is licensed from Microsoft.
PDFs, portable PDFs, bookmarks in PDFs, and language display in a Report Services document	Embed fonts when you are designing the document; this ensures that the fonts selected by the document designer are used to display and print the PDF, even on machines that do not have the fonts installed. Embedding fonts lets you: Use language fonts other than Simplified/Traditional Chinese, English, Japanese, Korean, and Western European in PDFs. Provide a true unicode environment, where one document can contain different languages. Create portable PDFs to email and to publish in Web. To embed fonts, in the Document Editor in Developer, go to Format > Document Properties> Export > Embed fonts in PDF. To view embedded fonts in Developer, the fonts must be installed on the Developer machine and the Intelligence Server machine. To view embedded fonts in Web, the fonts must be installed on the Intelligence Server machine. To display PDF bookmarks with the correct font, the language pack must be installed on the viewer's machine. This is true for any language other than English or Western European.
Character sets in Teradata databases	The Character Column Option and National Character Column Option VLDB properties let you support the character sets used in Teradata. For examples and details to enable these properties, see SQL Generation and Data Processing: VLDB Properties.
Double-byte language support	In Developer, from the Tools menu, select Developer Preferences.
User changing own language	In Web: Click the MicroStrategy > Preferences. In Developer: Go to Tools > Developer Preferences. The list of languages to choose from comes from the languages enabled for a project; see Enabling Metadata Languages for an Existing Project.
Default language preference for a particular user	In the User Editor, expand International, and then select Language. An administrator needs the Use User Editor and Configure Language Settings privileges, and ACL permissions to modify the user object.
Default language for all users in a project	Right-click a project, select Project Configuration > Language > User Preferences.
Different default language for a single user in different projects	Right-click a project, select Project Configuration > Language > User Preferences.
Translating the project's default language	By default, the project's default language cannot be translated in the Object Translation Editor. The first column in the editor corresponds to the project's default language. To translate terms in the default language, in the Object Translation Editor, click Options at the top of the Editor. Move the default language from the Selected View Languages box to the Selected Edit Languages box.
Function names	Function names are not translated. The MicroStrategy system expects function names to be in English.
An individual object	Use the Object Translation Editor. To access this, right-click the object and select Translate.
Caches in an internationalized environment	See Caching and Internationalization.
Intelligent Cubes	It is recommended that you use a SQL-based DI model when setting up internationalization, as described in Providing Data Internationalization. Because a single Intelligent Cube cannot connect to more than one data warehouse, using a connection-based DI model requires a separate Intelligent Cube to be created for each language, which can be resource-intensive. Details on this cost-benefit analysis, steps to enable a language when publishing an Intelligent Cube, and background information on Intelligent Cubes is in the MicroStrategy In-memory Analytics Help.
Subscriptions in an internationalized environment	Subscribed-to reports and documents behave like standard reports and documents, and are delivered in the language selected in My Preferences or User Preferences.
Repository Translation Wizard list of available languages	Enable languages the project supports for metadata objects (see Enabling Metadata Languages for an Existing Project).
Metadata object names and descriptions (such as report names, metric names, system folder names, embedded descriptors such as attribute aliases, prompt, instructions, and so on)	For a new project being created, select these in Architect. You can view the database table columns used for internationalization as you create the project. For an existing project, see Enabling Metadata Languages for an Existing Project.
Configuration objects in Developer	Displayed according to User-Project level language preference. Set this by right-clicking the project, selecting My Preferences> International, and setting the Metadata language for All Projects.
Attribute elements, for example, the Product attribute has an element called DVD player	First translate the element name in your data warehouse. Then enable the language; see Enabling Languages for Data Internationalization.
Project name and description	In the Project Configuration Editor, expand Project Definition, select General> Modify, > International > Translate.You can type both a project name and a description in the Object Description field.
When designing a project using Architect, see columns in the Warehouse Tables area that support data internationalization	In Architect, go to Options > Settings. On the Display Settings tab, select Display columns used for data internationalization.
Enable a new language for a project to support	See Enabling Metadata Languages for an Existing Project. User adding the language must have Browse permission for that language object's ACL.
Enable a custom language for a project to support	See Adding a New Language to the System. Then see Enabling Metadata Languages for an Existing Project. User adding the language must have Browse permission for that language object's ACL.
Searching the project	Searches are conducted in the user's preferred metadata language by default. A language-specific search can be conducted; open a project, then from the Tools menu select Search for Objects.
Project or object migration, or duplication	Object Manager, Project Merge, and the Project Duplication Wizard contain translation-specific conflict resolution options for migrating translated objects between projects.
Derived elements	In the Derived Element Editor, go to File > Properties > International.
MicroStrategy Office user interface and Excel format languages	This information applies to the legacy MicroStrategy Office add-in, the add‑in for Microsoft Office applications which is no longer actively developed. It was substituted with a new add‑in, MicroStrategy for Office, which supports Office 365 applications. The initial version does not yet have all the functionalities of the previous add‑in. If you are using MicroStrategy 2021 Update 2 or a later version, the legacy MicroStrategy Office add-in cannot be installed from Web.; For more information, see the MicroStrategy for Office page in the Readme and the MicroStrategy for Office Help. In MicroStrategy Office, go to Options > General > International.
MDX (Multidimensional Expressions) data sources	MicroStrategy passes a user's required language as a database connection parameter to the MDX cube provider; the cube provider supplies the correct translations.