Magnum 'finally' got around to uploading the file, so now you can find a 12 point version of the TERMINAL font that is also compatible with Licida Console. It should be compatible with all non-english characters that the normal terminal font doesn't have (or in some cases has in entirely different places in the list of characters it shows).
Some minor issues:
1. As the description file indicates, the file contains two identical copies, each with a different name. This is due to the fact that the program I used doesn't allow you to delete a font once written to the file. :(
2. It also only supports the 12 point version. This happens to be the size I use in my client and since making the new font required a lot of copy and paste into an empty font file, I didn't bother with other sizes.
3. For some reason Mushclient insists that it is a 6 point font. This is probably another bug in the program I used. Simply directly enter 12 for the size when selecting the font. ;)
------------------------------------------
Note (if things go wrong):
Another known issue I ran into is that apparently if a FON type font is damaged, it can cause Windows 9x (and maybe others) to not boot. I don't think this is an issue with this file, since I have been using it for weeks, but it is a nasty bug. Fixing it requires going into DOS mode and copying the existing TERMINAL.FON file over top of the damaged one (i.e. 'copy TERMINAL.FON MODTERM.FON'). This will allow you to reboot and then you can uninstall the font from the Font folder's menus. Trust MS to design an operating system so stupid it can't simply skip loading a font that doesn't work, but blows up instead... lol
As I said though, it was a damaged version of the font that did this, so it shouldn't be a problem. If it doesn't work, please tell me so I can check to make sure I zipped the right version of the file.
Some minor issues:
1. As the description file indicates, the file contains two identical copies, each with a different name. This is due to the fact that the program I used doesn't allow you to delete a font once written to the file. :(
2. It also only supports the 12 point version. This happens to be the size I use in my client and since making the new font required a lot of copy and paste into an empty font file, I didn't bother with other sizes.
3. For some reason Mushclient insists that it is a 6 point font. This is probably another bug in the program I used. Simply directly enter 12 for the size when selecting the font. ;)
------------------------------------------
Note (if things go wrong):
Another known issue I ran into is that apparently if a FON type font is damaged, it can cause Windows 9x (and maybe others) to not boot. I don't think this is an issue with this file, since I have been using it for weeks, but it is a nasty bug. Fixing it requires going into DOS mode and copying the existing TERMINAL.FON file over top of the damaged one (i.e. 'copy TERMINAL.FON MODTERM.FON'). This will allow you to reboot and then you can uninstall the font from the Font folder's menus. Trust MS to design an operating system so stupid it can't simply skip loading a font that doesn't work, but blows up instead... lol
As I said though, it was a damaged version of the font that did this, so it shouldn't be a problem. If it doesn't work, please tell me so I can check to make sure I zipped the right version of the file.