Recent Posts

Pages: 1 2 3 [4] 5 6 7 8 9 10
Beginner Talk / Re: Import pdf
« Last post by GarryP on September 21, 2017, 11:06:17 am »
Personally I wouldn't touch page transitions with a ten-foot barge pole.
At best, they distract from the content. At worst, they just make the creator/presenter look bad.

Page transitions on PDFs are a bit like flashing text and marquee scrolling in HTML. They were a gimmick that had their day in the sun but should now be retired in favour of more "mature" ways of doing things, I.e. Just go straight to the next page.

If you think you might need page transitions to make your content interesting and keep the viewer engaged then your content isn't interesting enough. Don't paper over the cracks, fix the cracks.

I think it would be a good idea if the Extras tab in the Export dialog was removed completely. I can't believe there's more than a tiny minority of people that actually use these things and it's extra code that needs to be kept up-to-date and tested which will take up valuable development time which could be better-used elsewhere.
Announcements and Forum Rules / Re: Image will not load into image frame
« Last post by GarryP on September 21, 2017, 10:37:11 am »
SLA files are just XML (text) and are no more or less susceptible to 'corruption' than other files, depending on what you mean by corruption. One thing they have on their side, compared to proprietary-format files, is that if the file does become corrupted in some way you can use a text editor to try and fix the problem (as long as you can understand the XML).

I've been using Scribus for a while now and can't remember ever having an SLA that didn't load back into the application that produced it. (1.5.x files can't be opened by earlier versions but that's to be expected.)

It's unusual to have the same problem with two separate files but if they were generated from the same original document then I would guess that it was the original document that was wrong in some way. As, has been said, SLAs are just XML it would be unusual if the file itself had a problem but you never know how the document was created. There's a chance that it was created via a script and the script created the problem but that's difficult to prove without the original. If you can attach the original then someone might be able to pick through it to find out what's wrong.

Overall it's better to use your own documents rather than relying on other people's templates and suchlike. It can be a lot more work at first but once you get the hang of using Scribus it's pretty easy to knock up something usable which can be refined later.
PDF Generation / Embeddable TTF text can't be embedded by Scribus
« Last post by Taartsel on September 21, 2017, 09:31:14 am »
Hi! I'm trying to export a Scribus file to a PDF, embedding the fonts. All the fonts I'm using should be embeddable (according to a check by Adobe Indesign) but only one of the fonts can be moved to the "Fonts to embed" list. They are both TTF and have the same level of rescrictions according to Indesign.
What could be the reason one of the fonts won't be embedded and the other has no problems being embedded?

(The font that won't be embedded is "Amatic Regular" and the font that can be embedded is "Caviar Dreams". Both TTF and free for commercial and personal use.)
Beginner Talk / Re: Import pdf
« Last post by a.l.e on September 21, 2017, 09:23:41 am »
yes, scribus cannot directly add transitions to a pdf.

but, sadly, scribus can create pdf with transitions, so you can do that with scribus.
but it's a bit silly.
most of all if you're using 1.4.x.
Raster and Vector Graphics / Re: Reduced DPI issues
« Last post by Taartsel on September 20, 2017, 08:29:40 pm »
That's what puzzles me too. Placing the image smaller should give it a larger dpi, not a smaller one.
I import the files by drawing an image frame the size I want it and then right-click and choose "Get image...". I pick the image from the folder, but there it starts showing some strange things; instead of 300 dpi (the image's dpi on the original image size of 3000px) it says the image is 72dpi. In fact, it says that about every image, even though the same images are saved as 300dpi files and show up larger than the drawn image frame when placed, making it seem that they indeed should be larger than 300dpi when adjusted to the image frame's size.
Announcements and Forum Rules / Re: Image will not load into image frame
« Last post by GregM on September 20, 2017, 08:18:16 pm »
I am not sure what happened.

I think the .sla file was corrupted. I chose another newsletter shell that was a .sla file and then was able to load the photo.

Do these .sla extension files corrupt easily?

I do thank everyone for the suggestions and I looked into every one of them. That did give me an opportunity to learn about both GIMP and Scribus.
Beginner Talk / Re: Import pdf
« Last post by Nermander on September 20, 2017, 08:13:08 pm »
I would say that Scribus cannot add transitions to a PDF.

What you can do in Scribus is import a PDF as text and vectors, and from that content create a new PDF that contains transisions.

Raster and Vector Graphics / Re: Reduced DPI issues
« Last post by Nermander on September 20, 2017, 08:09:04 pm »
DPI does not "exist", is computed from the number of pixels and the printed size of the image.

You image is 3000x3000 pixels. It will only become 300 DPI if printed as 10x10 inches.

If you print it at 5x5 inches it will become 600 DPI and if you print it at 20x20 inches it will become 150 DPI.

What puzzles me here is that Scribus reports the image as 117 DPI when it is in a frame that (as far as I understand) is smaller than 10x10 inches (since the document is just 5x7).

Can you explain how you import the image into Scribus? Because the numbers don't look correct, so I suspect you are doing something strange here.
Raster and Vector Graphics / Reduced DPI issues
« Last post by Taartsel on September 20, 2017, 07:52:13 pm »
Hi! So far I couldn't find anyone with this specific problem, so I was hoping someone could help me out. Maybe I'm just missing something, but here's the problem:
I have an image (or several actually) of 300dpi, 3000x3000px large. It's a .tif file. Whenever I check it with Windows image properties or the Linux equivalent of image properties, it says it's indeed 300dpi and 3000x3000px large. But whenever I import it into Scribus, it tells me the image is 72dpi, even though it's placed in a invitation sized (5" x 7" inch) document. When I do a preflight when exporting to PDF it tells me the image is 117dpi (probably because it imported as 72dpi and I resized it significantly smaller in the design).
When I try the same thing in Adobe Indesign (5" x 7" inch, 300dpi document, same image file imported), it loads just fine as a 300dpi image like it was meant to. What is going wrong in this process that results in this loss of dpi? I can't seem to figure it out.

Does anyone have a clue?
Scribus forums / Re: Scribus Webpage
« Last post by GarryP on September 20, 2017, 05:31:03 pm »
I completely understand why some level of oversight is needed. The example you gave about changing links to point to malware is absolutely something that should be watched for. The same goes for people adding malicious javascript to the pages. And the list goes on.

I wasn't trying to say that the site should be completely and freely editable by anyone. That would be a terrible way to do things. What I was trying to say is that using GitHub (or something similar) would allow anyone to be able to make changes to their own copy of the site and then put in a pull request to get those changes made to the site itself. The pull request would have to be checked by someone of course but the whole process would be opened up to anyone who wanted to give it a try rather than the current process where only a very small group of people (or just one individual?) has access to potentially make changes to the site.

Letting people collaborate on changes that can be later incorporated into the site makes it easier for people to get involved. Their changes might not "make the cut" for whatever reason but at least they can have a go.

Personally - if the proposed site does eventually go ahead - I would like to see more areas being created. For example, I would like to see a new "Build and Installation" area that tells people how to get Scribus up-and-running. This will be easier to keep up-to-date if it wasn't "stuck" in a wiki where you have to get special access before you even start looking at changes. I would also like to see a new "Tutorials" section where people can learn to use Scribus by doing, rather than having bits and pieces of documentation all over the place.

Basically I would like the new sections to replace the wiki completely. It has done its job - up to a point - but it's time for it to go now. Putting these new sections into a site where change management was done via something like GitHub would make it a lot easier for people to make new content and maintain it.

It would be great if all of the Scribus documentation and information could be accessible from one place rather than from distributed wikis, forums and other places. And putting it all in somewhere like GitHub would enable that to happen much more quickly.

I may have been over-reacting to your use of the words "proposal" and "managed". I have worked in places where more work is put into a proposal than is actually needed to get the job done and where management of something can mean a drawn out process that takes longer, and way more people, than just doing the thing in the first place. Yes there have to be procedures in place but sometimes the procedures can become more important than just getting stuff done.

Anyway, I think we're both saying the same things but from slightly different perspectives:
* The site should allow people to get involved easily but there should be controls in place to stop malicious acts;
* The site should allow quick updates to be made while "something" ensures that those updates are correct and reasonable;
* The site can only be productive if a large number of people have the ability - not necessarily access - to make changes.

I don't think any of this is unreasonable and I think it can all be achieved with GitHub. (I am not being sponsored by GitHub. Other development platforms are available.)
Pages: 1 2 3 [4] 5 6 7 8 9 10