The system is saying I'm typing in Japanese when I'm using Romaji. I'm only writing out Japanese names and this is happening. It should only be doing this when writing is in Hiragana (あ), Katakana(ア), or Kanji(人). This makes it very frustrating to create (voice)actor profiles or other uses of Japanese names throughout the system.
¿No encuentras una película o serie? Inicia sesión para crearla:
¿Quieres puntuar o añadir este elemento a una lista?
¿No eres miembro?
Contestado por Marr 🇳🇱
el 10 de junio de 2018 a las 09:48
Yes, then you have to write just a little bit more text. Until Google Translate deems it English. Otherwise, just leave it blank, maybe someone else can give it a try sometime :)
Contestado por irkillroy
el 10 de junio de 2018 a las 16:20
It's someone's name though like writing 'Yamada'. You're saying that is the reason why people have crazy spelling of people's names? How can the system be fixed? Why not treat Romaji as NOT Japanese?
Contestado por Marr 🇳🇱
el 10 de junio de 2018 a las 16:22
It's because of Google Translate. They deem it Japanese.
I don't know what you mean about the crazy spelling part. The name isn't checked for translations. It's also not translatable. Only the overviews/descriptions yaknow.
Contestado por irkillroy
el 10 de junio de 2018 a las 16:24
I just don't see why it can't be turned off unless it sees JIS input rather than having Google Translate as a identifier.
Contestado por Marr 🇳🇱
el 10 de junio de 2018 a las 16:25
I'm sorry, but unless you know a better way of language checking and @travis wants to review it and code it and god knows what else, you just gotta deal with it. Mind you: descriptions on people pages aren't required.
This system has been in place forever though. Nine times out of ten, it works just fine, for the cases were it doesn't, just rewrite the stuff.... Or don't add it at all if you feel like that's too much an effort. See another response by Travis here and here and here. With a suggestion to take it up with Google itself too :)
Contestado por irkillroy
el 11 de junio de 2018 a las 06:16
"That's the way it's always been" is a great phrase. It's how greatness is achieved.
あ and A are different. The Japanese character is written using 2-bytes while the Roman character uses 1-byte. So, is there a validation process that could be ran for Japanese and just outright skip the validation using google translate for Japanese? I'd think the 2-byte characters used for にほんご would be all that is required for the verification of a digital asian written language.
But hey, whatever.
Contestado por Travis Bell
el 11 de junio de 2018 a las 15:54
Heh, I'm actually surprised Google Translate is smart enough to detect that as Japanese to begin with.
Can you give me some example phrases that are being detected incorrectly? I can probably add some extra rules to message these out a bit. I've done similar things for Spanish and Norwegian.
Contestado por Banana
el 11 de junio de 2018 a las 22:11
@travisbell I think it's often an issue with very short Wiki-like sentences in biographies e.g. XXX is a Japanese writer and director.
Contestado por irkillroy
el 12 de junio de 2018 a las 07:46
Yes, when you are putting in the biographies they are tripping it, however, the names such a Yamada, Nakamura, etc. that are last names with english translations of Mountain and Town center are likely culprits. When I get a phrase I'll be sure to check back in with this thread. Thanks for the response.
Contestado por Marr 🇳🇱
el 15 de junio de 2018 a las 09:53
I had the same issue with
I just added another small sentence and it worked.
// EDIT: Same with (the even more basic) profile overview:
While this other one works:
Contestado por Travis Bell
el 15 de junio de 2018 a las 09:59
Ok, great. I'll play around with that text.