|
From: John G. <jge...@ny...> - 2002-01-31 21:01:35
|
> Under Global Options > Loading & Saving I've set the "jEdit" default > character encoding to ISO8859-1 which differs from the "System > Default" of > Cp1252. Now, any attempt to set mode specific options for a given > file type > makes the character encoding for that filetype revert to the system > default. Since the user is not able to select an encoding scheme on the > mode specifc panel, wouldn't it be more reasonable to retain the jEdit > default the user specified? > > It should also be made clear that "System Default" refers to the java > virtual machine in which jEdit is running not the operating > system, per se. > So, the user who didn't mind losing the two levels of default settings > (System/jEdit) could choose a system default encoding while loading > jEdit by adding -Dfile.encoding=<name of encoding> to command > line options > in jEdit launcher. But that's a drastic remedy. jEdit will store a "buffer.encoding" application property that is separate from the System's "file.encoding" property, so it looks like you can keep "System" (or, as you point out, "JVM" encoding) and default buffer encodings separate. I tried this on version 3.2.2, and jEdit retained a separate default encoding after I defined file.encoding as a java.exe option. You other points seem to me to be correct. John |