Recent Posts

Pages: [1] 2 3 4 5 6 7 8 ... 10
1
Windows / A lot of questions
« Last post by Reptorian on June 27, 2017, 09:37:08 pm »
1) How come I am getting weird colors if I try to view things in CMYK mode or even importing CMYK TIFF?

2) Why does .KRA import does not support CMYK yet?

3) How do I get image frame into the center of the page?

4) Is there a good snapping tool I don't know about other than grid?

5) How do I clip/mask into a shape?

Right now, I am using Krita, Inkscape, and Scribus to achieve CMYK output, but I am looking forward to learning Scribus and supporting it.

I am using Inkscape to generate the layout, Krita for 8-bit CMYK support and further work on layout, and Scribus for importing the Krita TIFF file.
2
General Discussion / Re: python APIs confusion
« Last post by eudoxos on June 27, 2017, 08:47:26 pm »
Alright, so if I try, should I go the scripter2 way? What made it broken?

I (co)wrote a large particle simulation package with tight c++/python bindings (https://woodem.org), so I will be able to understand what's going on. What I'm concerned is, long-term, that using raw pointers inside scribus is inherently limiting for tight wrapper.

Cheers! v.
3
General Discussion / Re: python APIs confusion
« Last post by a.l.e on June 27, 2017, 06:13:08 pm »
hi vaclav

- yes, scripter 1 is the default
- no, scripter 2 does not work anymore
- yes, there is not much missing to get the scripter 2 to work (again) but i failed and i would be happy if somebody could help!
- the api for the scripter 1 is in the help files you get with F1 in scribus (for developers > scripter API)

i don't know if you can style names through the script (i cannot check right now, but i think it should be possible) but if you know some c++ and python it should be easy to add that function if it's missing.

ciao
a.l.e
4
General Discussion / python APIs confusion
« Last post by eudoxos on June 27, 2017, 05:07:57 pm »
Hi everybody,

I would like to get some clarification on Python scripting in scribus. Is it correct that the default build comes with scripter "1" in scribus/plugins/scriptplugins with the clumsy stateful interface and one can build scripter2 with WANT_SCRIPTER2=1 in cmake which is in scribus/plugins/scripter? There are many documents on the wiki but many of them are perhaps obsolete.

Secondly, is the API documentation for scripter 1 available somewhere officially? I go by pprint.pprint(dir(scribus)) and print(scribus.something.__doc__) in the python console for now, which is not the most satisfactory thing I've done till now. For scripter2, I found http://scribus-scripter.readthedocs.io/en/latest/index.html.

Third, marginally related: is it possible (with either API) to take text in linked frames (i.e. the whole text that opens in story editor) and find its paragraph style name with python?

Thanks!

Vaclav
5
Installation and Setup / Re: Scribus 1.5.3 appimage - some issues
« Last post by a.l.e on June 27, 2017, 03:18:30 pm »
back to #4: you're doing it wrong.

you should load the html into scribus text frames, chapter by chapter.
then manually add the images.

depending on the way the formatting is done in the manual, you might first load the html into libreoffice, export it to odt and then load that into scribus' text frames.

currently, there is no way to get from an html layout to a scribus document. in some ways this feature could be added to scribus, but somebody has to sponsor (it could work in a similar way as idml works... if we can find out how to break the flow into pages...
images would be included, but at the wrong place.



about the reason why your workflow is flawed: when scribus reads a pdf, it converts the whole text to vectors and this not something you can use. really.
6
Installation and Setup / Re: Scribus 1.5.3 appimage - some issues
« Last post by utnik on June 27, 2017, 01:42:53 pm »
.pdf is a final document format!

…Scribus does its best to retrieve the information from the PDF but what you get depends on so many things the whole process is very hit and miss. This might change with Scribus 1.5.x…

yes, scribus1.5.x does a much better job in dealing with .pdf files – but it's still no .pdf editor…
Quote
Since a PDF is an output of Scribus it might be reasonable to assume that it can open its own output. After all, GIMP outputs PNGs and JPEGs and it can open them…

well – gim exports .pdf files as well; and scribus 1.5.x does a much better job when opening these files as gimp itself. but as mentioned by gary and by me: .pdf is a final format…

utnik
7
Windows / Re: Scribus can't find Ghostscript
« Last post by GarryP on June 27, 2017, 12:47:07 pm »
That's good to know, thanks for pointing that out a.l.e.

Drew, I would not recommend moving to 1.5.x just to stop the message from popping up. There should be ways to fix your current problem - see above - that are better than moving over to developmental software.
8
Installation and Setup / Re: Scribus 1.5.3 appimage - some issues
« Last post by GarryP on June 27, 2017, 12:41:20 pm »
While Scribus can "open" PDFs you probably should only think of that function as a kind of very limited "emergency recovery function" - even for PDFs created by Scribus itself. (I've just tried one of my own very simple newsletters and all of the images were missing and some of the text had been moved.) Scribus does its best to retrieve the information from the PDF but what you get depends on so many things the whole process is very hit and miss. This might change with Scribus 1.5.x - and maybe on to 1.6 - but I can only give advice on the current stable 1.4.6 as that's all I use.

Since a PDF is an output of Scribus it might be reasonable to assume that it can open its own output. After all, GIMP outputs PNGs and JPEGs and it can open them. Unfortunately, as you have seen, it just doesn't work in this case. Think of the PDF as a "final output" rather than an editable working document. A bit like an actual physical object being created by a 3D Printer from a CAD drawing. The PDF is the physical object while the SLA is the drawing.

Importing a PDF into an image frame should work just fine as long as the PDF doesn't use any of the more advanced PDF abilities but the PDF will still remain uneditable. You can do some basic stuff like "masking off" areas with shapes and adding text and images over those areas but it's not the same as real editing.

If you really need to modify a PDF then I can recommend Affinity Designer: https://affinity.serif.com/en-gb/designer/ It's not open source but it's cheap-as-chips and is a very capable bit of software, far more capable than its price would suggest. (For multi-page PDFs you will probably have to stitch the output back together after exporting the slices but there are lots of ways of doing that - too many to go into here.)

As for the Linux stuff, sorry but I can't help you any further. I'm only a casual Linux user and someone else will be much better placed to go into the technical details with you.

As for CUPS PDF Printer, I've not used it myself but I would assume that most of these sorts of things are only geared-up to produce PDFs as simply as possible and may not be producing 100%-Adobe-compatible PDFs. Even if it was, you still wouldn't be able to open it in Scribus anyway (as mentioned above).
9
Windows / Re: Scribus can't find Ghostscript
« Last post by a.l.e on June 27, 2017, 12:40:07 pm »
garry, the message has been changed in 1.5.x and it only pops up when scribus really needs gs!

https://www.scribus.net/websvn/comp.php?repname=Scribus&compare[]=/@19178&compare[]=/@19179
10
Windows / Re: Scribus can't find Ghostscript
« Last post by GarryP on June 27, 2017, 11:46:21 am »
If you get Ghostscript from an official/approved source then you should automatically get the files needed by Scribus.

I realise that you probably did what you said above just to see if you could get things running but picking individual files off the internet and scattering them around your hard drive is not good practice. You could end up in a right old mess with different applications using different versions of the same software, or worse. A full and consistent installation is best.

* For Windows, one good place to get GS from is here: https://ghostscript.com/

* For Mac, you can get GS from here: http://pages.uoregon.edu/koch/ (full Mac installation instructions are here: https://wiki.scribus.net/canvas/OS_X_-_Installing_Scribus_on_your_Mac_the_easy_way )

* For Linux, https://ghostscript.com/ is one source but it really depends on which flavour/version of Linux is being used (too many options to go into here).

If you install an official/approved copy of GS then you shouldn't have to hunt around for extra files, however you need to make sure that you get the right flavour of GS. Make sure it's the "Postscript and PDF interpreter/renderer" and not the PCL, PXL, XPS or PDL versions. (These other versions might also work but they're not needed and you could end up complicating things.)

I would suggest un-installing whatever GS you've installed and install a "proper" version instead and see what happens.

As a.l.e has said above, Scribus doesn't need GS installed to run. As per the Mac installation instructions: "[GS] allows you to import PostScript (PS) images, Extended PostScript (EPS) images, and PDF files (as images). It also allows you to export your document as PS or EPS (rather than the normal PDF export). It is also needed if you want to use the "Print Plate" Preview functions." If you don't need to do any of these things then you don't need GS.

However, Scribus will keep telling you that GS is not installed every time it runs even if you don't need these functions. This can be annoying. For instance, GIMP doesn't keep telling you that G'MIC is not installed, so why should Scribus keep telling you that GS is not installed? If GS was a requisite then it should come packaged with Scribus, otherwise Scribus should not be so fussy about it not being there.

When you first run Scribus it does a check to see if GS is installed. If it finds GS it adds the path automatically and everything is fine. Why Scribus doesn't check for GS every time it runs - until a path has been set - is a mystery to me. That would alleviate the need for the user to have to manually add the path once GS has been installed. The code to find GS is already there, so why only ever use it once? A strange situation.

At the same time, I think that the pop-up message about GS not being installed should be removed and replaced with a message on the splash screen saying that Scribus is running "without Postscript support" (or some better message which properly portrays the situation). The various PS functions can then be greyed-out until GS has been installed. Greyed-out PS functions with an obvious note (on the splash screen) telling the user they don't have GS installed would be more than enough to tell the user that more functionality could be available if they need it without being annoying.

That's just my view of course. I'm sure there will be arguments against what I've said above but I don't think I've said anything that is particularly unreasonable.
Pages: [1] 2 3 4 5 6 7 8 ... 10
palmate