JWPce Support Information

This page was created specifically to support JWPce. JWPce is a free Japanese Word Processor that I wrote. JWPce is distributed under the GNU General Public License, which means that within certain restrictions you are free to obtain, use and pass on the program. Since I wrote the program and this is my web page, this is as close to an official support site that you are going to find.

Contents

The GNU General Public License
What does this all mean?

A description of the GNU General Public License is shown below, taken directly from the license document. Your distribution kit should contain a copy of GNU General Public License in the file: GNUGPL.TXT (straight text).

GNU GENERAL PUBLIC LICENSE

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

All this basically means that you are free to get a copy of the program if you want, including the full source code.

Whenever a specific copyright notice conflicts with the GNU General Public License, the specific copyright provision(s) will take precedence over the GNU General Public License.

Disclaimers
The legal stuff, or you get what you pay for.

Because this program is free software, it is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This means that if you lose millions of dollars because you used the program, tough. So there!

If you encounter any bugs, have suggestions, want to make a comment, you should e-mail the information to me and I will attempt to fix them.

Acknowledgements
Thanks, to those who have had a hand in this project.

 The creation of JWPce is directly or indirectly the result of contributions from several people. I would like to take the time to thank them for their efforts, because without them, JWPce would never have been created!

What is JWPce and what can it do for me?
Please read this to get an idea of what is going on!

I enjoy learning Japanese. Over a year ago I discovered a free-ware Japanese word processor called JWP, which I found immensely useful in learning Japanese. It included a wonderful online dictionary, a kanji lookup by radical and a number other really useful features. This program is inspired by JWP, however, JWPce is a rewrite of the code starting from scratch. During the creation of JWPce I added a number of features designed to assist me in learning Japanese, you may find these same features to be useful. Additionally, JWPce contains a number of features to make it easier for me to read native Japanese text (in electron or print media), you may also find these features to be useful.

Historical Development

I wanted to be able to read Japanese text when traveling. However, for me to read a native Japanese text requires that I have access to both a Japanese dictionary and a kanji dictionary. Carrying these around is a nuisance and tends to prohibit casual reading. By using JWP's online dictionary and kanji lookup facilities, I could read a Japanese text much easier than by using a paper dictionary, but I still would have to carry a portable computer (and on top of that my portable only lasts for about one hour on battery power).

In 1997 I became aware of Windows CE machines. These are small computers (usually under a pound in weight) that run the Windows CE operating system (which is mostly like Windows 95/98/NT). I thought that if JWP could be ported (a computer term for moving a program to another system) to such a machine, I would be able to read Japanese text using the small machine (imagine a Japanese (English dictionary and kanji dictionary under a pound), and have my e-mail connection at the same time. Unfortunately, however, early Windows CE machines did not have sufficient memory to run JWP and thus the project stalled. In early 1998 Windows CE 2.0 machines were scheduled to be released. Two of these new models were available with 24MB and 32MBmemory, which is more than sufficient to run JWP, and the project was on again.

I had first intended simply to port JWP to Windows CE. However, examination of the code revealed that this was not a practical proposition. Instead, I decided to rewrite the code, and this is the result of that effort. It is important to keep in mind that JWPce was originally intended to run on Windows CE machines, which have limited screen and memory resources. As a result, several features of the original JWP were adapted to use less memory and work on smaller displays.

How Things Actually Turned Out

As things turned out, the scope of the JWPce project has increased. When I wrote JWPce I left out many features in JWP that I did not use, in order to reduce the code size. In addition, many features that I would have liked to have in JWP but that were not there were added to JWPce. The end result is that JWPce is a different program from JWP and has a different feature set. The answer to which one you should use is whichever you like better, or use them both. Personally I use JWPce, but then, since I wrote it, it works the way I want it to. (Actually, at this point I would suggest that anyone still using JWP switch to using JWPce. This is primarily because JWPce supports many more features that JWP and is much more stable on 32-bit operating systems.)

JWPce Online Manual
Everything you could possibly want to know

 The JWPce manual can now be accessed online. You can review features, and checkup on how to use the features.

HTML
Acrobat PDF

JWPce Features
A Brief List of Special Features

JWPce has many special features. The main ones are:
  • Online Dictionary: JWPce uses Jim Breen's Japanese-English dictionary. This dictionary allows the user to translate both to and from Japanese, using either kanji or kana. JWPce's dictionary features are highly expanded, the program allows searching of Jim Breen's EDICT (general word dictionary), and ENAMDIC (a name dictionary containing over 168k Japanese names), as well as a number of other Japanese(English dictionaries. Additionally, a user dictionary is supported for words that you cannot find in the online dictionaries.
  • Radical Lookup: JWPce has the ability to lookup kanji by stroke number, and by identifying any number of radicals contained within the kanji. Thus if you can identify two or more radicals within the kanji, you can search for all kanji containing all of those radicals.
  • Many Different Kanji Lookup Systems: JWPce contains no less than nine kanji lookup systems.
  • Kanji Information: JWPce has the ability to provide a large amount of information on any kanji character, including meanings, on-yomi, kun-yomi, etc.
  • Auto-detect Clipboard: When importing from the clipboard JWPce can automatically detect the clipboard format. This makes reading Japanese web pages much easier.
  • Unicode Support: JWPce supports Unicode both in files and on the clipboard. As Unicode applications become more dominant, this feature will become even more useful. (Current Unicode applications include Internet Explorer 4.x/5.x, Word, Netscape 4.x, and all native Windows CE applications.)
  • Color Kanji: JWPce can display kanji in a list you generate in a different color. This allows you to color either the kanji that you don't know or the kanji that you do know.
  • Advanced Search: JWPce has expanded search capabilities that allow searching over multiple files.
  • Kanji Counting: JWPce can identify the most common kanji in a file. This list is useful for students who want to identity common kanji to learn.
  • Regular Actions: JWPce has a very regular approach to user interactions. This allows you to call up the kanji information box from any location, or call up the radical lookup dialog box from any edit box.
  • Multiple Selections: JWPce allows multiple selection to be used in almost every location. This includes the Open File... dialog box, the dictionary dialog box, the Character Information dialog box, etc. Selection of multiple items is supported wherever it makes sense.
  • Highly Configurable: Although JWPce is not configurable in all the ways JWP was, in many ways it is more configurable. Look through the Utilities/Options... dialog box for the major options. (Note that dictionary search options cannot be set there, use the Utilities/Dictionary... dialog box to set these).
  • User Conveniences: JWPce has many user conveniences built into the interface, including remembering where your window is located, reloading files you were previously working on, etc.
  • Network Configuration: JWPce can be installed on a network where, each user is assigned a location to store his or her personal configuration.

Relationship between JWP and JWPce
Similar but different programs

JWPce was inspired by the original JWP program. There is still a lot of compatibility between the programs, but I consider the JWP program to be obsolete at this point and would only use it if I was working on a Windows 3.x system.

There was originally material on getting JWP and JWPce to cooperate, but at this point the only files shared between the programs are the font files. If you want this older material it has been moved.

Installation Requirements
What do I need to get it running?

 JWPce requires a PC computer system running Windows 95/98/ME/NT/2000/XP. Windows 3.x is not supported (I suggest that you consider upgrading). The amount of memory required by the program depends primarily on the fonts and dictionaries installed. With minimum font and dictionary installation, JWPce requires less than 8MB of disk space. A full install using all of the standard bitmapped fonts, dictionaries, and the manuals, requires approximately 19MB of disk space. If you install TrueType fonts, the space requirements depend on the fonts you install (TrueType fonts are not distributed with JWPce, unless someone wants to donate a public-domain Japanese TrueType font). Similarly, if you install a number of supplemental dictionaries, the space requirements will depend on exactly which supplemental dictionaries you install.

Installation Instructions
How to I get it working?

Installation of JWPce is very simple:
  1. Obtain the distribution .zip files: One way or another obtain the distribution .zip files. Depending on where you obtained your distribution copy you may have different numbers of zip files. Some of the JWPce distribution files are also available as a self-extracting executable (.exe file).
  2. Generate a directory: Make a directory that will be your installation directory. If you are installing over a previous version of JWPce or JWP you can simply use your existing directory.
  3. Decompress the .zip files: Decompress the .zip files into your installation directory. If you are using the self-extracting archives (.exe files), you can decompress the file by double clicking on it! If you are installing over an older version of JWPce or over JWP you can safely overwrite any files. At this point you can delete the .zip files, as they are no longer necessary. NOTE: Currently it is a requirement that essentially all the JWPce support files are located in the same directory as the executable (jwpce.exe).
  4. Run the Program: Run the executable program "jwpce.exe". This will automatically complete the installation, and prompt you for any information needed. Since Explorer does not normally show the file extensions, you should look for a file named "jwpce", with the kanji KAN from KANJI as an icon.

What if I already have JWP?

If you already have JWP, you can install JWPce in the same directory. For the most part they use the same files, so you will not have to duplicate files. Where they don't use the same files, the files have different names, so they will not interfere with each other.

Tip: My recommendation would be to upgrade completely to JWPce. At this point JWPce has many more features than JWP had, is smaller, faster, and more stable on 32-bit operating systems.

The only real problem is in whether or not to allow JWPce to take over the associations for the file extensions. These associations determine what program will be started when you double click on a file of the type (.jwp, .jis, .euc, etc.). Unfortunately, both programs use the same file extensions, so you will have to decide which one should handle the associations.

JWPce uses newer versions of EDICT and ENAMDICT (which was part of EDICT in JWP 1.31). The newer files can be used by JWP; and JWPce can use the older dictionary files, but doing so will disable some of its features. In particular, if you use the wrong dictionary version with one of the programs, that program will not be able to block name entries. The best choice is to use the newer dictionaries, then you can either add or not add ENAMDICT to JWP's dictionary list to get the best searching options.

If you have been using JWP, a few things will not be converted to JWPce. These include the following:

  • Options: JWPce options are somewhat different than those of JWP, and the method of storing the option settings is completely different. Thus, JWPce will not even attempt to read your JWP settings.
  • User Conversion Cache: When you convert kana to kanji, JWP and JWPce attempt to remember the choices you made for the kanji conversions. Although both programs store the choices in a conversion cache, they store the cache in very different ways. JWP uses a straightforward storage method, while JWPce uses a selective storage algorithm that allows it to effectively store a larger number of conversions in a smaller file. Since it is relatively painless to reselect your favorite kana-to-kanji conversions, JWPce does not attempt to read the JWP conversions file.
  • User kana-to-kanji conversions: JWP and JWPce allow you to specify custom kana-to-kanji conversions (since the Wnn dictionary cannot possibly contain all the conversions you might want). JWPce stores conversions in exactly the same format as the Wnn dictionary does, which allows me to use the same search engine for both the Wnn dictionary and the user conversion dictionary. JWP uses a slightly different format for its conversion file. This difference will require one to re-enter custom kana-to-kanji conversions. If this presents too much of a problem contact me and I will attempt to provide a utility program that will perform the conversion for you.
  • Glossary: JWPce does not implement the glossary feature of JWP. I did not use this feature because a number of bugs in it tended to crash the program. A similar feature can be generated by defining a custom kana-to-kanji conversion based on your mnemonic. You can then treat your string as a kana-to-kanji conversion.

Updating JWPce
What to do when things change (hopefully improve).

If you are installing an updated version of JWPce, you can either get an updated package or install a complete version of JWPce over your existing version.

Update packages are smaller and faster to download and install. If you get an update package, please check the instructions, since the update versions now require that you have at lease a certain version of JWPce to update from. This was done to keep the size of the update versions small.

Reinstalling JWPce over your existing version has some advantages too. In particular you will get the newest copy of the main dictionaries. These are not included in the update packages, because this would defeat the purpose of the updates.

Because there have been internal changes in the versions of JWPce I am now distributing a small program called UPDATE.EXE with each version of JWPce. This program will check your version of JWPce and update any necessary files to the current version. You run this program by simply double clicking on it. After you have run UPDATE.EXE you can simply delete the program, as it will no longer be necessary. You can run UPDATE.EXE as often as you like, it will not hurt any of the files.

Windows CE Updates

I have not generated a version of UPDATE.EXE for each of the Windows CE versions. I believe that most people who are using the CE versions also have a version on their desktop. You can simply copy the updated files from your desktop to your CE machine. Also the next section contains a list of things that have changed from version to version so you can see what UPDATE.EXE would be doing.

Update History

This section contains a history of major file changes in the various versions of JWPce. If you are updating from an older version of JWPce you can see what files have been modified.

Version 1.33:

Due to changes in the kana->kanji conversion system, the files WNN.DCT and WNN.IDX have been replaced with the files WNN.DAT and WNN.DIX. Additionally, the format of the user kana->knaji conversion file (USER.CNV) has changed to match the format used by WNN.DAT. UPDATE.EXE will update the format USER.CNV, as well as offer to delete the obsolete files.

Version 1.42:

Due to changes in the configuration file project files saved from earlier versions are not compatible with version 1.42.

Network Installation
How to get this working on a network.

WARNING! This section deals with technical issues related to setting up JWPce to be run over a shared network, or for a single user to run multiple configurations. If this does not fit your configuration or you are uncomfortable with such issues, simply skip this section.

JWPce was originally designed as a single user program. The program originally stored all information about the user configuration in the same directory as the executable. This is efficient, but makes the program difficult to use in a network configuration, where many different users may be using the program at the same time. In such a case multiple users would end up saving their configurations on top of each other and no one would be happy. Since JWPce is being used in academic situations over networks (something I never envisioned when I started the project), support for network configurations has become more important.

WARNING! Network configurations are not supported on Windows CE versions.

JWPce allows a command line argument to specify the directory for user configuration files. Normally JWPce will attempt to read all files from the user's directory, but if a configuration file is missing, it will read the file from the default directory (where the program is located). This allows the default configuration to be used to initialize all configurations. When writing, JWPce will always attempt to write user configuration information into the user directory, and will never write back into the default directory.

The command line argument to specify the user directory location is: 

        (+|-)user_directory

If the plus (+) option is used all error checking will remain active. This should be the normal configuration. If the minus (-) option is used errors will not be reported when writing user configuration files. Note: Using the minus option does not have any effect on user data files, where all error reporting remains active!

Generally the minus option should not be used, but it has some advantages in special situations. For example, if you do not want users to save their configuration files then you could use this option and provide an invalid directory for the user_directory. This will prevent the user form saving configurations and prevent generation of error messages. Another special situation might be if the users save their configurations on a floppy disk, but you want the program to run quietly when no disk is in the machine. In such a case you could use the configuration option: 

        -a:\

All JWPce features will work even when the user cannot save configuration information, however, any changes the user makes to the configuration will not be preserved from session to session.

Files Affected

Following is a list of the files that JWPce considers to be user configuration files. These are simply files that may change as the user works with JWPce but that are not actual data files:

    colkanji.lst Kanji list used by the color-kanji feature.
    jwpce.cfg JWPce configuration file, this will be generated when you run JWPce.
    jwpce.dic JWPce dictionary configuration file. This file contains information about supplemental dictionaries you have installed.
    jwpce_lang.dll Language interface (localization) file.
    user.cnv User kana->kanji conversions.
    user.dct User dictionary.
    user.sel Holds user selections for kana->kanji conversions.

Setup Procedure

The following section describes the things you need to think about and steps you need to take when installing JWPce on a network.

  1. Install JWPce: Install JWPce as normal on the server system.
  2. Set Default Configuration: Set up a default JWPce configuration on the server. At a minimum simply run JWPce, which will generate a jwpce.cfg file that will become the base configuration for the users. If this is not done, every new user (or users who forgot their disk) will get the message about being unable to load the configuration file, using default values.
  3. Install Supplemental Dictionaries: If you are going to install any of the supplemental dictionaries, you should do this now. This will set up a base dictionary search that the users can use.
  4. Do not generate a user dictionary: Generally you may NOT want to provide a common user dictionary. This is because if the user adds something to this dictionary, the entire dictionary will get copied into the user configuration directory. Additionally, once the user generates his or her own user dictionary, they will not be able to use any changes to the central dictionary that you may make (assuming this is an educational situation).
  5. If you want to provide a central dictionary: If you want to provide a central dictionary that all users can access, and that dictionary was generated as a user dictionary, you can simply rename the user.dct file to any other name and add it to the supplemental dictionaries list using the Searched Dictionaries dialog box. (Remember that the user dictionary is not indexed.)
  6. Setup User Executable: You will then need to modify the user executable command line to run JWPce with the correct command line arguments for your network. You may actually need to set up a script file of some kind to fetch the location of the user's directory and pass that information to JWPce. For a very simple setup, where the user is expected to store the configuration files on a floppy disk, you can modify the typical executable line from 
            JWPce.exe
    to 
            JWPce.exe +a:\

Windows CE Versions of JWPce
What is different? What do I do? How do I do it?
WARNING! This section deals with running the Windows CE version of JWPce. If this does not fit your situation, or you just don't care about Windows CE simply skip this section.

JWPce can run on Windows CE platforms. This section deals with specific issues related to running JWPce in such an environment. If you are using a PPC (Palm PC, then you may also want to look at the following section on PPC's.

Implementation Decisions

Generally Windows CE versions of JWPce are almost identical to the Windows 95/98/ME/NT/2000/XP version. However, a number of decisions were made when implementing JWPce on Windows CE platforms:

Requirements

Windows CE versions of JWPce are designed to operate on HPCs (Handheld Personal Computers) and PPCs (Palm Personal Computers) running the Windows CE operating system. The program has been developed and tested under Window CE version 2.0. I have not specifically excluded Windows CE versions earlier than 2.0, but I have not tested the program under any of these versions, and would expect that it will NOT work correctly.

Versions 1.40B (and beyond) read system parameters that are not supported on some early versions of Windows CE. I have generated versions of the code the use fixed directory locations for compatibility with older systems. This is not a perfect fix, since the fixed locations vary depending on the CE implementation, but I am just supporting the western system configuration.

Every attempt has been made to keep dialog boxes small enough so that 480x240 displays will be acceptable. There are a few dialog boxes that will have to be shifted for people using the smaller display (most notably the Radical Lookup dialog box, which is clearly 640x240).

My Windows CE machines are a Jornada 729, an Everex Freestyle, and a Casio E-700J. I have extensively tested JWPce using these systems without any problems.

The complete installation of JWPce with dictionaries and lookup tables but no help files takes about 8.5 MB of storage (not counting the storage compression used by Windows CE). Various files can be deleted to save space, if that is necessary (see below). JWPce will run on a machine with 8 MB of RAM (less if some of the files are removed). Here are my personal recommendations for system configurations:

MemoryConfiguration
8MBInstall program in main memory and all dictionaries on flash card. Install only the required basic F16X16.F00 font.
16MBInstall JWPce in memory. If your main application is JWPce you can install EDICT in main memory. Otherwise, install EDICT on a flash card. By moving EDICT to flash card you can save enough space to install additional fonts.
32MBInstall JWPce, fonts, and EDICT in main memory. Install ENAMDICT and other dictionaries on flash card.
64+MBYou can easily install all of JWPce, fonts, and dictionary in main memory. If you later need the memory back, you can move some of the dictionary files to a flash card.

Installation Instructions

Currently there is no installer for JWPce under Windows CE. I will eventually generate one, but this is a low priority. Until then the following steps can be used to install JWPce on a Windows CE machine:

  1. Obtain the distribution .zip files: One way or another obtain the distribution .zip files - the number of files will depend on where you obtain them.
  2. Make a temporary directory: Create a temporary directory on your desktop machine (such as c:\temp-wince).
  3. Decompress the .zip files: Decompress the .zip files into your temporary directory. Generally it is better first to decompress any general files and then to decompress files that are specific to your processor. At this point you can delete the .zip files as they are no longer necessary.
  4. Make an installation directory: Create a program directory on your Windows CE machine, e.g. \Program Files\JWPce.
  5. Copy the files: Copy the desired files from the temporary directory on your desktop machine to the installation directory on your Windows CE machine. You can now delete the temporary directory (and its contents) on your desktop machine, as it is no longer necessary.
  6. Run the Program: Run the executable program "jwpce.exe". This program will automatically complete the installation, and prompt you for any information needed, just like the Windows 95/98/ME/NT/2000/XP version.

Installing Help

Normal Windows CE help is implemented using the Pocket Help program, and help information is stored in a reduced form of HTML format. Unfortunately using Pocket Help, requires that most of the help files reside in the Windows\System directory. One of the problems with HTML formatted files, is that all Japanese text must be stored as small images in separate files* (in total, there are around 130 files in the help system).

I do not like the idea of dumping 130 or so files into the Windows\System directory so JWPce implements it's help using Pocket Internet Explorer. This has a number of advantages: First, this allows the full range of HTML to be used in the help system**. Second, this allows me to place the help files in any location. There are also a few disadvantages: Pocket Internet Explorer opens files slower than Pocket Help. Overall, I believe this is the best solution.

The following steps can be used to install help on a Windows CE system:

  1. Obtain the distribution zip files: One way or another obtain the distribution .zip files - the number of files will depend on where you obtain them.
  2. Make a temporary directory: Create a temporary directory on your desktop machine (such as c:\temp-help).
  3. Decompress the .zip files: Decompress the .zip file(s) into your temporary directory. At this point you can delete the .zip files, as they are no longer necessary.
  4. Make an installation directory: Create a help directory on your Windows CE machine. The directory must be named help, and must be a sub-directory of wherever you installed JWPce. For example, if you installed JWPce in \Program Files\JWPce you must install help in the directory \Program Files\JWPce\help.
  5. Copy the files: Copy the desired files from the temporary directory on your desktop machine to the help directory on your Windows CE machine. You can now delete the temporary directory (and its contents) on your desktop machine, as it is no longer necessary.

Compatibility Issues

This section deals with compatibility issues between the Windows CE versions of JWPce and the Windows 95/98/ME/NT/2000/XP versions.

Generally all files used by JWPce are directly compatible between Windows CE and Windows 95/98/ME/NT/2000/XP versions. The following files, however, cannot be directly moved from one system to the other:

All other files can be freely moved between the systems without any translation.

* Because help must work on all system I cannot assume a Japanese display system is present.

** Excluding the HTML tags that are not correctly implemented in Pocket Internet Explorer.

PocketPC/PPC Windows CE Versions of JWPce
It's small, but what else is it?
WARNING! The next section deals with running a Windows CE version of JWPce on a PPC (palm personal computer). If this does not fit your situation, or you just don't care about Windows CE simply skip this section.
JWPce is able to run on PocketPC / PPC Windows CE platforms, however, do to some severe limitations Microsoft has placed on the PPC versions Windows CE, these versions have some special issues.

Implementation Decisions

 Generally Windows CE PPC versions of JWPce are almost identical to the Windows CE version, however, a number of decisions had to be made when implementing JWPce on Windows CE PPC platforms.

    Specific to PPC's:

    1. Since there is no file management system on the PPC's, a delete command has been added. In addition, backup files are not created by default, since they are difficult to delete.
    2. Open file dialog on the PPC's does not support multiple file types, so the default file type has been changed to JWPce native (.jce).
    3. True Type fonts are not supported on PPC's, thus JWPce will allow the use of bitmapped fonts.
    4. Remember that the open and close dialog boxes will only look for files located in subdirectores or the \My Documents directory. This limits were supplemental dictionaries and other things can be located.
    5. Due to screen space limitations, many labels had to be abbreviated.
    6. Due to screen limitations, some information was dropped from the Character Information dialog.
    7. Because determining which programs are running, and changing the active program is difficult JWPce will only allow one version of the program to run. If you attempt to start a second version, the current version will simply be brought to the foreground.
    8. I did not adhere to Microsoft's nonsense idea that PPC programs not allow the user to exit. JWPce has a close box and an exit item on the menu.

    General Windows CE:

    1. The BITMAP clipboard format is not supported.
    2. Clipboard formats TEXT and OEMTEXT are not supported (just UNICODETEXT). These formats are not supported by most other programs.
    3. Support for half-width katakana has been dropped. I have not yet encountered a file using this and it saves some code space.
    4. Multi-file selects are not supported. Windows CE does not support this feature.
    5. Printing is not supported in Windows CE. This may be added at some later date.
    6. Some items were removed from the Edit menu, because the menu was too long for Windows CE display. The removed items are Insert page break, and the mode settings.
    7. Network startup options are not supported in Windows CE. The user cannot edit the command line arguments that are passed to a program.
    8. Some visual changes because of types of buttons or controls supported by Windows CE.
    9. Currently TrueType Japanese fonts are not supported on Windows CE machines. The PPC machines do not have a TrueType engine, and HPC machines doe not support glyph addressing, which is used by JWPce. (At some future date, TrueType font support will be reexamined, especially for the HPC machines.)

Installation Requirements

 Windows CE version 2.0 and higher should work with the PPC versions of JWPce. I have not specifically excluded Windows CE versions earlier than 2.0, but I have not tested the program under any of these versions, and would expect that it will NOT work correctly.

Versions 1.40B (and beyond) read system parameters that are not supported on some early versions of Windows CE. I have generated versions of the code the use fixed directory locations for compatibility with older systems. This is not a perfect fix, since the fixed locations vary depending on the CE implementation, but I am just supporting the western system configuration.

The complete installation of JWPce with dictionaries, and lookup tables takes about 8.5 MB of storage (not counting the storage compression used by Windows CE). Various files can be deleted to save space if that is of significance (see below). JWPce will run on a machine with 8 MB of RAM (less if some of the files are removed).

MemoryConfiguration
8MBInstall program in main memory and all dictionaries on flash card. Install only the required basic F16X16.F00 font.
16MBInstall JWPce in memory. If your main application is JWPce you can install EDICT in main memory. Otherwise, install EDICT on a flash card. By moving EDICT to flash card you can save enough space to install additional fonts.
32MBInstall JWPce, fonts, and EDICT in main memory. Install ENAMDICT and other dictionaries on flash card.
64+MBYou can easily install all of JWPce, fonts, and dictionary in main memory. If you later need the memory back, you can move some of the dictionary files to a flash card.

Installation Instructions

Currently there is no installer for JWPce under Windows CE. I will eventually generate one, but this is a low priority. Until then, the following steps can be used to install JWPce on a Windows CE PPC machine. Due to the absence of any type of file manager on the PPC versions of Windows CE, you will have to attach JWPce to the Start Menu [HT1]by hand to run the program. Do not worry, the steps are very straightforward.

  1. Obtain the distribution .zip files: One way or another obtain the distribution .zip files - the number of files will depend on where you obtain them.
  2. Make a temporary directory: Create a temporary directory on your desktop machine (such as c:\temp-wince).
  3. Decompress the .zip files: Decompress the .zip files into your temporary directory. Generally it is better first to decompress any general files and then to decompress files that are specific to your processor. At this point you can delete the .zip files, as they are no longer necessary.
  4. Make an installation directory: Create a program directory on your Windows CE machine, e.g. \Program Files\JWPce.
  5. Copy the files: Copy the desired files from the temporary directory on your desktop machine to the installation directory on your Windows CE machine. You can now delete the temporary directory (and its contents) on your desktop machine, as it is no longer necessary.

The next steps depend on which version of the Windows CE you have!

If you have Windows CE 3.0 or a PocketPC system:

  1. Run the Program: On your PPC machine there should now be a link to JWPce in the programs menu. Activate this link. The program will automatically complete the installation, and prompt you for any necessary information, just like the Windows XP version.
  2. Done! You are done.

If you have an older Windows CE device (from before the PocketPC), you probably don’t have a file explorer, so you will need to link JWPce into the Start Menu before you can run the program.

  1. Select the Program: Now you will need to generate a link in the start menu so you can execute the program. Find the file JWPce.exe on the PPC device (since you just copied the files, I am assuming that you are exploring your PPC), and click on it once.
  2. Copy the Program: Select Copy from the Edit menu on Explorer.
  3. Change Directories: Change the Explorer directory to /Windows/Start Menu/Programs.
  4. Make the Shortcut: Choose Paste Shortcut from the Edit menu on Explorer. If you would like a shorter name in your start menu, you can edit the name from "shortcut to JWPce.exe" to "JWPce", or whatever you like
  5. Run the Program: On your PPC machine there should now be a link to JWPce in the programs menu. Activate this link. The program will automatically complete the installation, and prompt you for any necessary information, just like the Windows 95/98/ME/NT/2000/XP version.
  6. Done! You are done.

Installing Help

Normal Windows CE help is implemented using the Pocket Help program, and help information is stored in a reduced form of HTML format. Unfortunately using Pocket Help, requires that most of the help files reside in the Windows\System directory. One of the problems with HTML formatted files, is that all Japanese text must be stored as small images in separate files* (in total, there are around 130 files in the help system).

I do not like the idea of dumping 130 or so files into the Windows\System directory so JWPce implements it's help using Pocket Internet Explorer. This has a number of advantages: First, this allows the full range of HTML to be used in the help system**. Second, this allows me to place the help files in any location. There are also a few disadvantages: Pocket Internet Explorer opens files slower than Pocket Help. Overall, I believe this is the best solution.

The following steps can be used to install help on a Windows CE system:

  1. Obtain the distribution zip files: One way or another obtain the distribution .zip files - the number of files will depend on where you obtain them.
  2. Make a temporary directory: Create a temporary directory on your desktop machine (such as c:\temp-help).
  3. Decompress the .zip files: Decompress the .zip file(s) into your temporary directory. At this point you can delete the .zip files, as they are no longer necessary.
  4. Make an installation directory: Create a help directory on your Windows CE machine. The directory must be named help, and must be a sub-directory of wherever you installed JWPce. For example, if you installed JWPce in \Program Files\JWPce you must install help in the directory \Program Files\JWPce\help.
  5. Copy the files: Copy the desired files from the temporary directory on your desktop machine to the help directory on your Windows CE machine. You can now delete the temporary directory (and its contents) on your desktop machine, as it is no longer necessary.

Compatibility Issues

This section deals with compatibility issues between the Windows CE versions of JWPce and the Windows 95/98/ME/NT/2000/XP versions.

Generally all files used by JWPce are directly compatible between Windows CE and Windows 95/98/ME/NT/2000/XP versions. The following files, however, cannot be directly moved from one system to the other:

All other files can be freely moved between the systems without any translation.

* Because help must work on all system I cannot assume a Japanese display system is present.

** Excluding the HTML tags that are not correctly implemented in Pocket Internet Explorer.

International Support
Does it speak My Language?

The appearance of JWPce's interface can be changed by the use of a language or localization file (JWPCE_LANG.DLL). These files can replace virtually all the text strings used by the program, as well as menus and dialog boxes. This system was designed to allow creation of alternative interface modules in different languages.

If a language support file is available for a language you are interested in, you can simply copy the support file to the same location as JWPCE.EXE. During startup JWPce will detect the language file and switch interfaces. There is an internal check to make sure the language support file matches the version of JWPce you are using.

Currently JWPce supports only one interface language at a time. Further the language is set when JWPce starts. At a later date, support for switching interface languages on the fly may be implemented.

If you are interested in translating JWPce's interface to another language please contact me or obtain the translation kit (jwpcetra.zip). This kit contains instructions, notes and tools used to generate a translation file. (Please don't underestimate the amount of effort that this will take, JWPce contains around 300 message strings, 50 dialog boxes, a two menus containing nearly 100 items. Most of these will require translation. This is not even considering the manual, help, or adjustments necessary for Windows CE PPCs and HPCs.) Well if I haven't managed to scare you off and you are interested in helping with translations please continue.

Translating to Another Language
DANGER! Hard work ahead!

In order to localize JWPce for your language you will need to download the translation kit (jwpcetra.zip). In the translation kit you will find instructions for localizing JWPce for a particular language. The translation kit supports programmers and non-programmers as well as all platforms that JWPce runs under.

Double translations are a problem. If more than one person does a translation to the same language, I have no way to telling which is the better translation. This is a problem, and I don't want to get involved in arguments about languages that I don't know.

If you are intending to do a translation (for public distribution), please send me an email. Include the language you will be translating to and I will put your name on the web. This should reduce the number of double translations.

If double translations occur I will either select one or put both on the web, or let both parties figure out which is better.

Thanks for helping and all the hard work.

LanguageTranslatorPlatformVersionStatus
FrenchChristophe Verré95/98/ME/NT/2000/XP
CE - HPC
CE - PPC		1.34
1.34
1.34		Posted
Ready
Ready
GermanGernot Hildebrandt 95/98/ME/NT/2000/XP1.34Posted
HungarianBalassy Mihály 95/98/ME/NT/2000/XP1.34Posted
ItalianCarlo Gherarducci95/98/ME/NT/2000/XP1.34Posted
Portuguese (Brazilian) Wladimir Mendes de Carvalho 95/98/ME/NT/2000/XP1.34Posted
Russian Slava Kravchenko 95/98/ME/NT/2000/XP1.34Posted
Spanish (???) Dagoberto Salas ???1.34In Progress
Spanish (???) Gerardo Campos 95/98/ME/NT/2000/XP1.34Posted
Spanish (Spain) Antonio Regidor García 95/98/ME/NT/2000/XP1.34Posted

Future Plans for JWPce
What is coming and when to expect it?

What follows is a list of features to be added to JWPce. This list gives the direction I expect things to go, but there could be any number of detours along the way.

  • Short Term:
    • Extended kana->kanji conversions.
    • User configurable keyboard.
  • Long Term:
    • Vocabulary Utility.
    • Font characteristics (bold, italic, underline, boxed).
  • Wish List:
    • Furigana.
    • Grammar dictionary (started collecting).

JWPce - Technical Information
More information than you really want to know.

This routine (writing a web page after programming, should be section, techno-humor) has answers to a number of technical questions related to JWPce. Some of the information gets very technical.

Style

I am not a Windows programmer (this is my first Windows program with an interface), and thus have bent the Windows programming style conventions somewhat. The most dominant of this is the multi-file single-window interface. This interface is one that I like since I always maximize child windows when working, which is essentially what this does, but this requires much less code. This model also translates to the Windows CE environment better.

Why C++

JWPce is written in C++, instead of C. Generally C can be more efficient than C++, but C++ makes it easier to reuse code. In the construction of JWPce, a number of precautions were taken to make the code very efficient. In particular, JWPce avoids use of the stream classes, because they include large amounts of code. Additionally, the C file system is not used. All system services that can be moved to system calls have been done so.

Also I wanted to write a C++ program (normally, I program in C).

Why no Foundation Class?

There are a number of reasons for this. First and foremost is that the foundation class tends to make for large code, and I wanted very small code. Additionally, I have little experience with the foundation class and wanted to bend the Windows programming styles conventions, so I did not use the foundation class.

Why limited use of the Registry?

JWPce does not use the registry to store the configuration. Instead the user configuration information is stored in a binary file "JWPCE.CFG", located in the same directory as the executable code. There are potentially a number of advantages to this -- having different configurations for executables stored in different locations, etc. All of these reasons are wrong. I had considered a number of alternatives for storing the configuration.

I rejected using the registry, for a number of reasons. Registry usage is different in Window 95/98/ME/NT/2000/XP and Windows CE. I don't like the registry, it is fragile (gets messed up easily). The user can edit it, but not easily -- A relatively inexperienced user can potentially edit an INI file, but finding and editing keys in the registry is scary, and difficult for most users, but some of them can, so you really need to check return values, but the user cannot change them. This is the worst of all worlds.

I rejected using an INI file (although I may change to one later), because the user can modify the value in the INI file, so a lot of code is necessary to check the values obtained form the INI file to make sure they make sense. Additionally, translating the internal representation of variables into text representation requires lots of code, for little return.

In the end, I decided on a binary file format, because it is small, easy to program, easy to protect using a magic number, and if the user wants to get rid of the configuration they just simply can delete the configuration file (JWPce will rebuild it with the default values). Additionally, since the file is binary it is small, and access is controlled, because users will not try to edit it, so values within are relatively reliable.

Why the restricted file locations?

JWP allowed users to place the support files in virtually any location the user wanted, however, JWPce requires most of the support files to be in the same directory as the main program.

Simply, I didn't think the added code was a good trade-off against the gained functionality of this feature. In JWP, this features can cause problems, if the user moves the program, because JWP does not always realize this has happened and correct the connections to the actual file locations. Further, the 19MB required for a full install is relatively modest by modern standards and should not represent a problem. Finally, JWPce file access is provided though a standard class function, thus if allowing the user to locate files at any location it can easily be added to the program at a later date.

Further, as was originally intended JWPce lets you move the dictionary files (which are the largest part of the system), and supplemental font files to any location on your system. Given this arrangement, I will probably continue to restrict all other support files to the same directory as the executable.

Why the keyboard layout?

JWPce uses a fixed keyboard layout that is somewhat different from that used by JWP's default. The choice of a fixed layout had to do with producing a small code size for the Windows CE environment. An added concern was to have a keyboard mapping that worked under Windows 95/98/ME/NT/2000/XP and Windows CE. This means that all actions must have a non-function key mapping (can also have a function key mapping), because Windows CE machines do not have function keys! I have included all key mappings in the menu shortcuts for commands with multiple key mappings (for example the dictionary lookup is either F6 or Ctrl+D).

Additionally, JWPce uses a trick to reduce the amount of coding necessary. In reality, a Japanese edit box is simply a file that is one line long, thus the same code is used for edit controls and for editing files. Some commands, however, do not make sense in the context of an edit box. JWPce implements these commands through menu controls, thus they are not available in an edit box automatically, and commands that do make sense in an edit box are implemented though the keyboard control with the menu command (if there is one) simply invoking the keyboard command. This could easily be revised to allow for configurable keyboard at some later date.

As for where the actual key assignments came from, well..., er..., um..., for the most part, there a cross between the JWP defaults, conventional Windows defaults, and my personal (well, when you do the programming you get the make the choices) JWP configuration.

Bugs! Suggestions! Comments! Help!
What is wrong, What can be done, and What you can do?

This section is dedicated to improving the program. Here, you can find reports of known problems with the code, ways to work-around them, and even ways you can help with the code.

If you encounter a bug, or what you think is a bug, please write as detailed description as you can and send it to me by e-mail. I will try to fix bugs in the next release.

Beyond bugs, I am interested in what you think of the program, and how it may be improved. I am not promising to implement all suggestions, by I will definitely consider all suggestions. If you really like some feature, let me know. If you really hate some feature, also let me know (any why please).

Some things I am looking for

If you find spelling mistakes please report them. I am a notorious bad speller!

Bugs and Work-Arounds

Recent Changes to JWPce
Okay... So what actually did change.

This section contains a short overview of changes in the most recent versions of JWPce. For a full list of changes see the CHANGES.TXT file.

About TrueType Fonts
Copyright and other problems

JWPce now supports TrueType fonts. Using TrueType fonts has a number of advantages. First the fonts are scaleable to virtually any point size without loss of resolution (this makes the printout and the large kanji in the Character Information dialog box look very nice).

TrueType fonts, however, also have some disadvantages. Unlike the bitmapped fonts, they are not optimized for a display at a specific size and often are difficult to read if displayed in a small size. Additionally, the fonts are larger than the bitmapped fonts for the small size. A typical TrueType font is 4-5 MB, where the k16x16.f00 font is only 220 kB.

The other problem with TrueType fonts is an issue of copyright. I currently do not have access to a TrueType font of which I can freely give away. I can, however, point out where you can get several (three at this time) different TrueType fonts that will work with JWPce.

Microsoft has made two TrueType fonts available with the Japanese support kit for Office (on the Office CD for Office 97, downloadable for Office 95), and the Japanese support kit for Internet Explorer. These fonts are MS Gothic, which is a serif font similar to Arial, and MS Mincho, which has a more classic look.

One other TrueType font (as well as the Microsoft fonts) can be obtained from The Monash Nihongo ftp Archive (many many thanks to Jim Breen).

JWPce Mail-List
When in the next version coming out?

If you send me an email (see link below), I will add your name to the JWPce mail-list. You will automatically get an e-mail when a new version is released. If you want to be removed from the list let me know and I will remove you. If your email address bounces I will automatically remove you from the list.

JWPce Mail-list

Download JWPce
Copyright (c) 1997-2004, 2005 glenn rosenthal, All rights reserved

There are currently two versions of JWPce available for download:

Download Version 1.50

This is the newest version of JWPce. In general I recommend you using this version, unless you need a localization file that is not offered for version 1.50.

.

Download Version 1.34

This version of JWPce has been out for a while. I would suggest using this version if you have trouble with version 1.50. The reason you may want to use version 1.34 is to use the localized interface. 

page maintained by glenn rosenthal
revision history

Back to top        Back to Home        e-mail