Scribus 1.5.4 Download

1 view

Skip to first unread message

Charise Zelnick

unread,

Aug 3, 2024, 11:25:28 AM8/3/24

to zendelasa

Hm, now I found an old forum thread at insert editable text frames in master page that suggests that this is not what master pages are for. If this is still true, that means the tutorial and even that on the Scribus wiki are plain wrong. At least they give a false impression on what the feature is. They say at Working with Master Pages - Scribus Wiki

The objects belonging to master pages cannot be changed in the normal Edit Mode. There is a good reason for it, since it could easily happen while working with a document that something on a master page would be unintentionally moved or changed.

edit:
Just tested the scrapbook feature. It works but defeats the purpose of masters. As you have to paste the layout into every page. Masters are usually a means of fixing the layout throughout a section of a document. Particularly useful when non designers are to fill out content.

Yes! You are correct. My comment was more a general one about the scribus feature. Usually you would have one master page that defines the layout including the image frame for a simple project like a photobook. Scibus just does it differently!

A master is like a background that you can quickly apply to many pages. Objects on a master appear on all pages with that master applied. Master items that appear on document pages are surrounded by a dotted border. Changes you make to a master are automatically applied to associated pages. Masters commonly contain repeating logos, page numbers, headers, and footers. They can also contain empty text or graphic frames that serve as placeholders on document pages. A master item cannot be selected on a document page unless the master item is overridden.

Masters can have multiple layers, just like pages in your document. Objects on a single layer have their own stacking order within that layer. Objects on a master page layer appear behind objects assigned to the same layer in the document page.

If you want a master item to appear in front of objects on the document page, assign a higher layer to the object on the master. A master item on a higher layer appears in front of all objects on lower layers. Merging all layers will move master items behind document page objects.

I am annoyed by that every time I use Scribus, too. My personal workaround is to have guides around the recurring image position and snapping the images to those. Having fillable image frames on master pages would be so nice.

It becomes less annoying when you realize that you can use the scrapbook for that purpose. When you do not drag&drop scrapbook elements onto the page but double-click them with the page you want them highlighted, all elements are positioned at their original position. Then you can drag images onto the frames. Unfortunately, you then have to resize them within the frame to better fill the frame, which I am using a script for. If you want to have templates for double pages/spreads, you have to highlight the right page to have the elements in the right position.

It works pretty well. I read through the tutorial here: _Albums several times, always thinking that it is cumbersome to have to align the scrapbook layouts on the page, but with double klicking it works pretty well.

@houz: There are still some little issues I have: The first I already mentioned, the images are inserted way too large, I assume they are scaled to match assumed printing dpi or display ppi. That makes no sense for me, a reasonable initial scaling would have the image filling the frame in one direction and centered in the other direction, such that the frame is filled.

The second issue is that you can position an image such that within the frame there is space around the picture. IMO the image borders and scaling should be lockable to the frame dimensions, such that there are no borders within the frame.

I am just trying out EndeavorOS (xfce version) on an ex-win7 mini-tower. I like it - very impressed with the speed.
I have installed Scribus-1.5.7, among other things, and even when running alone, every time I launch scribus, after initialising, as soon as it draws the application window, it displays a message box: scribus crashes due to signal #11.

Googling for this, it appears as a bug a number of times over the years, supposedly fixed at that time. The most recent was an Arch bug report from last Summer, described as low severity, and no indication of having been resolved:

Limit to suite:[buster][buster-updates][buster-backports][bullseye][bullseye-updates][bullseye-backports][bookworm][bookworm-updates][bookworm-backports][trixie][sid][experimental]Limit to a architecture: [alpha] [amd64] [arm] [arm64] [armel] [armhf] [avr32] [hppa] [hurd-i386] [i386] [ia64] [kfreebsd-amd64] [kfreebsd-i386] [m68k] [mips] [mips64el] [mipsel] [powerpc] [powerpcspe] [ppc64] [ppc64el] [riscv64] [s390] [s390x] [sh4] [sparc] [sparc64] [x32] You have searched for packages that names contain scribus in all suites, all sections, and all architectures.Found 9 matching packages.