Derek et al,
I want to be sure to clarify that I do consider this an important issue. We just want to make sure we address the situation while also educating users about using encodings properly (admittedly, it's a confusing topic). In Asciidoctor, we are very much focused on strong tooling while at the same time improving the state of the industry. We never want to suggest that people are doing it wrong, simply that we can help them find a path towards correctness for their own benefit.
> Restricting which editor or OS version must be used to create the input fed to asciidoctor will only ensure that hardly anybody ever uses it, which would be a shame.
We certainly don't want to restrict editor choice, except in the extreme case where the editor is actually putting garbage into the document like Notepad. In fact, I'd go far to say that we shouldn't view Notepad as an editor because it really isn't doing its job right. It's really the only exception. Everything else should be good.
> asciidoctor needs to handle whatever is thrown at it without throwing a Ruby error.
Agreed. Part of the issue here is that our hands are a little tied by Ruby < 1.9.3. As of Ruby 2.0 (and even Ruby 1.9.3 to a lesser extent), there are actually APIs to handle encodings elegantly. We can start making use of these APIs so that at least the conversion doesn't completely blow up. I'll file an issue to weave in String#scrub so that the worst that can happen is that bad characters are dropped, showing a warning in verbose mode.
> I meant to address it to Dan or perhaps he prefers to be called mojavelinux on this list.
Call me Dan, mojavelinux or crazy, whatever works for you :)
Cheers!
-Dan
Locked
