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

Multiple entries: Add "Kana reading" field for Japanese names #1490

Open
szc126 opened this issue Jan 17, 2021 · 7 comments
Open

Multiple entries: Add "Kana reading" field for Japanese names #1490

szc126 opened this issue Jan 17, 2021 · 7 comments
Labels
complexity: unknown Unknown days of work content: artists Artist entries content: songs Song entries feature request priority: low Issues/Tasks that are not so important

Comments

@szc126
Copy link
Collaborator

szc126 commented Jan 17, 2021

Most atwiki.jp and dic.nicovideo.jp entries have the pronunciation of the entry title written in hiragana. It's also sometimes given for usernames, UTAU names, etc.

For Japanese-language users of VocaDB, it can make searching easier (instead of having to input the precise kanji/katakana/hiragana used in a name: 唄 or 歌 or うた or ウタ, or inputting romaji), would be good for phonetic sorting, and would be a good addition to entries as well.

It is roughly related to the Romaji field, both being readings, but the Romaji field has potential searching barriers such as restoration of loanwords and word spacing, as opposed to a hiragana string.

@andreoda andreoda added content: artists Artist entries content: songs Song entries labels Jan 17, 2021
@VocaDB VocaDB locked and limited conversation to collaborators Feb 4, 2021
@VocaDB VocaDB unlocked this conversation Feb 24, 2021
@ycanardeau ycanardeau reopened this Feb 24, 2021
@github-actions github-actions bot closed this as completed Jun 1, 2021
@ycanardeau
Copy link
Contributor

ycanardeau commented Jun 1, 2021

Could this be done as part of #10 with the ja-Hira locale? AniDB and MusicBrainz will be useful as a reference.

@szc126
Copy link
Collaborator Author

szc126 commented Jun 1, 2021

I like that way of thinking of it.

@blueset
Copy link

blueset commented Sep 5, 2021

Here is a dump of automated ja-Hira name notations based on http://vocaloid.eu/vocadb/dump.zip in 2021 Sep 04. Only the titles able to be confirmed automatically are included (with some manual additions).

Hope this helps
vocadb_safe.csv

@ycanardeau
Copy link
Contributor

@blueset Thanks for your help! Note that the dump file isn't always up-to-date and it's manually done. Please let me know if you need the latest dump. By the way, I think it would be nice if you could share your automated script somewhere for future usage.

@blueset
Copy link

blueset commented Sep 5, 2021

Thanks for the suggestion. I’ve uploaded the source to https://github.com/blueset/vocaloid-yomigana, along with some data from Vocaloid Wiki (Fandom/Wikia) and 初音ミク wiki (atwiki). Hope this helps.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 7, 2022
@VocaDB VocaDB unlocked this conversation Aug 12, 2022
@ycanardeau ycanardeau transferred this issue from VocaDB/vocadb Aug 12, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 16, 2022
@VocaDB VocaDB unlocked this conversation Jun 4, 2023
@andreoda andreoda transferred this issue from VocaDB/community Jun 4, 2023
@andreoda andreoda reopened this Jun 4, 2023
@VocaDB VocaDB deleted a comment from github-actions bot Mar 6, 2024
@andreoda andreoda added the complexity: unknown Unknown days of work label Mar 6, 2024
@andreoda andreoda added the priority: low Issues/Tasks that are not so important label Mar 23, 2024
@szc126
Copy link
Collaborator Author

szc126 commented Oct 14, 2024

A related musing (alternative script forms): Do we "need" to restore lyrics that were only provided in romanized form? https://vocadb.net/S/289656 (romanized Russian, Japanese; Vocaloid Lyrics Wiki has produced a "restored" version); https://vocadb.net/S/68831 (romanized Japanese)? Perhaps we need lyrics tags like "ja-Latn + Original [from the producer]" instead of treating these as inferior ("Romanized" lyrics instead of "Original" lyrics). One would expect "Romanized" lyrics to be secondary, but in such cases the "Original" lyrics are secondary.

Also (related even more tenuously: script shenanigans) https://vocadb.net/S/594303 (provided in 2 Hokkien Romanizations and 1 Hokkien "Hangulization": hbl-Latn-TL, hbl-Latn-POJ, hbl-Hang? and the editing UI only allows one "Romanization")

@mn7216
Copy link
Contributor

mn7216 commented Nov 7, 2024

This would be an additional field in addition to the Non-English, Romanized, and English fields, correct?

@andreoda andreoda changed the title "Kana reading" field for Japanese names Add "Kana reading" field for Japanese names Nov 21, 2024
@andreoda andreoda changed the title Add "Kana reading" field for Japanese names Multiple entries: Add "Kana reading" field for Japanese names Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: unknown Unknown days of work content: artists Artist entries content: songs Song entries feature request priority: low Issues/Tasks that are not so important
Projects
Development

No branches or pull requests

6 participants