ccharset 1.2.1
A new ccharset version is out, courtesy of LaC.
The installation and everything stay the same.
Our software is not patent cucumbered
{ Category Archives }
A new ccharset version is out, courtesy of LaC.
The installation and everything stay the same.
Yep. It’s not my accomplishment, mind you, I was too lazy and just got used to the shortcomings. So the new version of ccharset comes courtesy of teh_LaC. Here you can get it. Readme stays the same as in the old version, but bear in mind the config file is no longer compatible, so you’ll have to set channel encodings again. Ah, and topic setting doesn’t, and isn’t going to work, yay XChat.
Here’s another small xchat hack I wrote to add missing functionality: privflash. It makes private messages behave the same as nick highlight you get in channels, ie., blue highlight + taskbar flash. Why it isn’t like that in default xchat I dunno, but finally I got annoyed enough to fix it. One day I’ll also add some sane nick availability notification, current “notify: <nick> is online” is completely laughable, but that’s later.
PS. The usual drill to install it: needs python plugin, drop it into ~/.xchat2/, it’ll get picked up next time you start xchat, or /py load privflash.py if you don’t want to wait. Enjoy.
Introducing CCharset!
If you were ever annoyed by XChat’s perpetual inability to follow per-channel encoding settings, then be no more! CCharset allows you to override encoding on a per-channel basis, so now you can use iso-2022-jp in the ever stubborn #nihongo and utf-8 everywhere else. Isn’t that cool? It does exactly this one thing, manages your encodings, nothing else, particularly won’t spew stupid messages on all channels you’re on and fuck with your colours, unlike certain other plugins (coughfreecharcough). Also supports saving your settings, so you don’t have to ever enter that info more than once.
Of course, the usual disclaimer applies, so if this plugin runs over your cat, then sorry for the cat, but you have only yourself to blame.
Update: It has come to my attention that the plugin messes with non-ASCII topic setting badly. So there. You have been warned. I’ll probably (attempt to) fix it someday, but right now, it’s not a top priority.