@Pepper: Sorry for such a late reply, but I'm afraid I can't do anything about the .ff .wav files as they are not in the same format as the .iwd ones. They usually have paths pointing to the same folders as in the .iwds, but there are no such .wavs in the .iwds, so those are unique to the .ff files....

Sure, no problem.
Send to [email protected]

^Sorry, but I doubt PS3 has the same .ff format. You can still try it yourself if you own the PS3 version, though.
Make backups!

MW2 files are easily readable after inflation, already done it: the strings are in the same format as in BO so no problems. Yes, the 'second size' is weird, but goes up the same as the normal size. For example, if 1 of your strings is by a char longer than the one in the original .ff, the size will ...

It seems that depends on how many you changed the original strings... I got fatal errors sometimes, but not at other times when changing only a couple of strings, which seems to be the result of the offset hardcoding. I'm sorry, but there is no direct cure to that. I'll try something else, but the h...

There will be a MW2 tool next week; the .ff structure is similar, but not identical, I just need to make some modifications. @Herdell: Yes, I see this happens for all menu-related strings. There is a way around the fatal error, but it seems the string offsets (some of them) are hardcoded, at least f...

Ok, I've been fiddling around with the .ff's and there is a way to remove the fatal error! However, string positions (some of them, not all!) seem to be hardcoded so you'll get text blanks somewhere, probably. Here's a test version of the injector: http://gljivolog.com/data/releases/test.rar There c...

Right, it seems most strings are longer so maybe you should use that? Try editing the registry entry, renaming all .ff files to their Spanish lang codes etc and then try to inject some text; there shouldn't be any errors, but you are still limited to the length of the Spanish strings. I'm afraid the...

I'm afraid so, yes. The offsets are hardcoded and there's just no way to tell the game "read at 0x2c, not 0x2e". So the only thing possible is to have shorter strings or of equal length, which the new version allows (because we can easily pad out the bytes not used by 0xff separators). How...

Thanks, Jurko! That helped me in additional researching of the files. UPDATE RELEASED: v1.2 Fixes : now should work with the notorious en_code_post_gfx.ff file (or any lang prefix) NOTE : Injecting your own text into en_code_post_gfx.ff requires that your strings are the same or shorter length than ...

Well, there's one thing I'm sure about: en_code_post_gfx.ff is the only file (talking about SP files) which uses this kind of approach. It seems Treyarch has for some reason decided to place static offsets for menu strings, so all strings in that .ff file are invalid if your length differs from the ...

Happened to me now, too. Of all the files I tested, I didn't test this one, sorry. I don't know why it happens, let me look into it, there may be an update soon.
Sorry for the inconvenience
P.S. play in windowed mode so you can exit those fatal errors (to avoid freezing which happens in FS mode)

Thanks. No, you don't have to respect the original string size - your strings can be both shorter and longer than the originals and everything will be functional in-game.
All extracted strings, of course, will be identical to the ones in-game, then you can edit them as much as you like.

Good day, this tiny tool will help you in the process of translating Call of Duty: Black ops for PC into some other language or simply fooling around with the texts. I saw some people asking about that, so here is a solution. It can extract&inject all textual elements, such as objectives, dialog...

Sure, thanks for noting that, didn't even think there would be any samples in .ff's. I'll take a look at it when I have the time and update the tool.