For the basics, yes. For some of the more advanced features, perhaps not so much.
Scribus’s interface will be familiar to those who have used QuarkXPress and InDesign in the past. There are tool bars (which initially are part of the window but which can be detached to create the feel of a QXP or ID interface), and the Properties palette combines quite a few features found in ID and QXP palettes and dialog boxes and can be kept open in the same manner as ID floaters. Switching between individual palettes is as easy as clicking on a title bar.
Read more on A Look At Scribus…
For the basics, yes. For some of the more advanced features, perhaps not so much.
Scribus’s interface will be familiar to those who have used QuarkXPress and InDesign in the past. There are tool bars (which initially are part of the window but which can be detached to create the feel of a QXP or ID interface), and the Properties palette combines quite a few features found in ID and QXP palettes and dialog boxes and can be kept open in the same manner as ID floaters. Switching between individual palettes is as easy as clicking on a title bar.
The essential workflow paradigm is also respected. Text goes into text frames, graphics into graphic frames. Things can be stacked atop other things, familiar things such as styles and master pages are available.
Like someone going from a QXP shop to an ID shop (or vice versa), one has to spend some time getting to know the program; some things are not in the same places, and some things are not in obvious places at all. For example, above where I attempted to find access to specify clipping paths, the title of the dialog, “Extended Image Properties”, didn’t immediately suggest to me that this is where I would find the clipping path list; moreover, it took a while to find (It turned out to be on the contextual menu or from the Item dropdown), and the online help was of no help in this case. Even when I had finally found this window and had selected the Paths tab it was kind of unclear what the palette did; its function had to be intuited, but once found, it was easy to use.
As we’ve said before, the program is a work in progress and the interface shows these growing pains. Zooming and panning were touch and go; window-zooming operated randomly, making the safest way to pan and zoom clicking with the mouse and using the scroll bars. Some of the controls on the Properties palette were undependable; the Edit Color button wouldn’t open the corresponding dialog box; we had to get that one from the menu dropdown. A particularly frustrating problem in AuqaScribus’s Aqua skin in the current release is the inability to enter text in text boxes by any other method but the Story Editor (although it worked fine in the other skins).
Another irritating problem was the gradient ramps in the Color panel of the Properties palette. Gradient stops could be added to the ramp with a single click, but not a thing I could try would get rid of them once there. Anyone building a gradient would be advised to duplicate the color first.
This being said, the interface in AquaScribus is very polished and every skin included looks very good. There’s even a “Platinum” skin for those of us who fondly remember the OS 9 look, and a Windows-style skin as well. Our text-box problem has been referred to the Scribus team, and this may well be corrected in the next release.
Whether or not a layout artist should add Scribus to their repertoire depends on where they’re coming from and where their needs are. It is a pleasingly complete application that can be used to put together layouts–the Scribus team has done its homework about what a layout artist might need and is working to satisfy most of those needs.
As it stands the application still needs to develop before it could be used in production settings with which we are familiar. The output is fabulous but it is available in two forms only–PDF and the native Scribus document (.sla) style. While most service bureaux accept PDFs there is also the question of whether the documents produced by Scribus will fly with individual providers. In as much as it is unlikely (as far as we know currently) that your local bureau will have Scribus set up, they may be of little or no help in diagnosing problems, and they certainly wouldn’t be able to accept native .sla files. Support, while knowledgeable and friendly, is provided by volunteers, who may not be able to address concerns straight away.
In its current stage of development we see Scribus as an application more suited to the needs of the independent designer or hobbyist who has a little more hackerly mojo than the standard end-user (and not a lot of cash to lay down on professional packages like QuarkXPress or InDesign).
This is not to say that Scribus is of poor quality: on the contrary, the production overall is quite polished, and when installed it seems to run with few problems. Rather we’d say that one who likes the open source alternative should keep their eyes on Scribus. It’s in a stage of development now that suggests that, as it nears maturity, with the passion and obvious devotion of the Scribus team, this could be the Open Source layout tool.


Worldlabel is a source for equivalent Avery® labels sizes and free label templates for designing.
Does it import Quark XPress files or Adobe InDesign files?
Hello, David. Thanks for the comment.
Sadly, no. Scribus does not import .qxd or .indd files and it looks like support isn’t in the offing any time soon. The Scribus online documentation actually attemps to explain why.
If I may be allowed the indulgence of paraphrasing:
1. Format Complexity: DTP file formats are reputedly amongst the most complex file format of any type. The help quotes an unnamed designer as comparing the Pagemaker document spec to “a 2m x 3m flow chart diagram with 6 point type”, then points out that it wasn’t until InDesign 2.0 that PM file import could be considered reliable.
2. Formats are proprietary: the formats are sometimes patent-protected and documentation is confidential, and reverse-engineering is something that could get them in deep legal trouble that they do not have the resources to meet. Interestingly, the documentation mentioned that they at one time had a .qxd importer in testing, but Quark apparently told them to bear off.
3. Wise use of resources: they simply feel that (perhaps partially as a result of the above), given the available pool of talent and effort, that energy at this time is best put toward developing a better Scribus, and that working on import filters is something of a distraction. Judging by the amount of development they’ve done with it, I’d say it was a pretty good call.
At this point the documentation suggest using EPS, SVG, or PDF exchange to work with other designers on other platforms. Most likely that would look to mean rebuilding these files under those other platforms.
DESIGNORATI
Hi!
Thanks for this favourable review. I would agree with most of the UI issues you raised and I promise we will address those on the road to Scribus 1.4. Especially new features like clip paths often start at some obscure place and wander to a reasonable place later when we get feedback from our users.
Some notes:
Scribus also exports printshop ready PostScript, just print to a file.
The paragraph on graphics formats mixed up PDF and PSD: Scribus does *not* import PDF yet, it can only place PDF as raster graphic in an imageframe.
PSD import is quite advanced though.
Scribus imports PS, EPS, SVG and OO Draw as vector formats — with varying quality. Improvements for that and also PDF import as vectors is on the roadmap.
Oh, yes, and a new bugfix release is available: 1.3.3.2. :-)
/Andreas
Andreas:
Thanks for your comment. I must give you credit for your commenting attitude: I’ve seen varying experiences with open source application providers that run from very good to very bad, and yours rates pretty hight.
I say that because there are, as you might be aware of, various open source developers who deal less well with commentary. While my review of Scribus was, in the preponderance, positive, there were items which I was less than impressed with; you dealt with that criticism with class. Since my overview of Scribus was focused on the technical, I couldn’t put it in that one reason I think that Scribus may well make it over the long term is because of the positive, affirmative engagement that Scribus team has about complaints and gripes I’ve experienced to date. I can, however, say that here.
Also, thank you for rectifying my comment on the PDF/PSD point. I’ll correct that with an update to the article.
You’ll also notice that I’ve announced the release of your 1.3.3.2 number. I was planning to do that before I saw your comment.
Good luck on your continuing development of Scribus!
DESIGNORATI
Is it possible to contact administration?
Thank for all