User interface languages in TM1

Introduction

As you know or might not know, I live in Belgium. It is that nice, tiny country in Western Europe that is known for beer, chocolate, mussels, waffles, Brussels sprouts, and so on. And also for non-food things, by the way. In general, the upper part of the country speaks Dutch while the Southern part speaks French. In the East, a geographically small area consists of people speaking German. Hence, by and large, Belgians speak their languages, including English. Also, being so small, a major part of the Belgian Gross Domestic Product consists of import and export: the companies often do trade with companies abroad, hence the need for the inhabitants to (at least) understand English. Many international companies have subsidiaries or headquarters in Brussels: a lot of nationalities gather.

Why am I telling this and what is the link to TM1? In TM1 we can set the language of the user interface. Below, I will present a chart containing the possible choices. 1 user might prefer French while the colleagues are using English, in 1 TM1 application. For this to work, set the Language parameter in the TM1p.ini file to the desired language (make sure clients like Perspectives and Architect are closed when setting the value). You can find the ini file in the folder %AppData%\Applix\TM1.

Other languages

Next to English, other languages are supported in the user interface. What follows is a chart containing parameter value, language name and 3 other useful terms:

  1. First, we have the localized name of what is 'Default' in English. Think about subsets and views
  2. Next, I present the localized name of what is 'All' in English. Again, think about a subset.
  3. Lastly, I show the localized name of 'Filter by level' in English. Oftentimes, I like to create level 0 subsets in dimensions through an MDX statement. In that case, I like to have them translated as well. This is of less importance compared to the localized names above.

If you choose a language that does not exist, English is the default.

Parameter value Language Default All Filter by level
ENG English Default All Filter by level
FRA French Par défaut Tout Filtrer par niveau
DEU German Standard Alle Nach Ebene filtern
JPN Japanese See below the chart
SCH Simplified Chinese See below the chart
BRA Brazilian Portuguese Padrão Tudo Filtrar por Nível
HRV Croatian Default Sve Filtriraj po razini
CSY Czech Výchozí Vše Filtrovat podle írovně
DAN Danish Standard Alle Filtrér efter niveau
NLD Dutch Standaard Alles Filteren op niveau
FIN Finnish Oletusarvo Kaikki Suodata tason mukaan
HUN Hungarian Alapértelmezés Mind Szúró szint szerint
ITA Italian Predefinito Tutto Filtra per livello
NOR Norwegian Standard Alle Filtrer etter nivå
POL Polish Domyślne Wszystkie Filtruj wg poziomu
ROM Romanian Implicit Toate Filtrare după nivel
RUS Russian По умолчанию Все Фильтр на основе уровня
SLV Slovanian Privzeto Vse Filtriraj po ravni
ESP Spanish Predeterminado Todo Filtrar por nivel
SVE Swedish Standard Alla Filtrera efter nivå
TRK Turkish Varsayılan Tümü Düzey Temelinde Süzgeç Uygula
KAZ Kazakh See below the chart
KOR Korean See below the chart
THA Thai See below the chart
TCH Traditional Chinese See below the chart

Other languages

There are a number of other languages with special characters that my computer does not seem to like very much :-) The characters are unlike those we normally use in our alphabet, or way too incomprehensible to me, and therefore I leave them out of the chart. I marked the 6 languages above. Please find out yourself what are the localized names.

The 'Why' of this page

Why do I write this down? There are a number of reasons. For example, if you have a Default view on a cube, languages other than English will not recognize it. Of course, the same holds true for Default subsets in dimensions.

The second reason has to do with Turbo Integrator processes. A process that uses the subset 'All' (set in the user interface of the Data source) on a given dimension, will work fine with English as the language. For a French user, for example, TI will translate the subset to 'Tout' (see above in the list) and it will work… fine. Using the function DATASOURCEDIMENSIONSUBSET = 'Tout'; in the Prolog tab, will work fine. But if we do the same exercise for a user with Italian language set, DATASOURCEDIMENSIONSUBSET = 'Tutto'; will refuse to work! However, for the Italian settings, it works if you use DATASOURCEDIMENSIONSUBSET = 'All'; or 'Alle' or 'Tout' (and possibly also the localized names for Japanese and Simplified Chinese - untested). In sum, without extensive testing, if you use the names for English or one of the other languages above the empty row in the chart, you are safe. Irrespective of the language of the user. Please let me know if you have remarks or when you spot errors.

Additional information

See this page by IBM.

The TM1s.cfg file

What about the Language parameter in the TM1s.cfg file? I played around with the possible languages, but I did not notice any differences. Can someone tell me the use of the Language parameter in the config file?




Homepage

Section contents

About Wim

Wim Gielis is a Business Intelligence consultant and Excel expert

Other links