Prototype and plan for a Japanese raylib cheatsheet

[LuisR385]

hi raylib community!

Following my previous discussion, I have started working on a Japanese
translation of the raylib cheatsheet.

I created a small local prototype based on the existing English and Chinese
cheatsheets. At the moment, only the descriptions of the cursor-related
functions in the rcore module have been translated.

The project is still in an experimental stage.

I plan to continue this project while consulting with friends who have
experience in IT and programming. I would also like to invite other Japanese
raylib users to review the translation in the future.

My current translation policy is:

• Keep function names unchanged
• Keep type names unchanged
• Keep parameter names unchanged
• Keep constants and enum values unchanged
• Keep function signatures unchanged
• Translate only section names and human-readable descriptions
• Prioritize technical accuracy and clarity for Japanese beginners

I am also using AI tools in a limited supporting role.

For example, I may use AI to:

• Help inspect the existing HTML structure
• Suggest initial translation candidates
• Help with English writing and Git-related questions
• Check for obvious omissions or inconsistent terminology

However, I do not plan to accept generated translations without review.
The final wording and technical meaning will be checked by humans, including
myself and people helping with the project.

Before translating the entire cheatsheet, I would appreciate feedback on:

1. Whether this translation policy is appropriate
2. Whether the current file structure is suitable
3. Whether there are any preferred conventions for translated cheatsheets
4. Whether this project could eventually be proposed for inclusion in raylib.com

Here is a screenshot of the current prototype:

---

Prototype: currently, only the cursor-related function descriptions are translated.

---

Prototype repository/branch:

here is my repo :
raylib.com/LuisR385

here is my branch :
feature/japanese-cheatsheet

Thank you!

[igrizzz]

I think your translation policy is a very good approach, especially keeping function names, types, parameters, constants, enums, and signatures unchanged.

For a cheatsheet aimed at beginners, I would also recommend keeping the terminology consistent across the whole document. It may be useful to create a small terminology/glossary file for recurring technical terms before translating the entire cheatsheet. That would make future reviews much easier and help avoid the same English term being translated in different ways.

Regarding the file structure, I would try to keep the Japanese version as close as possible to the existing English/Chinese cheatsheet structure. If the source structure changes later, this should make it easier to compare and synchronize the translations.

I also think using AI as a supporting tool is reasonable, as long as the final translation is reviewed by humans, as you described. For technical documentation, consistency and correctness are more important than translating everything literally.

For inclusion on raylib.com, I would suggest first getting the translation reasonably complete and reviewed by a few Japanese-speaking raylib users, then opening a PR or discussing the preferred integration approach with the maintainers. That would give the project a clear review history and make it easier to evaluate.

The idea is definitely useful. A Japanese cheatsheet could make raylib considerably more approachable for Japanese beginners.