Can anyone provide a set of *tests* that we can actually run
automatically for this? Honestly, until we have actual tests, this is
like playing whack-a-mole blind: the problems will just keep
resurfacing... What we need is a test file for unicode that can be
run reliably, by anyone, and that shows the various issues...
As I said earlier, it's quite possible that the various proposed fixes
work for *someone*, but without actual tests that we can include,
there's no way to know what they may break for someone else (as has
happened in the past).
Sorry to seem like a curmudgeon: I really appreciate people
contributing ideas and even code. But we need to fix these unicode
problems the right way, else we'll be hunting them forever.
Can anyone provide a set of *tests* that we can actually run
automatically for this? Honestly, until we have actual tests, this is
like playing whack-a-mole blind: the problems will just keep
resurfacing... What we need is a test file for unicode that can be
run reliably, by anyone, and that shows the various issues...
As I said earlier, it's quite possible that the various proposed fixes
work for *someone*, but without actual tests that we can include,
there's no way to know what they may break for someone else (as has
happened in the past).
Sorry to seem like a curmudgeon: I really appreciate people
contributing ideas and even code. But we need to fix these unicode
problems the right way, else we'll be hunting them forever.