You asked this 4 times already, again and again. You'll still get the same answers. Before people start to flame or anything I'm going to answer your question, if no one else has anything productive to add, don't post.

Think of addresses, like house numbers. Every house contains one letter of our text.

House 1: T
House 2: E
House 3: S
House 4: T
House 5: X

X is a special code that tells us the word is complete. You see that the information in those houses forms the word TEST this way.
The pointer points to one of those house numbers. It shows where the our text starts.
So the original pointer will point to House 1.
You can now change it to House 2 and the text displayed in the game will be 'EST'.

So, you have text that is longer than the original Japanese one. All you have to do is change the pointer to words after the one that you change to point to an address later in memory.

Ah, I see, so I could basically move delete one byte and move it next to Marth's name to make space? Sounds kind of complicated. Is simply expanding the rom space possible?

Sweet well I'll take a look at that guy and see if it helps. That post also helped me get a good understanding of pointers. Hopefully the madhacker thing will help me find them though.

You know, I was thinking the other day that it would be nice to have a more "modernized" pointer document. While the information in Mad Hacker's is still solid, to the best of my knowledge, the presentation is quite horrid by today's standards. Gil Galad wrote an appendix to Mad Hacker's guide, but I believe that simply added additional information and didn't re-present any of the original information. AnusP's 'Advanced Hacking Tutorial" is just as ancient as Mad Hacker's Guide. (They both turn 10 years old this year.) Gideon's "Using Pointers Effectively" guide is narrowly focused and short, while his Gameboy pointer doc is narrowly focused, short and assholish. (That's not a slam on Gideon, he intentionally made it that way.) XCalibur's pointer doc is decent, for what it is, but not comprehensive enough to serve as the main pointer tutorial, which leaves Duo's PSX Pointer doc, which again is narrowly focused.

A well written pointer document could serve the community well. I've contemplated writing one in the past, but always balked because I wouldn't really be adding any new information, simply presenting existing information in a more easily understood fashion. Of course, aside from my NES Title Screen Hacking doc, I can't really claim to have developed any of the techniques described in any other tutorials I've written, so I don't suppose that's a particularly valid excuse. Does anyone else think that it would be a good idea to put together a new pointer guide?

If a document is made, then perhaps a short section as to how pointers act the way they do.  From what I've seen on the NES, there are 2 spots in ram that are needed for a pointer to work.  You load the first byte in ram using an indexed value.  Then you save it to a spot on the ram map, usually zero page.  Then you do the same for the next value, and save it to the spot next to it in ram.  Then you do can perform and indirect opcode, which takes the values you loaded, then uses it to point to the data you wish to obtain, then it's loaded into memory in which it can be performed.  Pointers can be stored either as two byte pairs, or as seperate arrays, like in Megaman 4.  There is practically zero difference between a pointer defined as data and pointers that are used in opcodes to write to and values from the ram.

NES pointers are simple when you understand how ram works.  Depending on where in ram you wish to read or write to, the pointer will look different.  Standard pointers usually go from $0080 to $FFBF.  This is used to reference the switchable banks in ram.  $8000 to $BFFF are switchable using bankswapping routines.  From $C000 to $FFFF is the main program bank, which almost never changes.  In there, references to this section of ram go from $00C0 to $FFFF as far as pointers go.

Yeah, that's a crappy explanation but really untill you understand the function of ram, ASM and pointers will be pretty hard to figure out.  I litterally went from n00b to ASM hacking in a matter of weeks once I understood how ram on the NES was mapped out.

Well I reread a few docs, such as the MadHacker thing and I'm still confused as hell on how to find them. I keep putting what I'd interpret to be the pointers, but then when I find and modify them, nothing happens. I've tried several calculations and interpretations, but nothing. Madhackers guide was especially confusing(What the heck was 28210? Certainly not the offset where "Nothing" or "here" was located).

I'm thinking I should just give up though. I've tried a bunch of techniques, take the hex of the start text and decrease it to 2 hex values and flip it. Take the hex of the start text, subtract 200 THEN flip it. I just don't think this is ever going to make sense to me. FOR INSTANCE, in Fire Emblem: Monshou no Nazo 0x71A3C, is the "hex" offset of the starting text(Unless they perhaps wanted me to use "465468" the decimal value). I decreased it to 2 values, 1A and 3C, then I flipped them. But then however, I search for the pointers, modify them and nothing happens.

I'm trying to find the pointers for the text...

I've already expanded the rom, but that means nothing if I can't calculate the pointers.

Followed most tuts and I figured out a pointer of 3C18 and guess whaT? Didn't work and I did exactly what the tuts said.