[scribus] collecting for output

Rolf-Werner Eilert eilert-sprachen at t-online.de
Mon Dec 9 16:58:18 UTC 2013

Dear Martin,

I guess they are reading this mailing list and will answer you 

My C++ knowledge is not that good. I browsed the source (it's 
scribus/collect4output.cpp), but I couldn't make out where the 
appropriate place for that would be. So it will be better to let the 
developers do that ;)

But what do you think about a small script which would be called by the 
person who has collected for output just after output? You would only 
have to copy the script to everyone's computers and maybe connect it 
with an icon. The script can be in the directory together with the files 
or somewhere else. It only has to know the name of the directory then. 
Would you like me to help you making one? As far as I can see, it would 
only have to "chmod 655".

The only drawback would be that the person who has worked on the project 
has to remember to call the script after work and collect...



Am 09.12.2013 16:35, schrieb ZASKE Martin:
> Dear Rolf,
> thank you very much for looking into it.
> We have been happily using collecting-for-output for several years on
> several versions. Our project is somewhat dynamic, so we have often
> reason to move projects between computers, and we like it for
> all-in-one-backup too.
> We have so far understood its usefulness and its limitations. I like it.
> The compress does not claim to compress the entire folder; it just
> nicely compresses the scribus-file within that folder. We like it that way.
> The only issue we are having now, is the workflow between different
> users. I thank you for confirming that on your machine it also does
> assign surprising file-rights for fonts and illustrations. This tells me
> that it is not just some hiccup on our office machine.
> I guess I will after all pose this question to the developers, maybe
> they know where to tweak it. Where would I get in touch with them? Is
> filing a bug really the right thing to do; or should I not first ask it
> somewhere as a question?
> thanks,
> Martin
> On 09.12.2013 15:39, Rolf-Werner Eilert wrote:
>> Hi,
>> you are right. Just tested it, never used it before. The .sla keeps 655,
>> but pictures and/or fonts get 600.
>> Furthermore: Scribus itself sets its file pointer to this new directory.
>> That is confusing. I would expect this to act like an export function.
>> When I check "compress", I get a .gz file which is not unpackable by
>> unzip, the pictures have disappeared from it. But it has 655. Fonts are
>> not packed into it but delivered separately, they have 600.
>> Another confusing thing is that the directory has to exist before, the
>> function cannot make it.
>> Anyway, this is a Suse 12.1 with Scribus 1.4.2, so it is reproduceable
>> even on an older system, and to me it is kinda "not thought up to its end".
>> If you use it this way, I would not use the compress option but include
>> e. g. the fonts. And a script to change the files to 655 BEFORE they are
>> handed on (because at that time, they still belong to the person who
>> worked on them) should be the best workaround to cope with it.
>> Regards
>> Rolf
>> Am 09.12.2013 13:45, schrieb ZASKE Martin:
>>> Dear Peter and list,
>>> The ownership for the Scribus-collected-for-output never changes:
>>> Example:
>>> My wife was the owner of the folder and she has just finished layouting
>>> the children's-page. Then she has somehow managed to tweak the
>>> permissions (my temporary script) and now I got the rights to pull the
>>> entire folder to my home as a copy.
>>> Now the entire folder and all its content is owned by me (user =
>>> martin), since I created the copy.
>>> Now I open the scribus document and I do the layout for the
>>> agriculture-fertilizer-page. And when I am done I do
>>> collecting-for-output.
>>> I was the owner of each photo and of each font, when I started working
>>> with Scribus, but after the output, again the rights get turned to
>>> "owner only, group and others get lost".
>>> So now, before I can tell the next team member that I am done, and he or
>>> she can pull his/her copy, I need to tweak the rights again. Otherwise
>>> the next person would not even have the rights to pull a copy.
>>> So ownership does not seem to be the problem either.
>>> Thanks again and please keep the ideas coming. I am very hesitant to
>>> file a bug, for something I need to understand first. I appreciate those
>>> developers and the last thing they need is to be bothered. I just wonder
>>> where I might find documentation about the collecting-for-output.
>>> I learnt this morning that in dolphin I can display a column for the
>>> "rights" of each file or folder. Very useful for my problem. All morning
>>> I have done layout of another page. And I was using LibreOffice and Gimp
>>> a lot. I can report that the outputs (save or export) of the other
>>> programs produce a default right of "-rw-r--r--" as seems right with my
>>> umask (0022) that I quoted earlier today.
>>>      So I hope this means that my OS is not entirely messed up. In fact it
>>> is a fresh installation of OpenSuse 12.3 as of last week. I still hope
>>> to update, but we are talking hundreds of MB and our African internet
>>> has not even managed this morning to "refresh" the repositories, it
>>> keeps stalling on timeouts.
>>> At this stage I would hope there is some other user on this list, also
>>> using Scribus 1.4.2, preferably on OpenSuse, who would please do a
>>> collecting-for-output and let us know what rights get assigned to the
>>> Scribus files, and to the photos and to the fonts.
>>>      I did not mess with my OS and my Scribus is also fresh and all
>>> default
>>> (just the entire OS and Scribus are running in French, which is needed
>>> for this country).
>>> thanks
>>> Martin
>>> On 09.12.2013 13:19, Peter Nermander wrote:
>>>>> But, all the other files (.png and .ttf) did receive
>>>>> -rw-------
>>>>> which is exactly the problem, why I opened this thread.
>>>> What was the ownership of the original files and the ownership of the
>>>> copies?
>>>>> Peter, if you could help me further please, to localize, where exactly
>>>>> those rights are assigned (almost against what my user-umask
>>>>> prescribes)
>>>>> then I might be able to fix it - and get my whole team into a smooth
>>>>> work-flow.
>>>> I have no knowledge of what operations Scribus use to perform the
>>>> "collect for output", my comment about the umask was just "basic linux
>>>> knowledge", so you might need to get in contact with the devs (file a
>>>> bug report). But first make sure all other issues have been sorted out
>>>> so you can be sure it's a problem with Scribus.
>>>> /Peter
>>>> ___
>>>> 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
>> ___
>> 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

More information about the scribus mailing list