I agree! And I have restarted efforts in having these merged. Both are “suffering” from similar errors when it comes to outputting unicode chars in Windows, so we are now seeking some assistance from Windows users. David Smith has already offered to help, but if anyone else is available to diagnose/fix issue, please see this comment and this comment.
I agree with Carlton that a release note would suffice, but we should also check/update tutorials and howtos showing the output of these commands.