DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add or fix a phone UI translation with AIKON

Edit one text file per language and rebuild, so a native speaker can correct a draft UI language.

Who it is forA native speaker of Spanish, Portuguese, French, German, Russian or Indonesian, or of a new language, who wants to improve the phone menus.

The problemThe README marks six language files as first drafts, and the app's menus read awkwardly until a native speaker corrects them.

The outcomeA corrected or new language file is ready for a pull request, and the build confirms that it covers every required text.

What you need first

  • A Nokia S40 or S60 phone (tested on the Nokia 6300 and Nokia E63)
  • A Docker host with a public IPv4 address and TCP 443 open (a $4-6/month VPS is enough)
  • An API key from at least one provider: Claude, OpenAI, Gemini or Grok
  • Docker, OpenSSL or LibreSSL, and SSH access to the server
  • For building the phone app: JDK 11+ and make
  • For building the server: Go 1.26+

Steps

  1. Open the language file for your language in app/lang/, for example app/lang/de.txt, where each line is an English text, a TAB and its translation.
  2. Correct the translations, keeping one pair per line and the TAB between them.
  3. Run make -C app langs to copy the files to server/lang and show which texts each file covers.
  4. Run make -C app to confirm the build accepts the file, since the build refuses any file that misses a text. (inferred, check the README)
  5. Open a pull request that edits the file, which the README says is enough.

Prompt for your agent

In the AIKON repo, edit app/lang/<code>.txt to correct the translations I provide, then run `make -C app langs`. Expected output is the coverage report for that language and no build errors. Verify that every English line still has exactly one TAB-separated translation.

Caveat. Right-to-left languages such as Arabic and Hebrew need layout work first, and scripts the phone fonts lack are out of reach on this hardware.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page