Recent Posts

Pages: 1 2 3 4 5 6 7 [8] 9 10
General Discussion / Re: Another Possible New Scribus User Looking For A Path
« Last post by Derek on August 09, 2017, 12:40:49 pm »
Thank you. Garry and a.l.e. All very good points.

The one about handing over a file that'll only open in a development version of Scribus is, I think, the show-stopper. I have past experience with software design,  development and testing but, TBH, I'm not finding the learning curve for 1.5.3 easy and It would be unreasonable to expect others to be happy with it.  Given the exceedingly long history of the transition from 1.4 to 1.6 I cannot be confident that the next stable release will be launched any time in the next couple of years. Certainly not a complaint - just the way it is and what I have to plan around. I'll also need to test that what I produce in Linux also works in Windows (but I won't be able to test OS/X).

I'll be installing the current stable release today. I'll then need to see how it differs from 1.5.3 and see if it can do all I need to do. The magazine is probably not the most complex publication being produced in Scribus and, being greyscale due to printing limitations, simpler than most. I'd be surprised if the official current stable release can't cope.

The real attraction to 1.5.3, for me, was the possibility of being able to open Publisher files but, TBH, that doesn't appear to be working well for me at the moment. I seem to be gravitating to creating the magazine from scratch, which gets me through the learning curve quicker. I have a contributor who sends copy in Publisher format but that's only a bit over 2 pages a month. I'm not about to push her into the Scribus learning curve. In the worst case - open it in Publisher and copy/paste the components out or save it as an image.

Linux / Re: Scribus-1.5.3 Segfault on Slackware-14.2
« Last post by a.l.e on August 09, 2017, 11:57:42 am »
with so little details on what's installed in your computer and what exactly is the error (if you run scribus inside of a debugger (gdb) you might get more details).

what you can try is to get the current trunk sources (from the team's svn or from github community mirror), compile that code and see if it works.
this might or not be different than what slackbuild is doing.
General Discussion / Re: Another Possible New Scribus User Looking For A Path
« Last post by a.l.e on August 09, 2017, 11:55:11 am »
garry is right.

one small complement from my side: start with 1.4.

if you're happy with stick with it.

if you miss something important, try 1.5 and see if it's fixed / implemented there.

at the end judge what you prefer. keeping in mind that 1.5 is a moving target. it moves slowly, but it moves (in big leaps if you stick to the development releases and don't use the latest snapshots)
General Discussion / Re: Another Possible New Scribus User Looking For A Path
« Last post by GarryP on August 09, 2017, 11:23:13 am »
Welcome to the forum Derek.

Personally I would advise that you use the current stable 1.4.6 version of Scribus rather than any developmental version. There are various reasons for this, some of which are listed below:

The stable version has been around - without changes - for at least 18 months. This means that almost all of the usual bugs and weirdness have already been encountered and fixes/work-arounds are known. Because of this, if you come up against a problem it's likely that someone else has already been in the same situation and can advise on what to do. Also, more people are using the stable version so, even if you have a unique issue that's not been seen before, there are more people that are likely to be able to help and get you back up-and-running quicker (very handy if you have deadlines).

Some people are not comfortable with using developmental versions of software. Because of this, if you expect that someone else will take over the reins of editorship, using the stable version will mean that more people could be potential candidates. I.e. If you use 1.5.x and try and pass it on to someone who will only use 1.4.6 then they're not going to be able to edit the document as 1.4.6 cannot open 1.5.x documents. Best to keep to the version that most people will be comfortable using.

While the Scribus team frequently suggests that the core of the developmental versions is pretty stable for most users, if you are coming to Scribus afresh then it will be practically impossible for you to know which functions are core functions and which are not. This means that you will have no way of knowing which functions you should stay away from because they could cause trouble. As you don't know which functions are experimental you could end up having a lot more problems than you would wish for.

It can also be more difficult to get the latest developmental version of Scribus up-and-running. There are usually builds for Windows and OSX but I've heard that it can be difficult to get 1.5.x running on Linux depending on which version of which flavour of Linux you're using. And any future editor may not want to change Linux flavour just to use Scribus.

Also, the latest developmental version can change significantly from time to time which means that the developmental version that you use could be very different from one that someone else is using. Because of this, you could encounter problems where some functions either no longer exist or work in very different ways. Passing documents between people using different developmental versions could be a nightmare (especially if you have deadlines).

In addition to this, documentation for Scribus is patchy at best, and that's for the latest stable version. Most of the documentation that exists was written prior to 1.4.6 but is still pretty relevant to 1.4.6. A lot of the UI for 1.5.x has changed quite considerably and so most of the current documentation would have to be interpreted - rather than just followed - and that will make the learning experience much harder than it needs to be. Documentation for the developmental versions of Scribus - especially the new functionality - may not be around for a long time (if ever), so experimentation may be required.

So, all said, I would stick with 1.4.6 if I was you. It's been around for ages, how it works is well-known, and it's more accessible to more people.

As for your longer-term goal of importing content into Scribus, that's something that could well be possible but it really depends on specifics and how much you want to automate things. Probably best not to think about this until you need to go down that road. Once you need to think about it I'm sure there will be people who can help.

I hope what I've said has made it easier for you to decide on your next steps.
Linux / Scribus-1.5.3 Segfault on Slackware-14.2
« Last post by scriber on August 08, 2017, 08:36:23 pm »
Hi all,
I'd like to try scribus 1.5, but my seems to be just a 1.4.6 package for linux distribution: Slackware 14.2 64 bit.
I finally found a "Slackbuild" script to create a package of 1.5.3 scribus version, so I prepared the building directory and then launched the compile. All seemed working for the best: no errors returned and a new package installed.

But... when I launch "scribus" from the shell it return "segmentation fault". Why?
How could I know what's the problem?

Is there some slackware user that work with a working 1.5.x Scribus version?

Thanks a lot in advance!
General Discussion / Another Possible New Scribus User Looking For A Path
« Last post by Derek on August 08, 2017, 07:14:13 pm »
Hi All,

I'm the editor of a monthly community magazine which I inherited in Microsoft Publisher. I'm also fairly new to Linux. I'm on a mission to ditch everyting that's Microsoft branded - ever since Windows 10 started hijacking my laptop to install updates. I'm on a not very fast rural broadband connection, so a major update can take up to 8 to 10 hours. For some reason the Microsoft Monster always makes its presence known just after my copy deadline, during editing or before my print deadline.  >:(

My Linux Mint installation, on the other hand, is very polite. It never interferes with my life.  8)

Microsoft rant over. It's on it's way out of my life. For the first time in my life I feel free!  :)

Now, the question of the magazine which I currently edit in MS Publisher 2010 in a Windows 7 virtual machine. It's a bit graunchy and slow - my 64 bit hardware won't run 64 bit virtual machines. WINE isn't a good solution as MS Publisher doesn't run very well under WINE. It's rated as unstable and unusable for production by WineHQ. When the time comes to hand it on I, strictly should hand it over to the next incumbent in Publisher. However, I can see that there may be advantages in migrating to Scribus. Mostly that Scribus is available for Mac, Windows and Linux at zero cost for the next editor if they would rather not have to buy MS Publisher.

I've started with the Scribus learning curve. I've created a passable copy of the front cover  of last month's edition, and will carry on with some of the boilerplate pages (parish directories and advertising that are carried forward from month to month). For this I've installed 1.5.3 - the development version. Bearing in mind that I need reasonable stability, but don't mind hitting problems along the way, would it be advisable to take a step back to the official stable release before I get too far down the road with 1.5.3, or is 1.5.3 stable enough to continue with?

I also maintain the publication's sister web site - mainly an event calendar with some front-page news items - in WordPress. A long term goal is to be able to download the month's new web content in a format suitable for easy (enough) import into Scribus - accepting, of course, that some formatting will be necessary.

Given that I am far from experienced with Scribus does this sound, to those of you who are, like a sensible approach? Are there any major pitfalls and pratfalls I should be aware of? The first of these, I think I'm beginning to realise, is that the learning curve and documentation are likely to be very offputting for possible future editors  - though I am trying to find suitable volunteers who might want to take up publishing as either a full- or part-time career and, so, might benefit from learning Scribus which they may find used by future employers/customers. :-\

Beginner Talk / Re: Disappearing object box while trying to move a guide line
« Last post by a.l.e on August 04, 2017, 02:41:13 pm »
there is a ticket for it .

and, as i wrote in the ticket, now that we have snapping among items the feature would be even more welcome : - )
Beginner Talk / Re: Disappearing object box while trying to move a guide line
« Last post by Nermander on August 04, 2017, 02:23:34 pm »
It would be a nice feature if guides would honor the snap settings (I just tried in 1.5.2 and the guide didn't snap, while a drawn line did snap both to the edges and the center of test object).

Beginner Talk / Re: Disappearing object box while trying to move a guide line
« Last post by a.l.e on August 04, 2017, 11:13:13 am »
ok, i think that i see what you mean...

if if i would never do it the way you're doing it, it's indeed a bit awkward to see the item deselected and reselected afterwards.

i've filled a ticket for this:

anyway, you will probably want to use the snapping to item... or just the "edit > manage guides" to place the guide at a given coordinate.
with 1.5.3, your way is probably the least comfortable one...
Beginner Talk / Re: Disappearing object box while trying to move a guide line
« Last post by a.l.e on August 04, 2017, 11:06:36 am »
from your description it's hard for me to say what you are doing "wrong".
or what scribus is doing wrong

but if you activate the "page > snap to item" option, you can just align the items to each other (even center to center)...
Pages: 1 2 3 4 5 6 7 [8] 9 10