From 6df8ca5af49e5ceadbc473d2de68962cb892e8dc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= Date: Fri, 28 Mar 2014 06:43:06 +0100 Subject: Correct some spelling, grammar and punctation issues --- lib/asn1/doc/src/asn1_ug.xml | 44 ++++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) (limited to 'lib/asn1/doc/src') diff --git a/lib/asn1/doc/src/asn1_ug.xml b/lib/asn1/doc/src/asn1_ug.xml index 769d15cd02..297f542f40 100644 --- a/lib/asn1/doc/src/asn1_ug.xml +++ b/lib/asn1/doc/src/asn1_ug.xml @@ -174,7 +174,7 @@ ok

The ASN.1 module People is now accepted and the abstract syntax tree is saved in the People.asn1db file; the generated Erlang code is compiled using the Erlang compiler - and loaded into the Erlang runtime system. Now there is an API + and loaded into the Erlang run-time system. Now there is an API for encode/2 and decode/2 in the module People, which is invoked by:

, )]]> @@ -227,7 +227,7 @@ The encoder and the decoder can also be run from were imported from had to be compiled before the module that imported. This caused problems when asn1 modules had circular dependencies.

-

Now are referenced modules parsed when the compiler finds an +

Referenced modules are now parsed when the compiler finds an entity that is imported. There will not be any code generated for the referenced module. However, the compiled module rely on that the referenced modules also will be compiled.

@@ -291,8 +291,8 @@ erlc -o ../asnfiles -I ../asnfiles -I /usr/local/standards/asn1 Person.asn +asn1config -

This functionality works together with the flags - ber. It enables the +

This functionality works together with the + ber option. It enables the specialized decodes, see the Specialized Decode chapter.

@@ -310,7 +310,7 @@ erlc -o ../asnfiles -I ../asnfiles -I /usr/local/standards/asn1 Person.asn

You may add any option to the Erlang compiler when compiling the generated Erlang files. Any option - unrecognised by the asn1 compiler will be passed to the + unrecognized by the asn1 compiler will be passed to the Erlang compiler.

 @@ -354,7 +354,7 @@ asn1ct:compile("H323-MESSAGES.asn1",[per]). compile time appear on the screen together with a line number indicating where in the source file the error was detected. If no errors are found, an Erlang ASN.1 module will - be created as default.

+ be created.

The run-time encoders and decoders execute within a catch and returns {ok, Data} or {error, {asn1, Description}} where @@ -365,12 +365,12 @@ asn1ct:compile("H323-MESSAGES.asn1",[per]).

- Multi File Compilation -

There are various reasons for using a multi file compilation:

+ Multi-file Compilation +

There are various reasons for using multi-file compilation:

- You want to choose name for the generated module by - any reason. Maybe you need to compile the same specs for - different encoding/decoding standards. + You want to choose the name for the generated module, + perhaps because you need to compile the same specs for + different encoding rules. You want only one resulting module.

You need to specify which asn1 specs you will @@ -733,13 +733,11 @@ O2Val = <<"must be exactly 28 chars....">>, specified for a type are especially important for PER, where they affect the encoding.

-

Please note that all the Character strings are - supported and it is possible to use the following ASN.1 type - definitions:

+

Here are some examples:

 Digs ::= NumericString (SIZE(1..3))
 TextFile ::= IA5String (SIZE(0..64000))
-

and the following Erlang assignments:

+

with corresponding Erlang assignments:

 DigsVal1 = "456",
 DigsVal2 = "123",
@@ -866,9 +864,11 @@ OidVal1 = {1,2,55},
     

       
       Object Descriptor
-      
Values of this type can be assigned a value as an ordinary string i.e.        


+      
Values of this type can be assigned a value as an ordinary string
+      like this:

 
-        "This is the value of an Object descriptor"

+      
+      "This is the value of an Object descriptor"

     

 
     

@@ -1289,8 +1289,8 @@ SS ::= SET {
     
     ASN.1 Information Objects (X.681)
     
Information Object Classes, Information Objects and Information
-      Object Sets, (in the following called classes, objects and
-      object sets respectively), are defined in the standard
+      Object Sets (in the following called classes, objects and
+      object sets respectively) are defined in the standard
       definition []. In the following only a brief
       explanation is given. 

     
These constructs makes it possible to define open types,
@@ -1407,9 +1407,9 @@ T1 ::= General{PrintableString}
 T2 ::= General{BIT STRING}

An example of a value that can be encoded as type T1 is {12,"hello"}.

-

Observe that the compiler not generates encode/decode functions for - parameterized types, only for the instances of the parameterized - types. So, if a file contains the types General{}, T1 and T2 above, +

Note that the compiler does not generate encode/decode functions for + parameterized types, but only for the instances of the parameterized + types. Therefore, if a file contains the types General{}, T1 and T2 above, encode/decode functions will only be generated for T1 and T2.

-- cgit v1.2.3