Description
Bepinex - BepInEx bleeding edge version 725 and 729, Unity.IL2CPP-winx-64-6.0.0-be-### versions
Plugin - XUnityAutoTranslator-BepInEx-IL2CPP-5.4.5 and older versions as far back as 5.4.0
Issue Description -
We use this setup to perform Taiwan (Traditional Chinese) to English translations and are seeing recently that the translator seems to have started interpreting certain unicode character sets as their "regular" value while also adding an extra \n newline character. This seems to happen at least for characters in the "Halfwidth and Fullwidth forms" category, as well as "IDEOGRAPHIC FULL STOP". Examples are provided below.
We have also tested this by configuring different translation API endpoints (deepL + deepLLegit + googleV2), as well as running the dialogue strings manually thru those translators via chrome and are not able to reproduce, so it seems this might be something inside of the plugin itself?
Fullstop example -
開始探索。\n大家打起精神來。=Start exploring.\n\nEveryone cheer up.
You can see it changed the "ideographic full stop" period looking character (UTF-8 E3 80 82) to a regular period and added an extra linebreak
Fullwidth examples -
喲,辛苦了!\n今天感覺怎麼樣?=Thank you for your hard work!\n\nHow do you feel today?
Same idea here, it changed the "fullwidth form exclamation mark" (UTF-8 EF BC 81) to a regular exclamation mark and added an extra linebreak
嗯!?=Um!\n?
Interesting enough here, I would have expected it to add two \n but it for some reason only added one
Fullwidth we have also seen examples with Fullwidth left/right parenthesis as well as question marks
Appreciate any inputs you might have on this and whether there might be a config option that could be enabled for this!