diff options
| author | Leitwolf11 | 2026-10-12 06:19:10 +0300 |
|---|---|---|
| committer | Leitwolf11 | 2026-10-12 06:19:10 +0300 |
| commit | b71e93b547e9f6425cc83b121f01e7d82b88079f (patch) | |
| tree | afe81b1bb48b7d5867c5d8ace2b56b9ca776485c /docs | |
| parent | 84541a742a7dcd5d067e7532b33e61eaf3e0174d (diff) | |
| download | progmaweb-fix/tala-names.tar.gz | |
Call the language Tala on the Progmasoft and ViGet pagesfix/tala-names
The language Visual X# is now Tala. The Progmasoft home page, the ViGet
pages, the dashboard and the two footers name it so in the four languages of
the site; the project file is BUILD.kts, and the source link leads to
Progmasoft/tala. The README, the operations and localization documents and
the issue templates follow.
The localization document said that a left-to-right mark follows the name of
the language in Hebrew text. That was for the `#` of the old name; the
sentence now speaks of names that end in a symbol.
The links to xsharp-lang.xyz stay: the language site is still served there.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/LOCALIZATION.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/LOCALIZATION.md b/docs/LOCALIZATION.md index 7ba409d..e943ec6 100644 --- a/docs/LOCALIZATION.md +++ b/docs/LOCALIZATION.md @@ -74,7 +74,7 @@ follows the language. on its own still reads left to right. - Code and form inputs stay left to right. - The onward arrow comes from `forwardArrow(locale)` and points left in Hebrew. -- A left-to-right mark (``) follows `Visual X#` in Hebrew strings. Without it the `#` would jump to the other +- A left-to-right mark (``) follows a name that ends in a symbol, such as `C#`, in Hebrew strings. Without it the `#` would jump to the other side of the name inside right-to-left text. The rules are at the end of `apps/web/app/globals.css`. @@ -97,7 +97,7 @@ The tests in `apps/web/tests/localization.test.mjs` enforce that `localeByLanguage`. 2. If the language is written right to left, extend `textDirection`. 3. Add a complete message tree. Copy the `en-US` tree and translate every string; keep product names and technical - identifiers such as `Visual.XSharp.kts` unchanged. + identifiers such as `BUILD.kts` unchanged. 4. Extend the tests: the list of published locales and a negotiation case for the new language. 5. Run `pnpm check`, `pnpm test`, `pnpm lint` and `pnpm build`, then read every page in the new language in a browser, in both themes and at a narrow width. |