-
-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
From the Sept 2023 team planning meetings M4 review of websites
While we would like to localize all the websites, it's too much content (keyman and help.keyman), so the immediate priority is the keyboard search page.
- Get the keyboard search strings into Crowdin (may need to be separate from the Keyman project due to syncing
- Have a way for user to select locale
Design documents:
- Localize Keyboard Search to design review presentation
Items to note from preliminary review comments. Some are TODO's
Framework
Using associative arrays to handle the localized strings. The strings will fallback: e.g. es, es-ES, ..., finally en
Not installing locales in the Docker image.
Localized strings will be loaded by
$strings = [domain][locale]
File hierarchy
_includes/locale/strings/
keyboards/
en.php
es.php
home
en.php
es.php
km.php
TODOs
- How to specify locale:
- UI - dropdown list near the "Support" tab on the upper right
-
It would be good to look at best practices around embedding locale in query strings vs path or domain etc. We need to consider our technology stack in making this decision.
- Set the
langattribute when using localized strings
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
In Progress