![]() ![]() I’ll be looking at both Scribus 1.4.5 and Scribus 1.5.0. I’ll be using a Mac most of the time, but I’ll also take sneak peeks at the Windows and Linux versions along the way. ![]() What I intend to do here is keep track of my questions and the answers I found.Īnyone else in the automation game is bound to have similar questions and might find my notes useful. I just spent half an hour with Scribus and its documentation, and as far as I can tell, the available documentation is not a good resource for the kinds of questions I have as an system designer and automator. ![]() As I go, I try to map things I know from other environments onto things I discover in Scribus. I’m looking for things that I’m familiar with. Getting into Scribus will be different for everyone. ![]() And Scribus is definitely powerful enough to be useful for a range of real-life projects. I want to make sure I can help automate projects where Scribus is an option. Scribus will only improve if more people start using it it’s a chicken-and-egg situation. This time around I decided to look mainly at what it can do, rather than concentrate on what it cannot do. As far as I could tell, Scribus was nowhere near as powerful as InDesign, so it would not be an option for many people. I looked at Scribus a while back and did not get very far before I lost interest. So, after ten years of neglecting it, I’m getting back up to speed on automation with QuarkXPress 2015, and I am also looking at Scribus. The company becomes increasingly erratic and difficult to work with for a third-party developer. As far as I can tell, Adobe is ‘doing a Quark’ on a large subset of its users. I bit the bullet – I am going to dig into Scribus, and add it to my toolkit.Īdobe is not what it used to be. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |