-
Notifications
You must be signed in to change notification settings - Fork 120
DMP '25 Week 14 Blog: Refine Japanese Translations: Improved Kanji–Kana Balance & Machine Translation Markers #494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🎉 All Checks Passed!
✅ Completed Workflows
🚀 This PR is ready for review and can be safely merged to Great work! Your code meets all quality standards. 👏 |
pikurasa
left a comment
There was a problem hiding this 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. |
There was a problem hiding this comment.
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) |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
This PR updates the Japanese
.pofiles for Music Blocks with the following improvements:These changes address mentor feedback and improve the overall quality and readability of Japanese translations.