Create gh-pages branch via GitHub

index.html

@@ -31,17 +31,21 @@
     <!-- MAIN CONTENT -->
     <div id="main_content_wrap" class="outer">
       <section id="main_content" class="inner">
-        <p>Protocol Buffers - Google's data interchange format
-Copyright 2008 Google Inc.
-<a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a></p>
+        <h1>
+<a name="protocol-buffers---googles-data-interchange-format" class="anchor" href="#protocol-buffers---googles-data-interchange-format"><span class="octicon octicon-link"></span></a>Protocol Buffers - Google's data interchange format</h1>
 
-<h1>
-<a name="c-installation---unix" class="anchor" href="#c-installation---unix"><span class="octicon octicon-link"></span></a>C++ Installation - Unix</h1>
+<p>Copyright 2008 Google Inc.</p>
+
+<p><a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a></p>
+
+<h2>
+<a name="c-installation---unix" class="anchor" href="#c-installation---unix"><span class="octicon octicon-link"></span></a>C++ Installation - Unix</h2>
 
 <p>If you get the source from github, you need to generate the configure script
 first:</p>
 
-<p>$ ./autogen.sh</p>
+<pre><code>$ ./autogen.sh
+</code></pre>
 
 <p>This will download gtest source (which is used for C++ Protocol Buffer
 unit-tests) to the current directory and run automake, autoconf, etc.
@@ -53,10 +57,11 @@ contains gtest and the configure script).</p>
 <p>To build and install the C++ Protocol Buffer runtime and the Protocol
 Buffer compiler (protoc) execute the following:</p>
 
-<p>$ ./configure
-  $ make
-  $ make check
-  $ make install</p>
+<pre><code>$ ./configure
+$ make
+$ make check
+$ make install
+</code></pre>
 
 <p>If "make check" fails, you can still install, but it is likely that
 some features of this library will not work correctly on your system.
@@ -66,7 +71,7 @@ Proceed at your own risk.</p>
 
 <p>For advanced usage information on configure and make, see INSTALL.txt.</p>
 
-<p>** Hint on install location **</p>
+<p><strong>Hint on install location</strong></p>
 
 <p>By default, the package will be installed to /usr/local.  However,
   on many platforms, /usr/local/lib is not part of LD_LIBRARY_PATH.
@@ -79,7 +84,7 @@ Proceed at your own risk.</p>
 <p>If you already built the package with a different prefix, make sure
   to run "make clean" before building again.</p>
 
-<p>** Compiling dependent packages **</p>
+<p><strong>Compiling dependent packages</strong></p>
 
 <p>To compile a package that uses Protocol Buffers, you need to pass
   various flags to your compiler and linker.  As of version 2.2.0,
@@ -121,7 +126,7 @@ pkg-config --cflags --libs protobuf  # print both
 <p>If you only want protobuf-lite, substitute "protobuf-lite" in place
   of "protobuf" in these examples.</p>
 
-<p>** Note for cross-compiling **</p>
+<p><strong>Note for cross-compiling</strong></p>
 
 <p>The makefiles normally invoke the protoc executable that they just
   built in order to build tests.  When cross-compiling, the protoc
@@ -146,7 +151,7 @@ pkg-config --cflags --libs protobuf  # print both
   has the same version as the protobuf source code you are trying to
   use it with.</p>
 
-<p>** Note for Solaris users **</p>
+<p><strong>Note for Solaris users</strong></p>
 
 <p>Solaris 10 x86 has a bug that will make linking fail, complaining
   about libstdc++.la being invalid.  We have included a work-around
@@ -157,7 +162,7 @@ pkg-config --cflags --libs protobuf  # print both
 
 <p>See src/solaris/libstdc++.la for more info on this bug.</p>
 
-<p>** Note for HP C++ Tru64 users **</p>
+<p><strong>Note for HP C++ Tru64 users</strong></p>
 
 <p>To compile invoke configure as follows:</p>
 
@@ -166,16 +171,16 @@ pkg-config --cflags --libs protobuf  # print both
 
 <p>Also, you will need to use gmake instead of make.</p>
 
-<h1>
-<a name="c-installation---windows" class="anchor" href="#c-installation---windows"><span class="octicon octicon-link"></span></a>C++ Installation - Windows</h1>
+<h2>
+<a name="c-installation---windows" class="anchor" href="#c-installation---windows"><span class="octicon octicon-link"></span></a>C++ Installation - Windows</h2>
 
 <p>If you are using Microsoft Visual C++, see vsprojects/readme.txt.</p>
 
 <p>If you are using Cygwin or MinGW, follow the Unix installation
 instructions, above.</p>
 
-<h1>
-<a name="binary-compatibility-warning" class="anchor" href="#binary-compatibility-warning"><span class="octicon octicon-link"></span></a>Binary Compatibility Warning</h1>
+<h2>
+<a name="binary-compatibility-warning" class="anchor" href="#binary-compatibility-warning"><span class="octicon octicon-link"></span></a>Binary Compatibility Warning</h2>
 
 <p>Due to the nature of C++, it is unlikely that any two versions of the
 Protocol Buffers C++ runtime libraries will have compatible ABIs.
@@ -186,10 +191,11 @@ immediately on startup of your app.  Still, you may want to consider
 using static linkage.  You can configure this package to install
 static libraries only using:</p>
 
-<p>./configure --disable-shared</p>
+<pre><code>./configure --disable-shared
+</code></pre>
 
-<h1>
-<a name="java-and-python-installation" class="anchor" href="#java-and-python-installation"><span class="octicon octicon-link"></span></a>Java and Python Installation</h1>
+<h2>
+<a name="java-and-python-installation" class="anchor" href="#java-and-python-installation"><span class="octicon octicon-link"></span></a>Java and Python Installation</h2>
 
 <p>The Java and Python runtime libraries for Protocol Buffers are located
 in the java and python directories.  See the README file in each
@@ -197,13 +203,14 @@ directory for more information on how to compile and install them.
 Note that both of them require you to first install the Protocol
 Buffer compiler (protoc), which is part of the C++ package.</p>
 
-<h1>
-<a name="usage" class="anchor" href="#usage"><span class="octicon octicon-link"></span></a>Usage</h1>
+<h2>
+<a name="usage" class="anchor" href="#usage"><span class="octicon octicon-link"></span></a>Usage</h2>
 
 <p>The complete documentation for Protocol Buffers is available via the
 web at:</p>
 
-<p><a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a></p>
+<pre><code>https://developers.google.com/protocol-buffers/
+</code></pre>
       </section>
     </div>