Scribus 1.7.2 Imported Colors Disappear

Previous topic - Next topic

Portreve

I've just noticed and did some further testing, but when I import my existing Scribus-generated list of colors, they are brought in, I press OK, they're there, but then when I create a new document, the colors are all missing. In fact, I wind up with three options for both text and object coloring: "none", "black", and "white".

Using the same data file, I am successful in importing these colors in 1.6.x.

AdmFubar

Scribus' new document loads a default template that has just the those few colors. The solution would be to create your default document with the color palette  you want, save and copy it to the default document, or!, make a new template and save it in the templates and load that instead.
Using Scribus1.6.1, 1.7.0 openSUSE 15.6
Advanced hobbyist

a.l.e

I did a small test and could not notice anything wrong.

Would you mind giving a bit more details?
  • How did you create the list of colors?
  • Would you mind sharing a list of colors that can be used to reproduce the issue?
  • What are the steps you are doing before you get to the three only colors?

utnik

if you press 'delete unused' in 'colors and fills' without an open file, you will end up with black, white and registration only. (you need to select a color before 'delete unused' is clickable...)

to solve the problem you need to select a palette (or create a custom one) – again without an open file. if you change the palette when a document is open, your fix will just be for this single file.

utnik

Portreve

Quote from: AdmFubar on March 01, 2026, 08:40:24 PMScribus' new document loads a default template that has just the those few colors. The solution would be to create your default document with the color palette  you want, save and copy it to the default document, or!, make a new template and save it in the templates and load that instead.
That makes absolutely no sense, and is not how I'm interested in using Scribus.

Quote from: a.l.e on March 01, 2026, 08:45:02 PMI did a small test and could not notice anything wrong.

Would you mind giving a bit more details?
  • How did you create the list of colors?
  • Would you mind sharing a list of colors that can be used to reproduce the issue?
  • What are the steps you are doing before you get to the three only colors?

  • I created it by way of starting with the basic default colors that Scribus ships with, then manually looking up the values for traditional printer's colors (reflex blue, rhodamine red, etc.) and adding them in, then exporting that to a file straight out of Scribus. I've never had any problems importing them as my default list of colors in any prior version of Scribus I've been doing this with.
  • Sure, I can do that. What's the best way of uploading my exported color file so it can be examined?
  • If I do nothing, I only have those three colors. If I import my color file, I ultimately have only those same three colors.

Quote from: utnik on March 02, 2026, 12:07:13 AMif you press 'delete unused' in 'colors and fills' without an open file, you will end up with black, white and registration only. (you need to select a color before 'delete unused' is clickable...)

to solve the problem you need to select a palette (or create a custom one) – again without an open file. if you change the palette when a document is open, your fix will just be for this single file.
That's exactly how I do this. It's worked in Scribus 1.4.x, 1.5.x, and 1.6.x.

Portreve

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.