I have solved this problem!
<snip>
Seems more like an ugly hack than a problem solution to me. An end user will not be willing to do the registry hack that you're doing, and it's probably much easier to add a new CP to C::B's editor than to convince users to replace their default font. (We may like it, but the end users won't. And they'll like automatization even less.)
Regarding GNU/Linux machines, I don't know about their Cyrillic configuration (I didn't even fix it up for my Croatian == Central European glyphs), but it doesn't sound to me like most people will adapt their OS installation to suit their programs. If the distributions use CP 866, then coding for such distros is a bit harder with C::B.
Ok, I'll stfu.