Closed backwardsEric closed 6 months ago
Thanks for spotting that! There were more similar mistakes in earlier versions, but they were in data files outside source code.
The compiler, clang, caught it and issued a warning about invalid source encoding. That doesn't help find similar stuff in the data files. It does look there is currently at least one of those (lib/files/rumors_new_e.txt:379; "Brand arrows using materials" ends with a full-width colon rather than a standard colon) which is from before the 2.0.18 changes.
Thanks; I also found several other instances of leftover spaces from JP version in some quest files and replaced them.
That is the only instance I see where a non-ASCII character slipped into the English translation of the 2.0.18 changes.