Opt-out of/warn about replacing non-ascii characters by default

[henriquegasques]

It seems that, by default, when parsing or creating an ACH, non-ascii characters are replaced with a space or removed by replacing it with an empty string. That seems a bit dangerous since it's not really clear that it's doing it, and that character might be in an important position, so simply "ignoring" it might not be what people really want. I think at least a warning should be given, but for my current case, It might be ideal to consider the file to be invalid, or maybe only the section which has the bad character.

[henriquegasques]

Hey @jm81 and @adamdecaf, It would be interesting to hear your thoughts on this, if you have a minute. Please feel free to ignore this otherwise.

[jm81]

@henriquegasques To the best of my memory, the replacement with space was added as a quick fix for somebody years ago who had an issue. I vaguely remember thinking it needed a better solution, but dealing with encodings is not something I have much experience with, so I guess I just pushed off doing anything about it until I forgot about it. Your idea of a warning or considering the file invalid makes sense to me (maybe with an option to keep the current behavior).

[adamdecaf]

In the Go ach library I maintain we process the file rune by rune to handle non-ascii characters. Replacing them with blank characters doesn't seem good.