kroxiksut/win-store-region v0.1.2

WinStoreRegion 0.1.2

on GitHub

Eight new interface languages, two of which made the window read right to left.

• Arabic, Persian, Traditional Chinese, Korean, Japanese, Turkish, Brazilian
  Portuguese and European Spanish, taking the interface from three languages to
  eleven. All eight are machine-made drafts that no native reader has checked,
  and every file says so at the top. The Traditional Chinese is written in
  Taiwan wording rather than converted character by character from the
  Simplified draft.
• Arabic and Persian read right to left, and so does the window while one of
  them is chosen. A language file says which way its language reads, and the
  whole layout follows: the badge and the command row start on the right,
  checkboxes put their box on the right of their caption, table columns run
  right to left, and scrollbars move to the left edge. Hebrew now needs that
  one field and a file, and no code at all.
• The drafts were audited here rather than taken on trust: one file did not
  parse, two put grammar on a placeholder whose value nobody knows until run
  time, two had a button caption too long for its button, and one addressed the
  user formally in half its sentences and informally in the other half. All of
  that is fixed; none of it was in the translation agent's own report.
• The language chooser is sorted by language tag instead of by the order the
  languages were added, and a language file no longer carries a position for
  someone to assign. A language added later takes its place among the others
  rather than at the end, and no other file has to be renumbered for it.

Portable executables, no installer and no administrator rights. Pick the one
that matches the machine:

Only the x64 build has ever been run. All three are built by the same
workflow from this tag, so all three compile; the other two have never been
started on a real device. They are here because a machine that can run them is
the only way that changes — not because this release says they work. If you try
one, an issue saying what happened is the useful outcome either way.

The binaries are not signed. Windows shows "Windows protected your PC" on
first run and puts the button behind More info → Run anyway. A downloaded
file also carries a mark that keeps SmartScreen involved after extraction;
Unblock-File removes that mark. Only a code-signing certificate removes the
warning itself, and this release does not have one.

What can be checked is identity. SHA256SUMS.txt lists the digest of every file,
and the workflow run that produced them is public:

Get-FileHash .\WinStoreRegion-0.1.2-x64.exe -Algorithm SHA256

The full history is in CHANGELOG.md. What the program does, and
what it has and has not established, is in README.md, which links
to the same document in every other interface language.