New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't put utf8 in such a privileged position. #38

Open

barrucadu opened this issue Jan 5, 2017 · 1 comment

Labels

Owner

barrucadu commented Jan 5, 2017

It's a sensible default, but right now it's impossible to use irc-client with things that aren't utf-8!

barrucadu added the enhancement label

barrucadu added this to the 0.5 milestone

Owner Author

barrucadu commented Jan 5, 2017 •

edited

Loading

There are a couple of issues here:

irc-ctcp only has a nice decoder to Text (but that can be remedied with a small function)
matchCTCP is currently case-insensitive, but if it operates on an arbitrary ByteString it doesn't know enough to be able to do that.
nickMangler assumes the character encoding of the nick is known, so that it can substitute characters.

barrucadu removed this from the 1.0 milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment