Readme updates. Fold at 80 columns
diff --git a/README.md b/README.md
index dc6018d..0a6c046 100644
--- a/README.md
+++ b/README.md
@@ -4,31 +4,62 @@
## Characteristics
-**Implemented in C with minimal dependecy** – Only dependencies are C99, stdint.h, stddef.h, stdbool.h and string.h making it highly portable. There are no #ifdefs.
+**Implemented in C with minimal dependecy** – Only dependencies are
+C99, stdint.h, stddef.h, stdbool.h and string.h making it highly
+portable. There are no #ifdefs.
-**Focused on C / native data representation** – Simpler code because there is no support for encoding/decoding to/from JSON, pretty printing, diagnostic notation... Only encoding from native C representations and decoding to native C representations is supported.
+**Focused on C / native data representation** – Simpler code because
+there is no support for encoding/decoding to/from JSON, pretty
+printing, diagnostic notation... Only encoding from native C
+representations and decoding to native C representations is supported.
-**Small simple memory model** – Malloc is not needed. The encode context is 136 bytes, decode context is 104 bytes and the description of decoded data item is 56 bytes. Stack use is light and there is no recursion. The caller supplies the memory to hold the encoded CBOR and encode/decode contexts so caller has full control of memory usage making it good for embedded implementations that have to run in small fixed memory.
+**Small simple memory model** – Malloc is not needed. The encode
+ context is 136 bytes, decode context is 104 bytes and the
+ description of decoded data item is 56 bytes. Stack use is light and
+ there is no recursion. The caller supplies the memory to hold the
+ encoded CBOR and encode/decode contexts so caller has full control
+ of memory usage making it good for embedded implementations that
+ have to run in small fixed memory.
-**Supports nearly all of RFC 7049** – Only minor, corner-case parts of RFC 7049 are not directly supported (canonicalization, decimal fractions, big floats). Decoding indefinite length strings but requires a string allocator (see documentation). Encoding indefinite length strings is not supported, but is also not necessary or preferred.
+**Supports nearly all of RFC 7049** – Only minor, corner-case parts of
+ RFC 7049 are not directly supported (canonicalization, decimal
+ fractions, big floats). Decoding indefinite length strings but
+ requires a string allocator (see documentation). Encoding indefinite
+ length strings is not supported, but is also not necessary or
+ preferred.
-**Extensible and General** – Provides a way to handle data types that are not directly supported.
+**Extensible and General** – Provides a way to handle data types that
+ are not directly supported.
-**Secure Coding Style** – Uses a construct called UsefulBuf as a discipline for very safe coding the handling of binary data.
+**Secure Coding Style** – Uses a construct called UsefulBuf as a
+ discipline for very safe coding the handling of binary data.
-**Small Code Size** – When optimized for size using the compiler -Os option, x86 code is less than 5KB (~1.7B encode, ~2.8KB decode, ~0.4KB common).
+**Small Code Size** – When optimized for size using the compiler -Os
+ option, x86 code is less than 5KB (~1.7B encode, ~2.8KB decode,
+ ~0.4KB common).
-**Clear documented public interface** – The public interface is separated from the implementation. It can be put to use without reading the source.
+**Clear documented public interface** – The public interface is
+ separated from the implementation. It can be put to use without
+ reading the source.
## Code Status
-QCBOR was originally developed by Qualcomm. It was [open sourced through CAF](https://source.codeaurora.org/quic/QCBOR/QCBOR/) with a permissive Linux license, September 2018 (thanks Qualcomm!).
-This code in Laurence's GitHub has diverged some from the CAF source with some small simplifications and tidying up.
+QCBOR was originally developed by Qualcomm. It was [open sourced
+through CAF](https://source.codeaurora.org/quic/QCBOR/QCBOR/) with a
+permissive Linux license, September 2018 (thanks Qualcomm!).
-From Nov 3, 2018, the interface and code are fairly stable. Large changes are not planned or expected, particularly in the interface. The test coverage is pretty good.
+This code in [Laurence's
+GitHub](https://github.com/laurencelundblade/QCBOR) has diverged from
+the CAF source with some small simplifications and tidying up.
+
+From Nov 3, 2018, the interface and code are fairly stable. Large
+changes are not planned or expected, particularly in the
+interface. The test coverage is pretty good.
## Building
-There is a simple makefile for the UNIX style command line binary that compiles everything to run the tests.
+
+There is a simple makefile for the UNIX style command line binary that
+compiles everything to run the tests.
The actual non-test source files are these eight:
* inc/UsefulBuf.h
@@ -36,19 +67,28 @@
* src/UsefulBuf.c
* src/qcbor_encode.c
* src/qcbor_decode.c
-* src/qcbor_decode_malloc.c (optional; only for indefinite length strings you want handled with malloc)
+* src/qcbor_decode_malloc.c (optional; only for indefinite length
+strings you want handled with malloc)
* src/ieee754.h
* src/ieee754.c
-For most use cases you should just be able to add them to your project. Hopefully the easy portability of this implementation makes this work straight away, whatever your development environment is.
+For most use cases you should just be able to add them to your
+project. Hopefully the easy portability of this implementation makes
+this work straight away, whatever your development environment is.
-The files ieee754.c and ieee754.h are support for half-precision floating point. The encoding side of the floating point functionality is about 500 bytes. If it is never called because no floating point numbers are ever encoded, all 500 bytes will be dead stripped and not
-impact code size. The decoding side is about 150 bytes of object code. It is never dead stripped because it directly referenced by
-the core decoder, however it doesn't add very much to the size.
+The files ieee754.c and ieee754.h are support for half-precision
+floating point. The encoding side of the floating point functionality
+is about 500 bytes. If it is never called because no floating point
+numbers are ever encoded, all 500 bytes will be dead stripped and not
+impact code size. The decoding side is about 150 bytes of object
+code. It is never dead stripped because it directly referenced by the
+core decoder, however it doesn't add very much to the size.
-The test directory includes some tests that are nearly as portable as the main implementation. If your development environment
-doesn't support UNIX style command line and make, you should be able to make a simple project and add the test files to it.
-Then just call run_tests() to invoke them all.
+The test directory includes some tests that are nearly as portable as
+the main implementation. If your development environment doesn't
+support UNIX style command line and make, you should be able to make a
+simple project and add the test files to it. Then just call
+run_tests() to invoke them all.
## Changes from CAF Version
@@ -56,19 +96,23 @@
* Minimal length float encoding is added
* indefinite length arrays/maps are supported
* indefinite length strings are supported
-* Tag decoding is changed; unlimited number of tags supported, any tag value supported, tag utility function for easier tag checking
+* Tag decoding is changed; unlimited number of tags supported, any tag
+value supported, tag utility function for easier tag checking
* Addition functions in UsefulBuf
* QCBOREncode_Init takes a UsefulBuf instead of a pointer and size
* QCBOREncode_Finish takes a UsefulBufC and EncodedCBOR is remove
* bstr wrapping of arrays/maps is replaced with OpenBstrwrap
-* AddRaw renamed to AddEncoded and can now only add whole arrays or maps, not partial maps and arrays (simplification; was a dangerous feature)
-* Finish cannot be called repeatedly on a partial decode (some tests used this, but it is not really a good thing to use in the first place)
+* AddRaw renamed to AddEncoded and can now only add whole arrays or maps,
+not partial maps and arrays (simplification; was a dangerous feature)
+* Finish cannot be called repeatedly on a partial decode (some tests used
+this, but it is not really a good thing to use in the first place)
* UsefulOutBuf_OutUBuf changed to work differently
* UsefulOutBuf_Init works differently
-* The "_3" functions are replaced with "_2" functions (the macros that referenced _3, now reference _2 and work the same)
-* There is a new AddTag functon instead of the "_3" functions, making the interface simpler and saving some code
-* QCBOREncode_AddRawSimple_2 is removed (the macros that referenced still exist and work the same)
-
+* The "_3" functions are replaced with a small number of simpler functions
+* There is a new AddTag functon instead of the "_3" functions, making
+the interface simpler and saving some code
+* QCBOREncode_AddRawSimple_2 is removed (the macros that referenced
+still exist and work the same)