Maintaining websites through remote ssh connections, requires using console editors which should start fast, do not require huge amounts of memory and are easy to use.
The powerfull editors Vim and Emacs are not good for this task - although VIM is virtually guaranteed to be installed and it is fast, can be customized and so on, it is hardly easy to learn. Emacs may be easier, it has menus and tutorial, it is very customizable, but is not too fast to start.
In contrast, Jed is a very light weight editor which is ideal for quick changes, because it starts instantly, supports syntax highlighting for many common programming languages and has good UTF8 support. It has emacs like macro recorder, buffers, and auto indenting too. It also supports emacs keyboard shortcuts by default, so if you use emacs for longer programming sessions, you probably will like jed when you need to edit quickly some remote files.
Unfortunately bulgarian texts (and sites) are often written using 2 different common encodings, and so there is a catch - you need some tweaks for your programs (and jed in particular), to support both encodings equally well:
In order to edit utf8 files with jed, first, you need to have the correct bulgarian locale for utf8 generated.
You can do this using this command:
sudo localedef -i bg_BG -f UTF-8 bg_BG.UTF8
You can install jed and some jed goodies with the following instructions (Debian/Ubuntu):
sudo apt-get install jed jed-extra jedstate
For RedHat/Centos, try to google for a jed rpm, or try:
wget ftp://ftp.pbone.net/mirror/centos.karan.org/el5/extras/testing/i386/RPMS/jed-0.99.18-5.el5.kb.i386.rpm rpm -i jed-0.99.18-5.el5.kb.i386.rpm
Next, you add these lines to your .bashrc file:
alias jed.cp1251='LANG=C jed' alias jed.utf8='LANG=bg_BG.UTF-8 jed'
Restart your shell, or do:
in your current shell, so that the changes can be applied.
After all this preparation, when you want to edit a file encoded using utf8, do it like this:
For cp1251/windows1251, the command should be:
Note, that the selected encoding of your terminal application should match the encoding of your editor, or else you will see some funny characters instead of the proper ones. For this and other reasons, I recommend you to use the KDE's konsole application. It is stable, has good internationalization support, and it is pretty fast, even when you have a large scroll buffer.
You can also use PuTTY in case you are trapped in a windows only shop .