>Second, in commit 9f6e3f5a997f484548bd03e7e7573c38a95c8d09, I changed >string ports to honor it, like other port types, instead of forcing >'error. This seems like the right thing to me, for the sake of >consistency (in fact, I’d consider the previous behavior as a bug), but >it’s an observable change.
Sounds fair. The 'error behavior for was once coupled with UTF-8, making the error mostly moot at the time, but, if string ports are honoring encoding they should probably honor the conversion strategy as well. -Mike
