var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-17626091-1']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
-> Config management
-> Localization management
-> Strong typing - no deviation from the standards
-> Multi-channel publishing
-> Integration with business applications
-> Dynamic content delivery
-> Conditional processing
-> Profiling and Re-use
-> Cost savings in the long run
-> Blah, blah, blah
So, if you are looking to achieve the above, the following comparison may help you as a starting point for comparing AuthorIt and DITA (click on the image to enlarge it):
1 comment:
Hi Gyanesh,
Thanks for starting this interesting thread. I've updated some elements in your table and will email you a copy.
Also, DITA itself doesn't provide localization management (LM), but it helps to have your XML in Topic level files. A user will need a DITA CMS with specific LM functionality. Or use 'modifiction dates' and manage localizations manually.
Matt (Author-it Software Corporation)
Post a Comment