BUR #53943 has been approved by @evazion.
rename yachiyo_runami -> runami_yachiyo
rename iroha_sakayori -> sakayori_iroha
Character tags created with the wrong name order
Posted under Tags
BUR #53943 has been approved by @evazion.
rename yachiyo_runami -> runami_yachiyo
rename iroha_sakayori -> sakayori_iroha
Character tags created with the wrong name order
The bulk update request #53943 (forum #415321) has been approved by @evazion.
BUR #53948 has been approved by @evazion.
rename akira_mikado_(chou_kaguya-hime!) -> mikado_akira_(chou_kaguya-hime!)
rename koto_okkoteru_(chou_kaguya-hime!) -> okkoteru_koto_(chou_kaguya-hime!)
rename mami_isayama_(chou_kaguya-hime!) -> isayama_mami_(chou_kaguya-hime!)
rename noi_komazawa -> komazawa_noi
rename okako_chuken_(chou_kaguya-hime!) -> chuken_okako_(chou_kaguya-hime!)
rename rai_komazawa -> komazawa_rai
rename roka_ayatsumugi_(chou_kaguya-hime!) -> ayatsumugi_roka_(chou_kaguya-hime!)
These character names also need to be changed to Japanese name order.
john133803son said in forum #415369:
BUR #53948 has been approved by @evazion.
rename akira_mikado_(chou_kaguya-hime!) -> mikado_akira_(chou_kaguya-hime!)
rename koto_okkoteru_(chou_kaguya-hime!) -> okkoteru_koto_(chou_kaguya-hime!)
rename mami_isayama_(chou_kaguya-hime!) -> isayama_mami_(chou_kaguya-hime!)
rename noi_komazawa -> komazawa_noi
rename okako_chuken_(chou_kaguya-hime!) -> chuken_okako_(chou_kaguya-hime!)
rename rai_komazawa -> komazawa_rai
rename roka_ayatsumugi_(chou_kaguya-hime!) -> ayatsumugi_roka_(chou_kaguya-hime!)These character names also need to be changed to Japanese name order.
Did I do it correctly? The edited names are blue.
Do I need to add "char:" before the renamed character names?
john133803son said in forum #415381:
Did I do it correctly? The edited names are blue.
Do I need to add "char:" before the renamed character names?
Tag categories will automatically be updated in BURs like this, you did it correctly.
ANON_TOKYO said in forum #415383:
Tag categories will automatically be updated in BURs like this, you did it correctly.
Thank you for the confirmation!
The bulk update request #53948 (forum #415369) has been approved by @evazion.
https://www.cho-kaguyahime.com/#character
It's an official romanisation. The common Japanese convention doesn't denote long vowels.
Edit: oops, i focused on the wrong thing. "otako" is the correct one
Updated by Spatula22
Spatula22 said in forum #415420:
https://www.cho-kaguyahime.com/#character
It's an official romanisation. The common Japanese convention doesn't denote long vowels.
I understand if you want to remove the long vowels if it's the official localization choice, but then the series name should be cho_kaguya-hime! for consistency.
And it still don't address that her name is supposed to be Otako and not Okako. The Okako in the official website is just plain wrong if we consider the Japanese text.
siraco said in forum #415424:
I understand if you want to remove the long vowels if it's the official localization choice, but then the series name should be cho_kaguya-hime! for consistency.
Kiiind of. Generally we try to follow official romanizations unless they're particularly stupid (or just not commonly used). At least in my experience though, web addresses etc. can eb a bit less consistent. Looking further though, all socials use "Cho" too, so going for that is probably the best:
And it still don't address that her name is supposed to be Otako and not Okako. The Okako in the official website is just plain wrong if we consider the Japanese text.
Yeah the Japanese in combination with the giant "Otako" in the back, probably just a mistake.
BUR #53970 has been approved by @evazion.
create alias chou_kaguya-hime! -> cho_kaguya-hime!
create alias mikado_akira_(chou_kaguya-hime!) -> mikado_akira_(cho_kaguya-hime!)
create alias fushi_(chou_kaguya-hime!) -> fushi_(cho_kaguya-hime!)
create alias kaguya_(chou_kaguya-hime!) -> kaguya_(cho_kaguya-hime!)
As per forum #415427, official socials and website seem to prefer "Cho" over "Chou"
The bulk update request #53970 (forum #415429) has been approved by @evazion.
