Oblivion Mod talk:File Format Conventions

Strings

Kind of a lot of string types. Hmmm, and we haven't really looked at the unicode situation yet. We need to distinguish between zero terminated and non-zero-terminated bstrings (especially when writing), hence I've added the b-string type. However, I'd prefer that we do without the "string" type, as that is already covered by "char[size]", which has the advantage of being more explicit. --Wrye 19:46, 26 April 2006 (EDT)

No unicode apparently. I just did a quick test and it appears that Oblivion simply uses latin-1 encoding. --Wrye 01:15, 3 May 2006 (EDT)

Actually, it's Windows-1252 encoding. Bethesda occasionally uses characters in the range 0x80-0x9f, which aren't used for characters in latin-1. Double-checking what those characters are I'm seeing examples such as 0x85 for ..., 0x92 for ', and 0x94 for ", all of which match Windows-1252. FWIW, Fallout 3 and Fallout New Vegas have also continued to use Windows-1252. --Nephele^Talk 16:30, 18 October 2011 (UTC)

Long/Ulong

Reflection had a good point that int/uint were used as well as long/ulong to mean the same thing. However, solution is not to allow both, but to stick with the existing standard (long/ulong). I've searched for and corrected pages that I could find, but may have missed some. --Wrye 01:24, 4 October 2006 (EDT)