Diego Argueta

This would require storing the codebook along with the file somehow. There are many ways to do that, so you'd have to determine how you want to strike a balance...

What "formatting issues" are you running into? Error messages or a stack trace would be helpful.

Are we guaranteed the codec will always be 1418 bytes though? If not we'd have to have a simple way for someone to figure out the codec length ahead of...

I haven't, actually. Thanks for pointing it out!

Thanks for the warning. I'll be sure to do that!

By the way @srittau I have a few problems with this code and was wondering if there are conventions for handling them. Most of these surround incompatible subclasses. ### "Overloaded...

I've been poking at it locally but haven't pushed anything up yet.

I'll try to get to it this weekend.

I'll check it out, thanks

~@pylipp git says that the patch is corrupt on the very last line but it looks fine to me. Any idea what that's about?~ Never mind, I just did it...