I do. See also the issue #4837 for my initial ad-hoc attempt.
The inevitable problem here is, of course, whether we should reuse the
existing iconv library or make our own. This is also deeply connected
to the assumption that `str` only contains a valid UTF-8 string (which
some standard modules break, `ReaderUtil::each_line` for instance).
Maybe we should start making an wiki page for entire character
encoding issues?
Note: If you copy Python's design (which is actually quite good
compared to many others but not without caveats), try not to copy
`Stream{Reader,Writer}` at least. These are mostly replaced by newer
`Incremental{Reader,Writer}` which doesn't require streams at all.
2013/4/11 Fredrik Håård <[email protected]>:
> So, I take it no-one is working on codecs, is anyone interested in codecs?
> I've started prototyping a solution patterned on Python (i.e. a tool to
> generate specific codec modules from the specs).
>
> /fredrik
>
>
> 2013/4/9 Fredrik Håård <[email protected]>
>>
>> Hi all,
>>
>> is anyone working on generic (i.e. iso-*, cp*) string encoding/decoding?
>>
>> I googled and looked through the wiki, but apart from the from/to_bytes
>> and from_to utf-16 I came up with nothing. Are there plans for what it
>> should look like?
>>
>> Also, how come utf-16 has special treatment?
>> --
>> /fredrik
>>
>> I reject your reality and substitute my own.
>> http://courteous.ly/yp3Zgd
>
>
>
>
> --
> /f
>
> I reject your reality and substitute my own.
> http://courteous.ly/yp3Zgd
>
> _______________________________________________
> Rust-dev mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/rust-dev
>
--
-- Kang Seonghoon | Software Engineer, iPlateia Inc. | http://mearie.org/
-- Opinions expressed in this email do not necessarily represent the
views of my employer.
--
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
