Skip to content
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

Sinitic and Japanese names should be handled differently #507

Open
dchan3 opened this issue May 18, 2018 · 0 comments
Open

Sinitic and Japanese names should be handled differently #507

dchan3 opened this issue May 18, 2018 · 0 comments

Comments

@dchan3
Copy link

dchan3 commented May 18, 2018

First of all, I'd like to say this is a cool project. It's just that I think the schema is suitable for names that are not Chinese, Japanese, Korean, or Vietnamese.

  1. Homophones tend to be an issue when dealing with such names.
  • Take the file mei.json for instance. According to the file, "mei" means "plum" in Chinese. This is only true if the word is said with the correct tone (Chinese is a tonal language) and within a context where it would be implied that "plums" are being discussed. Disregarding tone, another possible candidate for the definition would include "beautiful."
  • I will use the file sora.json as another example. At first glance of the file, it is clear that there are multiple candidates for the Japanese translation in the form of kanji. I would suggest using kana instead of kanji. One kanji could have multiple homophones that are names, by either its on or kun reading.
  1. Such names are usually not monosyllabic or just a single character.

While I admit that this is a lot to take in, I would strongly suggest that you research this. Thank you for your time.

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

No branches or pull requests

1 participant