setup: ascii-ify the README.rst because distutils in Python < 2.6 assumes ascii in...

Ignore-this: e0b4c659f866bb4b7778fdc871bc1193
This was detected by the Tahoe-LAFS buildbot attempting to build zfec 1.4.15.

darcs-hash:aa0f9a3af1130bcb6c6ecd25ad5ac2681ef89bbd

diff --git a/zfec/README.rst b/zfec/README.rst
index 53d655ea57b88ced35f04df7ecca5eec0e403cfa..e09d8f3449b64b9a6c87fda1036d50a9cf4d4787 100644 (file)
--- a/zfec/README.rst
+++ b/zfec/README.rst
@@ -1,4 +1,4 @@
-zfec -- efficient, portable erasure coding tool
+zfec -- efficient, portable erasure coding tool
 ===============================================
 
 Generate redundant blocks of information such that if some of the
@@ -126,7 +126,7 @@ will also ensure integrity, so the use of sha256sum is unnecessary in
 that case. Note also that you also need to do integrity checking (such
 as with sha256sum) on the blocks that result from the erasure coding
 in *addition* to doing it on the file contents! (There are two
-different subtle failure modes—see "more than one file can match an
+different subtle failure modes -- see "more than one file can match an
 immutable file cap" on the `Hack Tahoe-LAFS!`_ Hall of Fame.)
 
 The `Tahoe-LAFS`_ project uses zfec as part of a complete distributed