Struct tectonic_bundles::zip::ZipBundle

pub struct ZipBundle<R: Read + Seek> { /* private fields */ }

A bundle backed by a ZIP file.

Implementations

impl<R: Read + Seek> ZipBundle<R>

pub fn new(reader: R) -> Result<ZipBundle<R>>

Create a new ZIP bundle for a generic readable and seekable stream.

impl ZipBundle<File>

pub fn open<P: AsRef<Path>>(path: P) -> Result<ZipBundle<File>>

Open a file on the filesystem as a ZIP bundle.

Trait Implementations

impl<R: Read + Seek> Bundle for ZipBundle<R>

fn all_files(&mut self, _status: &mut dyn StatusBackend) -> Result<Vec<String>>

Enumerate the files in this bundle.

fn get_digest(&mut self, status: &mut dyn StatusBackend) -> Result<DigestData>

Get a cryptographic digest summarizing this bundle’s contents.

impl<R: Read + Seek> IoProvider for ZipBundle<R>

fn input_open_name( &mut self, name: &str, _status: &mut dyn StatusBackend ) -> OpenResult<InputHandle>

Open the named file for input.

fn output_open_name(&mut self, _name: &str) -> OpenResult<OutputHandle>

Open the named file for output.

fn output_open_stdout(&mut self) -> OpenResult<OutputHandle>

Open the standard output stream.

fn input_open_name_with_abspath( &mut self, name: &str, status: &mut dyn StatusBackend ) -> OpenResult<(InputHandle, Option<PathBuf>)>

Open the named file for input and return filesystem path information.

fn input_open_primary( &mut self, _status: &mut dyn StatusBackend ) -> OpenResult<InputHandle>

Open the “primary” input file, which in the context of TeX is the main input that it’s given. When the build is being done using the filesystem and the input is a file on the filesystem, this function isn’t necesssarily that important, but those conditions don’t always hold.

fn input_open_primary_with_abspath( &mut self, status: &mut dyn StatusBackend ) -> OpenResult<(InputHandle, Option<PathBuf>)>

Open the primary input and return filesystem path information.

fn input_open_format( &mut self, name: &str, status: &mut dyn StatusBackend ) -> OpenResult<InputHandle>

Open a format file with the specified name. Format files have a specialized entry point because IOProviders may wish to handle them specially: namely, to munge the filename to one that includes the current version of the Tectonic engine, since the format contents depend sensitively on the engine internals.

fn write_format( &mut self, _name: &str, _data: &[u8], _status: &mut dyn StatusBackend ) -> Result<(), Error>

Save an a format dump in some way that this provider may be able to recover in the future. This awkward interface is needed to write formats with their special munged file names.