diff --git a/doc/mini_review_topics.html b/doc/mini_review_topics.html
index e8a3662..ca07cc0 100644
--- a/doc/mini_review_topics.html
+++ b/doc/mini_review_topics.html
@@ -4,15 +4,9 @@
-Here is what needs to be done to get the library ready for a mini
-
+Endian Mini-Review
-
+
Here is what needs to be done to get the library ready for a mini-review:
@@ -100,7 +94,7 @@ might used inadvertently or inappropriately. The impact of adding an endian_buff
diff --git a/doc/styles.css b/doc/styles.css
new file mode 100644
index 0000000..7bd2260
--- /dev/null
+++ b/doc/styles.css
@@ -0,0 +1,13 @@
+
+body
+{
+ font-family: sans-serif;
+ max-width: 6.5in;
+ font-size: 85%;
+}
+ ins {background-color: #CCFFCC;}
+ del {background-color: #FFCACA;}
+ pre {background-color: #D7EEFF; font-size: 100%;}
+ code {font-size: 110%;}
+ table{font-size: 100%;}
+
\ No newline at end of file
diff --git a/doc/types.html b/doc/types.html
index 172a6a2..af7c5ad 100644
--- a/doc/types.html
+++ b/doc/types.html
@@ -5,12 +5,8 @@
-Boost Endian Integers
-
@@ -119,10 +115,10 @@ using namespace boost::endian;
namespace
{
- // This is an extract from a very widely used GIS file format. Who knows
- // why a designer would mix big and little endians in the same file - but
- // this is a real-world format and users wishing to write low level code
- // manipulating these files have to deal with the mixed endianness.
+ // This is an extract from a very widely used GIS file format. It seems odd
+ // to mix big and little endians in the same file - but this is a real-world
+ // format and users wishing to write low level code manipulating these files
+ // must deal with the mixed endianness.
struct header
{
@@ -147,10 +143,10 @@ int main(int, char* [])
h.shape_type = 0x01020304;
// Low-level I/O such as POSIX read/write or <cstdio> fread/fwrite is sometimes
- // used for binary file operations when ultimate efficiency is important.
- // Such I/O is often performed in some C++ wrapper class, but to drive home the
- // point that endian integers are often used in fairly low-level code that
- // does bulk I/O operations, <cstdio> fopen/fwrite is used for I/O in this example.
+ // used for binary file operations when ultimate efficiency is important. Such
+ // I/O is often performed in some C++ wrapper class, but to drive home the
+ // point that endian integers are often used in fairly low-level code that does
+ // bulk I/O operations, <cstdio> fopen/fwrite is used for I/O in this example.
std::FILE* fi = std::fopen(filename, "wb"); // MUST BE BINARY
@@ -680,7 +676,7 @@ differs from endian representation size. Vicente Botet and other reviewers
suggested supporting floating point types.