It wasn't machine translTion.
War gave me script and instantly I knew it was translated via machine because the letters were all wrong. FAILED.
And we have to edit text not font.
Unlike English, japanese is written in katakana, kanji and hiragana.
The font will have each individual letter of all 3. So if a is hiragana and b is kanji, Japanese would write xyz in English as a and b combining the two govng ab which is equal to xyz.
However in English a is the letter g and b is h so we would get gh instead of ab which wouldn't be xyz.
Thats also how translators work. AND FAIL.
Well done on the progress. Time to work on mah project
Look, I have been programming and ROMhacking for more than you, and I know what I am talking about.
Here- check out some of my sites
www.pbtrans.wordpress.com
www.ystrans.wordpress.com
First of all, the script War gave you was legit. A google translate/etc will NEVER accurately translate ANYTHING. You'll need a legit Japanese speaker and ask them to translate.
QUOTE said:
Unlike English, japanese is written in katakana, kanji and hiragana.
The font will have each individual letter of all 3. So if a is hiragana and b is kanji, Japanese would write xyz in English as a and b combining the two govng ab which is equal to xyz.
Everybody knows that Japanese is written in kanji, kata+hira.
An NFTR font is set up so EVERYTHING that is required is defined. BPP, bitmap character, width, size, and more. ab doesn't equal xyz.
In an NFTR font file, because the structure has already been analyzed, it is pretty easy to add your own characters.
Because this type of font file is a defined font in nitroSDK, any NFTR fonts are interchangeable. This is the reason why I said if you have encountered this font file, you will have an easy time to edit anything you wish.
Posts merged
QUOTE(Noitora @ May 30 2009, 08:20 PM)
I will show something better after I return from the beach
"