This crate provides streaming adapters for the
encoding_rs
crate. Adapters implement the standard library I/O traits and provide streaming
transcoding support.
https://docs.rs/encodingrsio
Add this to your Cargo.toml:
toml
[dependencies]
encoding_rs_io = "0.1"
and this to your crate root:
rust
extern crate encoding_rs_io;
This example shows how to create a decoder that transcodes UTF-16LE (the source, indicated by a BOM) to UTF-8 (the destination).
```rust extern crate encodingrs; extern crate encodingrs_io;
use std::error::Error; use std::io::Read;
use encodingrsio::DecodeReaderBytes;
fn main() { example().unwrap(); }
fn example() -> Result<(), Boxsource_data can be any arbitrary io::Read implementation.
let mut decoder = DecodeReaderBytes::new(sourcedata);
let mut dest = String::new();
// decoder implements the io::Read trait, so it can easily be plugged
// into any consumer expecting an arbitrary reader.
decoder.read_to_string(&mut dest)?;
assert_eq!(dest, "foobar");
Ok(())
} ```
Currently, this crate only provides a way to get possibly valid UTF-8 from some source encoding. There are other transformations that may be useful that we could include in this crate. Namely:
std::io::Write implementation and
takes valid UTF-8 and transcodes it to a selected destination encoding. This
encoder would implement std::fmt::Write.std::fmt::Write implementation and
takes arbitrary bytes and transcodes them from a selected source
encoding to valid UTF-8. This decoder would implement std::io::Write.UnicodeRead implementation and
takes valid UTF-8 and transcodes it to a selected destination encoding.
This encoder would implement std::io::Read.std::io::Read implementation and
takes arbitrary bytes and transcodes them from a selected source encoding
to valid UTF-8. This decoder would implement the UnicodeRead trait.Where UnicodeRead is a hypothetical trait that does not yet exist. Its
definition might look something like this:
ignore
trait UnicodeRead {
fn read(&mut self, buf: &mut str) -> Result<usize>;
}
Interestingly, of the above transformations, none of them correspond to
DecodeReaderBytes. Namely, DecodeReaderBytes most closely corresponds to
the last option, but instead of guaranteeing valid UTF-8 by implementing a
trait like UnicodeRead, it instead implements std::io::Read, which pushes
UTF-8 handling on to the caller. However, it turns out that this particular
use case is important for operations like search, which can often be written
in a way that don't assume UTF-8 validity but still benefit from it.
It's not clear which of the above transformations is actually useful, but all of them could theoretically exist. There is more discussion on this topic here (and in particular, the above formulation was taken almost verbatim from Simon Sapin's comments): https://github.com/hsivonen/encoding_rs/issues/8
It is also perhaps worth stating that this crate very much intends on
remaining coupled to encoding_rs, which helps restrict the scope, but may be
too biased toward Web oriented encoding to solve grander encoding challenges.
As such, it may very well be that this crate is actually a stepping stone to
something with a larger scope. But first, we must learn.
This project is licensed under either of
at your option.