Localize/Translate Interface (Japanese)

[GoogleCodeExporter]

Note issues/corrections to the Japanese UI text in this issue page.

Original issue reported on code.google.com by [email protected] on 1 Sep 2009 at 4:00

[GoogleCodeExporter]

Hi I'm Japanese.

I have tried k-parser and the interface is fully wrong Japanese.
I would like to change it. Could you advice me how to do it?
and, all the other function than Chat are not working in Japanese FFXI.
Any chance to help you on fixing it?

Let me know.

Original comment by [email protected] on 27 Oct 2009 at 11:50

[GoogleCodeExporter]

Hi, thanks for your interest.

I'm not surprised that there's plenty wrong with the translations.  There was a 
lot
of guesswork involved.

There are two aspects to be dealt with.  This bug deals only with the user 
interface
portion (menus, tabs, etc; not actual parsing of the game).  If you want to 
help with
translating the parsing code, so that the parser works properly with the 
Japanese
version of FFXI, that will take a bit more work in a separate section of the 
code.

For the user interface, the resource files need to be translated.  There's a 
set of
resource files for each project under their Resources directory (you can browse 
the
source right here on google code):

FFXILogParser/Resources
ParserCore/Resources
ParserMelee/Resources
ParserNonCombat/Resources
ParserUnparsed/Resources

In addition, each dialog window has its own set of resources (eg: 
ParserWindow.cs has
resource files of ParserWindow.resx, ParserWindow.ja.resx, etc).

ParserCore has 3 sets of resource files, the rest of 1 set each.  A file like
PublicResources.resx is the default English text for each field.  To be 
translated,
that field needs to have its value in the other language files (for Japanese,
PublicResources.ja.resx) defined.  That's easiest to do inside Visual Studio, 
though
it's also possible with a text editor or word processor that can handle UTF text
(you'll want to only work on fields that are marked as .Text).

You can either edit the files themselves and upload them here, or simply 
provide all
the translations in a document and I can edit the files on my end.


I'd greatly appreciate any help you can provide in this area.  

Original comment by [email protected] on 28 Oct 2009 at 4:00

[GoogleCodeExporter]

Hi

I will first translate the whole thing.
Then I need your help to fix the parsing
It only shows the chat log.

Let me first download the source.

Original comment by [email protected] on 3 Nov 2009 at 12:57

[GoogleCodeExporter]

Hi I have downloaded and changed some of the text, but I cannot compile.
Which version of Studio you use?

Original comment by [email protected] on 4 Dec 2009 at 1:42

[GoogleCodeExporter]

I currently use Visual Studio 2008 Professional.

Original comment by [email protected] on 6 Dec 2009 at 6:28

[GoogleCodeExporter]

I'll be going on vacation in a few days, so I won't be able to answer questions 
for a
while after that.

Are you still having trouble getting the program to compile?  Are you able to 
compile
the version directly pulled from the SVN repository?  What sorts of errors are 
you
seeing?

If it's not compiling at all, what process are you going through to get the 
code and
attempt to compile?  Note that you don't have to compile anything to do the
translations, just be able to open the project up in Visual Studio and edit 
some files.

Original comment by [email protected] on 17 Dec 2009 at 4:39

[GoogleCodeExporter]

If you're still following this issue, I've updated the code to the point where
translation of the actual parsing mechanism is possible now.  In other words, it
should be possible to parse the Japanse or French or German FFXI client, at 
least
once the translated strings are determined.  I'd appreciate any help in getting 
that
info localized.

Original comment by [email protected] on 13 Jan 2010 at 9:50

[GoogleCodeExporter]

So I'm hoping there has been a fix for this but perhaps not yet? I use the JP 
client and would like to use KParser.

Original comment by [email protected] on 16 Jan 2014 at 8:30

[GoogleCodeExporter]

I am more than willing to translate text if you can point me to the right 
direction. 

Original comment by [email protected] on 16 Jan 2014 at 8:39