Discussion:
[scribus] making your own Pantone color list
Gregory Pittman
2013-09-20 01:40:14 UTC
Permalink
As we all know, Pantone so far maintains its position to not officially
allow for Scribus to release its color list.
When I checked today, it seemed that the link in the wiki no longer
leads to a zip file you can get from Adobe for the Pantone colors.

Searching around, I found this site:

http://www.printingassoc.com/pmscolor.html

where you can see quite a list of Pantone colors. So here is a new
workaround

1. View the source of this page (Ctrl+U in Firefox), then save the file.
2. Open up this file, and make a copy - you might as well have it end in
.txt, since you're going to destroy it as an HTML file anyway.
3. What you see is standard HTML, with bits like this in it once you get
to the table of colors:

<TD align=middle><FONT
face="Verdana, Arial, Helvetica, sans-serif"
size=1>PMS
100</FONT></TD></TR>
<TR>
<TD width=75 bgColor=#f4ed7c

Your key information here is in 2 parts - 'PMS 100' and '#f4ed7c', the
name of the color and its RGB representation (as the site notes, do not
believe that this RGB is necessarily accurate for this spot color, which
is an ink). Notice how they have (intentionally?) split the name in two,
so it's not easily searchable. It's Ok, we're smarter than that anyway.

4. Now use a text editor that can use regular expressions for Replace. I
used KWrite. The reason for reg exp is so you can put something like
</FONT></TD></TR>\n into the Find field, replace with nothing, to not
only remove the tags but also the carriage return at the end of the
line. There is some variability, but all the same a LOT of
repetitiveness of this HTML file. There are a lot of spaces to contend
with as you go, but again, use the Replace function to get rid of those
en masse.

5. Eventually you end up with a file consisting only of lines like:

PMS 100 bgColor=#f4ed7c

but this is a bit of trouble. Why? Look at a line from a Scribus color
swatch XML file such as you might want to end up with:

<COLOR RGB="#f4ed7c" NAME="PMS 100" Spot="1" />

We want the RGB before the color name, bummer. Now, let's shape our
lines into what we need, again using Replace, out of order, but adding a
comma to split the halves:

NAME="PMS 100" Spot="1" />,<COLOR RGB="#f4ed7c"

6. Here is a small Python script which reads your file a line at a time,
splits it at the comma, then saves in another file with the parts
switched (don't forget the #!/usr/bin/env python at the beginning):

file_object = open('output.txt','w')
for line in open('pmscolor.txt'):
line.strip('\n')
L = line.split(',')
file_object.write(L[1]+L[0]+'\n')
file_object.close()

I tried to strip out the carriage returns at the end of each line, but
it didn't work, so once again, back to KWrite and reg exp to turn
'\n<COLOR' into '<COLOR'. Make sure you scan the file for any mistakes
or omissions.
Now the only thing to do is add the XML tags at beginning and end, with
a suitable name for your Pantone color file, and save with an .xml
extension.

7. Is this legal? AFAIK, it's as legal as a web page displayed openly on
the internet. We've just taken the information from it and transformed
it to something we can use in Scribus.

Greg


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus/attachments/20130919/76940187/attachment.html>
Gregory Pittman
2013-09-20 02:04:59 UTC
Permalink
On 09/19/2013 09:40 PM, Gregory Pittman wrote:
>
> I tried to strip out the carriage returns at the end of each line, but
> it didn't work, so once again, back to KWrite and reg exp to turn
> '\n<COLOR' into '<COLOR'. Make sure you scan the file for any
> mistakes or omissions.
Sorry - change '\nNAME' to 'NAME'. The line was splitting after the RGB
color.

Greg
Gabriel Grosso
2013-09-20 14:45:31 UTC
Permalink
Hi
Thanks for the workaround.
What changes with using this way or using SwatchBooker?

Gabriel


2013/9/19 Gregory Pittman <gpittman at iglou.com>

> On 09/19/2013 09:40 PM, Gregory Pittman wrote:
>
>>
>> I tried to strip out the carriage returns at the end of each line, but it
>> didn't work, so once again, back to KWrite and reg exp to turn '\n<COLOR'
>> into '<COLOR'. Make sure you scan the file for any mistakes or omissions.
>>
> Sorry - change '\nNAME' to 'NAME'. The line was splitting after the RGB
> color.
>
> Greg
>
>
> ___
> Scribus Mailing List: scribus at lists.scribus.net
> Edit your options or unsubscribe:
> http://lists.scribus.net/**mailman/listinfo/scribus<http://lists.scribus.net/mailman/listinfo/scribus>
> See also:
> http://wiki.scribus.net
> http://forums.scribus.net
>



--
----------------------------------
Gabriel Alberto Grosso
flickr.com/gabotrotamundos
Ober?, Misiones
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus/attachments/20130920/9050c448/attachment.html>
Gregory Pittman
2013-09-20 15:45:37 UTC
Permalink
On 09/20/2013 10:45 AM, Gabriel Grosso wrote:
> Hi
> Thanks for the workaround.
> What changes with using this way or using SwatchBooker?
>

Swatchbooker is an external app to generate swatch from appropriate sources.

This new method is simply a way to generate a semblance of an RGB
equivalent of these spot colors, attached to the PMS name of the swatch.
What I showed was how to reduce that webpage down to a list of color
names and RGB values, so that you could then create a usable XML file
for Scribus.

Greg
William Adams
2013-09-20 15:50:24 UTC
Permalink
On Sep 19, 2013, at 9:40 PM, Gregory Pittman wrote:

> As we all know, Pantone so far maintains its position to not officially allow for Scribus to release its color list.

It's available for a license fee --- I'm sure if someone ponied up the money there'd be no problem.

Rather than going through such chicanery, why not just adopt a standard publicly available color profile such as the one GCMI used to promulgate?

Here's a .pdf showing Pantone equivalents:

http://www.ipaper.com/documents/EN/KraftBag/GCMI_COLORS.PDF

More about it here:

http://www.jimdandyboxes.com/flexographicinkcolors.html

Then we could tell users how to create PANTONE spot colours when they work out w/ their printer that they'll be printing w/ such and their printer can tell them what values to use for previewing on-screen. Adobe and Quark making PANTONE spot colours so accessible results in untold millions of dollars of lost productivity every year when printers have to verify that it's okay to convert such back to CMYK, when ad files are rendered unusable when spot colours are used w/ transparency and such conversion doesn't work, &c.

William

--
William Adams
senior graphic designer
Fry Communications
Sphinx of black quartz, judge my vow.
Gregory Pittman
2013-09-20 16:57:46 UTC
Permalink
On 09/20/2013 11:50 AM, William Adams wrote:
> On Sep 19, 2013, at 9:40 PM, Gregory Pittman wrote:
>
>> As we all know, Pantone so far maintains its position to not officially allow for Scribus to release its color list.
>
> It's available for a license fee --- I'm sure if someone ponied up the money there'd be no problem.
>

It would be great if we had such a pony, I guess, but I think there is
also the principle that someone using a Pantone spot color in Scribus is
a direct benefit to Pantone. We're not supplying free swatchbooks or
other things Pantone has for sale, so what's their issue?

Greg
William Adams
2013-09-23 11:50:31 UTC
Permalink
On Sep 20, 2013, at 12:57 PM, Gregory Pittman wrote:

> I think there is
> also the principle that someone using a Pantone spot color in Scribus is
> a direct benefit to Pantone. We're not supplying free swatchbooks or
> other things Pantone has for sale, so what's their issue?

Their issue is that they assert ownership over those numbers as a collection, and control over the usage of ``PANTONE'' as a trademark.

``I think'' does not equal legal advice and is not a protection in court.

Glad to learn that GCMI is already present.

On Sep 21, 2013, at 3:41 AM, Christoph Sch?fer wrote:

> As to Pantone's request for fees for digital colour palettes: One day, corporate greed will be replaced by pragmatism, and there are many alternatives to Pantone, some of which are already part of Scribus.

Agreed.

On Sep 22, 2013, at 3:12 AM, Christoph Sch?fer wrote:

> This is some sort of a clever hack that uses a particular Pantone online repo for mobile apps, but it doesn't actually suit our users' requirements, and it's at best condoned by X-Rite. Moreover, there's a reason for not including this script in Scribus: We can't afford to be sued by X-Rite for copyright and/or trademark abuse.

Which was the gist of my initial post.

William

--
William Adams
senior graphic designer
Fry Communications
Sphinx of black quartz, judge my vow.
Gregory Pittman
2013-09-23 13:23:36 UTC
Permalink
On 09/23/2013 07:50 AM, William Adams wrote:
> On Sep 20, 2013, at 12:57 PM, Gregory Pittman wrote:
>
>> I think there is
>> also the principle that someone using a Pantone spot color in Scribus is
>> a direct benefit to Pantone. We're not supplying free swatchbooks or
>> other things Pantone has for sale, so what's their issue?
>
> Their issue is that they assert ownership over those numbers as a collection, and control over the usage of ``PANTONE'' as a trademark.
>

But there is absurdity here. "ownership over those numbers" -- what?
They don't want anyone to use these numbers? Even if we tack on "as a
collection" -- still absurd for a company who purports to be selling
color-matched inks. As far as "control over the usage of PANTONE", this
is a public, commercial company. They can't control every mention of
their company's name.

In the meantime, we are just trying to help users who wish to specify
Pantone ink in spite of any thoughts we have about their attitude.

Greg
William Adams
2013-09-23 16:06:09 UTC
Permalink
On Sep 23, 2013, at 9:23 AM, Gregory Pittman wrote:

> But there is absurdity here. "ownership over those numbers" -- what?
> They don't want anyone to use these numbers? Even if we tack on "as a
> collection" -- still absurd for a company who purports to be selling
> color-matched inks. As far as "control over the usage of PANTONE", this
> is a public, commercial company. They can't control every mention of
> their company's name.

Take it up w/ their lawyers and discuss it w/ your corporate counsel --- my observations do not constitute legal advice.

> In the meantime, we are just trying to help users who wish to specify
> Pantone ink in spite of any thoughts we have about their attitude.

That's probably going to need to be done conservatively and carefully if you don't want to get lawyers involved.

William

--
William Adams
senior graphic designer
Fry Communications
Sphinx of black quartz, judge my vow.
Joe Zeff
2013-09-23 17:16:43 UTC
Permalink
On 09/23/2013 06:23 AM, Gregory Pittman wrote:
> As far as "control over the usage of PANTONE", this
> is a public, commercial company. They can't control every mention of
> their company's name.

Why not? Coke, Pepsi, Ford and Disney certainly do their best to do
exactly that. That's what trademarks are all about.

About fifteen years ago, a dentist's professional society decided to
have a convention. As it was for all members from around the world,
they decided to call it WorldCon. They had to change it because that
term is in use for the World Science Fiction Convention and trademarked
and, of course, they hadn't asked permission first. Would they have
gotten it if they'd asked? Well, knowing some of the people involved in
running that, both directly and indirectly, probably not.
&quot;Christoph Schäfer&quot;
2013-09-21 07:41:39 UTC
Permalink
> On Sep 19, 2013, at 9:40 PM, Gregory Pittman wrote:
>
> > As we all know, Pantone so far maintains its position to not officially allow for Scribus to release its color list.
>
> It's available for a license fee --- I'm sure if someone ponied up the money there'd be no problem.
>
> Rather than going through such chicanery, why not just adopt a standard publicly available color profile such as the one GCMI used to promulgate?
>
> Here's a .pdf showing Pantone equivalents:
>
> http://www.ipaper.com/documents/EN/KraftBag/GCMI_COLORS.PDF
>
> More about it here:
>
> http://www.jimdandyboxes.com/flexographicinkcolors.html
>
> Then we could tell users how to create PANTONE spot colours when they work out w/ their printer that they'll be printing w/ such and their printer can tell them what values to use for previewing on-screen. Adobe and Quark making PANTONE spot colours so accessible results in untold millions of dollars of lost productivity every year when printers have to verify that it's okay to convert such back to CMYK, when ad files are rendered unusable when spot colours are used w/ transparency and such conversion doesn't work, &c.
>
> William
>

Hi William,

GCMI colours are already being shipped with Scribus since ... I don't exactly remember when, and they're not, by default, compatible with Pantone. All you have to do to use the palette is to make it the default swatch by using Edit > Colours with no document open.

The other link you provided is far from being reliable.

Today, Pantone colour palettes are (mostly) being delivered as CIE L*a*b* files -- at least internally, and even for older Pantone swatch formats we cannot rely on simple (s)RGB or CMYK values. Moreover, Scribus needs to fully support CIE L*a*b* palettes before it can integrate current Pantone files one way or the other.

Technical considerations aside, we mustn't forget legal issues. Colour systems are subject to copyright, and we also have to deal with trademarks.

That being said, Scribus, in its current stable 1.4.x incarnation, already supports more commercial colour systems than any other software. Moreover, we are currently in deliberations with an important commercial vendor, which may result in an unprecedented number of available professional colour systems.

As to Pantone's request for fees for digital colour palettes: One day, corporate greed will be replaced by pragmatism, and there are many alternatives to Pantone, some of which are already part of Scribus.

Christoph
Alexandre Prokoudine
2013-09-21 09:44:40 UTC
Permalink
On Sat, Sep 21, 2013 at 11:41 AM, "Christoph Sch?fer" wrote:

> As to Pantone's request for fees for digital colour palettes:
> One day, corporate greed will be replaced by pragmatism,
> and there are many alternatives to Pantone, some of which
> are already part of Scribus.

Yeah, if only Pantone saw things clearly and created some sort of an
online service to request color sets directly from applications...

Oh wait! http://www.selapa.net/scribus/

Alexandre
Gregory Pittman
2013-09-21 14:08:58 UTC
Permalink
On 09/21/2013 05:44 AM, Alexandre Prokoudine wrote:
> On Sat, Sep 21, 2013 at 11:41 AM, "Christoph Sch?fer" wrote:
>
>> As to Pantone's request for fees for digital colour palettes:
>> One day, corporate greed will be replaced by pragmatism,
>> and there are many alternatives to Pantone, some of which
>> are already part of Scribus.
> Yeah, if only Pantone saw things clearly and created some sort of an
> online service to request color sets directly from applications...
>
> Oh wait! http://www.selapa.net/scribus/
>
>
It works quite well!
Makes my 1.5.0 crash, so I had to run as standalone.

the script does have this disclaimer:

"This software is not affiliated with or endorsed by PANTONE, Inc. ? PANTONE? and other Pantone, Inc. trademarks are the property of Pantone, Inc. ? Pantone, Inc."

so it remains to be seen what Pantone thinks of it. In their traditional
generosity, I'm sure they're just about ready to allow us to release
their palettes with Scribus.

I'll put this link on the wiki page.

Greg
&quot;Christoph Schäfer&quot;
2013-09-22 07:12:26 UTC
Permalink
> > As to Pantone's request for fees for digital colour palettes:
> > One day, corporate greed will be replaced by pragmatism,
> > and there are many alternatives to Pantone, some of which
> > are already part of Scribus.
>
> Yeah, if only Pantone saw things clearly and created some sort of an
> online service to request color sets directly from applications...
>
> Oh wait! http://www.selapa.net/scribus/

This is some sort of a clever hack that uses a particular Pantone online repo for mobile apps, but it doesn't actually suit our users' requirements, and it's at best condoned by X-Rite. Moreover, there's a reason for not including this script in Scribus: We can't afford to be sued by X-Rite for copyright and/or trademark abuse.

Christoph
Alexandre Prokoudine
2013-09-22 11:28:05 UTC
Permalink
On Sun, Sep 22, 2013 at 11:12 AM, "Christoph Sch?fer" wrote:

>> > As to Pantone's request for fees for digital colour palettes:
>> > One day, corporate greed will be replaced by pragmatism,
>> > and there are many alternatives to Pantone, some of which
>> > are already part of Scribus.
>>
>> Yeah, if only Pantone saw things clearly and created some sort of an
>> online service to request color sets directly from applications...
>>
>> Oh wait! http://www.selapa.net/scribus/
>
> but it doesn't actually suit our users' requirements

Why?

> and it's at best condoned by X-Rite

Of course :)

> Moreover, there's a reason for not including this script in Scribus:
> We can't afford to be sued by X-Rite for copyright and/or trademark
> abuse.

Was I suggesting that? :)

Alexandre
Boris Samorodov
2013-09-20 16:18:17 UTC
Permalink
Hi Gregory and All,

20.09.2013 05:40, Gregory Pittman ?????:

> Searching around, I found this site:
> http://www.printingassoc.com/pmscolor.html

Gregory, thanks for the link.

As a side note: there are two "PMS 803" colors (the first one appears
to be a "PMS 8503" one).

--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
Boris Samorodov
2013-09-20 19:40:43 UTC
Permalink
20.09.2013 20:18, Boris Samorodov ?????:
> Hi Gregory and All,
>
> 20.09.2013 05:40, Gregory Pittman ?????:
>
>> Searching around, I found this site:
>> http://www.printingassoc.com/pmscolor.html
>
> Gregory, thanks for the link.
>
> As a side note: there are two "PMS 803" colors (the first one appears
> to be a "PMS 8503" one).

And there are six hex number duplicates:
-----
#003f54 PMS 303
#003f54 PMS 547
--
#007aa5 PMS 307
#007aa5 PMS 641
--
#008c82 PMS 327
#008c82 PMS 3282
--
#c1b5a5 PMS 401
#c1b5a5 Warm Gray4
--
#ef2b2d PMS 1788
#ef2b2d Red 032
--
#f95602 PMS 1655
#f95602 PMS 1665
-----

--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
Jeffrey Merrow
2013-09-20 21:05:26 UTC
Permalink
The duplication of target hex values would simply be 'closest match' to the pantone source identifiers.
This ought to be permitted, and is not considered a duplicate, but an additional match to that destination color. ?Unless, of course one knows the source is NOT that shade, in that case it is a blatant error.
?

There's no point in being grown up if you can't be childish sometimes. -- Doctor Who


________________________________
From: Boris Samorodov <bsam at passap.ru>
To: scribus at lists.scribus.net
Sent: Friday, September 20, 2013 3:40 PM
Subject: Re: [scribus] making your own Pantone color list


20.09.2013 20:18, Boris Samorodov ?????:
> Hi Gregory and All,
>
> 20.09.2013 05:40, Gregory Pittman ?????:
>
>> Searching around, I found this site:
>> http://www.printingassoc.com/pmscolor.html
>
> Gregory, thanks for the link.
>
> As a side note: there are two "PMS 803" colors (the first one appears
> to be a "PMS 8503" one).

And there are six hex number duplicates:
-----
#003f54 ??? PMS 303
#003f54 ??? PMS 547
--
#007aa5 ??? PMS 307
#007aa5 ??? PMS 641
--
#008c82 ??? PMS 327
#008c82 ??? PMS 3282
--
#c1b5a5 ??? PMS 401
#c1b5a5 ??? Warm Gray4
--
#ef2b2d ??? PMS 1788
#ef2b2d ??? Red 032
--
#f95602 ??? PMS 1655
#f95602 ??? PMS 1665
-----

--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve

___
Scribus Mailing List: scribus at lists.scribus.net
Edit your options or unsubscribe:
http://lists.scribus.net/mailman/listinfo/scribus
See also:
http://wiki.scribus.net
http://forums.scribus.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus/attachments/20130920/301f0c1c/attachment.html>
Craig Bradney
2013-09-20 21:37:15 UTC
Permalink
> On 20 Sep 2013, at 23:05, Jeffrey Merrow <jeffmerrow at yahoo.com> wrote:
>
> The duplication of target hex values would simply be 'closest match' to the pantone source identifiers.
> This ought to be permitted, and is not considered a duplicate, but an additional match to that destination color. Unless, of course one knows the source is NOT that shade, in that case it is a blatant error.
>
>

Of course you want a reasonable approximation on the screen, however the important part for the print job is not the hex values for the on screen colour, but the spot colour naming which matches the colour cards you look at off screen.

Craig
Rolf-Werner Eilert
2013-09-23 13:55:16 UTC
Permalink
Thanks for your idea, Gregory. I made a quick and dirty implementation
of it in Gambas, and ended up with some error.

Strangely enough, I had go into the original resource directory to find
a number of color .xml files delivered with Scribus. Isn't there a
standard directory for these? And why are they hidden in the source?

Anyway, according to your idea this is what my program should deliver:

> <COLOR RGB="#f4ed7c" NAME="PMS 100" Spot="1" />

When I offer a list like this, Scribus imports it with all color fields
black and just the original xml code behind it. So I looked into the xml
files provided, and they showed a header and start-end tags, of course.

Adding those, however, resulted in Scribus telling "not an XML color file".

So, what now? Here's an excerpt of what my program produces:


<?xml version="1.0" encoding="UTF-8"?>
<SCRIBUSCOLORS Name="Pantone-Farben">
< Name="PMS 100" COLOR RGB="#f4ed7c" Spot="1" />
< Name="PMS 101" COLOR RGB="#f4ed47" Spot="1" />
< Name="PMS 102" COLOR RGB="#f9e814" Spot="1" />
...
...
...
</SCRIBUSCOLORS>

Do you see any mistakes?

When I looked into the other files, I saw there are more fields, but are
they required?

Rolf
Gregory Pittman
2013-09-23 15:29:07 UTC
Permalink
On 09/23/2013 09:55 AM, Rolf-Werner Eilert wrote:
> Thanks for your idea, Gregory. I made a quick and dirty implementation
> of it in Gambas, and ended up with some error.
>
> Strangely enough, I had go into the original resource directory to find
> a number of color .xml files delivered with Scribus. Isn't there a
> standard directory for these? And why are they hidden in the source?
>
> Anyway, according to your idea this is what my program should deliver:
>
>> <COLOR RGB="#f4ed7c" NAME="PMS 100" Spot="1" />
>
> When I offer a list like this, Scribus imports it with all color fields
> black and just the original xml code behind it. So I looked into the xml
> files provided, and they showed a header and start-end tags, of course.
>
> Adding those, however, resulted in Scribus telling "not an XML color file".
>
> So, what now? Here's an excerpt of what my program produces:
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <SCRIBUSCOLORS Name="Pantone-Farben">
> < Name="PMS 100" COLOR RGB="#f4ed7c" Spot="1" />
> < Name="PMS 101" COLOR RGB="#f4ed47" Spot="1" />
> < Name="PMS 102" COLOR RGB="#f9e814" Spot="1" />
> ...
> ...
> ...
> </SCRIBUSCOLORS>
>

Yes.
The lines should be:

< COLOR RGB="#f4ed7c" Name="PMS 100" Spot="1" />

and so on.

Greg
Rolf-Werner Eilert
2013-09-23 16:08:37 UTC
Permalink
Am 23.09.2013 17:29, schrieb Gregory Pittman:
> On 09/23/2013 09:55 AM, Rolf-Werner Eilert wrote:
>> Thanks for your idea, Gregory. I made a quick and dirty implementation
>> of it in Gambas, and ended up with some error.
>>
>> Strangely enough, I had go into the original resource directory to find
>> a number of color .xml files delivered with Scribus. Isn't there a
>> standard directory for these? And why are they hidden in the source?
>>
>> Anyway, according to your idea this is what my program should deliver:
>>
>>> <COLOR RGB="#f4ed7c" NAME="PMS 100" Spot="1" />
>>
>> When I offer a list like this, Scribus imports it with all color fields
>> black and just the original xml code behind it. So I looked into the xml
>> files provided, and they showed a header and start-end tags, of course.
>>
>> Adding those, however, resulted in Scribus telling "not an XML color file".
>>
>> So, what now? Here's an excerpt of what my program produces:
>>
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <SCRIBUSCOLORS Name="Pantone-Farben">
>> < Name="PMS 100" COLOR RGB="#f4ed7c" Spot="1" />
>> < Name="PMS 101" COLOR RGB="#f4ed47" Spot="1" />
>> < Name="PMS 102" COLOR RGB="#f9e814" Spot="1" />
>> ...
>> ...
>> ...
>> </SCRIBUSCOLORS>
>>
>
> Yes.
> The lines should be:
>
> < COLOR RGB="#f4ed7c" Name="PMS 100" Spot="1" />
>
> and so on.
>
> Greg
>

Hm. That alone won't help either. And the order of RGB, Name and Spot
shouldn't matter, as it doesn't in the other xml files. But there is one
more tag called Register, it's missing here, what is it good for?

When I leave out the whitespaces after < and before />, Scribus won't
complain anymore, but it imports only one single color without any
description.

Rolf
Gregory Pittman
2013-09-23 16:33:18 UTC
Permalink
On 09/23/2013 12:08 PM, Rolf-Werner Eilert wrote:
>
>
> Am 23.09.2013 17:29, schrieb Gregory Pittman:
>> On 09/23/2013 09:55 AM, Rolf-Werner Eilert wrote:
>>> Thanks for your idea, Gregory. I made a quick and dirty implementation
>>> of it in Gambas, and ended up with some error.
>>>
>>> Strangely enough, I had go into the original resource directory to find
>>> a number of color .xml files delivered with Scribus. Isn't there a
>>> standard directory for these? And why are they hidden in the source?
>>>
>>> Anyway, according to your idea this is what my program should deliver:
>>>
>>>> <COLOR RGB="#f4ed7c" NAME="PMS 100" Spot="1" />
>>>
>>> When I offer a list like this, Scribus imports it with all color fields
>>> black and just the original xml code behind it. So I looked into the xml
>>> files provided, and they showed a header and start-end tags, of course.
>>>
>>> Adding those, however, resulted in Scribus telling "not an XML color
>>> file".
>>>
>>> So, what now? Here's an excerpt of what my program produces:
>>>
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <SCRIBUSCOLORS Name="Pantone-Farben">
>>> < Name="PMS 100" COLOR RGB="#f4ed7c" Spot="1" />
>>> < Name="PMS 101" COLOR RGB="#f4ed47" Spot="1" />
>>> < Name="PMS 102" COLOR RGB="#f9e814" Spot="1" />
>>> ...
>>> ...
>>> ...
>>> </SCRIBUSCOLORS>
>>>
>>
>> Yes.
>> The lines should be:
>>
>> < COLOR RGB="#f4ed7c" Name="PMS 100" Spot="1" />
>>
>> and so on.
>>
>> Greg
>>
>
> Hm. That alone won't help either. And the order of RGB, Name and Spot
> shouldn't matter, as it doesn't in the other xml files. But there is one
> more tag called Register, it's missing here, what is it good for?
>
> When I leave out the whitespaces after < and before />, Scribus won't
> complain anymore, but it imports only one single color without any
> description.

My guess is that it's important to have COLOR the first word in the tag.

Greg
Craig Bradney
2013-09-23 17:37:39 UTC
Permalink
On 23/09/13 6:33 PM, Gregory Pittman wrote:
> On 09/23/2013 12:08 PM, Rolf-Werner Eilert wrote:
>>
>>
>> Am 23.09.2013 17:29, schrieb Gregory Pittman:
>>> On 09/23/2013 09:55 AM, Rolf-Werner Eilert wrote:
>>>> Thanks for your idea, Gregory. I made a quick and dirty implementation
>>>> of it in Gambas, and ended up with some error.
>>>>
>>>> Strangely enough, I had go into the original resource directory to find
>>>> a number of color .xml files delivered with Scribus. Isn't there a
>>>> standard directory for these? And why are they hidden in the source?
>>>>
>>>> Anyway, according to your idea this is what my program should deliver:
>>>>
>>>>> <COLOR RGB="#f4ed7c" NAME="PMS 100" Spot="1" />
>>>>
>>>> When I offer a list like this, Scribus imports it with all color fields
>>>> black and just the original xml code behind it. So I looked into the xml
>>>> files provided, and they showed a header and start-end tags, of course.
>>>>
>>>> Adding those, however, resulted in Scribus telling "not an XML color
>>>> file".
>>>>
>>>> So, what now? Here's an excerpt of what my program produces:
>>>>
>>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <SCRIBUSCOLORS Name="Pantone-Farben">
>>>> < Name="PMS 100" COLOR RGB="#f4ed7c" Spot="1" />
>>>> < Name="PMS 101" COLOR RGB="#f4ed47" Spot="1" />
>>>> < Name="PMS 102" COLOR RGB="#f9e814" Spot="1" />
>>>> ...
>>>> ...
>>>> ...
>>>> </SCRIBUSCOLORS>
>>>>
>>>
>>> Yes.
>>> The lines should be:
>>>
>>> < COLOR RGB="#f4ed7c" Name="PMS 100" Spot="1" />
>>>
>>> and so on.
>>>
>>> Greg
>>>
>>
>> Hm. That alone won't help either. And the order of RGB, Name and Spot
>> shouldn't matter, as it doesn't in the other xml files. But there is one
>> more tag called Register, it's missing here, what is it good for?
>>
>> When I leave out the whitespaces after < and before />, Scribus won't
>> complain anymore, but it imports only one single color without any
>> description.
>
> My guess is that it's important to have COLOR the first word in the tag.
>
> Greg
>


Of course, COLOR is what you are describing, the rest are attributes of the COLOR.

Craig
>
Continue reading on narkive:
Loading...