<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -9,7 +9,7 @@ target: book book/default.css book.html book.pdf
 # The book consists of these text files in the following order:
 
 TXTFILES := preface.txt intro.txt basic.txt clone.txt branch.txt history.txt \
-    grandmaster.txt secrets.txt drawbacks.txt
+    grandmaster.txt secrets.txt drawbacks.txt translate.txt
 
 book.xml: $(addprefix $(LANG)/,$(TXTFILES))
 	# Kludge to make preface sections work for languages besides English.</diff>
      <filename>Makefile</filename>
    </modified>
    <modified>
      <diff>@@ -46,32 +46,3 @@ or from one of the mirrors:
 
  $ git clone git://github.com/blynn/gitmagic.git
  $ git clone git://gitorious.org/gitmagic/mainline.git
-
-=== How to Translate This Guide ===
-
-Clone the source, then create a directory corresponding to the target http://www.iana.org/assignments/language-subtag-registry[language's IETF tag]: see
-http://www.w3.org/International/articles/language-tags/Overview.en.php[the W3C article on internationalization]. For example, English is &quot;en&quot;, Japanese is &quot;ja&quot;, and Traditional Chinese is &quot;zh-Hant&quot;. In the new directory, and translate the +txt+ files from the &quot;en&quot; subdirectory. 
-
-For instance, to translate the guide into http://en.wikipedia.org/wiki/Klingon_language[Klingon], you might type:
-
- $ git clone git://repo.or.cz/gitmagic.git
- $ cd gitmagic
- $ mkdir tlh  # &quot;tlh&quot; is the IETF language code for Klingon.
- $ cd tlh
- $ cp ../en/intro.txt .
- $ edit intro.txt  # Translate the file.
-
-and so on for each text file. You can review your work incrementally:
-
- $ make LANG=tlh
- $ firefox book.html
-
-Commit your changes often, then let me know when they're ready.
-GitHub.com has an interface that facilitates this: fork the &quot;gitmagic&quot; project,
-push your changes, then ask me to merge.
-
-I like to have translations follow the above scheme so my scripts can produce
-HTML and PDF versions. Also, it conveniently keeps all the translations in the
-official repository. But please do whatever suits you best: for example, the
-Chinese translators used Google Docs. I'm happy as long as your work
-enables more people to access my work.</diff>
      <filename>en/preface.txt</filename>
    </modified>
    <modified>
      <diff>@@ -30,16 +30,15 @@ do
     sed 's/pr01\.html/index.html/g' -i $FILE
     # Paste ToC into beginning and add div section with class content for CSS.
     sed '/&lt;body/{n; r toc.tmp
-  a &lt;div class=&quot;content&quot;&gt;
-  } ' -i $FILE
+a &lt;div class=&quot;content&quot;&gt;
+}' -i $FILE
     sed '/^&lt;\/body/i &lt;/div&gt;' -i $FILE
   fi
 done
 
 # Originally this link was &quot;My Homepage&quot;. Since it appears on translations of
 # the guide, I changed it to my name so it doesn't have to be translated.
-sed '/^&lt;\/body/i &lt;/div&gt;&lt;div class=&quot;footer&quot;&gt;&lt;a href=&quot;/~blynn/&quot;&gt;Ben
-Lynn&lt;/a&gt;&lt;/div&gt;' -i $BOOKDIR/*.html
+sed '/^&lt;\/body/i &lt;/div&gt;&lt;div class=&quot;footer&quot;&gt;&lt;a href=&quot;/~blynn/&quot;&gt;Ben Lynn&lt;/a&gt;&lt;/div&gt;' -i $BOOKDIR/*.html
 
 cp $BOOKDIR/pr01.html $BOOKDIR/index.html
 rm toc.tmp</diff>
      <filename>makeover</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>e39c56dc7d659d459b55546e701ce9652bab4681</id>
    </parent>
  </parents>
  <author>
    <name>Ben Lynn</name>
    <email>benlynn@gmail.com</email>
  </author>
  <url>http://github.com/blynn/gitmagic/commit/9b5b4ef73f24d471f9241b89f1dfb4b928f8fd80</url>
  <id>9b5b4ef73f24d471f9241b89f1dfb4b928f8fd80</id>
  <committed-date>2009-06-09T00:02:15-07:00</committed-date>
  <authored-date>2009-06-09T00:02:15-07:00</authored-date>
  <message>Moved translation hints to appendix.</message>
  <tree>74b1f3354b477b5c5994e953fbf2498e6a1ac2b7</tree>
  <committer>
    <name>Ben Lynn</name>
    <email>benlynn@gmail.com</email>
  </committer>
</commit>
