blob: 4a9edfc222ea5f49575006d7da4a38dccd6286bf [file] [log] [blame]
vlmeda244a2004-09-24 21:00:15 +00001.de Vb
2.sp
3.ft CW
4.nf
5..
6.de Ve
7.ft R
8.fi
9.sp
10..
11.TH ENBER 1 "\*(Dt" "unber counterpart" "unber counterpart"
12.SH NAME
13enber \- Convert the unber XML output back into BER
14.SH SYNOPSIS
vlm91ac31c2004-09-27 20:31:19 +000015enber [\fB-n\fR] [\fB-\fR] \fIinfile\fR...
vlmeda244a2004-09-24 21:00:15 +000016.SH DESCRIPTION
vlm91ac31c2004-09-27 20:31:19 +000017enber takes the XML-formatted files produced by \fIunber\fR\|(1) and converts
vlmeda244a2004-09-24 21:00:15 +000018them back into the BER format.
19A single dash represents the standard input.
vlm91ac31c2004-09-27 20:31:19 +000020.SH OPTIONS
21.TP
22\fB\-n\fR
23Disable input validation. By default, enber performs some basic validity checks
24against the XML input. This option disables such checks.
vlmeda244a2004-09-24 21:00:15 +000025.SH EXAMPLES
26Decode the BER sequence and immediately encode it back
27.Vb
vlm7bbc5772004-09-24 23:51:53 +000028\& unber \fB-p\fR \fIfilename.ber\fR | enber \fB-\fR > \fIreconstructed.ber\fR
vlmeda244a2004-09-24 21:00:15 +000029.Ve
vlm91ac31c2004-09-27 20:31:19 +000030.SH FOOTNOTES
31This program does not attempt to perform full-fledged XML parsing. It is merely
32compatible with \fIunber\fR\|(1)'s output.
33In particular, the XML comments are not supported.
34The following characters after the initial white space indicate
35the start of a comment: "\fB#\fR" (a hash) and "\fB--\fR" (two dashes).
36The whole comment line is ignored completely. Empty lines are ignored as well.
37.P
38The following example demostrates the use of comments:
39.Vb
40\& <C T="[1]" TL="2" V="2">
41\& <I T="[1]" TL="2" V="Indefinite">
42\& -- </I>
43\& # Do not terminate:
44\& # the absence of end-of-content octets is intentional!
45\& </C>
46.Ve
vlmeda244a2004-09-24 21:00:15 +000047.SH SEE ALSO
48.TP
49\&\fIunber\fR\|(1), \&\fIasn1c\fR\|(1)
50.SH AUTHORS
51Lev Walkin <vlm@lionet.info>