Skip to content

Conversation

@ac-mmi
Copy link
Contributor

@ac-mmi ac-mmi commented Oct 16, 2025

This PR updates the Japanese .po files for Music Blocks with the following improvements:

  • Refined translation prompts to better balance Kanji (for advanced readers) and Kana (for child-friendly UI).
  • Marked AI-generated strings with Trans-Comment: machine translation for transparency.
  • Repository workflow improvements:
    • Dedicated branch for easier review
    • Minimal diffs including only affected files

These changes address mentor feedback and improve the overall quality and readability of Japanese translations.

@github-actions
Copy link

🎉 All Checks Passed!

Status: ✅ Ready to merge

✅ Completed Workflows

Workflow Status Details
🔨 Continuous Integration ✅ Passed Build completed successfully
📝 Code Linting ✅ Passed All formatting and style checks passed

🚀 This PR is ready for review and can be safely merged to main branch!

Great work! Your code meets all quality standards. 👏

Copy link
Contributor

@pikurasa pikurasa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "et --hard HEAD2git reset --hard HEAD2" file shouldn't be here as well as the "git" empty file. Please remove those.

Also, please address the comments about bold text and the comment about "Kanji".


## Mentor Feedback on Japanese Translations

This week, I received valuable feedback from mentor **Devin Ulibarri** regarding the Japanese translations. He noted that many of the generated strings were **phonetic translations** rather than proper contextual ones.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the bold text here. It smells strongly of a machine-generated artifact.

This week, I received valuable feedback from mentor **Devin Ulibarri** regarding the Japanese translations. He noted that many of the generated strings were **phonetic translations** rather than proper contextual ones.

Devin explained that the Japanese language employs three writing systems:
- **Hiragana** and **Katakana** (phonetic alphabets)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm /ok/ with the bold text here, if you believe it is necessary.

- **Hiragana** and **Katakana** (phonetic alphabets)
- **Kanji** (logographic characters derived from Chinese)

He clarified that in Japanese educational contexts, **kana** (Hiragana/Katakana) is used for younger readers, while **Kanji** is used for more advanced readers. For Music Blocks, we aim to use Kanji where appropriate—so that the translations are natural to fluent readers—while keeping kana for child-friendly UI strings.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the bold text here. It smells strongly of a machine-generated artifact.


## Reflection

This week was about **listening, refining, and improving**. Understanding how Japanese writing systems interact with user experience helped me bridge linguistic nuances in AI translation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the bold text here. It smells strongly of a machine-generated artifact.


## Translation Prompt Refinement

Based on this feedback, I revisited and **refined the translation prompt** used in my Selenium automation script.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the bold text here. It smells strongly of a machine-generated artifact.

## Translation Prompt Refinement

Based on this feedback, I revisited and **refined the translation prompt** used in my Selenium automation script.
- The updated prompt now encourages GPT to **prefer Kanji** for formal or educational terms while maintaining **Kana** for simpler UI elements.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the bold text here. It smells strongly of a machine-generated artifact.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, this sentence is either a misrepresentation of your methodology, or it shows evidence of a misguided methodology.

We have two language settings for Japanese: one is "Kanji", which is intended for more advanced readers; and one is "Kana", which is intended for less advanced readers.

Our Kanji setting should always include some kana -- both Hiragana and Katakana. This is because intermediate and even the most advanced written Japanese includes kana. Kana, for example, will always be used for articles (such as noun marker は and object marker を).

So, there is no particular preference for "formal or educational terms" as you put it here. Rather, it has more to do with whether or not Japanese has a Kanji term for that word. In fact, because Katakana is mainly used for foreign words, a lot of specialized terms would be written in Katakana, because the Japanese language has adopted them from those languages.

Also, I think readers would be interested to know what the updated prompt is. I recommend that you either link to it in the code, or paste it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants