summaryrefslogtreecommitdiff
path: root/bin/rbot
diff options
context:
space:
mode:
authordmitry kim <jason@nichego.net>2008-03-12 02:53:35 +0300
committerdmitry kim <jason@nichego.net>2008-03-12 02:53:35 +0300
commit8fbdb921f39e2262f01c1011d0c6c8d5c885ad5a (patch)
treeef4f29688c831d5a24828828444625487c8ee5a0 /bin/rbot
parent15846be1af87eefbb2d339c4c28ffbc9c1268d6a (diff)
- (bin/rbot) no need to set $KCODE
Diffstat (limited to 'bin/rbot')
-rwxr-xr-xbin/rbot11
1 files changed, 0 insertions, 11 deletions
diff --git a/bin/rbot b/bin/rbot
index 6d8ecec3..a5b7865a 100755
--- a/bin/rbot
+++ b/bin/rbot
@@ -57,17 +57,6 @@ Please note that the logfile doesn't contain IRC logs (which are located at
# IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
# CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-# Most of the string processing across rbot is done against IRC messages, which
-# do not have a well-defined encoding. Although many clients are now using
-# UTF-8, there is no guarantee that an arbitrary string received from IRC will
-# be UTF-8 encoded. We have to force ASCII (byte-wise/charset agnostic)
-# matching because otherwise some strings can give problems: in particular, for
-# example, the bytesequence "\340\350\354\362\371" (that is the aeiou vowels,
-# each with a grave accent) will cause the string to be considered up to the
-# "\354" (i with grave accent) only: so either the rest of the message is
-# ignored, or the matching fails.
-$KCODE = 'a'
-
$VERBOSE=true
require 'etc'