You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hooks usually return dialog text alongside with character names which sometimes cause mistranslation. A mechanism such as a dictionary blacklist, using delimiters, semi-automatic name detection (keep a list of most encountered name-like substrings and make the user choose one) etc. would be useful. Probably more than one mechanism is needed, semi-automatic detection might be too expensive since it would require extra parsing and keeping everything in memory but it might be made togglable so the user only activates it when needed and disables it after adding string to the blacklist.
The text was updated successfully, but these errors were encountered:
Nah it's a lot simpler than that. Basically when you have a name in the text google translate will still send the translation back, but in a way that NH can't correctly parse it. To parse it correctly I basically just have to replicate this line of code in C++: const processGoogleTranslateData = data => JSON.parse(data)[0].filter(v => v[0]).map(v => v[0]).join(" ");
but that's such a pain that I've put it off for weeks xD. Anyway, known bug, it'll be fixed somewhat soon maybe.
Hooks usually return dialog text alongside with character names which sometimes cause mistranslation. A mechanism such as a dictionary blacklist, using delimiters, semi-automatic name detection (keep a list of most encountered name-like substrings and make the user choose one) etc. would be useful. Probably more than one mechanism is needed, semi-automatic detection might be too expensive since it would require extra parsing and keeping everything in memory but it might be made togglable so the user only activates it when needed and disables it after adding string to the blacklist.
The text was updated successfully, but these errors were encountered: