The eight languages of the program, and how numbers, dates and names follow them
DSPX speaks eight languages: US English, in which it is written, and German, Spanish, French, Italian, Japanese, Brazilian Portuguese and Simplified Chinese. The menus, windows, panels, tooltips, messages and the processes' settings are translated; numbers, sizes and dates follow the language's own conventions; the files DSPX writes do not. This chapter says how to choose a language, what follows it, and what always stays in English.
The program is written in US English, and that is the source of every translation. The other languages are translations of all the texts a window, dialog, menu, toolbar, panel, tooltip or message shows, and of every process's and tool's name, description, settings, choices and progress phases.
| Language | Identifier |
|---|---|
| English (United States) | en_US |
| German (Germany) | de_DE |
| Spanish (Spain) | es_ES |
| French (France) | fr_FR |
| Italian (Italy) | it_IT |
| Japanese (Japan) | ja_JP |
| Portuguese (Brazil) | pt_BR |
| Chinese (China, Simplified) | zh_CN |
Each language is listed in the program by its own name, in its own language, followed by its country in the same way, and US English as "English (United States)". A text without a translation, which can happen after a new feature is added and before its translation is finished, shows in English.
The choice is kept. A language can also be given for one run on the command line, with the option --language and the
identifier, which is not kept; --languages prints the list as the Preferences show it
(Command Line). The page's Reset Page goes back to the system default.
With a translation, the standard buttons of dialogs (Open, Cancel, Yes, No) and the system's file dialogs are in the language too, when the translation of those texts comes with the program, and the program's locale becomes the language's.
By default a process keeps its English name in every language, so that a process is called the same in the menus, in the documentation, in a saved process and in the conversation of two people who use different languages; the tools, the settings and everything else are translated. Translate Process names, next to the language list, translates the process names too. It is dimmed when the language is US English, and like the language it applies from the next start, with the same question to restart now.
Numbers, sizes and percentages that we read follow the language's conventions: the decimal mark, the grouping of thousands, and the units' spelling. A German user reads 0,5 where a US user reads 0.5. This holds for the settings of the process panels, the tables, the plots' axes, the status line, the Report of a pre-processing session and the sizes of files.
With US English the conventions are those of the system's region, not always the US's: a German user of the English program reads 0,5, a Mexican one 0.5. A system with no region set gets the US conventions with no group separator.
Dates and times that are shown, such as an approval date, the start time in a report, or the observation date of a frame in the Frame Selection table and its tooltips, appear in the language's short format. Sorting by date is by the time itself, not by the text.
Names that a list or menu shows are sorted by the text we read, in the language's own order, ignoring the case and with numbers by their value: the Process menu and its categories, and the Scripts panel. keeps the order of a night's work, since that order says which step comes next.
What DSPX writes to a file does not depend on the language. Numbers in FITS keywords, in XISF properties, in saved processes
(.dsproc), in sessions, projects and themes are always written with a point, and dates in files and reports are in ISO form, so a file
saved in one language reads the same in any other. The names of the settings in a saved process are DSPX's own identifiers, which are
not translated.
Translations are often a third longer than the English. The windows are laid out from the length of the text, labels wrap, and columns of the tables are as wide as their translated headings need.
DSPX --version, --setup-scripts and the dsw_ tools write English.Languages written from right to left are not supported yet. Languages with large character sets, Japanese and Chinese, use the system's font, with the system's fallback for characters it lacks, in every widget, and lines break without spaces.
The eight languages above are built into the program. If yours is not among them, you can add it yourself, with no build and no tool of ours to install: DSPX gives you its English texts as a file, you translate the file with an AI or by hand, and DSPX reads it back. The language then appears in the Language list, with the translator's name, and works like the built-in ones.
dspx_en_US.ts, a Qt
translation file, about 10,000 texts), a guide for the translator (AI-GUIDE.md) and a glossary (glossary.json) that gives each
main term in the eight built-in languages, for consistency.<translation> write the text and remove
type="unfinished". Set the language code in the first line (language="nl_NL") and put your name in the file's first comment or in the
info.json of a language pack (the guide says how).info.json). DSPX checks it,
prepares it, and reports how many texts it took; the ones it dropped, and why, are in the details of the report.The language can also be added and removed on the command line: --import-translation <file>, --remove-translation <id> and
--export-translation-template <folder> (Command Line). A language removed this way or with the button
Remove, which asks first, leaves the built-in ones untouched; only a language you added can be removed, and the button is off while a built-in language is chosen.
Open folder opens the folder where DSPX keeps the languages you added. The language you add is listed with its coverage and the translator's name,
and it is used from the next start.
%1, %n and {name} are kept with their meaning, and the tags (<b>, <i>, links) are the source's:
none is added.& kept in a menu text, the plural forms your language has, no claim
the English does not make, and what DSPX stands for is never written out.An entry that breaks a rule that the program can check (a missing or extra code, a tag the English does not have, a character that is not text) is dropped, and the English shows for it; the rest of the file is taken.
Languages written from right to left have not been tried with community translations, and may not lay out correctly.
A text without a translation shows in English, text by text, so a translation that is not finished works. The Language list shows how much of the
current version a language covers. A new version of DSPX adds and changes texts, and the coverage of a language falls until it is brought up to date:
choose your language in the list and click Export what is left... (off while a built-in language is chosen), or give --export-translation-delta <id> <folder> on the command line.
DSPX writes just the texts that the imported file does not have or
has left unfinished, and says how many; translate them and import the file again.
Community translations are not reviewed by us: the Language group says so ("Community translations are not reviewed by DSPX."), and the translator is named in and in the list. The translation is yours, and you keep the authorship. If you send it to us so that it is included among the built-in languages, you give us the right to ship it with DSPX, with your name.
To have a translation included among the built-in languages, write to rba@deepskycolors.com with the file, your name as it should appear and the version of DSPX you translated. Nothing is sent by DSPX itself.