Hand-merge from borked repository. Main changes are a Ruby version (with

[xml-template] / doc / intro.txt

diff --git a/doc/intro.txt b/doc/intro.txt
index 448ded6c6138d2a81103ddc5b5fe88ba92579606..f4f7e978d23fec4c2e320d6f16c293b2adb54302 100644 (file)
--- a/doc/intro.txt
+++ b/doc/intro.txt
@@ -16,9 +16,9 @@ favourite distribution and do "bzr get http://bzr.sesse.net/xml-template/"
 to check out the code and this documentation.
 
 There is a lot to be said about design philosophy, but let's first give a
-simple example to give you the feel of how it works. (The example is in
-Perl, but there are also functionally equivalent PHP and Python versions,
-and more languages should probably come soon.)
+simple example to give you the feel of how it works. (The example is in Perl,
+but there are also functionally equivalent PHP, Python and Ruby versions, and
+more languages should probably come soon.)
 
 Template (simple.xml):
 
@@ -249,8 +249,8 @@ The main thoughts behind XML::Template have been, in no particular order:
    the entire DOM with wrappers for each language. (Thankfully, by relying on
    the DOM support in each language, the code so far is under 200 lines per
    implementation, so maintaining this hopefully shouldn't be much work.)
-   As proof-of-concept, I've got Perl, PHP and Python implementations that work
-   and feel largely the same -- Ruby and other implementations are welcome.
+   As proof-of-concept, I've got Perl, PHP, Python and Ruby implementations
+   that work and feel largely the same -- other implementations are welcome.
    (This is backed up by a test suite, which ensures that all the different
    implementations return structurally equivalent XML for a certain set of
    test cases. Porting to a new language is not difficult, and once you've