+  RHDN Forum Archive
|-+  Romhacking
| |-+  ROM Hacking Discussion
| | |-+  translation question from a new romhacker
Pages: [1] 2 3
Author Topic: translation question from a new romhacker  (Read 2 times)
Kaoii
Guest
« on: April 15, 2008, 06:16:52 pm »
Hi, I'm just now starting to get into romhacking and thus far I have found it to be a very fulfilling hobby that I would like to continue expanding on.

Right now, I'm trying to translate a bit of Rockman and Forte: Challengers From the Future for the WonderSwan. I already know there are at least two other translation projects going on for this particular game, and I'm in no way trying to compete with them. I just want to resolve an issue I'm having.

I've read just about every translation tutorial on this website and on the web that I can find. I still can't find a solution for my problem. Hopefully you guys can help.

Image

As you can see in the screenshot above, I have replaced a good portion of the Japanese font with English. There are still some anomalies, but you can see what I'm getting at. I had assumed that if I did a relative search on the new text as shown in the screenshot, it would pull something up that I could make a tablefile from and then work from there. Unfortunately, that isn't how things worked out. When I do a relative search for any of this cavespeak I get absolutely no results. I am using WindHex for relative searching.

What can I do?
« Last Edit: April 15, 2008, 06:17:41 pm by RedComet »
RedComet
Guest
« Reply #1 on: April 15, 2008, 06:21:42 pm »
I edited your post to link to the image instead of embedding it in the post. In the future, if an image breaks the board like that, i.e. it's really big, link to it or post a thumbnail linking to the full sized screen.

As for your question, you don't want to include characters that have symbols above them in your search. In your screenshot that would be K and Y. More than likely they're stored using a hex value that is different from a regular K and Y. Try searching for just "JROZ" instead. Smiley
Kaoii
Guest
« Reply #2 on: April 15, 2008, 06:30:35 pm »
Sorry about the image, it won't happen again Wink

As for the JROZ relative search, I still get no results. I also tried JQHY (which is shown in the right of the screenshot) and still got nothing.
RedComet
Guest
« Reply #3 on: April 15, 2008, 06:36:05 pm »
Try it with wildcards in between each letter. The characters might be stored as 2 bytes instead of 1. You'll have to check WindHex's documentation for how to insert wild cards.
Kaoii
Guest
« Reply #4 on: April 15, 2008, 07:23:47 pm »
That's a good idea, but I tried J*R*O*Z and J*Q*H*Y (*'s representing wildcards) and still got nothing >.<

edit: Upon further inspection with a Zelda II rom, it looks like there was a problem with wildcards in WindHex relative searching. Translhextion actually found four results using wildcards, I'm testing them now to see if they are winners.

edit2: Looks like we have a winner. I was able to change JROZ to QROZ ^_^

Thankyou so much for your help, I won't forget it! Smiley
« Last Edit: April 15, 2008, 07:38:47 pm by Kaoii »
RedComet
Guest
« Reply #5 on: April 15, 2008, 08:31:47 pm »
Awesome. I'm glad you were able to find the text. Cheesy
Kitsune Sniper
Guest
« Reply #6 on: April 15, 2008, 08:38:21 pm »
Just a suggestion, be sure to use both hex editors back and forth. Translhextion has its own share of bugs, and so does WindHex at times. If one fails, try the other. Grin
Kaoii
Guest
« Reply #7 on: April 15, 2008, 08:42:09 pm »
I'm surprised no one has stepped up to make a universal hex editor that doesn't have these kinds of problems and bugs o.O
RedComet
Guest
« Reply #8 on: April 15, 2008, 09:51:22 pm »
There's already plenty of bug free hex editors available. It's just that most of them didn't have romhackers in mind when their authors implemented features. Wink
InVerse
Guest
« Reply #9 on: April 15, 2008, 09:55:41 pm »
If you're just searching for ASCII text, such as in this case, Monkey Moore is much better than Translhextion. Hopefully, the author will add support for Value Scan Relative soon (he stated that he intends to do so, but is a bit busy at the moment. If he doesn't do it, I'm going to try doing so myself.)

As for a hex editor with no bugs, that would require quite a bit of programming, something most people aren't willing to do. I've started coding a ROM hacking centered hex editor a couple of times, then generally decide that it's not worth the effort. If Hex Workshop's table function didn't suck so bad, I'd suggest using it, unfortunately the table system is a complete pain in the ass to use. (At least, as of v4.00, though I doubt they've done anything to improve it in v4.23.)
Kaoii
Guest
« Reply #10 on: April 16, 2008, 03:53:19 pm »
Alright, I'm having another problem that I can't seem to work around. Maybe you guys can help >.<

There is an introduction screen for this game. It uses a different font as the normal text, so I replaced it with the English alphabet. I assumed using the same process of the text with relative searching I could find bits of pieces of it, however, using a relative search here gets absolutely nothing. I do it with and without wildcards and I still get no results. Check the screenshot here:

http://bb.xieke.com/files/untitled24.JPG

Any suggestions on how to find some of that text?
Ryusui
Guest
« Reply #11 on: April 16, 2008, 04:05:37 pm »
Did you try just relative searching PKJO without the wildcards?
RedComet
Guest
« Reply #12 on: April 16, 2008, 04:08:10 pm »
Quote from: Ryusui on April 16, 2008, 04:05:37 pm
Did you try just relative searching PKJO without the wildcards?

Quote from: Kaoii on April 16, 2008, 03:53:19 pm
I do it with and without wildcards and I still get no results.

I'm gonna say, yes. Tongue

As for the problem, have you tried searching for a different string of text in the intro?
Kaoii
Guest
« Reply #13 on: April 16, 2008, 04:20:05 pm »
I resolved it :p

I realized that when I replaced the font, I had to do it in a very weird way by slanting all of the characters down four pixels and arranging them top-to-bottom instead of side-to-side. This resulted in the relative search not recognizing the characters (A to B wasn't separated by 1, it was separated by like 4 instead). So when I searched for something like "AB" I would actually enter the search in as "AE" and I would get the result.
DarknessSavior
Guest
« Reply #14 on: April 16, 2008, 04:25:53 pm »
Good. I'd like to see someone do work on that MM game. ^_^

~DS
Pages: [1] 2 3  


Powered by SMF 1.1.4 | SMF © 2006-2007, Simple Machines LLC