cif2cbf(1) [debian man page]
CIF2CBF(1) General Commands Manual CIF2CBF(1) NAME
cif2cbf - convert a CIF to a CBF file SYNOPSIS
cif2cbf [options] DESCRIPTION
cif2cbf is a program that accepts either a CIF or a CBF as input and outputs a CBF file. OPTIONS
-i input_cif (default: stdin) the input file in CIF or CBF format. If input_cif is not specified or is given as "-", it is copied from stdin to a temporary file. -o output_cbf (default: stdout) the output cif (if base64 or quoted-printable encoding is used) or cbf (if no encoding is used). if no output_cif is specified or is given as "-", the output is written to stdout if the output_cbf is /dev/null, no output is written. The remaining options specify the characteristics of the output cbf. The characteristics of the input cif are derived from context. -c compression_scheme (packed, canonical, byte_offset, v2packed, flatpacked or none, default packed) -m [no]headers (default headers for cifs, noheaders for cbfs) selects MIME (N. Freed, N. Borenstein, RFC 2045, November 1996) headers within binary data value text fields. -d [no]digest (default md5 digest [R. Rivest, RFC 1321, April 1992 using"RSA Data Security, Inc. MD5 Message-Digest Algorithm"] when MIME headers are selected) -e encoding (base64, quoted-printable or none, default base64) specifies one of the standard MIME encodings for an ascii cif or "none" for a binary cbf -b byte_order (forward or backwards, default forward (1234) on little-endian machines, backwards (4321) on big-endian machines -p K_of_padding (0, 1, 2, 4) for no padding after binary data 1023, 2047 or 4095 bytes of padding after binary data -v dictionary specifies a dictionary to be used to validate the input cif and to apply aliases to the output cif. This option may be specified multiple times, with dictionaries layered in the order given. -w process wide (2048 character) lines SEE ALSO
convert_image(1), img2cif(1), makecbf(1). AUTHOR
cif2cbf was written by Herbert J. Bernstein. This manual page was written by Morten Kjeldgaard <mok@bioxray.au.dk>, for the Debian project (but may be used by others). April 2008 CIF2CBF(1)
Check Out this Related Man Page
MIME::Decoder::NBit(3) User Contributed Perl Documentation MIME::Decoder::NBit(3) NAME
MIME::Decoder::NBit - encode/decode a "7bit" or "8bit" stream SYNOPSIS
A generic decoder object; see MIME::Decoder for usage. DESCRIPTION
This is a MIME::Decoder subclass for the "7bit" and "8bit" content transfer encodings. These are not "encodings" per se: rather, they are simply assertions of the content of the message. From RFC-2045 Section 6.2.: Three transformations are currently defined: identity, the "quoted- printable" encoding, and the "base64" encoding. The domains are "binary", "8bit" and "7bit". The Content-Transfer-Encoding values "7bit", "8bit", and "binary" all mean that the identity (i.e. NO) encoding transformation has been performed. As such, they serve simply as indicators of the domain of the body data, and provide useful information about the sort of encoding that might be needed for transmission in a given transport system. In keeping with this: as of MIME-tools 4.x, this class does no modification of its input when encoding; all it does is attempt to detect violations of the 7bit/8bit assertion, and issue a warning (one per message) if any are found. Legal 7bit data RFC-2045 Section 2.7 defines legal "7bit" data: "7bit data" refers to data that is all represented as relatively short lines with 998 octets or less between CRLF line separation sequences [RFC-821]. No octets with decimal values greater than 127 are allowed and neither are NULs (octets with decimal value 0). CR (decimal value 13) and LF (decimal value 10) octets only occur as part of CRLF line separation sequences. Legal 8bit data RFC-2045 Section 2.8 defines legal "8bit" data: "8bit data" refers to data that is all represented as relatively short lines with 998 octets or less between CRLF line separation sequences [RFC-821]), but octets with decimal values greater than 127 may be used. As with "7bit data" CR and LF octets only occur as part of CRLF line separation sequences and no NULs are allowed. How decoding is done The decoder does a line-by-line pass-through from input to output, leaving the data unchanged except that an end-of-line sequence of CRLF is converted to a newline " ". Given the line-oriented nature of 7bit and 8bit, this seems relatively sensible. How encoding is done The encoder does a line-by-line pass-through from input to output, and simply attempts to detect violations of the "7bit"/"8bit" domain. The default action is to warn once per encoding if violations are detected; the warnings may be silenced with the QUIET configuration of MIME::Tools. SEE ALSO
MIME::Decoder AUTHOR
Eryq (eryq@zeegee.com), ZeeGee Software Inc (http://www.zeegee.com). All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.18.2 2013-11-14 MIME::Decoder::NBit(3)