Well, first off, there's this:

The Newbie Package of REQUIRED Material

ROMHacking.net FAQ: You ask, we answer!
ROMHacking.net Getting Started Section: Newbies Go HERE!
ROMHacking.net Documents Section!
How to ask questions the smart way.
On the Essence of ROM Hacking

Now, what you'd need to do:

- Make a table for the GBA version of the game.
- Dump the script using romjuice or other appropriate text-dumping software.
- Make a table for the NES/FC version.
- Then you'd be stuck typing it in by hand, because I'm sure that reinserting it would probably lead to some issues. Mostly due to lack of space.

Good luck,

~DS

Because it's NOT just copy and pasting. It's as much work as a complete translation from scratch hacking wise. Waste of time.

Not to mention there was a story somewhere they couldn't even fit everything they wanted in Japanese, let alone English.
(it'd be possible but difficult to expand the ROM. As you'd need to know ASM to use the space.)

Thanks for the replies, guys.  I didn't quite mean a full-force Ctrl+C/Ctrl+P, but the idea that one could just plop things into their equivalent places.  With how you've responded, I still have much to learn about.  I prolly won't get around to looking into these processes until tomorrow (my sis's graduation is later today), but I'm quite fine with typing things in by hand.  ASM... would that also enable the modification of monospace to [term for not-monospace]?  I'm not too exposed, but I'm of the mind that these games were defaulted to monospace, which cut down on how much hired translators could push in.  Oh, I don't speak Japanese, so I was thinking I might end up using an existing translation to match up what I can fit of the GBA one, however that'd come to be.

And, no, I've never been to Kentucky (though I do like some KFC-brand).

It's even possible to pull it off on Game Boy. However, if Final Fantasy 2 uses CHR-ROM, you're pretty much screwed in this respect.

I'm a little fuzzy on the details, but I do have some hands-on experience. See, NES games have one major difference from a lot of their descendants. Instead of storing graphics all willy-nilly throughout the ROM and copying them to VRAM as needed, NES games often used CHR-ROM instead. Imagine if VRAM were one huge fixed chunk of graphics: tilemaps still apply (the term in this case is "PPU", if memory serves, though damned if I can remember what it stands for), but you can only ever display what's been burned into CHR-ROM. So no VWF, since that means you have to write new graphics into VRAM on-the-fly.

There are also games that simply used CHR-RAM, emphasis on RAM (though I may have the term wrong), which means they behaved like any modern console title. On those games, VWF is very much a possibility.

I don't know which way FFII leans, but if it uses CHR-ROM, you can kiss your dreams of VWF goodbye.