[Densetsu]

Many games are released in Japanese before they're released in English or any other language. In most cases, they're released in Japanese years before they're localized. Sometimes they don't get localized at all and never see the light of day outside of Japan.

Enter the ROM translator.

This is a compilation of some useful websites and tools for translating ROMs. Unfortunately, there is no tool or app that will let you go from "Zero Japanese to Translator" instantly. Believe it or not, n00bs have asked for such a magical tool on this forum. I hate to break it to you, but it doesn't exist. You have to know Japanese to translate a ROM into your target language. This thread assumes a knowledge of intermediate Japanese, which is the absolute minimum skill level I would recommend for anyone attempting to translate a ROM.

What is "Intermediate Level?"
By intermediate level, I mean you should be able to read a standard conversation in Japanese ON PAPER covering an everyday topic (such as discussing games/movies, talking about work, etc.) and be able to understand it without the use of a dictionary. You should know at least 400~500 kanji and be able to look up kanji you don't know by radicals, stroke count and stroke order. You should be able to read manga containing furigana (ex: anything by Shōnen Jump) in Japanese and understand colloquial conversations (non-textbook Japanese).

To All Aspiring and Prospective Translators
If you are interested in helping out with future translation projects, please post in this thread, along with your Japanese language experience, favorite games, manga and anime. Since some games are based on manga and anime, knowledge of certain manga/anime titles is helpful. Feel free to provide any other information you feel might be relevant. My hope is that we can use this thread as a sort of directory that others can refer to when they need a translator.

Suggested Readings from Loekalization
Anyone attempting to translate a ROM should read through these articles to learn more about the logistics and problems one may encounter in translating (thanks DS1!)

• Biggest Mistakes
  
• Urban Myths
  
• Project From Hell: Read the section regarding too much leniency and computer-assisted translation.

Useful Websites

• Romhacking dot net: The go-to site for ROM hacking projects, including translation projects. In order to start translating a ROM, you need to extract the text and any images containing Japanese text from the ROM. If you can't find anyone to extract the text here, you'll most certainly be able to find someone there. And they're always looking for translators, so it's a great place to try your hand at a few projects.
  
• Japanese Programming Madness: There are things that both the ROM hacker and the ROM translator have to take into consideration when working together. This thread discusses those considerations.
  
• The Japanese Page: An excellent forum with many great resources and lots of fluent Japanese speakers willing to help. There's a subforum for translation help, but they will not help you if you're lazy. If you encounter a particularly tough translation, ask for help here after attempting it yourself. Make sure to provide your translation attempt, as well as plenty of context. And read this before asking for help!
  
• Google Docs: Creating a translation spreadsheet is a good way to organize your translation. It allows others involved in the project to open the spreadsheet and see at a glance how much has been translated, what still needs to be translated, and provides plenty of space for collaboration between translators. (Translation spreadsheet samples: Image 1 Image 2 Image 3 Image 4)
  
• weblio辞書: (weblio Jisho) A very good online dictionary that includes a dictionary for native Japanese, a E-J / J-E dictionary, a Japanese thesaurus and even a Japanese sign language dictionary with videos for every sign. The latter two are less useful for translating from Japanese to English, but the former two are well-suited to that purpose. The E-J / J-E dictionary grabs results from Kenkyusha (the Oxford of Japanese), JMdict (the dictionary used by Rikaichan), Wikipedia Japan (including pictures), among other sources. All definitions come with sample sentences, both in English and Japanese (thanks Nagato!).
  
• 英辞郎 on the WEB: (Eijirō on the WEB) Another good online dictionary for looking up not just definitions of words, but proper word usage in sentences. Just about every dictionary entry provides sample sentences both in Japanese and English so you'll be a lot less likely to make a mistake on how a word is used in Japanese.
  
• goo辞書: (goo Jisho) A multi-dictionary search that also provides sample sentences. Sometimes has words that you won't find in Eijirō.
  
• ニコニコ大百科: (Nico Nico Pedia) Essentially the Japanese version of Urban Dictionary. Japanese is a constantly evolving language, and it is just as rich in slang, Internet lingo and memes as is the English language. Games tend to use a lot of "trend words" and pop culture references, and this website will help you stay up to speed (thanks Nagato!)
  
• 三省堂 Web Dictionary: (Sanseidō Web Dictionary) A dictionary for native Japanese speakers. Like goo Jisho, It tends to have words in it that you can't find in Eijirō. Great with fuzzy searches, for example when you extract an image containing a string of several kanji and you only know a few of the kanji. If you input the few kanji you know, sometimes it will return results containing the entire kanji combination that you can then look up.
  
• Rikaichan: For on-the-fly translating on translation spreadsheets. After installing, simply hover your mouse over any Japanese word you don't know, and it will instantly display the English definition. Requires Firefox and ability to read hiragana at the very least. CAVEAT: This is absolutely useless if you do not have a strong command of Japanese grammar! Without knowing grammar, your translations using Rikaichan are no better than Google Translate. Use sparingly, and rely more on your own Japanese knowledge and reputable dictionaries like weblio and Eijirō.
  
• Denshi Jisho: Good for looking up kanji by radicals. Uses the same dictionary as Rikaichan, so there's no need to use it for looking up words.
  
• Wikipedia Japan: Use for a variety of reasons, particularly looking up rare Japanese words and pronunciations, obscure cultural, historical and religious references, etc.
  
• Google: When you can't find a Japanese word in any dictionary, chances are that it's not a real Japanese word. In these cases, sometimes even native Japanese speakers wouldn't know what the term is. With Google you can usually find something containing the term, and perhaps more context. For example, I was approached for help translating a phrase that appeared in an Japanese otome DS game: "ひゃにょひぃにょきゃい？" (Hyanyohii nyo kyai?) which doesn't make any sense. But Googling the term yielded several hits, one of which was particularly helpful in translating the phrase. It turns out that the character in the game was saying "楽しいのかい？" (Tanoshii no kai? = Are you having fun?). He says it all weird because the player is pinching his cheeks (or rather, tapping his cheeks with the stylus) while he says it. So that bit of context was crucial to the translation, as well.
  
• Text Mechanic: Depending on the ROM you're translating and the way the text is formatted, you may have to insert line breaks, full stops, and various other codes within your translated text in order to get it to display properly in-game. This website can help you automate much of that tedious process and save you a lot of time.

Guidelines for Translating ROMs

If you're already experienced with translating, these guidelines may be seen as an insult to your intelligence. This is not meant for you, but rather for those who are thinking about translating a game but have little to no Japanese knowledge. Anyone who cannot meet the following minimum requirements should learn more Japanese before attempting a translation.

As a translator, you should:

• be able to actually read and understand everyday Japanese WITHOUT using an online translator or dictionary (in other words, have a functional knowledge of kanji (400~500 characters minimum) and at least intermediate-level grammar)
  
• know how verbs are conjugated in Japanese (be familiar with all conjugations, including causative, passive, conditional, etc.)
  
• know how to look up kanji by radicals if you can't read a particular kanji off-hand (including knowledge of counting strokes and stroke order)
  
• have excellent grammar, writing and editing abilities (especially in the target language--usually English)
  
• play through the entire game before translating (absolutely crucial for context)
  
• use Firefox (for rikaichan)
  
• (recommended) have some familiarity with Kansai-ben and other Japanese dialects

As a beta tester, you should:

• be extremely meticulous and pay great attention to detail
  
• play through the entire game and be aggressive about unlocking secrets, accessing menus, etc.
  
• be willing to do 2-3 complete playthroughs if necessary
  
• have excellent English grammar and spelling
  
• be as thorough and specific in your bug reports as possible
  
• be capable of taking CLEAR screenshots (whether capturing from emulator or taking a picture of the DS screen)
  
• be able to upload screenshots (using puush, imgur, or other preferred methods) to include with your reports
  
• be able to remain in regular contact with the rest of the project team

Other stuff for translators:

• Avoid open translation projects (where anyone can join). This leads to morons sabotaging your projects. Stick with a few people whom you know and trust--the fewer, the better. I would recommend translating solo, but if you plan to have two translators on one project, they have to be in constant communication with each other. Three translators would be pushing it--instead, the third translator can serve as an editor whose sole job is to make sure that the first two translators' writing styles blend together seamlessly.
  
• Any group working on a translation together should ideally have the same messaging client or use IRC so they can collaborate with each other in real-time.
  
• PLAY THE GAME! I cannot stress this enough. If you're going to translate a game, you need to be able to see everything in context. You could be a native Japanese speaker, and you still wouldn't be able to translate a game properly unless you play it. Ideally, you should be translating lines as you see them appear in-game, when you have all the context you can possibly have.
  
• Use other dictionaries when one doesn't yield the results you need. Sometimes the only way to get results is to search the 国語 dictionaries (for native Japanese speakers). The definitions will be in Japanese, but you should be able to understand the definitions with no problem. When none of the dictionaries give you any results, Wikipedia Japan does wonders.
  
• When all else fails, Google the term! And no, I don't mean Google Translate. If you can't find a Japanese word or phrase in any dictionaries or Wikipedia Japan, chances are it's probably not a real Japanese word. When you Google an obscure Japanese term, you might be able to find some information about the term in blogs or articles discussing the term (these blogs and articles will be in Japanese, but again, you're a translator and not a "translator" so that shouldn't be a problem to you).
  
• Don't be so hell-bent on keeping translations literal. A lot of times Japanese is difficult to literally translate into English and still make sense to the target audience (those who will be playing the translation patch). Feel free to take liberties with your translations, but don't stray too far from the original Japanese. Taking liberties does NOT mean: "Eh, I don't understand this, so I'm going to make something up."
  
• Revisit your translations after a few days. The hallmark of a good translator is that their translations sound like native English, not Japanese translated into English. You may not see it on the first pass, but when you remove yourself from the translation and then come back to it after a few days, you'll notice that it could be worded to sound more like natural English (or whatever the target language is). This is why a translator should have excellent grammar, editing and writing abilities.
  
• Relying on editors to check your translations can relieve some of the burden of your work, but if your editors don't know Japanese, it's possible that they can change your translation so that it loses some of the original Japanese meaning. That is not to say that you shouldn't use editors who don't know Japanese, but just be aware of the pros and cons and make your decision on editors accordingly.
  
• Translators should keep a translation log. It's essentially a personal document of translations you have done on the project--particularly difficult translations or disputed translations. In it you should log your thought processes and rationales for translating things the way you did. It can help you improve your translations and prevent inconsistencies if used correctly. This can be in any format you want. Of course, to keep a successful translation log, you have to actually know how to translate.
  
• Google Translate yields bad translations for the purpose of localizing a ROM--just don't use it. It's passable when used for English or the Romance languages, but it just screws up with Japanese. If you can't translate without using it, then you need to find another translator before you start your project.
  
• Translating is a constant learning process. Even as a native English speaker, occasionally I still come across English words that I don't know when I'm reading a book, article, etc. So expect this to happen while translating Japanese (or whatever your second language is), and don't get frustrated. Instead, use it as an opportunity to learn more vocabulary and grammar.
  
• DO NOT call yourself a Japanese-English "translator" or say that you're "translating" if you can't read this image, or don't at least know enough about radicals to look up the kanji in this image. It makes you the translator's equivalent of a script kiddie.

Disclaimer

I have studied Japanese off and on for 14 years, and have spent 3 of those years studying it in earnest while living in Japan (in addition to studying it for 4 years in university). At the peak of my abilities I passed Level N1 of the JLPT (the hardest level), so I can safely say that I understand Japanese to a level where I am able to translate most things with little difficulty. But I am by no means a professional translator. None of the information in this topic is meant to be professional advice for localizing games. It is only meant to serve as a general guide for aspiring ROM translators who want to localize games as a hobby. I am sure that there are members on this forum who are much more experienced with Japanese, and I invite them to share their resources and tips for translating ROMs on this thread. 宜しくお願いします！

[Phoenix Goddess]

As a translator who learned about 100+ Kanji characters from translating, knowing about 400 or more is absolutely necessary for translating or you'll end up constantly going to dictionaries and radicals.

You can know Kana, but that doesn't mean you can translate properly, yet. Kana is just as important to know as Kanji and to translate video games, you have to have knowledge of both, as well as verbs, sentence structures, grammar, etc. It's really the only way you'll be able to translate without going to a dictionary every five seconds. (And there would be a lot less dropped projects.)

Another thing to watch out for are text limits. You can translate freely as long as you stay within text limits.

Densetsu listed some amazing dictionaries and help(my personal favorite is jisho and 英辞郎.).

To those who do want to learn Japanese or start translation projects, good luck to you

Edited by phoenixgoddess27, 18 October 2011 - 11:16 AM.

[StorMyu]

phoenixgoddess27, on 18 October 2011 - 11:04 AM, said:

You can know Kana, but that doesn't mean you can translate properly, yet. Kana is just as important to know as Kanji and to translate video games, you have to have knowledge of both, as well as verbs, sentence structures, grammar, etc. It's really the only way you'll be able to translate without going to a dictionary every five seconds. (And there would be a lot less dropped projects.)

Sure, but it's not only about reading Kana/Kanji, like you said, if you don't know what they mean, that's futile ^^

phoenixgoddess27, on 18 October 2011 - 11:04 AM, said:

Another thing to watch out for are text limits. You can translate freely as long as you stay within text limits.

As a Romhacker, I tend to only limit the lenght of the textbox, not the translation itself.
You can always add a textbox if the sentence is too long for the one you were translating or anything else.

[Phoenix Goddess]

StorMyu, on 18 October 2011 - 11:33 AM, said:

As a Romhacker, I tend to only limit the lenght of the textbox, not the translation itself.
You can always add a textbox if the sentence is too long for the one you were translating or anything else.

Indeed, but not every romhacker is going to know how to add a textbox to a sentence. In cases such as those, there are text limits that even translators will have to follow or things won't fit, games will crash, worlds will be destroyed, and the zombie apocalypse will start. (Exaggeration there.)

[Nagato]

Here's my favorite dictionary when I need to look up something: http://www.weblio.jp/
Also, for understanding Japanese memes the nico nico pedia is really good: http://dic.nicovideo.jp/

[FAST6191]

Nice thread, I am struggling to word it but something on the various fonts/calligraphy styles/typefaces might be an idea (kaisho, gyosho and such). I see some translators have fun with certain styles where they would breeze through it in a more conventional one.

It is not so bad normally when you can change it like any other font but when dealing with text in images and occasionally when roms use it as a narrative device (having a tradition bound character use an older style font or a robot use a coding style font- not so much a problem back when but today you can spin twenty fonts at once and not have a system break a sweat) or one has to leave it in as the font is custom and carries either custom characters (button presses as the like), occasionally DTE/character names in a single byte or multiple encodings of text (think the shiftJIS technically having standard unicode Roman characters and the ones up in the 824f and onwards range but for Japanese) as porting it out is more hassle than it is worth.

[Densetsu]

Nagato, on 18 October 2011 - 04:11 PM, said:

Here's my favorite dictionary when I need to look up something: http://www.weblio.jp/
Also, for understanding Japanese memes the nico nico pedia is really good: http://dic.nicovideo.jp/

I just spent a good 20 minutes checking out weblio and it's definitely got its strengths over some of the ones I've already listed. And the Nico Nico Pedia is awesome especially for those Japanese visual novels like Hacker: 覚醒 and the ときめきメモリアル: Girls' Side games.

I just did a search for "KY" in NicoNico Pedia and it gave me the definition: 「空気が読めない」の略語。 Nice!

Definitely including them in the first post. Thanks for the links!

FAST6191, on 18 October 2011 - 06:21 PM, said:

Nice thread, I am struggling to word it but something on the various fonts/calligraphy styles/typefaces might be an idea (kaisho, gyosho and such). I see some translators have fun with certain styles where they would breeze through it in a more conventional one.

It is not so bad normally when you can change it like any other font but when dealing with text in images and occasionally when roms use it as a narrative device (having a tradition bound character use an older style font or a robot use a coding style font- not so much a problem but today you can spin twenty fonts at once and not have a system break a sweat) or one has to leave it in as the font is custom and carries either custom characters (button presses as the like), occasionally DTE/character names in a single byte or multiple encodings of text (think the shiftJIS technically having standard unicode Roman characters and the ones up in the 824f and onwards range but for Japanese).

Hmm, not sure what I could say about translating different fonts, other than the fact that tensho (Imperial seal script) is a pain in the ass to read (although it is my favorite style). Take, for instance, the kanji "pun" for yoroshiku, which can be roughly translated as "thank you" or "regards."

よろしく 

The last style on that list, tensho, hardly resembles the characters in their standard kaisho and cursive gyosho forms (tai means "form"). Fortunately I have not had to translate much text written in tensho (or rather carved, as it usually is). In the rare instances where I've had to read something in tensho, I would defer to a native Japanese person.

I think the topic on fonts would be better suited to explanation by someone more graphically-oriented than I. Some amazing work was done on Nanashi no Game. I played both the Japanese and English-patched versions to compare several things, one of which was choice of font style, and I was impressed. Fonts are not my area of expertise, so if anyone else would be able to shed some light on it in this topic, the discussion would be welcomed.

[the_randomizer]

To be perfectly honest, I've always had a desire to do some ROM translating, even though I know it can be a daunting task in and of itself. I've known the language since 2004 (intermediate level), I spent two of those years actually living in Japan (awesome place to live by the way)and immersed myself in the culture/language. I can read a fair amount of kanji (don't know exact the number, but way more than I can actually write) and understand the grammar well (bases, conjugation, etc). Favorite games include Final Fantasy IV through X, Chrono Trigger, Earthbound, Bahamut Lagoon and Super Mario RPG.

The main reason for me wanting to delve into doing translation is there are often words/phrases that I don't agree with (Tales of Phantasia for the SFC especially). While I don't expect to translate an entire ROM by myself, I would like to pitch in whenever I can, as I'm new to the ROM translation scene (doing the actual translating).

Favorite anime (I refuse to watch dubbed versions, due to horrible voice acting):

- One Piece (up to episode 518)
- Dragon Drive
- Naruto
- Inuyasha
- Most of Studio Ghibli movies
- Digimon Savers (I know, I'm a nerd)

So, I don't know how much I can actually contribute, or how much my efforts will amount to, but I want to at least give it a shot.

-宜しくお願い致します。

Edited by the_randomizer, 19 October 2011 - 01:19 AM.

[Densetsu]

the_randomizer, on 19 October 2011 - 01:13 AM, said:

-宜しくお願い致します。

You certainly sound like you've got what it takes! If I take up another translation project after Blood of Bahamut, I'd be more than happy to use some help in the future (if you don't get picked up for another project before then).

[the_randomizer]

Heh, thanks. How knowledgeable does one have to be with hex editing? I'm not....100% comfortable with hex editors yet.... I really want to get into ROM translating, but I honestly don't know where to begin; sorry if it looks like I'm being a coward.

Edited by the_randomizer, 19 October 2011 - 01:35 AM.

[kevan]

These kind of topics always wow me 0_o...
I wouldnt mind getting into translating (but the dodgy google translate side of things )

[Densetsu]

the_randomizer, on 19 October 2011 - 01:32 AM, said:

Heh, thanks. How knowledgeable does one have to be with hex editing? I'm not....100% comfortable with hex editors yet....

Well, I guess the more you know, the better. But truth be told, I know next to nothing about hex editing, or ROM hacking in general, for that matter. I strictly translate. You're good to go

[the_randomizer]

Densetsu, on 19 October 2011 - 01:35 AM, said:

Well, I guess the more you know, the better. But truth be told, I know next to nothing about hex editing, or ROM hacking in general, for that matter. I strictly translate. You're good to go

So, by that logic, if I simply made spreadsheets/text documents containing the translated script itself (like dumped text or what have you), that would be sufficient?

Now, to find text dumping tools.

Edited by the_randomizer, 19 October 2011 - 01:45 AM.

[Densetsu]

kevan, on 19 October 2011 - 01:34 AM, said:

These kind of topics always wow me 0_o...
I wouldnt mind getting into translating (but the dodgy google translate side of things )

Sorry, not interested in Google translations, but come back after you've learned some Japanese. The ROM translation scene is always looking for people who can actually translate.

the_randomizer, on 19 October 2011 - 01:41 AM, said:

Densetsu, on 19 October 2011 - 01:35 AM, said:

Well, I guess the more you know, the better. But truth be told, I know next to nothing about hex editing, or ROM hacking in general, for that matter. I strictly translate. You're good to go

So, by that logic, if I simply made spreadsheets/text documents containing the translated script itself (like dumped text or what have you), that would be sufficient?

Now, to find text dumping tools.

That's essentially all you would need to do to start a translation project. But since different ROMs compress and store text differently, you'd have to ask someone to make a text extraction tool for you if you can't do it yourself. Sometimes the text is stored uncompressed within standard .txt files in the ROM, so those are the easiest to extract. Usually you'll need a ROM hacker to help you with the non-translating aspects of the project. I don't worry about that stuff--generally it's easier to find someone to dump text/extract images for you than it is to find someone willing (and skilled enough) to translate a game.

[the_randomizer]

I was thinking of tinkering around with Breath of Fire - The Dragon Warrior, as it's called in Japan - ブレス・オブ・ファイア：竜の戦士. Granted, it has better grammar than BOF2's original crap translation since Ted Woolsey worked on it, but I still find it to be lacking. Finding the tools to dump it should be easy if go to Romhacking.net or something.

Update: Right now, I have to take screenshots of each individual text box since there are no up-to-date and/or working tools that will assist me with extracting the necessary scripts. Crap. I was afraid this would happen. None of the tools I found do what I need to do (neither does Geiger's Snes9x). Any suggestions?