Languages of the WKL Office SDK
The add-in, the command line wkl-office and the MSBuild tasks show their texts in English, German, Slovenian,
Croatian or Italian, the same languages as WKL Forms Object Library. This page names which language each part chooses and
which output stays English in every language.
Which language each part speaks
| Part | Language | Order of the choice |
|---|---|---|
| Access add-in (ribbon tab WKL SDK, work area, dialogs, messages) | The language of Access | WKL_SDK_LANGUAGE when set, else the setting behavior.language, else the user interface language of Office, else of Windows, else English |
| Command line started in the terminal of the add-in | The language of the add-in | Taken over from the add-in |
| Command line started on its own, MSBuild tasks | The language of Windows | WKL_SDK_LANGUAGE when set (the add-in sets it for its terminal), else the setting behavior.language, else WKL_UI_LANGUAGE of the process, else the user interface language of Windows, else English |
A language outside the five falls through to the next source: an Access with a French user interface shows the add-in in the Windows language, and in English when Windows is French too. Office changes its language at the next start, and the add-in follows it then.
To use the SDK in one language regardless of Office and Windows - for example in English in a German Office - choose
the language in the SDK settings (Language of the SDK on the Behavior page, behavior.language); it
applies from the next start of Access. For one computer only, or for a single call, set WKL_SDK_LANGUAGE to en,
de, sl, hr or it instead. For the add-in it must be set before Access starts, for the user
(Windows settings, environment variables) or in the shell that starts Access; for one call of the command line:
$env:WKL_SDK_LANGUAGE = 'en' wkl-office status MyApp.acproj
A value outside the five is ignored. The variable changes only the SDK: WKL Forms Object Library chooses its language on its own (the application's setting, then Office).
What stays English
| Output | Why |
|---|---|
Command names and options (build, --keep access) | They are the interface of scripts and build servers. |
Exit codes and problem codes (WKL010) | Scripts and build logs test them. |
JSON output (--json) | Its property names and values are a format, not text for people. |
File formats and file names (.acproj, relations.json, the source layout) | Sources move between developers with different languages. |
| Key tips of the ribbon (Alt, W, K, letter) | The documented key sequences then hold in every language. |
| Product names (WKL Office SDK, Access, git) | Names are not translated. |
Number and date formats follow the regional settings of Windows in every language, as Access does.
Related topics
- Command-line reference: commands, options, exit codes and JSON output.
- Keyboard shortcuts of the Access add-in: the key tips that stay the same in every language.