FNAME in data files: a bug or a feature? -)

Support for running, installing or compiling OpenMW

Before you submit a bug report for the first time, please read: Bug reporting guidelines
Post Reply
ftaru
Posts: 8
Joined: 03 Dec 2022, 07:15

FNAME in data files: a bug or a feature? -)

Post by ftaru »

openMW 0.48

FNAME field in omwaddon is encoded in win-1251 for russian morrowind installation
in omwsave it is encoded in utf8
User avatar
akortunov
Posts: 898
Joined: 13 Mar 2017, 13:49
Location: Samara, Russian Federation

Re: FNAME in data files: a bug or a feature? -)

Post by akortunov »

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).
Chris
Posts: 1625
Joined: 04 Sep 2011, 08:33

Re: FNAME in data files: a bug or a feature? -)

Post by Chris »

akortunov wrote: 11 Dec 2022, 15:46 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).
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.
User avatar
AnyOldName3
Posts: 2660
Joined: 26 Nov 2015, 03:25

Re: FNAME in data files: a bug or a feature? -)

Post by AnyOldName3 »

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.
Post Reply