GiellaLT provides an infrastructure for rule-based language technology aimed at minority and indigenous languages, and streamlines building anything from keyboards to speech technology.
The following apps & webapps need localisation:
Localisation of each of them is described below.
All pathnames in this section are relative to the root of the borealium.org repository.
data/languages.ts
contains a list of all languages covered by the site. It has four sections:
data/categories.ts
contains localised names and descriptions of categories.
It is seen on top of each category page. One gets to these pages when clicking on a category label.
data/resources/
contains the definition of all resources described on the site. Except for the file mod.ts
, all files contain strings that should be localised. The strings are the following:
name
- the name of the resourcedescription
- a short description of the resourcemoreInfo
- a longer description of the resource, if wantedlinks:text
- text to appear on the link button. Often this can just use the English text, but sometimes a translation will work betterMost of the content for the portal lives in src/
. All localisable text is placed in .flt
files, including in subdirs. At present, the following dirs contain .flt
files to be localised:
src/
├── _components
│ └── landing
├── _includes
├── about
├── doc
│ ├── divvun-manager
│ └── website
├── post
│ └── ...
└── privacy
See the README. But it boils down to the following:
Sources/Support/LocalisationResources/
strut-icu-generate swift Support/LocalisationResources/base.yaml \
Support/LocalisationResources/{your other langs}.yaml \
-o .
See the README. But it boils down to the following:
DivvunInstaller/Strings.[your_lang].resx
(add a new for new languages)Divvun.Installer/UI/Settings/SettingsWindow.xaml.cs
(Windows only)
TBW - support and documentation missing
Packages are what we distribute to users, such as speller and keyboard packages. They are listed in various places, always with a name, and often with a corresponding description, both of which can be localised.
Below is an example of how both strings show up in borealium.org:
and in the package listing in Divvun Manager:
Package names & descriptions are stored and localised in the following files:
keyboard-XXX/XXX.kbdgen/project.yaml
lang-XXX/manifest.toml.in
, but:
lang-XXX/configure.ac
, and automatically added to lang-XXX/manifest.toml
lang-XXX/manifest.toml.in
As a general rule, the minimum localisation should be:
This ensures that the tool is presented in an expected language for most users. Other localisations can of course be added ad lib.
The names and descriptions will be propagated in two steps:
Both steps are automatic and happen regularly, so on average, new package descriptions will be available pretty soon after they have been committed and pushed.
Category and channel labels are defined in .toml
files in main/strings/
. The following is the content of the en.toml
(English) file:
[tags]
"cat:keyboard-layouts" = "Keyboards"
"cat:spellers" = "Spellers"
"cat:speller-engines" = "Speller Engines"
[channels]
"default" = "Stable"
"nightly" = "Nightly"
"beta" = "Beta"
The category labels are used as category headings in Borealium.org:
and the channel labels show up in the settings in Divvun Manager:
There are a couple of other strings as well that could or should be translated.
This is defined in main/index.toml
:
[name]
en = "Divvun Languages"
ru = "Языки Divvun"
[description]
en = "The repository of all languages supported by Divvun."
(The description is presently not being used anywhere, AFAIK.)
This text is found several places:
The following files and directories contain localisable strings:
tools/index.toml
tools/strings/*.toml
It is unclear whether these strings are displayed, if at all.
TBW