hmm, no I'm not sure I get it, but, basically what my code is doing is converting the string to a raw string, then treating \ + 'any other character' as one character throughout the subsequent steps. This is what I think is expected based on the authors response and reading the expected output for the tests. I've rechecked every module of my code and it is doing exactly what I expect it to do, which is why I can only think that I am not expecting it to do what the tests are expecting.

Also what about \ followed by any other character? Should that be counted as a single character? I'm passing all tests without line breaks, and my encode decode functions work with themselves on the line break test strings, but it seems there is something the tests are expecting my functions to do with \ that I am not getting from the description.

Sooo, \n should be treated as a single character? Or two seperate characters?

aha that makes sense, thank you!

Classy Kata.

Haven't finished this yet but was definitely wondering about these. Seems like an easy fix since there are only 8 possible inputs that are affected. (a8, b7)(h1,g2)(a1, b2)(h7,g8) and their opposites.

Great kata imo.

Maybe I'm missing something, but it seemed to me there was some inconsistency in the expected results of this kata. For example, if input was (1,1,1) output was 1, BUT if input was (0,0,0) or (2,2,2), output was not 0 or 2 respectively. This seems wrong to me, unless I'm missing something. I did my code recursively so that is probably why it bothered me. Maybe it's just me?