Settings LanguageSettings/en: Unterschied zwischen den Versionen
Cg (Diskussion | Beiträge) |
Sv (Diskussion | Beiträge) |
||
| Zeile 4: | Zeile 4: | ||
By the time of writing of this document, the following languages are |
By the time of writing of this document, the following languages are |
||
directly supported: |
directly supported: |
||
* German |
* German |
||
* English (UK) |
* English (UK) |
||
* English (US) |
* English (US) |
||
Support for additional languages can be provided by exept, third parties |
Support for additional languages can be provided by exept, third parties |
||
| Zeile 25: | Zeile 25: | ||
shell environment variable ``<code>LANG</code>'' (Unix) or under Windows, |
shell environment variable ``<code>LANG</code>'' (Unix) or under Windows, |
||
from the user's standard Windows language settings (in the registry). |
from the user's standard Windows language settings (in the registry). |
||
<p> |
|||
Therefore, to change the language, Unix/Linux users, may add a line such as: |
Therefore, to change the language, Unix/Linux users, may add a line such as: |
||
setenv LANG de |
|||
or: |
or: |
||
LANG=de |
|||
export LANG</pre> |
export LANG</pre> |
||
or: |
or: |
||
export LANG=de |
|||
to their login profile (if not already present) and login again. |
to their login profile (if not already present) and login again. |
||
Windows users simply change their Windows language setting and |
Windows users simply change their Windows language setting and |
||
restart expecco (expecco reads the language setting from the registry). |
restart expecco (expecco reads the language setting from the registry). |
||
=== Model Language vs. GUI Language === |
=== Model Language vs. GUI Language === |
||
In multinational companies, it is often useful to define language-specific names for the |
In multinational companies, it is often useful to define language-specific names for the |
||
model elements (Activities, Steps, Pins, etc.). |
model elements (Activities, Steps, Pins, etc.). |
||
To support this, the item-tree's |
To support this, the item-tree's pop up menu provides a "<VAR>Translate</VAR>" function, |
||
which lets you add language specific names to an element. |
which lets you add language specific names to an element. |
||
By changing the model-language setting, those translated names are shown, if possible. |
By changing the model-language setting, those translated names are shown, if possible. |
||
<BR> |
|||
Notice that model-language strings are defined by the user and are stored with the project |
Notice that model-language strings are defined by the user and are stored with the project |
||
file. |
file. |
||
| Zeile 55: | Zeile 55: | ||
(which makes sense, if you have to generate reports in multiple languages or |
(which makes sense, if you have to generate reports in multiple languages or |
||
for a boss which speaks a different one...). |
for a boss which speaks a different one...). |
||
<P> |
|||
A number of common formats are provided in the combo list, |
A number of common formats are provided in the combo list, |
||
but you are free to enter any other format, by combining |
but you are free to enter any other format, by combining |
||
| Zeile 66: | Zeile 66: | ||
<LI>%(year) - the year, as a 4-digit number (2012) |
<LI>%(year) - the year, as a 4-digit number (2012) |
||
<LI>%(Year) - the year, as a 2-digit number (12) |
<LI>%(Year) - the year, as a 2-digit number (12) |
||
<LI>%(MonthName) - the month's name, first |
<LI>%(MonthName) - the month's name, first character in uppercase (November) |
||
<LI>%(monthname) - the month's name, all lowercase (november) |
<LI>%(monthname) - the month's name, all lowercase (november) |
||
<LI>%(MONTHNAME) - the month's name, all uppercase (NOVEMBER) |
<LI>%(MONTHNAME) - the month's name, all uppercase (NOVEMBER) |
||
<LI>%(ShortMonthName) - the month's short name, first |
<LI>%(ShortMonthName) - the month's short name, first character in uppercase (Nov) |
||
<LI>%(shortmonthname) - the month's short name, all lowercase (nov) |
<LI>%(shortmonthname) - the month's short name, all lowercase (nov) |
||
<LI>%(SHORTMONTHNAME) - the month's short name, all uppercase (NOV) |
<LI>%(SHORTMONTHNAME) - the month's short name, all uppercase (NOV) |
||
<LI>%(DayName) - the |
<LI>%(DayName) - the day's name, first character in uppercase (Monday) |
||
<LI>%(dayname) - the |
<LI>%(dayname) - the day's name, all lowercase (monday) |
||
<LI>%(DAYNAME) - the |
<LI>%(DAYNAME) - the day's name, all uppercase (MONDAY) |
||
<LI>%(ShortDayName) - the |
<LI>%(ShortDayName) - the day's short name, first character in uppercase (Mo) |
||
<LI>%(shortdayname) - the |
<LI>%(shortdayname) - the day's short name, all lowercase (mo) |
||
<LI>%(SHORTDAYNAME) - the |
<LI>%(SHORTDAYNAME) - the day's short name, all uppercase (MO) |
||
<LI>%(weekDay) - the |
<LI>%(weekDay) - the European day in week (1=Monday) |
||
<LI>%(weekDayUS) - the us day in week (1=Sunday) |
<LI>%(weekDayUS) - the us day in week (1=Sunday) |
||
<LI>%(nth) - |
<LI>%(nth) - English count abbreviation for day ('st', 'nd', 'rd',...) |
||
<LI>%(weekDayNth) - |
<LI>%(weekDayNth) - English count abbreviation for weekDay ('st', 'nd', 'rd',...) |
||
<LI>%(weekDayUSNth) - |
<LI>%(weekDayUSNth) - English count abbreviation for weekDayUS ('st', 'nd', 'rd',...) |
||
</UL> |
</UL> |
||
For example, the |
For example, the format string: |
||
"%(DayName), the %(day)%(nth) of %(MonthName)" |
|||
generates "Monday, the 2nd of November", |
generates "Monday, the 2nd of November", |
||
and |
and |
||
"%(DayName), den %(Day). %(MonthName)" |
|||
generates a |
generates a German date like "Montag, den 5. November". |
||
=== Time Format === |
=== Time Format === |
||
| Zeile 97: | Zeile 97: | ||
(useful, if you have to generate reports in multiple languages or |
(useful, if you have to generate reports in multiple languages or |
||
for a boss which speaks a different one...). |
for a boss which speaks a different one...). |
||
<P> |
|||
Two common formats are provided in the combo list, |
Two common formats are provided in the combo list, |
||
but you are free to enter any other format, by combining |
but you are free to enter any other format, by combining |
||
one or multiple of the following placeholders: |
one or multiple of the following placeholders: |
||
<UL> |
<UL> |
||
<LI>%(h) - hour, |
<LI>%(h) - hour, European format (00..23) |
||
<LI>%(u) - hour, |
<LI>%(u) - hour, US format (00..12) |
||
<LI>%(m) - minute with leading zero (00..59) |
<LI>%(m) - minute with leading zero (00..59) |
||
<LI>%(s) - second with leading zero (00..59) |
<LI>%(s) - second with leading zero (00..59) |
||
| Zeile 117: | Zeile 117: | ||
</UL> |
</UL> |
||
[[Category:Settings]] |
|||
Back to [[SettingsDialog/en | Settings Dialog]]. |
|||
Version vom 7. April 2014, 17:53 Uhr
Inhaltsverzeichnis
Language Settings[Bearbeiten]
Supported GUI Languages[Bearbeiten]
By the time of writing of this document, the following languages are directly supported:
- German
- English (UK)
- English (US)
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.
Changing the GUI Language during your Session[Bearbeiten]
Changing the language during a session only affects new views; existing views (either iconified or open) keep their resources as valid when created. The reason is that these language translations are cached internally within the view instances. However, the settings dialog application, will close and reopen itself and all expecco browser windows when the language changes.
Setting a Default Language[Bearbeiten]
When started, expecco sets the language from the
shell environment variable ``LANG (Unix) or under Windows,
from the user's standard Windows language settings (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 simply change their Windows language setting and restart expecco (expecco reads the language setting from the registry).
Model Language vs. GUI 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.
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 (November)
- %(monthname) - the month's name, all lowercase (november)
- %(MONTHNAME) - the month's name, all uppercase (NOVEMBER)
- %(ShortMonthName) - the month's short name, first character in uppercase (Nov)
- %(shortmonthname) - the month's short name, all lowercase (nov)
- %(SHORTMONTHNAME) - the month's short name, all uppercase (NOV)
- %(DayName) - the day's name, first character in uppercase (Monday)
- %(dayname) - the day's name, all lowercase (monday)
- %(DAYNAME) - the day's name, all uppercase (MONDAY)
- %(ShortDayName) - the day's short name, first character in uppercase (Mo)
- %(shortdayname) - the day's short name, all lowercase (mo)
- %(SHORTDAYNAME) - the day's short name, all uppercase (MO)
- %(weekDay) - the European day in week (1=Monday)
- %(weekDayUS) - the us day in week (1=Sunday)
- %(nth) - English count abbreviation for day ('st', 'nd', 'rd',...)
- %(weekDayNth) - English count abbreviation for weekDay ('st', 'nd', 'rd',...)
- %(weekDayUSNth) - English count abbreviation for weekDayUS ('st', 'nd', 'rd',...)
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-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...).
Two 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:
- %(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
