You need to use instead the iso-8859-15 character set, which is a modification of iso-8859-1 that includes the Euro sign and some Finnish and French characters. The Euro sign represents character value 0xA4 in this 8-bit set.

There is a new addition to the downloads area, euro.bsh, that can be used as a startup script to provide macro methods to help you with your use of the Euro. The methods let you insert a Euro currency character, change the current buffer's encoding to iso-8859-15, and open a file with that encoding.

To upgrade an operating version of jEditLauncher, simply unpack the contents of the archive in your jEdit installation directory. The file jeshlstb.dl_ may be deleted. If your current version of jEditLauncher is not working for any reason, copy the contents of the archive in your jEdit installation directory, run jedit.exe /i from a command line, and reboot your machine if requested to do so.

In connection with the development of jEdit 4.0, jEditLauncher will be enhanced further to provide additional logging options and to wrap more of jEdit's own command line option for greater flexibility and ease of use.

I have created a PayPal account for accepting monetary donations to jEdit development. Note that this is entirely optional; jEdit is not, and will never become, shareware. You can use it as much as you want, guilt-free, without donating a single cent. Details here.

jEdit 4.0pre3 is now available. This release features improved folding, context-sensitive commenting commands, ActionScript syntax highlighting, and some miscellaneous enhancements and bug fixes. Full changelog can be found here.

The changes are as follows:

• The EditBus plugin has been dissolved, and all classes have been moved to the ErrorList plugin. So you must remove any dependencies on "EditBusPlugin" from your plugin's property file.
  
• All ErrorSource API classes have been moved to the "errorlist" package; so you will need to add "import errorlist.*;" where necessary.
  
• To register an error source, you must now call:
  ErrorSource.registerErrorSource(errorSource);
  Instead of
  EditBus.addToBus(errorSource);
EditBus.addToNamedList(ErrorSource.ERROR_SOURCES_LIST,errorSource);

New Features

• MacOS plugin bundled (Kris Kopicki)
  
  
  
  • jEdit exits cleanly when Command+Q is pressed
    
  • Files created or associated with jEdit can now be opened from the Finder by double-clicking on them, or dragging them to the jEdit icon
    
  • jEdit is assigned as the creator of new files
    
  
  
• A few Alt-key shortcuts added for commonly-used commands so that you don't have to move your fingers all over the keyboard:
  
  
  
  • A+i, A+k: prev, next line
    
  • A+j, A+l: prev, next character

First, I decided that I would do without the help documentation and the "Tip of the day" feature. Opening jedit.jar with a zip file utility, I removed all of the files in the /doc directory and all of the HTML tip files. The resulting jedit.jar shrunk to 986KB. Not bad for a start.

Next, I looked at the edit modes in the /modes directory. What would I really need on the road? I narrowed the selection down to the following: beanshell, c, cplusplus, html, java, javascript, perl, php, python, text, xml and xsl. The largest price paid was for the php mode: the file was 97KB, over four times the size of the next largest. Maybe someday we'll have a php-lite mode, but I decided to keep it in.

This release has a lot of new features, but is also likely to be very buggy, and the documentation has not been updated for any of the new goodies yet. Also, a number of plugins (including mine) are broken by this release. Take care and have fun.

I would like to release jEdit 4.0pre2 two weeks from now, along with an updated set of plugins at the same time. There will then be a pre3 release at the start of December, right before I move back to New Zealand, where I will buy a new computer and switch to Java 1.3 as my primary JDK. 4.0pre4 will follow soon after, and this release will finally drop 1.1 compatibility.

Like nearly every software project, jEdit is built from its source code using what is called a "make" or "makefile" system. These terms come from the original "make" utility that was created for use on the UNIX operating system; there are now a variety of makefile utilities available for all operating systems. Besides the source code and related resources, a makefile system has two main elements. The first is a "makefile", a plain text file that specifies the steps necessary to build the application, such as the invocation of a compiler, an object code linker or an archiving program. The makefile also describes the dependencies among the final product, intermediate files and the underlying source code. This file will be written in a special format designed to satisfy the requirements of the second major element, the "make" utility.