openMW 0.48
FNAME field in omwaddon is encoded in win-1251 for russian morrowind installation
in omwsave it is encoded in utf8
FNAME in data files: a bug or a feature? -)
Re: FNAME in data files: a bug or a feature? -)
IIRC, it is a feature for a backward compatibility with original engine's ESM format (which is pretty pointless since we do not store scripts bytecode, so there is no compatibility anyway).
Re: FNAME in data files: a bug or a feature? -)
It's important for properly reading the original engine's esm/esp files, and currently omwaddon is just an esp with a different name (and lacking script bytecode if made with OpenMW-CS, which the original CS can load and create). Once omwgame/omwaddon become truly different and no longer usable by the original engine or CS, it would make sense to always use UTF-8 for strings like omwsave, instead of some ANSI encoding.
- AnyOldName3
- Posts: 2685
- Joined: 26 Nov 2015, 03:25
Re: FNAME in data files: a bug or a feature? -)
There's actually already a record type related to Lua scripting that we can load, but the CS can't write, so practically speaking, it can only be created with a hex editor.