I can do the translation, but I'm not that great with scripts - I keep running into problems with the dictionary compression, and I don't know how to change pointers. Anyone interested and good with this, contact me, I'll send you what I've been working with.

Also, if anyone knows the solution to the conversation where Miho skips rehearsal to see you at the cafe, please let me know. I think this is the last scene, but I don't know how to get past it, and want to be able to check text in this area.

Hopefully I put this in the right area...

Mind being a little bit more specific about the problems you are encountering?

Why was this in the Community Project Board?

There's generally a few ways to handle pointers (haven't looked at this particular game).
String counting. Does it count end-of-line markers? (might be one way to save space in the FDS' woefully limited RAM). Get two strings that are next to each other, that you can easily access in the game. Try lengthing string A, so it overwrites some of string B. If string B starts after the end-of-line marker, it uses string counting.
If not, then it probably uses a pointer table.
They can be nasty to calculate if you're hacking the .fds file directly. Better to use a file splitter/merger. (then the pointer is just the file offset + the RAM address it's loaded into).
But if you're hacking the .fds directly, then the best way would be to use FCEUltra XD SP. Play the game until you get to the string you want to calculate the pointer for. Open the built-in hex editor. Search for the hex values of the string in CPU RAM (should be between $6000 and $DFFF). Where it starts is your pointer value. (so like if you found the string was at $8765 in RAM, then you'd search for 65 87 in the .fds.)

Ok. Well do you have a table for the dictionary? I would start by knowing what the hex value for each entry is and then knowing how long  each entry is.

Remember, in the script, each dictionary entry is represented by one or two bytes. It's just an entry. Aside from that is the actual dictionary table. This contains the full dictionary text for each entry.

If you want to change an entry or the size of an entry, you must do so in the dictionary table. There are usually two common ways the dictionary is stored. 1.) Each entry has an end byte. 2.) The entries are all jumbled together, but have a pointer table that will mark the beginning of each entry.

What exactly is your goal right now? If you're trying to dump a script, you don't need to mess with the dictionary at all. You just need to have those entries in your table for a script dump.

If you're trying to insert. You have a few options. You can not insert any dictionary bytes and insert everything in full. That's simplest, but of course takes up the most space.

Option 2 is probably what you're doing. That's filling in the dictionary with English words for script insertion. For that, you'll need to figure out how your dictionary table is stored in the ROM.

Let's start there. Have you found the dictionary table?

OK. So, take a clean ROM. Now, try to shorten the length of ONE dictionary entry by ONE byte. All you need to do is move the end byte back one location. Does that work?

When exactly do you get the '9999' issue? There is a reason it is happening and you can figure it out by working step by step.

Assuming you can reduce the length by one without any issues, next try replacing that dictionary entry in the script to see if you get the desired results. You say you have a table made up, so it should be trivial. Just replace the entry byte/bytes with another.

If those two things work, all that is left is expanding a dictionary entry. THAT however may be more difficult and cause problems because now you most likely have to deal with starting pointers unless your dictionary routine is counting based which it probably isn't.

So, what are your results from this?