Need to add a new charset to allow accents for french and german version

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I put the Final Fantasy in french (my language)
2. I run Kparser
3. Only chat window of Kparser works, nothing on others windows

What is the expected output? What do you see instead?
Actualy, only english version is supported by Kparser, all languages with
accents like éàèïîöôç... don't work. So on french version and german
version of final fantasy, Kparser can't work

What version of the product are you using? On what operating system?
Last version of Kpaser.

Please provide any additional information below.
There is no bug here, just need to add an other format to allow french
users and german users to use Kparser

Original issue reported on code.google.com by gael.mon...@gmail.com on 1 Dec 2008 at 9:23

[GoogleCodeExporter]

It's more than just the character set that's needed.  Full 
translation/localization
of all messages received in the game would be needed to allow parsing French or
German (or Japanese for that matter) versions of FFXI.  At this time I don't 
have
anyone to assist me on that.

Original comment by Kinemati...@gmail.com on 2 Dec 2008 at 4:08

• Changed state: Accepted
• Added labels: Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

Is it hard ? If you have a list of all term used in Kparser, i can give you all 
of
them in french :p

Original comment by gael.mon...@gmail.com on 2 Dec 2008 at 7:04

[GoogleCodeExporter]

The following page shows the code file that contains the vast majority of what 
would
need to be translated:

http://code.google.com/p/kparser/source/browse/tags/Release%201.1.6.2/ParserCore
/Messages/Parsing/ParseExpressions.cs

Don't worry about working on the name/target/repeatname/npcname entries, as 
those
don't change between versions (and were a headache to develop, so wouldn't want 
to
force someone else to figure them out).  Though the "the" prefix for mob names 
is
probably la/le/les in French, so they'd still need slight tweaking.

Further work would be needed to translate the interface and parsing output 
text, but
that could be treated as a separate issue.


Anyway, if you're willing to translate that, put it in a text file and attach 
it to
this bug and I'll start working on the localization refactoring.

Original comment by Kinemati...@gmail.com on 2 Dec 2008 at 3:43

[GoogleCodeExporter]

ok i'll start tomorrow and i will send you the file as soon i'm done ^^
For the prefix "the", i guess SE always put the same thing and he don't adapt. 
Before
send you the file, i'll try to see every term IG to be sure that it is the same 
thing
that i wrote.

I'm ok to translate the interface and all others things but i guess it is 
better to
wait to complete this part before to start an other one =)

Original comment by gael.mon...@gmail.com on 2 Dec 2008 at 5:49

[GoogleCodeExporter]

Closing this bug in favor of the more specific issues 69 and 70.

Original comment by Kinemati...@gmail.com on 25 Jul 2010 at 10:45

• Changed state: Duplicate