Recent posts

#1

PDF Generation / Re: White line appearing in pd...

Last post by molekingq - Today at 02:54:04 PM

Hi sorry I know this topic appeared recently but I couldn't make head or tails of the answer. Basically I have a project that when I export to pdf, when you open the pdf to read it has a small white line on the bottom and in print preview there is a small white line on the right. I'm not sure why as I have image frames on every page that match the dimensions of A4.
This is the background image I'm using: image
Any help would be appreciated.
Richard

#2

PDF Generation / Re: White line appearing in pd...

Last post by molekingq - Today at 02:50:36 PM

I don't think it's that as I increased the size of the image and that didn't help.

#3

PDF Generation / Re: White line appearing in pd...

Last post by utnik - Today at 01:54:17 PM

hi richard

an image that doesn't really fill the frame is one possible reason. but without the images i can't check this.

utnik

#4

PDF Generation / White line appearing in pdfs

Last post by molekingq - Today at 01:19:28 PM

Hi sorry I know this topic appeared recently but I couldn't make head or tails of the answer. Basically I have a project that when I export to pdf, when you open the pdf to read it has a small white line on the bottom and in print preview there is a small white line on the right. I'm not sure why as I have image frames on every page that match the dimensions of A4.
Any help would be appreciated.
Richard

#5

User Interface / Re: Indigo UI: Text Properties

Last post by AdmFubar - October 06, 2024, 10:39:04 PM

like a tab for each section?

#6

Scripts and Plugins / Re: Looking for Advice on Usin...

Last post by Derek - October 05, 2024, 10:13:43 AM

Bug. bug!

Damned autocorrect!

Gets us all sooner or later!

For issue 2 (empty frames being created) I changed AUTOTEXT in the sla file to 0. On running the build process, empty frames are no longer being created. I'm not really able to say, yet, whether editing the sla file directly will cause problems further down the line, but perhaps changing that option should be available under Document Setup or Preferences. Perhaps even as a Scripter command (it might even be useful to be able to choose programmatically).

This also helps with issue 3 (losing linkage between imported frames). I have to edit the aggregated document anyway, so it's easy and quick enough to identify the correct frame to link to without the additional autotext frame causing confusion. This doesn't, of course, fix the bug - but does give me an easy workaround.

I think it's time to improve what I've got, so far, so that it's in shape to produce the next (December) edition.

Progress has definitely been made - thank-you.

#7

Scripts and Plugins / Re: Looking for Advice on Usin...

Last post by a.l.e - October 04, 2024, 10:17:19 PM

3

That might be a business pages import, independent from the script API...

Bug. bug!

Damned autocorrect!

#8

Layout Issues / Re: Table of contents changes ...

Last post by Flaxx - October 04, 2024, 08:48:48 PM

hi flaxx

...it often happens that the top-down order of those articles appears random...

...What is the parameter, that Scribus is looking for? It doesn't seems to be the internal frame number nor an alphabetical order.

it should be the level of the frames. (it's the order in which you've created the frames in the first place. but you may change it in 'preferences' → 'x,y,z' → 'level'...)

utnik

Thanks, this seems promising and I'm a bit upset about my own blindness. I've just tried it and it works.

#9

Scripts and Plugins / Re: Looking for Advice on Usin...

Last post by Derek - October 04, 2024, 07:57:28 PM

Hi Derek

A few short answers from my side...


1

According to https://impagina.org/scribus-scripter-api/page/#importpage it seems to be possible to pass a range of pages...

In order to know which pages you want to be imported, you might want to get the script to first open the sla, analyze it, close it, before importing the pages.

2

Did you enable auto frames when creating the document?

3

That might be a business pages import, independent from the script API...

Hi A.L.E.:

1) That's exactly what I'm doing. I preprocess each section to get the page count. That's stored in a mySQL table which is used to control the build process. Each page count (integer) is converted to a tuple {1, 2, 3, 4, ....} for the importPaqe process. I was hoping for a wildcard ('*' or similar) that I have missed or is not documented. That would enable me to drop that process completely - which would give me a worthwhile time saving. (The process is automated, but I haven't managed to get it into the background, yet - it's on my list, so the gui is tied up while it runs.

2) That's a strong possibility. I'm sure I saw that when I created the original documents - which was, perhaps, 5 or 6 years ago! If that is the issue, can that setting be changed in an existing document (I haven't found it - perhaps it's a straightforward edit to the XML that I haven't dived into yet), or must I start from scratch? Would 'enable auto frames' have to be unset for all the section files, or just the first one loaded?

3) I'm not sure what you mean by 'business pages import'. Perhaps something lost in translation?

#10

Scripts and Plugins / Re: Looking for Advice on Usin...

Last post by Derek - October 04, 2024, 07:08:13 PM

depending on the total pages in the magazine you may run into a performance issue with large .sla files. Appending the sections as a finished pdfs, into one will be much easier.

Unfortunately, not possible in my use case. The aggregate sla is an intermediate stage that requires further editing to complete the magazine. Mainly making final decisions about content, adding adverts, sorting out white space and the transitions between sections, sometimes finding filler content to pad out the magazine to a multiple of 4 pages (it's an A5 magazine printed on A4 stock) and building a TOC.

Performance, so far, hasn't been an issue. There's usually about 50 to 100 pages (with text and images) in the aggregate sla file, and I'm happy to go get a cup of coffee while I'm waiting for the script to complete. The current test data (which produces 54 pages) is the last edition's live data. The script completes in under 800 seconds. I haven't seen any memory issues (and the machine I run this on only has 8Gb). In its final form it was edited down to 44 pages - one of my larger editions.