Skip to content

fix(i18n): fix machine converted kana from Hiragana to Katakana#7784

Merged
walterbender merged 1 commit into
sugarlabs:masterfrom
pikurasa:kana-prerelease-workshop-2026
Jul 11, 2026
Merged

fix(i18n): fix machine converted kana from Hiragana to Katakana#7784
walterbender merged 1 commit into
sugarlabs:masterfrom
pikurasa:kana-prerelease-workshop-2026

Conversation

@pikurasa

Copy link
Copy Markdown
Collaborator
  • Ignore editorial fixes; Ignore Kanji
  • Change words that should be read as Katakana from Hiragana

* Ignore editorial fixes; Ignore Kanji
* Change words that should be read as Katakana from Hiragana
@codecov

codecov Bot commented Jul 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.00%. Comparing base (7ee23aa) to head (1ad5a26).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #7784   +/-   ##
=======================================
  Coverage   59.00%   59.00%           
=======================================
  Files         175      175           
  Lines       57920    57920           
=======================================
  Hits        34176    34176           
  Misses      23744    23744           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@pikurasa

Copy link
Copy Markdown
Collaborator Author

Here is my working draft of my notes as I worked through this:

2026-07-02JA-working.txt

There were a few different issues to resolve. This PR /mainly/ (but not perfectly) focuses on converting words that should be Katakana from Hiragana. We're assuming ~2nd grade reading level, so they will know Katakana.

What I tried not to focus on, but I jotted down as I was working was:

  • Flagging Kanji, because that shouldn't have been passed over at all. The original ja.po needs reviewed in those places. Example: "周波数" for "frequency"
  • Flagging English (Romaji) as some of those should be translated. Many times it was a block name that seems to have not been translated. Example: " Get-dict" or "get-red" or "Forever、Repeat、While、またはUntil。"
  • Flagging something that needs some editorial decision or documentation. Example: The word for "code" and "chord" are now the exact same (コード) in some places. For "chord" we may want to disambiguate by putting コード(和音)
  • Flagging something that just plain didn't make much sense. Example: "The Turtle sync block aligns the beat count between turtles." -- weird translation
  • Flagging something where I just couldn't help but fix the translation, but that will make it diverge from ja (kanji). I think "nth mouse name" was one of those... (need to review my notes)

Hope this helps...

@walterbender walterbender merged commit 7f47ad3 into sugarlabs:master Jul 11, 2026
11 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants