News:
Problems registering, no confirmation email - see http://wiki.scribus.net/canvas/Forums_Registration
Recent posts
#41
Beginner Talk / my own templates don't show up...
Last post by inkfountain - September 09, 2024, 03:38:26 AMI saved a couple of documents as templates, but they do not show up on the chooser when I try to create a new document from a template. I can find them in the folder where I stored them on my computer. How can I make them show up in the template chooser? Where am I going wrong?
#42
Code / Re: Best forum
Last post by MrB - September 08, 2024, 05:57:14 PMQuote from: BN_Dev on September 08, 2024, 07:28:12 AMMy hope is if the features are possible and the patches are accepted, and the cost to sponsor the development is comparable to the cost of QXP/CS/QPP NG, then it would be a no-brainer for us to switch production to being fully open-source. I'm encouraged one of the roadmap wiki pages has some things on similar to what we need so hopefully the discussions will be fruitful.
Hi Paul
We'd be more than happy to review proposals and code for inclusion.
As you've identified, quite a portion of the wiki needs updating but we can provide direct responses to questions.
Note 1.6.x is our stable branch. 1.7.x is our development series where most development occurs - significant changes to the UI, table of contents and index generation are there.
Scribus is used in some newspapers and magazines, with some good examples from India in particular. Some examples come up on this Facebook page at times: https://www.facebook.com/groups/scribus/
thanks
Craig
#43
Code / Re: Best forum
Last post by MrB - September 08, 2024, 05:43:31 PMThis forum plus the bug tracker, along with IRC for live chat, are the best methods to discuss development.
#44
Code / Re: Best forum
Last post by Nermander - September 08, 2024, 09:57:33 AMIf you can "sponsor" with developer time to develop the code this is probably the best way. It has been discussed many times before that the main problem with the development is time, not money. And also donating money causes issues when it comes to taxes etc.
But there are features in Scribus that were developed as Google Summer of Code projects and and think a lot of the support for complex script was developed with support from the government in a country who wanted good open source support for their language (it might have been Tamil, but I am not 100%).
So contributing with code is the best way to help.
But there are features in Scribus that were developed as Google Summer of Code projects and and think a lot of the support for complex script was developed with support from the government in a country who wanted good open source support for their language (it might have been Tamil, but I am not 100%).
So contributing with code is the best way to help.
#45
Code / Re: Best forum
Last post by BN_Dev - September 08, 2024, 07:28:12 AMThanks a.l.e,
Git workflows have been the de facto for my career for a while, but I accept the core devs have their own preference. I'd like to be involved so I'm more than happy to put in the effort to work directly with what the project uses to reduce friction for patches to be contributed. Besides, working with svn might be a fun change.
I'm currently heading a project in a publishing company that acquired a large regional newspaper with an existing production workflow based on QuarkXPress + Adobe CC. There's a plan to enable more editors to perform layout tasks and to introduce some automation for various things (such as announcements, events, sports results, etc.) We've evaluated Quark's CopyDesk (CD) and Publishing Platform (QPP NextGen) and although they capable of doing what's needed, our company culture is open-source first.
To evaluate Scribus we've been recreating a previous issue in it to compare the output (and the process) to see if it's production ready for our use cases; and so far the results are very promising. There are a few rough edges and we're currently sifting through these to see if it's a lack of knowledge on our part (we need more learning/training), or there are bugs which we can report, or there are missing required features (that are available in QXP), and if it can support our future requirements (match some features in CD/QPP NG).
Over the course of the next week I'll open separate threads for each feature to keep the discussion focused to that particular feature. I'll also try submitting some basic patches to see how well I do with svn and how smooth the process is.
My hope is if the features are possible and the patches are accepted, and the cost to sponsor the development is comparable to the cost of QXP/CS/QPP NG, then it would be a no-brainer for us to switch production to being fully open-source. I'm encouraged one of the roadmap wiki pages has some things on similar to what we need so hopefully the discussions will be fruitful.
Many thanks,
Paul
Git workflows have been the de facto for my career for a while, but I accept the core devs have their own preference. I'd like to be involved so I'm more than happy to put in the effort to work directly with what the project uses to reduce friction for patches to be contributed. Besides, working with svn might be a fun change.
I'm currently heading a project in a publishing company that acquired a large regional newspaper with an existing production workflow based on QuarkXPress + Adobe CC. There's a plan to enable more editors to perform layout tasks and to introduce some automation for various things (such as announcements, events, sports results, etc.) We've evaluated Quark's CopyDesk (CD) and Publishing Platform (QPP NextGen) and although they capable of doing what's needed, our company culture is open-source first.
To evaluate Scribus we've been recreating a previous issue in it to compare the output (and the process) to see if it's production ready for our use cases; and so far the results are very promising. There are a few rough edges and we're currently sifting through these to see if it's a lack of knowledge on our part (we need more learning/training), or there are bugs which we can report, or there are missing required features (that are available in QXP), and if it can support our future requirements (match some features in CD/QPP NG).
Over the course of the next week I'll open separate threads for each feature to keep the discussion focused to that particular feature. I'll also try submitting some basic patches to see how well I do with svn and how smooth the process is.
My hope is if the features are possible and the patches are accepted, and the cost to sponsor the development is comparable to the cost of QXP/CS/QPP NG, then it would be a no-brainer for us to switch production to being fully open-source. I'm encouraged one of the roadmap wiki pages has some things on similar to what we need so hopefully the discussions will be fruitful.
Many thanks,
Paul
#46
General Discussion / Re: Looking for Advice on Usin...
Last post by Nermander - September 07, 2024, 07:31:33 AMIf you are producing PDFs for other uses than print, I am not sure Scribus is the right tool.
Scribus has always had the focus on print production, there are a lot of other options out there if you don't need PDFs for high quality printing.
Scribus has always had the focus on print production, there are a lot of other options out there if you don't need PDFs for high quality printing.
#47
Code / Re: Best forum
Last post by a.l.e - September 06, 2024, 06:26:57 PMYes, this is probably the best place for starting discussions on the Scribus development.
As a side note, you're welcome to use Git instead of SVN... there are even community maintenance mirrors on Gitlab and Github...
But, indeed, at the end you are supposed to propose the patches as attachments in the Scribus own bug tracker.
P.s.: there is a bit of dev discussions in the bug tracker, but ideas are probably better discussed in here....
As a side note, you're welcome to use Git instead of SVN... there are even community maintenance mirrors on Gitlab and Github...
But, indeed, at the end you are supposed to propose the patches as attachments in the Scribus own bug tracker.
P.s.: there is a bit of dev discussions in the bug tracker, but ideas are probably better discussed in here....
#48
Code / Best forum
Last post by BN_Dev - September 06, 2024, 05:58:47 PMHi all,
This forum doesn't seem overly active with regards to development chat. The Wiki is also a little out of date with regards to the articles on getting involved with development hence me asking.
Is this still the best place to discuss code changes? We found an old mailing list which is deactivated and points to the forum. I have registered at the issue tracker and I'm aware there is an IRC channel too.
I note the development model is a bit more closed compared to most projects on GitHub, with the development happening on SVN. The issue tracker on GitHub is also quite quiet and not all patches there get merged in. I understand submitting .patch files against the SVN is the preferred option for the core developers.
I would like to discuss some ideas and get feedback on proposed changes before working on any patches, to ensure that the work matches the development roadplan and would not be wasted. Which is the best place to thrash out these sorts of ideas and get feedback before doing any work?
Many thanks,
Paul
This forum doesn't seem overly active with regards to development chat. The Wiki is also a little out of date with regards to the articles on getting involved with development hence me asking.
Is this still the best place to discuss code changes? We found an old mailing list which is deactivated and points to the forum. I have registered at the issue tracker and I'm aware there is an IRC channel too.
I note the development model is a bit more closed compared to most projects on GitHub, with the development happening on SVN. The issue tracker on GitHub is also quite quiet and not all patches there get merged in. I understand submitting .patch files against the SVN is the preferred option for the core developers.
I would like to discuss some ideas and get feedback on proposed changes before working on any patches, to ensure that the work matches the development roadplan and would not be wasted. Which is the best place to thrash out these sorts of ideas and get feedback before doing any work?
Many thanks,
Paul
#49
Text and Typography / Re: Column flow
Last post by BN_Dev - September 06, 2024, 05:44:20 PMThanks utnik, I have added our use case and other information to the existing ticket. Hopefully the developers could consider this. I'm sure you're aware how much more productive the feature would make doing layouts; on a large publication it adds up to entire hours per day per person! Many thanks, Paul
#50
General Discussion / Re: Looking for Advice on Usin...
Last post by Flaxx - September 06, 2024, 11:45:16 AMQuote from: mnawij on July 30, 2024, 09:01:37 PMHi Jessy, I would recommend saving them as image format or pdf from excel and placing them into Scribus, unless you need to edit the tables in Scribus. It is the best way that I have found for quick work to get the job done.
Cheers!
mnawij
Even if I love Scribus and even if your proposal works fine for printed media, it doesn't in cases where you finally want to produce a readable PDF that should be accessible for people needing screen readers as they have reduced visual abilities.
I really would prefer a future Scribus version being able to import PDF or SVG files containing readable text - even correctly formatted if the fonts are either installed or (in case of PDF) properly embedded.