[svnbook commit] r2138 - trunk/src/en/book

[cmpilato]

Author: cmpilato
Date: Tue May  9 10:36:38 2006
New Revision: 2138

Modified:
   trunk/src/en/book/ch03.xml

Log:
* src/en/book/ch03.xml
  (What's in a Name?): Tweak broken text which made claims about
    Subversion's handling of file contents and use of UTF-8 which were
    at best confusing, at worst just plain wrong.


Modified: trunk/src/en/book/ch03.xml
==============================================================================
--- trunk/src/en/book/ch03.xml	(original)
+++ trunk/src/en/book/ch03.xml	Tue May  9 10:36:38 2006
@@ -330,16 +330,15 @@
         Subversion places restrictions on information it
         stores.</para>
 
-      <para>Subversion handles text internally as UTF-8 encoded
-        Unicode.  As a result, certain items which are inherently
-        <quote>textual</quote>, such as property names, path names,
-        and log messages, can only contain legal UTF-8 characters.  It
-        also provides a minimum requirement for use of the
-        <literal>svn:mime-type</literal> property—if a file's
-        contents aren't compatible with UTF-8, you should mark it as a
-        binary file.  Otherwise, Subversion will attempt to merge
-        differences using UTF-8, which is likely to leave garbage in
-        the file.</para>
+      <para>Subversion internally handles certain bits of
+        data—for example, property names, path names, and log
+        messages—as UTF-8 encoded Unicode.  This is not to say
+        that all your interactions with Subversion must involve UTF-8,
+        though.  As a general rule, Subversion clients will gracefully
+        and transparently handle conversions between UTF-8 and the
+        encoding system in use on your computer, if such a conversion
+        can meaningfully be done (which is the case for most common
+        encodings in use today).</para>
 
       <para>In addition, path names are used as XML attribute values
         in WebDAV exchanges, as well in as some of Subversion's