This is the readme file from winjdic.zip. As you will notice, it refers to "KIHON", which is the name of the commercial version. Released with kihon/winjdic is a tiny version of the edict electronic dictionary file. To use the full version, you will need to get the latest version of edict, and the matching edict.jdx file, from the master ftp site (ftp.cc.monash.edu.au:pub/nihongo) or one of its mirror sites. Two sets of user comment are added at the end. Jim Breen ================================================================== Kihon - a Japanese Dictionary for Windows by KiCompWare Oct 1994 1. Introduction Kihon is a Japanese dictionary reader program for MS-Windows 3.1 or higher. You must have Jim Breen's JDIC and Kanji Info disks to make use of this program 2. Installation The Kihon archive must be unarchived to use. 1. Select Run from the Program Manager, or File Manager 2. Type: b:setup where b: is the floppy disk drive or hard disk drive where the installation files are located. The program will install to the directory you specify and make a new Program Manager group file with the Kihon Icon in it. 3. Configuration There are two path parameters that may need attention: Dictionary Path Font Path After you start Kihon, select the Path Setup dialog box. Enter the path to your dictionary, and/or where you would like to get the JIS fonts from. 4. Files readme kihon.exe kihon.hlp kijis16.fnt radical.ind 5. Questions, Comments, Bug Reports, etc. KiCompWare P.O. Box 240418 Apple Valley, MN 55124 USA Phone: 612- compuserve: 101015,206 Internet: edwards@winternet.com [The following application note has been provided by Don Peters (dpeters@HK.Super.NET)] 1. The Radical.IND file included in the WinJDic8.LZH file is old, and should be replaced by the Radicals.TM file in JDic. This is done by copying Radicals.TM to Radical.IND in the directory where WinJDic is located. Also, when copying the Radicals.TM to Radical.IND it is necessary to edit out all brackets. WinJDic does not like the brackets and will not call the character lists for bracketed numbers. 2. I am running WinJDic under 1024x768 screen resolution, and there are a couple of problems with the Kanji Radical and Stroke Lookups. The most troublesome of which is the fact that the display window is only 14 Character Buttons Wide whilst the material to be dispalyed is 16 Character buttons wide. Therefore I cannot see the last two character buttons on every line. I overcame this for the Radical Lookup Window by editing Radical.IND in WRITE (using No Conversion) and inserting two lines of "[space][space][space]0" after every 14 lines of real radical information. I have yet to workout how to solve the problem in the Stroke Lookup Window. Any sugggestions would be gratefully received. The following note is from Fred Kochman: I have a suggested clarification for the installation notes in the winjdic8.rme file at the Monash Nihongo site. (I would write to Mike Edwards, but a Google search suggests that the email address included is not current.) I found, after considerable trial and error, that not only should the included skeleton edict and edict index files be replaced with complete ones (as you cate), but also the kinfo.dat file, from the kinfo26.zip archive, must be included in the same directory in which WinJDIC is instructed to find EDICT and its index. In fact, I'm not certain that some other file might not also be necessary -- I grabbed so many files out of JWPce, etc., that I no longer remember exactly what I did! But I could not get the kanji-stroke-lookup to function --nor the kanji information facility in the radical-lookup table-- until I dumped the entire kinfo26.zip archive alongside the EDICT files. So a sentence or two about this in the .rme file would surely help persons like myself. The WinJDIC help file, unfortunately, merely suggests that the above sophisticated user eventually notes that the "dictionary information dialogue" reached from the lookup menu makes mention of KINFO but does not say where it might be found, nor with what file extension, nor where it must be placed if despite this it does get found. (This all takes place, incidentally, on a Windows XP PC -- so WinJDIC is forward compatible.)