Ukrainian outside the window: the Windows installer, Linux menus and the README

Open
#647 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
markdown, rust, xml

Research direction

The work is already on branch localization/ukrainian (Tusko/kiri); start by reading that diff rather than writing code. Files in play: installer/windows/kiri.uk-UA.wxl, kiri.wxs (package language, codepage, downgrade message), kiri.desktop, the metainfo file, then README.uk.md and docs/features.uk.md. The open question to settle first is MSI packaging: one MSI per language versus embedded transforms, and the updater still shipping the English MSI. Done means Ukrainian appears in the installer, the Linux menu/polkit text, and linked Ukrainian docs.

Written by the indexing model from the issue text.

Description

What you're trying to do

Kiri's window is fully Ukrainian, but a Ukrainian user still meets English everywhere around it:

  • The Windows installer (MSI) is English only.
  • On Linux, the app menu entry, the software center listing and the polkit password prompt are English only.
  • The README and docs/features.md have no Ukrainian version.
What you'd like Kiri to do

I have this written on a branch (Tusko/kiri, localization/ukrainian) and would like to agree on the approach before opening pull requests, one per part:

  1. Windows installer. installer/windows/kiri.uk-UA.wxl (the 11 Kiri strings, LCID 1058, codepage 1251; WixUI supplies its own uk-UA strings). kiri.wxs takes the package language and the downgrade message from the .wxl, and drops its fixed Codepage="1252" so the .wxl sets it (1252 for English, as now). KIRI_MSI_CULTURE=uk-UA cargo xtask msi builds Kiri-<version>-<arch>-uk-UA.msi and leaves the update feed to the English MSI. Open questions: is a second MSI per language acceptable, or would you rather have one MSI with embedded language transforms? And the updater would still install the English MSI.
  2. Linux. Name/GenericName/Comment/Keywords[uk] in kiri.desktop, xml:lang="uk" summary and description in the metainfo, and the polkit description and message. No build change.
  3. Docs. README.uk.md and docs/features.uk.md, linked from the English pages.

Is this wanted, and if so, would you prefer it for Ukrainian alone or a pattern that other languages can follow (for example, translations of these files only where a translator offers one)?

Would you like to build it?

Yes, once we've agreed on the approach

Dominant language
Rust
Stars
7.5k
Forks
329
Avg merge
14h 18m
Merged PRs (30d)
204

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libracoder/kiri

All issues in libracoder/kiri

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.