HexChat for Windows uses MySpell for spelling via the Enchant library. The required libraries are included in the installer, but the dictionaries are big so they are distributed in a separate archive. They’re from Debian Lenny.
If you want to have spelling, do the following:
For portable installs, you can use the share\myspell\dicts subfolder instead of %LOCALAPPDATA%\enchant\myspell (both will work, but the former one can be carried on a pendrive unlike the latter one).
Install your spelling dictionaries via your package manager (something like myspell-en-us or hunspell-en for English). Then make sure to enable spelling under Settings ‣ Preferences ‣ Interface ‣ Input box.
If you use static spelling (this is the default for manual builds) make sure to specify the languages you wish to have spelling for in Settings ‣ Preferences ‣ Interface ‣ Input box. You need to specify their language codes (i.e. de_DE for german), separated by commas. You will also have to manually install the libenchant-dev package for static spelling to work.
Installs using libsexy (most packages should use this) should be using your systems default, but it can be overriden by starting HexChat with “LANG=en hexchat“
In order to start HexChat in a different language (for which a translation exists here) you can use the regional settings of Windows, or set the LC_ALL user environmental variable. The value of the variable must be the two letter country code for your country. If in doubt, have a look at the sharelocale folder. You have to restart HexChat for the changes to apply.
You can also use a batch file to affect only HexChat:
@echo off set LC_ALL=en start hexchat.exe
This sets the language to English. You may use fr for French, de for German, etc. Save the code above as run.bat, and copy it to the HexChat install folder. You can then start HexChat in the desired language by running the batch file.
There are many symbols which may not be supported by the main font you selected to use in HexChat, especially Asian glyphs and special characters, like a peace sign. In this case, you’ll see “lego blocks” instead of them.
To circumvent this, you need to specify alternative fonts for glyphs not supported by your current font. You can specify them in Settings ‣ Preferences ‣ Chatting ‣ Advanced ‣ Alternative fonts. By default, it is set to Arial Unicode MS,Lucida Sans Unicode,MS Gothic,Unifont, which should fix most rendering errors.
Unifont is freely available, so it is recommended to install it - it should solve most of your rendering problems.
In case you still get lego blocks, you’ll need to add additional fonts to the list which support those obscure glyphs. Feel free to extend the list. You only need to specify font names, other info (such as size, weight, style etc.) should be omitted, otherwise those entries will be ignored. All font names must be separated by a comma and there mustn’t be spaces before and/or after commas.
Please bear in mind that for some reason certain fonts that can display a certain glyph when used as the main font may not work when specified as an alternative font so you might have to play around it a bit.
Client Certificates allows you to identify to networks services using a certificate. Please do not mistake it for server certificate which allows you to connect to network with invalid certificate, right now Hexchat can’t do it.
To use one you need to put your certificate file inside certs directory in HexChat’s config folder.
Certificate should be named after the network where it will be used, for example if you want to use it on Rizon, certificate file should look like this: Rizon.pem. If that does not exist every network will try client.pem.
On Windows it is possible to edit cert.pem file in Hexchat main installation directory and add custom certificate there. But this method isn’t very effective as cert.pem is overwritten each time Hexchat installer is used.
Other than channel messages and private messages, IRC has a notice type of message. This is intended to be used as a reply, something that will not cause the other client to send any acknowledgement back. When HexChat displays these messages, it shows them in a tab that it figures is appropriate.
When HexChat decides where to print a notice, it does so in the following order:
This means that if you issue a /cs info #yourchannel from your channel, the reply may show up elsewhere if ChanServ isn’t in your channel, but is in some other channel.
The simplest method is to set the location in Settings ‣ Preferences ‣ Channel switcher ‣ Placement of notices, and select “in an extra tab” or “in the front tab”. The former will cause all server notices to go into a (snotices) tab, and all user notices to go into a (notices) tab. The latter will always print the notices where you are, this can cause odd positioning of channel notices but you will never miss them.
If you know who will notice you before hand, you can simply query the user before they notice you. This way, all notices from that user will show up in the query tab. In the case of ChanServ, this may allow an easier archive of commands you have done anyway.
For other locations, a separate script would be required. While not currently implemented, it would be possible with a script to treat all notices like private messages (open a new query window when received), or place them in a specific existing tab, such as the server tab. At this point, the choice is up to you (or whoever designs the script).