Take the time to find out how you can get - and properly keep up-to-date - the "bleeding edge" version (most likely by compiling it yourself). You can't take a 1.5.2 document back into 1.4.6 Scribus documents aren't backwards compatible.)ģ. Use the stable version until you can go no further, then create a copy of your document and take that over to the latest version to add the "extras" while you still have a stable version of the document you can go back to if you get into trouble. It's not perfect and it doesn't have all of the latest bells and whistles but if you're working to a deadline and need answers quickly then that's the best option.Ģ. ![]() Most people use it and you can get support quickly. So what does all this mean? In my opinion there are three reasonable options:ġ. Because of this someone will probably recommend that you install a copy of the latest version you can find and see if that makes a difference. In cases like this it's very difficult for anyone to bug-fix as it can be very difficult to find/compile the exact version the problem is occurring in in order to see what's going wrong. This means that one person's 1.5.x which was compiled last week probably won't be the same as another person's 1.5.x which was compiled today. Not only that, but for some developmental versions you can have a lot of different "sub-versions" all masquerading under the same version number, all with slightly different functionality as bugs get fixed and the changes get implemented into the latest one. I've seen plenty of "bugs" reported that are just the result of people not knowing what they are doing. SIDEBAR: If someone is a Scribus beginner and they come across a problem with a developmental version, how do they know if the problem is a bug or whether it's a new feature or they're just not using the software correctly? They have no baseline for comparison and people who haven't used the latest version won't know about the new features. Also, developmental versions are, by their nature, unstable which means that they might contain features that haven't been tested fully or they might do things in a different way. On the other hand, developmental versions are used by a much smaller subset of the Scribus user base (judging by the SourceForge weekly downloads data) and as such, when a problem occurs, there are fewer people that can help which means that a solution can take longer to find. In these cases a solution is usually quick to find and you can move on with your project. This means that if you have a problem with the stable version it's much more likely that someone already knows about it and can advise accordingly. ![]() ![]() This means that most people who use it on a regular basis know how it is supposed to work and what weird little "ticks" it sometimes does which aren't wanted but are expected. That version has been around for quite a while and its functionality is well known and documented as a lot of people use it. For most people I'd recommend them sticking with the latest stable version (currently 1.4.6).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |