On Wed, Apr 26, 2017 at 5:17 PM, Robert Kern <robert.kern@gmail.com> wrote:
The proposal is for only latin-1 and UTF-32 to be supported at first, and the eventual support of UTF-8 will be constrained by specification of the width in terms of characters rather than bytes, which conflicts with the use cases of UTF-8 that have been brought forth.


thanks -- I had forgotten (clearly) it was that limited.

But my question now is -- if there is a encoding-parameterized string dtype, then is it much more effort to have it support all the encodings in the stdlib?

It seems that would solve everyone's issue.



Christopher Barker, Ph.D.

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception