Recent posts

#1
Linux / Re: Scribus 1.7.2 Imported Col...
Last post by Lynn - Today at 01:52:05 AM
Oh that is weird. I tested it on my computer in 1.7.2 and while my custom color selection persists when there isn't a file open even if I relaunch Scribus, when a new file is made it doesn't inherit my custom color scheme.

When I did the exact same thing in 1.6.4 (set a color scheme with no file open, then made a new document) the new file automatically was given that default color scheme. It feels like this is a file creation bug.
#2
Features / Re: PDF Export Profiles
Last post by Lynn - Today at 01:32:27 AM
You can do something like this currently with the built-in scripter and the pdfFile object - https://impagina.org/scribus-scripter-api/pdf-export/. You can even write a script that does all three exports in one go (see below).

You'd probably need to customize it to fit your use-case - the scripter lets you set lots of pdf export settings by adding more lines of the format pdf.[variablename] = value. I assume the rest of the values are pulled from your defaults set within Preferences -> PDF Export.

I do agree it would be great to have easy access to multiple profiles in the pdf export window.


import os.path
import string

try:
import scribus
except ImportError:
pass

def main():
try:
scribus # pylint: disable=pointless-statement
except NameError:
return

#get base filename and subdirectory so we save to the right folder
fileName = scribus.getDocName()
entry = fileName.rsplit('.sla', 1)[0]

#make pdf file object, set any PDF export settings here
pdf = scribus.PDFfile()
pdf.info = "Invitation"
pdf.version = 14

#example exporting three times with different page ranges
pdf.pages = [1,4]
pdf.file = entry+'Attendees.pdf'
pdf.save()

pdf.pages = [2,4]
pdf.file = entry+'Virtual.pdf'
pdf.save()

pdf.pages = [3,4]
pdf.file = entry+'VIP.pdf'
pdf.save()

return

if __name__ == '__main__':
main()
#3
It doesn't change where the file dialogue opens by default, but you can click and drag any folder to the sidebar on the left to save it as a favorite folder & use that as a shortcut.
#4
Linux / Re: Scribus 1.7.2 Imported Col...
Last post by Portreve - March 06, 2026, 11:13:47 PM
Quote from: a.l.e on March 05, 2026, 08:47:51 AMI gave it a try:

  • I've created a Scribus document.
  • In "Edit > Colors and Fills", I've removed the unused colors.
  • I've created a couple of colors.
  • Saved the .sla document as "colors.sla" and closed it.
  • I've created another new document
  • In "Edit > Colors and Fills", I've removed the unused colors, then used the "Import" button to select the "colors.sla" file I've previously saved and imported the colors.
  • Now I have the colors I've defined in the first few steps in the second document.

On the other hand, I could not get the "Colors Sets" feature in the "Colors and Fills" dialog to work.
Are you using this one?
Yep, that's exactly the one. I can import colors as many times as I want, and they just won't stay. They'll be there in that moment, when I try to access them in a document, or when I open the program again, they're gone.

EDIT: Ok, I just tried what you did, @a.l.e, and all the colors showed up then disappeared again.
#5
Tutorials, Tips and How-Tos / Re: How do I change the defaul...
Last post by AdmFubar - March 06, 2026, 07:42:51 PM
There isnt a direct path to set. But there is a work around. The collect for output option to save a document creates a directory for images, If you have at least one image in your document  the path for getting an image is set to this directory. This path is unique to the document only. It might help the issue you are having.
#6
Features / PDF Export Profiles
Last post by NathanUp - March 06, 2026, 04:49:07 PM
I regularly work on event invitations that have three versions: one for normal attendees, one for virtual attendees, and another for VIP attendees. My file consists of four pages: one for each type of attendee, and a "thanking our sponsors" page including sponsor logos that will be attached to each invitation type. To export these invitations, as I do every time a new sponsor logo is added, I currently have to export three times: page 1 and 4, 2 and 4, and finally 3 and 4. This got me thinking. Wouldn't it be nice to be able to save each export configuration as an "export profile," and then execute them all at once? I don't recall seeing this feature in any other software, so it may be unique. This would also be handy for people who export files for both print and web, or who need different levels of compression for different applications. Here's how I envisage it working:

Profile Creation Workflow
===================

  • User clicks File > Export > Export as PDF
  • User chooses export configuration as usual: output path and filename, crop marks, bleed, max image resolution, et cetera. A new text input field would be available to complete: "Profile Name"
  • Buttons on the bottom of the export dialog consist of "Export," "Save Export Profile," and "Cancel." User clicks "Save Export Profile."
  • User repeats 2 and 3 as necessary.
  • When all profiles are specified and saved, the user clicks "Export" and an export is automatically executed for each profile, abiding by the configuration specified in that profile. 
  • The profiles should automatically be saved as a part of the document.

Profile Management Workflow
=======================

  • To manage profiles, a new tab could be added to the export dialog: "Profiles." 
  • Under this tab, there would be a list of profiles, each with "Edit" and "Delete" buttons. 
  • When the user clicks "Edit," the relevant profile name should be appended to the the title displayed on titlebar: ( | Profile: Profile Name), the "General" tab should open, and the export dialog should be populated with settings as specified during the creation of the profile.
  • After adjusting the settings, the user should click "Save Export Profile." The profile name should then be cleared from the title bar and the "Profile Name" field. If the user clicks "Save Export Profile," a new profile should be created.

Errors and Exceptions
=================

  • If the user ignores the "Profile Name" field and exports, the export is carried out as usual.
  • If the user ignores the "Profile Name" field and attempts to save a profile, they should receive an error message highlighting the "Profile Name" field.

I think that this would a useful and exciting feature for many. Thanks for your time!
#7
Tutorials, Tips and How-Tos / How do I change the default di...
Last post by pops34 - March 06, 2026, 10:58:13 AM
Hello, when I create an image frame and want to import an image, the dialog box that opens displays a file explorer with always the same default folder (home/user/documents - I'm using Linux). It offers a few other default folders in the left frame (root of the hard drive, etc.). I would like to know if it's possible to change the default directory, or create a favorite folder, because when you have to import images repeatedly, it's very tedious to have to find the correct source folder each time, especially if the path is a bit complicated. In the preferences, there's a "paths" tab, but it doesn't seem to allow me to change this default folder. Any help would be appreciated.
#8
Linux / Re: Scribus 1.7.2 Imported Col...
Last post by a.l.e - March 05, 2026, 11:29:42 AM
Now that I've finally found out where the palettes are stored, I can see that, indeed, your file is "wrong".

In more recent 1.7.x versions, the all caps items and attributes have been replaced by ones that have a more sane title case.

This is the test file I've created while doing the test described previously
<?xml version="1.0" encoding="UTF-8"?>
<ScribusColors>
    <Color Name="Base Color" Space="RGB" R="0" G="106" B="255"/>
    <Color Name="Black" Space="CMYK" C="0" M="0" Y="0" K="100"/>
    <Color Name="Complementary" Space="RGB" R="255" G="149" B="0"/>
    <Color Name="Registration" Space="CMYK" C="100" M="100" Y="100" K="100" Register="1"/>
    <Color Name="White" Space="CMYK" C="0" M="0" Y="0" K="0"/>
</ScribusColors>

I guess that only few Scribus users are using custom palettes: I'd prefer to produce a Python script that converts the old palettes in the new format, rather than adding more bloat to the Scribus code...
#9
Linux / Re: Scribus 1.7.2 Imported Col...
Last post by a.l.e - March 05, 2026, 08:47:51 AM
I gave it a try:

  • I've created a Scribus document.
  • In "Edit > Colors and Fills", I've removed the unused colors.
  • I've created a couple of colors.
  • Saved the .sla document as "colors.sla" and closed it.
  • I've created another new document
  • In "Edit > Colors and Fills", I've removed the unused colors, then used the "Import" button to select the "colors.sla" file I've previously saved and imported the colors.
  • Now I have the colors I've defined in the first few steps in the second document.

On the other hand, I could not get the "Colors Sets" feature in the "Colors and Fills" dialog to work.
Are you using this one?
#10
Linux / Re: Scribus 1.7.2 Imported Col...
Last post by Portreve - March 04, 2026, 06:21:27 AM
Actually, @a.l.e, here's a better idea. It's a straight .xml file. Here's the contents:
<SCRIBUSCOLORS Name="Expanded Printers Colors">
<COLOR Spot="0" Register="0" NAME="Black" CMYK="#000000ff"/>
<COLOR Spot="0" RGB="#0000ff" Register="0" NAME="Blue"/>
<COLOR Spot="0" Register="0" NAME="Cool Black" CMYK="#990000ff"/>
<COLOR Spot="0" Register="0" NAME="Cyan" CMYK="#ff000000"/>
<COLOR Spot="0" RGB="#00ff00" Register="0" NAME="Green"/>
<COLOR Spot="0" Register="0" NAME="Magenta" CMYK="#00ff0000"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® 12-0851 TPG Minion Yellow™" CMYK="#00289c01"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® 3514 C" CMYK="#0045ff00"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® 3596 C" CMYK="#0d428503"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Black C" CMYK="#a19e96f0"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Blue 072 C" CMYK="#fff20008"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Bright Red C" CMYK="#00c7bd00"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Dark Blue C" CMYK="#fad10000"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Green C" CMYK="#ed00b000"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Medium Purple C" CMYK="#e8f70000"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Orange 021 C" CMYK="#00a6ff00"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Pink C" CMYK="#2ede0000"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Process Blue C" CMYK="#ff210305"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Purple C" CMYK="#66e50000"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Red 032 C" CMYK="#00dba100"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Reflex Blue C" CMYK="#ffe30000"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Rhodamine Red C" CMYK="#17de0000"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Rubine RED C" CMYK="#00ff3808"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Violet C" CMYK="#e5fc0000"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Warm Red C" CMYK="#00d4cc00"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Yellow 012 C" CMYK="#0005fa00"/>
<COLOR Spot="1" Register="0" NAME="PANTONE® Yellow C" CMYK="#0003ff00"/>
<COLOR Spot="0" RGB="#ff0000" Register="0" NAME="Red"/>
<COLOR Spot="0" Register="1" NAME="Registration" CMYK="#ffffffff"/>
<COLOR Spot="0" Register="0" NAME="Rich Black" CMYK="#996666ff"/>
<COLOR Spot="0" Register="0" NAME="Warm Black" CMYK="#00994cff"/>
<COLOR Spot="0" Register="0" NAME="White" CMYK="#00000000"/>
<COLOR Spot="0" Register="0" NAME="Yellow" CMYK="#0000ff00"/>
</SCRIBUSCOLORS>
Again, it was generated originally by Scribus. Open your favorite text editor, copy-n-paste, save it as an .xml file, and give it a shot.

It's not the file; it's some change in 1.7.x's functionality that's causing this.