Add complete Hindi,Chinese(Simplified) and Japanese (Kana & Kanji) translations

[ac-mmi]

This PR adds full localization support for:

• Hindi (hi) – complete translations for all strings.
• Chinese (zh-CN) – complete translations for all strings.
• Japanese (ja) – complete translations in both Kana and Kanji for better readability and coverage.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[pikurasa]

I'm doing a spot check right now.

I've run across something problematic that seems to be pervasive in these new translations (at least for kana)

Example: Pitch staircase

The test of this branch is on the left; the https://musicblocks.sugarlabs.org/ version is on the right (I cannot get https://sugarlabs.github.io/musicblocks/ to run, for some reason).

The left is a phonetic spelling out, in katakana, of what we already have. It would be kind of like me saying that "Watashi no namae wa Devin desu" is an English translation of the Japanese 私の名前はデヴィンです。It's not a translation; an English speaker wouldn't understand it. It's just a phonetic version of the Japanese, written in the Roman alphabet.

[pikurasa]

This is a regression:

In the dropdown list, it's suppose to be にほんご (in kana); but, instead, it says something that looks like maybe the word Japanese in Chinese.

[pikurasa]

This is another category of regression:

The translation we have in https://musicblocks.sugarlabs.org/ is better than this branch.

I don't recommend overwriting any of the human-made translations that we currently have.

[ac-mmi]

@pikurasa In my prompt, I specifically enforced that only Japanese kana should be used. Because of this, the output ended up being phonetic spellings in katakana rather than proper translations. Not every Japanese word can be represented accurately in kana, so the meaning wasn’t fully conveyed. I will change the prompt. I only realized this when you pointed out the flaw.

[ac-mmi]

This is a regression:

In the dropdown list, it's suppose to be にほんご (in kana); but, instead, it says something that looks like maybe the word Japanese in Chinese.

I don’t know how you were able to run this, because it takes the localStorage language preference as the filename and then calls the file. Right now it showed zhcn instead of zh_cn, which is the filename in my locales folder. I corrected it, so you can check now.

[github-actions]

❌ Some Jest tests failed. Please check the logs and fix the issues before merging.

Failed Tests:

languagebox.test.js

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[pikurasa]

It is still giving phonetic spellings.

This, for example, is the same for Set Drum:
ザ ピッチ ステアケース ツール トゥ イズ ユーズド トゥ ジェネレート ピッチズ フロム ア ギブン レイシオ

[pikurasa]

[ac-mmi]

@pikurasa but i haven't changed the JA file yet

[pikurasa]

@pikurasa In my prompt, I specifically enforced that only Japanese kana should be used. Because of this, the output ended up being phonetic spellings in katakana rather than proper translations. Not every Japanese word can be represented accurately in kana, so the meaning wasn’t fully conveyed. I will change the prompt. I only realized this when you pointed out the flaw.

It still displays the same as before, and your particular change seems unrelated to fixing this particular issue.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.