C:\nihongo>x64\release\Nihongo.exe test.txt output.txt 0 9999
Loading dictionary.
ERROR: Unable to open dictionary file 'Dictionary.dat' for reading.
Building dictionary file from EDICT.
170107 dictionary entries.
Loading additional words.
Dumping dictionary to text file.
Building word/phrase index.
7084827 index entries.
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I just wanted to update it. ^^' (I already tried and fetched the latest version of the .zip and tried with it, but I get the same error.)
Any idea ? A workaround maybe ?
It's dying for you, but not for me. And I don't have it equipped like I would do for my day-job programs to give me detailed information about the failure...
BTW, the latest update was yesterday.
Could you pass me your "test.txt" file, to see if it does the same thing to me?
C:\nihongo>x64\release\nihongo test.txt output.txt 0 9999 /regen
Building dictionary file from EDICT.
170107 dictionary entries.
Loading additional words.
Dumping dictionary to text file.
Building word/phrase index.
7084827 index entries.
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I always overwrite my AddedWord with the one in the zip, since it seems you're changing it quite often
Only in very small increments, since I also submit most new words to WWWJDICT directly. The only thing there being that it takes a few weeks before the new words appear in EDICT.
Anyway, taking a quick look at the code, I see that I didn't put any exception recovery into it at all, let alone exception capture. It may take a while for me to cook up something to see what the problem is on your system. In the last ten years Microsoft has made a lot of progress in that area, but having written my own exception capture stuff long ago, I haven't bothered to learn their way yet. And in this case, it would be a good idea to do it their way: my stuff is complicated, and I never ported it to X64.
That was easier than I expected. Please download a new copy of the project, and try your test again. This time, it should generate a minidump, in a file called "Nihongo.dmp". I need that file to get more details as to your problem.
C:\nihongo>x64\release\Nihongo.exe test.txt output.txt 0 9999
Loading dictionary.
ERROR: Unable to open dictionary file 'Dictionary.dat' for reading.
Building dictionary file from EDICT.
170107 dictionary entries.
Loading additional words.
Dumping dictionary to text file.
Building word/phrase index.
7084827 index entries.
Minidump created.
OK. Let's try that again. I made the appropriate changes to generate the minidump, but I didn't build the "Release" version of the program with debugging information, so when I went to check it out it showed me nothing.
I have just uploaded an update. The changes are the following:
(1) The interactive parser now has a checkbox to alternate between my parser and the JUMAN one. The JUMAN parser is better for some things, and mine better for others. Mileage may vary.
(2) The kana to Latin conversion tables have been updated for more multi-kana conversions: pyaa, pyuu, pyoo, etc.