[scribus] collecting for output

ZASKE Martin zm at revue-gugu.org
Tue Dec 10 13:05:46 UTC 2013

Please remember what collecting-for-output is all about:

I have some photos and fonts, I am the user who put them into some
Scribus document, so obviously I got the necessary rights to use those
as I need to.

Now all that should happen (and mainly does) is that Scribus will write
copies(!) of those photos and fonts into a certain folder that I
designate. This folder (and this feature) is meant for output, i.e. to
take either somewhere or to someone (a print shop).

It is my responsibility at this stage, of course, to check whether I
have the rights to share those photos or fonts with other people, but
that is normal. It has got nothing to do with the file rights during
c-f-o of my own document.

So by definition Scribus cannot CHANGE any rights, because it is Scribus
itself who is writing those copies into the folder during c-f-o. And
Scribus is assigning fantasy-rights; and nobody on this list has been
able to explain a possible or worthy reason why this is happening.

If it was meant initially as a security feature, it is useless;
especially since the Scribus files during c-f-o receive different rights
(and text and layout would deserve protection too, not just fonts or
photos; I bet users on this list would agree).

So to help with the bug-fix we need to discuss what Scribus should use
to assign the rights for those fresh copies:

1- the rights of the containing folder?

2- the rights of the user who started Scribus, according to his settings
of umask (I learnt that yesterday, thanks people)

3- the rights of the original file that Scribus was "looking at" before

There are pros and cons for each of those. But all are better than just
creating accessible Scribus files together with inaccessible photos and
fonts against all system settings.

I personally would vote for 2- because I believe that to be the expected
behavior of any normal program which I started: It will write files
according to my umask. Right?

for your consideration,


On 10.12.2013 11:18, Craig Bradney wrote:
> On 10 Dec 2013, at 9:19, Peter Nermander <peter at nermander.se> wrote:
>>> Why is that important?  Shouldn't Scribus follow standard Linux practice
>>> by setting the permissions to the same as the directory they're in?
>> Yes, Scribus should. But is doesn't.
>> As I understand it:
>> Directory har permissions 755
>> The .sla gets permissions 644
>> All images and fonts get permissions 600
>> THAT is the problem. The images and fonts should become 644 just like the .sla.
> I agree that Scribus should maintain ownership settings on files however the idea that it should change permissions on files based on the parent directory permissions is false. There's no standard saying that a directory's settings must determine the file settings at all, anywhere on any OS .
> Craig
> ___
> 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

ZASKE Martin
responsable GʊGʊ
BP 50 - Bassila - Bénin
tel GʊGʊ
tel pers

More information about the scribus mailing list