So in order to read a "translation" the reader must identify Japanese sentence structures and kanji? Not that I have that problem but sounds to me like it's defeating its purpose.
So in order to read a "translation" the reader must identify Japanese sentence structures and kanji? Not that I have that problem but sounds to me like it's defeating its purpose.
That's what I thought. I can't tell which Japanese phrases in the translation match which English phrases in the original.
Is "navel" indicating a misspelled word on Iowa's behalf?
Don't think so, I took the liberty to correct it.
For the others, I can always put on comments the full english translation (thankfully I know katakana much better so I understood) if you guys want, I won't modify the notes to respect of the translator's choice.
So in order to read a "translation" the reader must identify Japanese sentence structures and kanji? Not that I have that problem but sounds to me like it's defeating its purpose.
You could play with the Ruby 'furigana' tags and maybe put the english on top of the japanese.
ReadActually, I already have a prior engagement.Prior engagement?Yes, I'm aware of that.ハーイ! ウォースパイト!That's right~!
You know a lot about it.あっ、ごめんね、アイオワ。Since it's a good opportunity, why don't you come with me and Sara to 三越?Looks like our naval base is having a コラボレーション at Japan's 三越, y'know?三越 is like a representative for 日本の百貨店, isn't it?Hyakka-ten (百貨店): shopping mall