Settings LanguageSettings/en

Aus expecco Wiki (Version 2.x)
Zur Navigation springen Zur Suche springen

German Version

Language Settings[Bearbeiten]

This dialog is used to set the language both for the user interface (the "UI Language") and the so called "Model Language", which controls the language in which pin, step and block names are represented.

Supported UI Languages[Bearbeiten]

By the time of writing of this document, the following languages are (supposed to be) completely supported:

  • German
  • English (UK)
  • English (US)

Although other languages (French, Italian, Dutch, Spanish, Portuguese) are supported, some elements of the UI may be shown in English due to missing translations.

Support for additional languages can be provided by eXept, third parties or yourself, by creating a corresponding language-translation file, which is to be placed into the "resources" directory of the expecco installation. These language files contain a list of English-to-language translation. Each line consisting of two string entries, where the first string is the English original, and the second is the target language translation. If any such string contains spaces, the string must be surrounded by single quotes.

Many texts have been translated automatically, and we are also sorry, if any translation is wrong, funny or even offending. We'd be very thankful for notices and corrections.

Changing the UI Language during your Session[Bearbeiten]

Changing the language during a session only affects new views; existing views (either iconified or open) may keep their resources as valid when created. The reason is that these language translations are cached internally within some view instances. However, the settings dialog application, will close and reopen all expecco browser windows when the language changes. If any window insist on showing the old language, you should close and reopen it. The settings dialog itself remains in the old language until closed and reopened. This makes returning to the previous setting easier, in case the chosen language cannot be represented due to missing characters in the font.

We are sorry for any untranslated language strings still being present in the user interface: the initial development is in English, and translations to other languages are done later (and occasionally even forgotten), and it takes some time until new features are completely translated.

Setting a Default Language[Bearbeiten]

When started, expecco sets the language from the operating system's language setting. On Unix/Linux, this is the shell environment variable named "LANG, under Windows, this is the user's Windows language settings (stored in the registry).

Therefore, to change the language, Unix/Linux users, may add a line such as:

   setenv LANG de

or:

   LANG=de
   export LANG

or:

   export LANG=de

to their login profile (if not already present) and login again.

Windows users may change their Windows language setting and restart expecco (expecco reads the language setting from the registry).

Alternatively, you can tell expecco to ignore the OS language setting and use which ever is defined and stored in the settings file. For that, uncheck the "Use OS Language on Startup" flag in the language settings dialog.

Model Language vs. UI Language[Bearbeiten]

In multinational companies, it is often useful to define language-specific names for the model elements (Activities, Steps, Pins, etc.). To support this, the item-tree's pop up menu provides a "Translate" function, which lets you add language specific names to an element. By changing the model-language setting, those translated names are shown, if possible.

Notice that model-language strings are defined by the user and are stored with the project file (the ".ets"), in contrast to UI language translations, which are stored in the resource files.

Date Format[Bearbeiten]

The format used to present calendar dates in the user interface. Notice that the format in a report is specified in the report template and may be different from the format used in the UI (which makes sense, if you have to generate reports in multiple languages or for a boss which speaks a different one...).

A number of common formats are provided in the combo list, but you are free to enter any other format, by combining one or multiple of the following placeholders:

  • %(day) - the day of month, with a leading zero if required (01..31)
  • %(Day) - the day of month, without leading zero (1..31)
  • %(month) - the month number, with a leading zero if required (01..12)
  • %(Month) - the month number, without leading zero (1..12)
  • %(year) - the year, as a 4-digit number (2012)
  • %(Year) - the year, as a 2-digit number (12)
  • %(MonthName) - the month's name, first character in uppercase (eg. "November")
  • %(monthname) - the month's name, all lowercase (eg. "november")
  • %(MONTHNAME) - the month's name, all uppercase (eg. "NOVEMBER")
  • %(ShortMonthName) - the month's short name, first character in uppercase (eg. "Nov")
  • %(shortmonthname) - the month's short name, all lowercase (eg. "nov")
  • %(SHORTMONTHNAME) - the month's short name, all uppercase (eg. "NOV")
  • %(DayName) - the day's name, first character in uppercase (eg. "Monday")
  • %(dayname) - the day's name, all lowercase (eg. "monday")
  • %(DAYNAME) - the day's name, all uppercase (eg. "MONDAY")
  • %(ShortDayName) - the day's short name, first character in uppercase (eg. "Mo")
  • %(shortdayname) - the day's short name, all lowercase (eg. "mo")
  • %(SHORTDAYNAME) - the day's short name, all uppercase (eg. "MO")
  • %(weekDay) - the European day-in-week (1=Monday, 2=Tuesday,...)
  • %(weekDayUS) - the US day-in-week (1=Sunday, 2=Monday,...)
  • %(nth) - English abbrev. ordinal of day-in-month (i.e. "st", "nd", "rd",...)
  • %(weekDayNth) - English count abbreviation for weekDay ("st" for monday)
  • %(weekDayUSNth) - US English count abbreviation for weekDayUS ("st" for sunday)
  • %(iso8601) - long iso format with separators (i.e. "yyyy-mm-dd")
  • %(iso8601-compact) - short iso format without separators (i.e. "yyyymmdd")

For example, the format string:

   "%(DayName), the %(day)%(nth) of %(MonthName)"

generates "Monday, the 2nd of November", and

   "%(DayName), den %(Day). %(MonthName)"

generates a German date like "Montag, den 5. November".

Time Format[Bearbeiten]

The format used to present time and time-of-day values in the user interface.
Again notice, that the format in a report is specified in the report template and may be different from the format used in the UI (useful, if you have to generate reports in multiple languages or for a boss which speaks a different one...).

The most common formats are provided in the combo list:

  • european 24-hour format (eg. 14:02:20)
  • US 12-hour format (eg. 02:02:20 PM)
  • ISO standard (adds a 'T' as separator between date and time)
  • ISO standard compact format

but you are free to enter any other format, by combining one or multiple of the following placeholders:

  • %(h) - hour, European format (00..23)
  • %(u) - hour, US format (00..12)
  • %(m) - minute with leading zero (00..59)
  • %(s) - second with leading zero (00..59)
  • %(a) - am/pm lowercase (only useful with %u above)
  • %(A) - am/pm uppercase (only useful with %u above)
  • %(T) - second from midnight
  • %(t) - second within hour
  • %(i) - millisecond
  • %(milli1) - millisecond truncated to 1/10th of a second
  • %(milli2) - millisecond truncated to 1/100th of a second
  • %(z) - timezone lowercase
  • %(Z) - timezone uppercase
  • %(iso8601) - long iso format with separators (i.e. hh:mm:ss)
  • %(iso8601-compact) - short iso format without separators (i.e. hhmmss)



Copyright © 2014-2024 eXept Software AG