| .TH enber 1 "2014-10-23" "unber counterpart" |
| .if n .ad l \" Turn off justifications |
| .nh \" Turn off hyphenation; can damage formatting in technical documents. |
| .de Vb \" Verbatim begin. |
| .sp |
| .in +4 |
| .ft CW |
| .nf |
| .. |
| .de Ve \" Verbatim end. |
| .ft R |
| .in |
| .fi |
| .. |
| .SH NAME |
| enber \(em Convert the unber XML output back into BER |
| .SH SYNOPSIS |
| enber [\fB\-n\fR] [\fB\-\fR] [\fIinput-filenames\fR...] |
| .SH DESCRIPTION |
| enber convers the XML-formatted files produced by \fIunber\fR\|(1) back into the BER format. |
| A single dash denotes the standard input. |
| .SH OPTIONS |
| .TP 4 |
| \fB\-n\fR |
| Disable input validation. |
| By default, enber performs some basic validity checks |
| against XML input. |
| .SH EXAMPLES |
| Decode a BER sequence and immediately encode it back |
| .Vb |
| unber \fB\-p\fR \fIfilename.ber\fR | enber \fB\-\fR > \fIreconstructed.ber\fR |
| .Ve |
| .SH FOOTNOTES |
| This program does not attempt to perform full-fledged XML parsing. |
| It is merely compatible with \fIunber\fR\|(1)'s output. |
| In particular, XML style comments are not supported. |
| A hash "\fB#\fR" or two dashes "\fB--\fR" following a whitespace is treated as a beginning of a comment line, which is ignored completely. |
| Empty lines are ignored as well. |
| .P |
| The following example demostrates the use of comments: |
| .Vb |
| <C O="0" T="[1]" TL="2" V="2"> |
| <I O="2" T="[1]" TL="2" V="Indefinite"> |
| \fB--\fR </I O="4" T="[UNIVERSAL 0]" L="4"> |
| \fB#\fR Do not terminate: |
| \fB#\fR the absence of end-of-content octets is intentional! |
| </C O="6" T="[1]" L="6"> |
| .Ve |
| .SH SEE ALSO |
| .TP |
| \fIunber\fR\|(1), \&\fIasn1c\fR\|(1) |
| .SH AUTHORS |
| Lev Walkin <vlm@lionet.info> |