And this is why google translate(and machine translators in general) is always a bad idea.
Not to mention that machine translators can't help you with verbs, particles, direct objects, or hardly anything else to make the sentences sound less like gibberish and more like accurate sentences. They will almost always get them wrong.

 

Hopefully the following will not be too much rambling and something nice will come of it.
I already went and although I could bash machine translation (I certainly throw my hat in with those that consider it all but useless) it would serve little purpose at this point, however I have been thinking about writing a post or something about what level of Japanese a ROM hacker should know if they intend to work with Japanese ROMs. While I can do the hacking side of things I thought it best to also ask those that do translating to make sure I am not saying something truly silly. I am not aiming for the the bare minimum (which is arguably next to nothing) but something that allows people to be reasonably functional.

To this end
Things one should appreciate about the Japanese language when playing ROM hacker (hacker side of the fence)
The types of Japanese characters and how they work-
Hiragana and Katakana which are collectively known as the kana. They are the basic constructs of the language with katakana usually being used for loanwords and foreign words and being somewhat more angular than the more freeform hiragana which are used for native words. There are some fairly accepted ordering/sorting methods (I believe gojuon order is the name of the most popular- stuff like http://www.romhackin...t/utilities/55/ should add it) and few games deviate here but said ordering might well leave out some of less common, possibly obsolete, ones the script writer might use or that the game might add entire characters for characters with punctuation (see Dakuten and Handakuten) so be aware of this when constructing tables and the fonts they match up with.

Kanji- the elaborate symbols that originally came out of China. There are many such symbols and most consider to be the harder part of the language, to the point where translators tend to know a selection (there are various levels but there is not a set upper limit of kanji) and some works/fields are known for downplaying their use (most notably in the game/anime world for the likes of shounen manga and anime which is nice as games aimed at those audiences are some of the most popular targets for translation). There is no universally accepted ordering of kanji which makes relative searching, one of the most powerful yet simple tools available to the ROM hacker dealing with an unknown text encoding, tricky at best.
However there are lists of selected Kanji that are taught to people but unless you also find yourself interested in Japanese education/orthographic history you probably do not need to delve into it as a ROM hacker (if I am not overstepping my mark then as a translator it might help as games tend to be written by modern writers for a modern audience and knowing the way the modern language is taught/learned/graded can be a good thing*). More modern games do often share orderings or parts thereof between games so do give it a look to other games, especially ones from the same developer/publisher. Although the lists, the distinction between kokuji, kokkun and categories/moji (such that might still be considered to exist) might not be that important you should know the terms radical and stroke ordering of which radical refers to the base stroke/component it derives from and stroke is quite literally how many strokes are needed to finish the deal and is about as close as you might get to a proper ordering system (everything else is so much good luck if you happen to encounter it).
I do not know of any ROM hacking tools (or really much in the way of tools in general) that can add these lists like you might be able to add kana or Roman alphabets.
Equally know that games can and have picked and chosen only the ones they use (although they can be in say the order of the script/use in the game/use in the font) or a subset of common ones and added any extras to them.

*for instance a game writer will probably not be calling on some ultra obscure kanji in general text (if in a game as a "magic symbol" or decoration however then all bets are off) so there is probably no need to bust out your copy of Dai Kan-Wa Jiten for the help screen of the latest shounen tie in game.

All three can be intermingled in the text effectively at random; obviously there are situations in the language where things are expected to follow others but as far as your basic regex searches are concerned it is random. If however you want to change a bit of the font to allow for some basic translation and keep some Japanese intact it is probably better to axe a few kanji.

Furigana- ostensibly an optional pronunciation key for Kanji, however it can go well beyond that for certain games/authors. Officially the concept is designed for those that might not know Kanji that well to read things in it (in Japan it is supposed to be for younger people, ones that might know the spoken word but not the symbol that represents it, but it often helps those with less familiarity with the language too). Uncommon back on 16 bit and earlier systems things changed for the DS (especially with the touch screen) and it has seen a fair bit of it (the first Zelda I believe is a good example). This can often be the reason a sentence might be longer than it should be at first glance or pointers might be odd.

Japanese characters in general are fixed width unlike the Roman alphabet (think ijlt vs WQMK and such to say nothing of punctuation) and tend to sit within lines (think jypqf) unlike Roman character sporting languages, this then leads to one of the harder aspects of text hacking in variable width fonts (not necessary for Japanese so they tend not to be added in to the game code) and if you are really flash true line handling code. This cuts the other way as well but I am not sure this is the venue to deal with half width and full width characters/encodings, not to mention I will go so far as to accuse it of largely being a historical quirk (indeed one might argue some of the insane stuff the older consoles did was to work around these sorts of issues) and not something that warrants more than a passing mention for most hacking work.

Japanese text by virtue of Kanji but often in general tends to be somewhat shorter in terms of actual characters (the debate still rages when it comes to speech) so expect issues when it comes to fixed width menus (if you have hacked the font then you might consider adding two or more characters into a single tile as a crude but effective workaround) and to have to deal with pointers a lot.

Japanese technically does not have spaces between words with any you see being more aesthetic thanservingavitalfunctioninthelanguage so some of the more cute sentence structure hacking methods (When playing with a relative search tool on an English game I quite often assume there will be a sentence using the word the with a space either side, such a thing often yields an entire basic table with just that search. Equally if you assume the most common character in text is space and work from there you can get far) or pointer inferences (if you are unfortunate enough to be dealing with word level pointers so be it but thinking more a variation on the space being the most common/coming in given locations).
More importantly you should consider this when making a script dump if you are heading down that path and are using such things as a boundary and at least be prepared to be a bit flexible for your translator (I said aesthetic but fitting things in a text box can still be problem for those using Japanese).

However Japanese is not my forte so to the translators short of true language skills what would you like any hackers you work with to have an appreciation of? If you can tie it into a hacking concept like I did for some above even better but that is certainly not necessary. Equally some of my things to know might be given too much emphasis (I can not think of any real occasions where furigana has troubled me as a ROM hacker and I mainly mentioned it as it can be a nice place to stick a note or two) or too little (I can not say I have examined custom or standard encodings to see if there is much in the way of kanji ordering vis a vis the ?-moji or schoolboy versions of kyoiku/gakushu vs joyo and if it would help to at least scan over such when dealing with custom kanji encoding setups then yeah). The only things I think I would want to add/expand upon is something on the various Japanese encoding methods (shiftJIS, EUC-JP and such) and how they might fall short but I have yet to be bored enough to vet the encodings against the language (did it once for Arabic and some of the lesser encoding systems there and pretty much vowed never again), something on the vertical vs horizontal writings but intro sequences and graphics aside I am not sure I have seen a game use tategaki (vertical) and maybe something on romaji but that is more of an IME problem than something that worries hackers (if truly necessary I would imagine it would be kicked to OS level, a nice library or to a programmer that knows Japanese).

On a different note entirely it has come up once or twice in recent months in various conversations so I figured it might be worth mentioning- translators official and otherwise have on occasion not shown the Japanese language much reverence (one of the many reasons several games have got retranslations over the years) and it does cut the other way so should something come into a Japanese game from another source (quite often Chinese and European history but certainly not limited to it) and have got butchered along the way then you can "revert" it to how it is/"should be". A less than brilliant example might be some of the names of creatures/concepts in Final Fantasy but if you prefer an analogy it is a bit like treating your DVD or some such as a perfect source for your video- the people charged with the initial encoding might still have hosed it up/phoned it in.

Also as for nice links I linked it up in the past but it was not here so http://www.loekaliza...m/mistakes.html might be worth a scan through and to save me digging up the thread I also linked up http://www.joelonsof...es/Unicode.html .

 

This topic may contain more information relevant to your question:
Japanese Programming Madness

 

Agreed. After all, we don't translate words like "sushi." Sushi is sushi is sushi. The same is true for all the other words you mentioned. In my last post I forgot to mention that we probably could have just rendered 巨獣 as simply "kyojuu" and left it at that.

Warning: Spoilers inside!

This reminds me of another well-known Japanese word: 将軍 (shōgun). It can be translated as "general" or "warlord," but we typically render it as-is by sticking with a straight-up transliteration to "shogun." From this word we get "shogunate," which is not a Japanese word. This word sounds silly to me because it's a Japanese word with an English suffix attached to it. "Shogunate" is a word invented by English speakers to refer to the shogun's administration. The actual word for a shogun's administration is 幕府 bakufu.

To illustrate my point on the silliness of "shogunate," consider the Japanese word for "beautiful," which is 美しい (utsukushii). Using the word "shogunate" to mean "administration" is as strange as using the word "utsukushii-ness" to mean "beauty." But no one makes a fuss over "shogunate" because it's a word we adopted into the English lexicon and turned into our own long ago.

This is the point I was trying to get across in defense of our decision to translate 巨獣 (kyojuu) into "behemoth." Square-Enix has taken the words "behemoth" and "Bahamut" and made them into their own. So our translation was based on SE's lexicon, not the Semitic lexicon.

 

I think the general concensus is that a shogun is the supreme general and a daimyo is a lord / vassal of the shogun. The daimyo themselves then had samurai underneath them.

But the importation of such words does raise the question of how much of the original semantic value is imported along with it. To my knowledge, a shogun is defined as a "barbarian-quelling genrealissimo", but I would probably equate him to a "commander-in-chief" instead. However, I usually see the term shogun equated with "general", and people seem pretty happy with that.

You can draw a parallel between the "behemoth" issue and 和製英語 ("Japanese-made English"). A deconstruction of the term is enough to give it away: they should be treated as Japanese terms. The easiest example I can think of is テンション. More often than not, I see it being used to mean spirits (e.g テンション高い), and not in the sense that native English speakers would use it "There was a lot of tension between the two".


Extending that argument when it comes to the translation of games: it's important to translate a game on the game's terms (such as how said game "imports" words or how they perceive / treat different terms). This is particularly true for a fantasy-genre game like Blood of Bahamut; real world knowledge is less important than specific lexical knowledge (where the lexicon is the Square Enix lexicon).

 

I stumbled across it when writing the little Japanese section of the ROM hacking docs so can I also recommend at least http://www.sljfaq.org/afaq/symbol.html (and probably the site as a whole); you have http://kanji.sljfaq.org/draw.html as a offhanded link but the main site is pretty good (it being web distillation of a fairly old newsgroup after all) for both hacking* and translation/general language learning. I am sure people would have dropped back down to the main site but a push in that direction might be good too.

*earlier and for the most part it is still in effect I advised against some regular expressions style searches but 「 and 」being the equivalent of quotes would make it very good for sentence length and punctuation driven decoding both of which are quite powerful techniques for figuring out a custom encoding.

Also from the guide I grabbed a few tools and started a list of CAT tools.
----
General Japanese capable text editors

Although given an input method editor and an appropriate configured operating system just about anything will do there are certain features that are useful to have in a text editor when you are editing Japanese. To this end a link to a couple of them

NJStar
NJStar
This is the most commonly used text editor for the Japanese language and has found favour among the translation teams working on ROM hacking. It is largely shareware/trial although paid options do exist.

JWPCE
JWPCE
An older freeware program that in many ways sits alongside NJStar above.

Rom hacking tools

A hex editor capable of reading tables is quite useful but there are a couple of other tools that are useful

Get My Hex
Filetrip download
Author homepage

Does what it is named for and will return the hexadecimal equivalent of the input text for several common encoding methods.

CAT tools

Although this is not a language document there are things you can do as a ROM hacker to help projects along and one of those is Computer assisted translation (CAT). This is not the same as machine translation but a kind of lookup program and database for previous translations and helps to ensure consistency in terms and other such things; for instance if you are translating a massive RPG and you meet a concept three times in a game but translate it three different ways it is not going to look good.

Free and Open source tools

Although the professional field is dominated by a handful of pricey tools there are some freeware/open source tools

Anaphraseus
Project sourceforge page

OmegaT
Project sourceforge page
A java based tool and one of the more popular open source programs.

XLIFF Translator
Project homepage
XLIFF is about as close as to an inter software conversion standard as it gets in CAT tool world. The program itself is an MIT licensed hook for a piece of professional software but functions none the less.

Commercial tools

On the paid/commercial front there are other options. Being “industrial”/professional/industry specific software though the prices have a habit of getting rather high and there is a fairly well recognised/supported format known as XLIFF (an XML based format aimed specifically at translation) many of the open source tools support as well as some of the commercial ones.
Still

Trados
Homepage
Arguably the market leader in the professional CAT tools.

memoQ
Homepage
Not as popular as the other two and similarly priced but rapidly gaining a following.

Wordfast
Homepage
Various tools have been released under this branding and depending where you go the term wordfast can refer to any or all of them. Still a very popular series of CAT tools and related technologies.[/url]