osmocom
/
asn1c
mirror of https://gerrit.osmocom.org/asn1c
11
0
Fork 0
Code Issues Projects Releases Wiki Activity

*** empty log message *** 

git-svn-id: https://asn1c.svn.sourceforge.net/svnroot/asn1c/trunk@1058 59561ff5-6e30-0410-9f3c-9617f08c8826
This commit is contained in:
vlm 2006-03-07 14:09:38 +00:00
parent bb667c6067
commit 02e6e55263
2 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
asn1c/enber.1
View File

@ -14,16 +14,15 @@ enber \- Convert the unber XML output back into BER
.SH SYNOPSIS
enber [\fB-n\fR] [\fB-\fR] [\fIinfile\fR...]
.SH DESCRIPTION
enber takes the XML-formatted files produced by \fIunber\fR\|(1) and converts
them back into the BER format.
A single dash represents the standard input.
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
\fB\-n\fR
Disable input validation. By default, enber performs some basic validity checks
against the XML input. This option disables such checks.
against the XML input.
.SH EXAMPLES
Decode the BER sequence and immediately encode it back
Decode a BER sequence and immediately encode it back
.Vb
\& unber \fB-p\fR \fIfilename.ber\fR | enber \fB-\fR > \fIreconstructed.ber\fR
.Ve

4
asn1c/unber.1
View File

@ -105,9 +105,9 @@ The constructed XML output is not necessarily well-formed.
When indefinite length encoding is being used, the BER sequence, which is not
terminated with the end-of-content octets, will cause the terminating \fB</I>\fR
XML tag to disappear.
Thus, the invalid BER framing directly causes invalid XML output.
Thus, invalid BER framing directly causes invalid XML output.
.P
The \&\fIenber\fR\|(1) utility understands this convention correctly.
The \&\fIenber\fR\|(1) utility understands such XML correctly.
.SH SEE ALSO
.TP
\&\fIenber\fR\|(1), \&\fIasn1c\fR\|(1)