Custom LCF header parsing fails for strings with values >= 0x80

[fdelapena]

The following game uses a character upper than 7-bit ASCII for a similar approach to "RM Protection Utility" (overwriting "LcfMapTree", "LcfDataBase" and "LcfMapUnit", but likely tailored to display the game name there.
This tool only uses 7-bit ASCII, so all games using this kind of "protection" are not affected.

elvespell.zip

liblcf uses ReadString to compare the value, and 0x80 and upper are affected by the ReadString BER parsing, so this game fails when doing the comparison. A possible solution would be a string comparison without ReadString.