> Unfortunately this is part of a public facing API, so it's a bit tough to
> change without breaking a bunch of dependent code. So, I think despite the
> annoying spelling mistake, it's not worth the pain to fix because of the API
> breakage :(
Yes, I fully agree. Changing public APIs is a monster.
> If you find other spelling mistakes that are parts of internal APIs, feel
> free to file JIRAs and patches to fix!
The changes I was thinking about are limited to the junit testing
files for the codecs. --> fully internal
Specifically this one:
Which contains (among others) this method: testSplitableCodecs
As I'm actually touching these methods I'll include the changes in the
patch I'm currently working on.
Met vriendelijke groeten,