Jedit4.0 FAQ
As "Jedit4.0 For Mac OS X"is a Carbon application, it basically works on Mac OS X native architectures. As it now stands in December 2000, Mac OS X is still under development. The available version of Mac OS X is the "Public Beta," released on September 13th 2000. The initial "Public Beta" release was yet to support the handling of Japanese language and characters. If you want to use Jedit in its Japanese environment, please use Mac OS X Public Beta Build 2E14 or later. Build 2E14 was released on the 21st of October 2000 and does supports Japanese.
When using Jedit4.0 on Mac OS X, several restrictions do occur. For more information, please refer the file "Note on Mac OS X" in the Jedit4.0 folder.
The trouble of key response is caused by the CarbonLib-J 1.1.1 in Mac OS 9.1J. It's the bug of CarbonLin-J 1.1.1.
Please update your Jedit to non-Carbon "Jedit4.0 For Classic OS" (Rev4.0.5 or later) which is free from many problems caused by CarbonLib.
Please update your Jedit to non-Carbon "Jedit4.0 For Classic OS" (Rev4.0.5 or later) which is free from many problems caused by CarbonLib.
Please update your Jedit to non-Carbon "Jedit4.0 For Classic OS" (Rev4.0.5 or later) which is free from many problems caused by CarbonLib.
ATOK will inherit the text color from Jedit's default text color. Jedit's default text color is the line number color. When Jedit's line number color is set to a bright color, you will not able to see letters in ATOK window because ATOK's background color is also bright. Change Jedit's line number color to a darker color with the menu "Format">"Other Colors."
Or please use Jedit Rev.4.0.4 or later which is free from the above bug.
This problem will occur when you use old WXG in Carbon applications such as AppleWorks or Carbonized Jedit4.0 ( Rev4.0.4 or earlier) .
Please update your Jedit to non-Carbon "Jedit4.0 For Classic OS" (Rev4.0.5 or later) which is free from many problems caused by CarbonLib.
Under Japanese input method EGBridge11 or WXG, when pressing option+command short cut keys (such as option+command+I), the option key will be neglected and the command short cut function (command+I) will be wrongly executed. This problem is caused by the mismatch between CarbonLib and the Japanese input methods.
Please update your Jedit to non-Carbon "Jedit4.0 For Classic OS" (Rev4.0.5 or later) which is free from many problems caused by CarbonLib.
It is a system (Mac OS 9) bug. The same problem will also occur on other applications. To remove this problem, find the file "Drag" with Sherlock, then you will find it in Temporary Items folder. Put this file "Drag" onto the trash and reboot your machine.
Carbonized Jedit4.0 ( Rev4.0.4 or earlier) works under CarbonLib. Some Copy&Paste Extensions, such as CopyPaste-4.3, may not work well under CarbonLib.
Please update your Jedit to non-Carbon "Jedit4.0 For Classic OS" (Rev4.0.5 or later) which is free from many problems caused by CarbonLib.
This problem will occur only when you are using a Logitech (LogiCool) mouse in Carbon applications such as Carbonized Jedit4.0 ( Rev4.0.4 or earlier) or AppleWorks.
Please update your Jedit to non-Carbon "Jedit4.0 For Classic OS" (Rev4.0.5 or later) which is free from many problems caused by CarbonLib.
The Page Setup function in CarbonLib is still unfinished and has several bugs.
Please update your Jedit to non-Carbon "Jedit4.0 For Classic OS" (Rev4.0.5 or later) which is free from many problems caused by CarbonLib.
When the "Customize Page Setup Dialog" in the Preference "Print" is set to on, the settings of the Customize Page Setup Dialog will reflect on actual printing. If you set the "Customize Page Setup Dialog" in the Preference "Print" is set to off, the settings of the Preference "Print" will reflect on actual printing.
Note: If you are using Jedit4.0 Rev4.0.1 (the initial version), update it to the latest because it has a bug in printing.
When you are using Jedit4.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, 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.
Such problems will occur just after the execution of some macros which do not preserve the Japanese input mode correctly.
You should execute preDialog/postDialog commands just before/after the display dialog or choose file command in order to preserve the Japanese input mode.
You should execute suspend command before invoking another application from your script.
Jedit detects the type of Kanji encoding when it opens the file. But in the following case, Jedit might fail to detect the encoding. 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.
When the "Intelligent Paste" in the Preference "General" is set to on, a space code will be automatically inserted at the word boundary. But these spaces might be redundant in the Japanese text. If you wish to edit Japanese text, set this option to off.
The ruler column scaling is determined by both font and size, set within "Ruler Font" found under the "Format" menu. When your are editing with the different font or size, the actual column locations do not match the ruler columns.
Or when you specified a proportional font as "Ruler Font", the actual column locations will not match the ruler even if the actual font is as same as "Ruler Font" because the width will vary with each character.
This is the case when the hanging wordwrap is specified. The actual document width should be wider 2 columns than the setting because the Japanese 2-byte punctuation characters at the top of the line will be moved at the end of the previous line. When the normal wordwrap is specified, the maximum ruler width will match the setting value.
The maximum file size will be determined according to your free memory size. Roughly speaking, you may need 2.5 times larger free memory than a file you want to edit.
When your file size is theFileLength bytes and the number of lines is theLineNum, you may need following size of free memory.
(theFileLength * 2) + 32 * theLineNum
Assuming the average byte length of 1 line were about 60 bytes, you may need 2.5 times larger free memory according to the above formula.
