README.rdoc in tracksperanto-2.9.3 vs README.rdoc in tracksperanto-2.9.4

@@ -1,13 +1,7 @@
-= Tracksperanto
-
-* http://guerilla-di.org/tracksperanto
-
 {<img src="https://secure.travis-ci.org/guerilla-di/tracksperanto.png" />}[http://travis-ci.org/guerilla-di/tracksperanto]
 
-== Description
-
 Tracksperanto is a universal 2D-track translator between many apps.
 
 == Why Tracksperanto?
 
 Historically, every matchmoving app uses it's own UI for tracking 2D features.
@@ -61,22 +55,24 @@
 == Format support
 
 Import and export support:
 * Nuke v5 script (Tracker3 nodes, also known as Tracker in the UI - this is the node that you track with)
 * Shake tracker node export (textfile with many tracks per file)
-* PFTrack 2dt files (version 4 and 5)
+* PFTrack 2dt (version 4 and 5) anf PFMatchit/PFTrack 2011 point track exports
 * Syntheyes 2D tracking data exports
 * 3DE point exports (as output by the default script) - versions 3 and 4
 * MatchMover Pro .rz2
 * MayaLive track export (square pixel aspect only, you will need to write some extra code if your tracks are based on nonsquare pixels)
 * Flame .stabilizer file
 * Boujou feature track export
 
 Import only:
-* Shake script (Tracker, Matchmove and Stabilize nodes embedded in ANY shake script)
+* Shake scripts (Tracker, Matchmove and Stabilize nodes embedded in ANY shake script)
+* MatchMover RZML files
 
 Export only:
-* Ruby (will make calls to Tracksperanto to create trackers/keyframes)
+* AfterEffects .jsx script that creates one null object per tracker (run through the script editor)
+* Ruby (will make calls to Tracksperanto to create trackers/keyframes) - useful if you want to play with trackers as data
 * Maya locators (animated locators on an image plane)
 
 == Modularity
 
 Tracksperanto is very modular and can process data passing through it (like