0.7.2 release, includes new Linux type code & true GUID generation in
Windows
diff --git a/README b/README
index 3449210..e818c2c 100644
--- a/README
+++ b/README
@@ -160,19 +160,26 @@
   called uuid-dev or something similar to get the headers. On FreeBSD, the
   e2fsprogs-libuuid port must be installed.
 
-* The ICU library (http://site.icu-project.org) is required on all
-  platforms except Windows. This library is normally installed in Linux,
-  but you may need to install the development headers (libicu-dev or
-  something similar).
+* The ICU library (http://site.icu-project.org), which provides support for
+  Unicode partition names, is recommended on all
+  platforms except Windows. This library is normally installed in Linux and
+  OS X, but you may need to install the development headers (libicu-dev or
+  something similar in Linux; or the libicu36-dev Fink package in OS X). To
+  compile without ICU support, you must modify the Makefile: Remove the
+  "-D USE_UTF16" part from the CXXFLAGS line and remove references to
+  -licuio, -licuuc, -licudata, and -licucore (details vary between
+  platforms) from the compilation options. Suitable lines are present, but
+  commented out, in the Makefile, Makefile.mac, and Makefile.bsd files.
 
 * The sgdisk program also requires the popt library and its development
   files (headers). Most Linux distributions install popt by default, but
   you may need to install a package called popt-dev, popt-devel, or
   something similar to obtain the header files. Mac OS users can find a
-  version of popt for Mac OS from http://popt.darwinports.com; however,
-  you'll first need to install DarwinPorts (instructions exist on the
-  preceding page). Alternatively, you can compile gdisk alone, without
-  sgdisk; gdisk doesn't require popt.
+  version of popt for Mac OS from Drawin Ports (http://popt.darwinports.com)
+  or Fink (http://www.finkproject.org); however, you'll first need to
+  install DarwinPorts or Fink (instructions exist on the relevant projects'
+  pages). Alternatively, you can compile gdisk alone, without sgdisk; gdisk
+  doesn't require popt.
 
 When all the necessary development tools and libraries are installed, you
 can uncompress the package and type "make" at the command prompt in the
@@ -192,17 +199,17 @@
 
 THIS SOFTWARE IS BETA SOFTWARE! IF IT WIPES OUT YOUR HARD DISK OR EATS YOUR
 CAT, DON'T BLAME ME! To date, I've tested the software on several USB flash
-drives, a handful of PATA and SATA hard disks, and several virtual disks in
-the QEMU and VirtualBox environments. Many others have now used the
-software on their computers, as well. I believe all data-corruption bugs to
-be squashed, but I know full well that the odds of my missing something are
-high. This is particularly true for large drives; my only direct testing
-with such disks is with virtual QEMU disks. I've received user reports of
-success with RAID arrays over 2TiB in size, though.
+drives, physical hard disks, and virtual disks in the QEMU and VirtualBox
+environments. Many others have now used the software on their computers, as
+well. I believe all data-corruption bugs to be squashed, but I know full well
+that the odds of my missing something are high. This is particularly true for
+large (over-2TiB) drives; my only direct testing with such disks is with
+virtual QEMU and VirtualBox disks. I've received user reports of success with
+RAID arrays over 2TiB in size, though.
 
 My main development platform is a system running the 64-bit version of
 Gentoo Linux (previously Ubuntu 8.04). I've also tested on several other
-32- and 64-bit Linux distributions Intel-based Mac OS X 10.5 and 10.6,
+32- and 64-bit Linux distributions, Intel-based Mac OS X 10.5 and 10.6,
 64-bit FreeBSD 7.1, and Windows 7.
 
 Redistribution