<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div><pre wrap="" style="font-family: arial, helvetica, sans-serif; ">I agree with most comments and I am very happy of what Scribus provides me for free. On the other hand I have also seen what InDesign does and would say that the price difference between 0 and 600 USD for InDesign is justified. It is just a matter of time and profitability of the investment but I admit that sooner or later I will switch to InDesign.
</pre>
<pre wrap="" style="font-family: arial, helvetica, sans-serif; ">I suppose that what InDesign most has that Scribus doesn't is a layer of
people who we might describe as usability experts, who are something of
an interpreter of user needs and requests into features that might be
programmed into the software.
We try to do this now, but it's rather individualized and therefore
disorganized.
Greg</pre><pre wrap="" style="font-family: arial, helvetica, sans-serif; "><br></pre><pre wrap="" style="font-family: arial, helvetica, sans-serif; ">No Greg, Adobe simply has money to pay developers because people buy their software. </pre><pre wrap="" style="font-family: arial, helvetica, sans-serif; ">Unfortunately 500-1000 USD donated to Scribus will not get me the same result as the same money spent to buy an InDesign license. Scribus is great but honestly if you are making money from DTP you'll want the tool to be fast and efficient to maximize your income. </pre><pre wrap="" style="font-family: arial, helvetica, sans-serif; ">I ran the 30 day trial of InDesign and on a similar project InDesign is way faster and memory efficient than Scribus, and I'm not talking about the features like conditional text, tables, data merge, object properties or the integration with Illustrator, which is a lot better than the integration of Scribus with
Inkscape. There are also some very clever tricks in the UI of InDesign, in particular the collapsing palettes.</pre><pre wrap="" style="font-family: arial, helvetica, sans-serif; ">The Scribus development team also showed their capacity to take on board frequent requests (for example fit image to frame and fit frame to image on the image right click menu). This has made working on images quicker but initially the dev team was reluctant and argued that one action was on the image and the other on the frame so they were separated in the UI.</pre><pre wrap="" style="font-family: arial, helvetica, sans-serif; ">And then there's the time when Scribus allows you to set dpi arbitrarily for an image and InDesign just doesn't do it.</pre><pre wrap="" style="font-family: arial, helvetica, sans-serif; ">C</pre></div> </div></body></html>