When Tcl communicates with other applications like
Word or Excel, it communicates using the CF_TEXT
clipboard format using utf-8. This goes wrong if
the other application doesn't assume utf-8 but
the system encoding, as Word and Excel do.
Nowadays, Word and Excel communicate in
the CF_UNICODETEXT clipboard format.
If Tcl starts using that, it would immediately
solve the encoding problem mentioned
in TIP #106.
The "-binary" option will still be needed
in order to communicate with external
programs which don't know
CF_UNICODETEXT, and for test-cases
that check upwards compabitbility.