When you are using Jedit3.0 in Japanese OS (not in English OS), you may feel why Jedit takes so long time to start up. The most of startup time is spent by loading the shared library of the Japanese Language Analysis Manager. To accelerate the Jedit startup time, there are two methods.
1) Install Jedit startup accelerator "JLAA"in your Startup Items folder of System Folder. Jedit will start up in a few seconds. For more details of JLAA, please refer JLAA pages.
2) Use Jedit3.0 68K version which does not use shared libraries at all. In PM9500(240MHZ G3), the 68K version starts up in 1.8 seconds while the PPC version in 4.6 seconds. If you don't need to use shared library specific functions such as Unicode, Japanese speech and QuickDraw3D, please try to use the 68K version.
If you can't start up Jedit by some system error, please check if the following QuickDraw 3D files are properly installed in your Extensions folder. If one of them was lacked, Jedit3.0 would stall at startup.
QuickDraw 3D IR
QuickDraw 3D RAVE
QuickDraw 3D Viewer
Or if you don't want to use QuickDraw3D functions, please remove all the above files.
If a driver of USB Floppy disk (Yano or Logitec$B!K(Bis installed in the Extensions Folder, Jedit sometimes stalls when inputting Japanese words. As this problem happens not only in Jedit but also in other applications, it may be the problem between the driver of USB Floppy disk and the Japanese Input Method. If you are using such driver of USB Floppy disk, please remove the driver from Extensions folder and then test Jedit3.0.
When some special control codes such as null were contained in the file, Jedit would misjudge the character encoding as Unicode and sometimes content would not be displayed in the window. In such cases, please set the checkbox "Alert none-Mac encodings" in the "Encodings" of "Preference" to ON and check if the auto-detection of character encodings works properly or not.
Jedit detects the type of Kanji encoding when it opens the file. But in the following cases, Jedit might fail to detect the encoding.
1) If the file contained some High ASCII codes which are popular in French or German text, Jedit would misjudge these codes as Kanji codes. So If you don't need to handle Japanese text, please set the checkbox "Judge Kanji encodings" in the "Encodings" of "Preference" to OFF.
2) If the strings of "(J~(By" or "(J~(Bz" were contained in the text, Jedit would judge the kanji encoding as "CIS-JIS". But as "(J~(By" or "(J~(Bz" sometimes appears in the URL string, these strings lead Jedit to misjudge the Kanji encoding. As "CIS-JIS" is very minor Kanji encoding, I recommend to set the "Jedge CIS-JIS Kanji" in the "Encodings" of "Preference" to OFF.
If the file contains null codes, Jedit will judge the encoding as Unicode. But when none-Unicode file contains null codes by some reason, these codes will lead Jedit to misjudge the encoding. If you don't need to handle Unicode files, please set the "Support Unicode/UTF-8" in the "Encodings" of "Preference" to OFF. You can also remove null codes from your text by the menu "Tools">"Remove Null Code".