Recent posts

#81
Showcase / Re: Importing text only but wi...
Last post by Aleks100 - November 29, 2025, 12:59:37 PM
Have you tried to export text as markdown, check it if everything is fine (delete # headers), and then to import it in Scribus?
#82
Showcase / Re: Importing text only but wi...
Last post by a.l.e - November 29, 2025, 08:52:27 AM
If I understand you correctly, this has been discussed recently in this thread:

Importing LO Writer text without over-writing existing styles
https://forums.scribus.net/index.php/topic,6642.msg27393.html

Last Thursday, with the help of a few people at our local Hackergarten, I had a second look at the ODT importer and managed to find one of the switches that would allow to import the text and apply the formatting from the Scribus document.

But there is a lot more work to be done.
We will see, if I succeed.
#83
Showcase / Importing text only but with a...
Last post by Denis ROUQUIER - November 28, 2025, 06:19:01 PM
Hello

I am currently preparing the second Scribus-based issue of our journal (the first went fine).
Everything is about OK ; I still feel a bit uneasy with text import.

I have tried several methods :
- copy-paste
- import (text only)
- import not-text-only

I have seen several problems :
- « Ctrl-space » characters become ordinary space characters   (typical of copy-paste from word) ;
- missing space characters here and there (from word, random, difficult to reproduce) ;
- local changes (like one word in bold or one sentence in italic) are not reproduced ;
  this is normal with copy-paste or with text-import-text-only, but it is a problem for me ;
- several new styles created (but not used ??) ; this is normal with « import text not-text-only »
  but I really want to keep the list of styles under control.

I wish Sribus could offer a text import function with the following features :
- no new style is created
- no existing style is modified
- the imported text appears in « default paragraph style »
- the local changes (like one word in bold or one sentence in italic) are reproduced.

The nearest I can go to this is by using the following method :
- start with a writer text (or with a writer version of a word text) ;
- use import text (not text only ; not prefix style names ...) ;
- click once in the frame and apply « default paragraph style » without bracket
- delete the newly created styles (this may be shared between several imports).

All this seems a bit complex, and I might have to use the old method (import text only, and carefully read the imported text to manually reproduce the local changes, like one word in bold or one sentence in italic).


#84
PDF Generation / Re: pdf too big
Last post by utnik - November 25, 2025, 12:44:49 PM
i would rather send a more usual test document with an end format (.pdf trim box) of 210x155mm and 3mm bleeds (bleed box: 216x161mm). i guess, that's what the printer really wants.

utnik
#85
PDF Generation / Re: pdf too big
Last post by a.l.e - November 25, 2025, 07:08:07 AM
That's a bit unusual, but what speaks against having pages 6 mm smaler than that and a bleed of 3 mm?

I would do a test document and send it to the printer, to check that you got it right.

P.S.: after reading utnik's comment: of course, if you have not sent a "normal" test document with the expected size + the bleeds around it, you should first send that! From your replies, I assumed you already did that, but I cannot be sure : - )
#86
PDF Generation / Re: pdf too big
Last post by Eric van Dusseldorp - November 25, 2025, 03:22:33 AM
Quote from: Eric van Dusseldorp on November 22, 2025, 05:53:22 AMHi, I made a book with Scribus. It is oblong 210x155 mm. By making a pdf, the system makes a far bigger format. I want exactly 210x155 and no crop marks.What to do?

Thank for the answers.
But the printer wants:
pdf in exactly the right format (210x155)
No crop marks but... Bleeding 3 mm.
How to do that?
#87
Scripts and Plugins / Re: LibreOffice > InDesign (ID...
Last post by a.l.e - November 24, 2025, 05:51:58 PM
Hi Michael,

I still don't really get which features related to RDF, you would like to see in Scribus.
But I have to admit that I don't really get yet, what exactly is the Resource Description Framework in our context and how it can be used in text documents.
You might want to provide example of what you plan to do with it.
(Of course, I get why having a standard for defining a tree of properties and values is very useful.)

From the screenshots and slides you linked to, I guess that Scribus needs a good way (ok, theoretically, a better way...) to show properties attached to text.
We have limited support for bookmarks and references, but they are not implemented in a good way and the user interface is not comfortable.

From my point of view, if I somehow understood correctly your goal, I would approach the issue by first implementing from scratch HTTP links.
I think that this is the simplest thing that looks like an RDF resource (but has a much smaller scope).
The issues to be solved are:
  • How to display the URLs in the document
  • How to let the Scribus user edit the values attached to each URL
  • How to add the URLs in document intended for print and how to do it in the case of Web distribution.

I think that we would need to already know what the exact scope of the RDF support in Scribus needs to be, to make sure that the implementation can scale to support your RDF requirements.
Another requirement that should be taken into consideration: in the future, the link should also work inside of the PDF document (as an example for the TOC). But this part does not need to be implemented yet (if it's not useful for RDF).

Without doing this preparation work, and without exact requirements on what needs to be supported, it's very hard to say how much effort is needed.

So, instead of thinking about how much time it will be to implement the feature, I think that it would be more suitable to define a maximal effort to do an explorative work.

On the other side, I've not yet had the chance to work on the ODT import code, but from what I've seen, it's one of the nicest part of the Scribus code base.
And the ODT format also looks very clean.
And if the PDF has a way to store those value, that part should not be hard, either.

Sorry, that I can't give you more precise information.
#88
Windows / Re: Aanpassen van de werkbalke...
Last post by a.l.e - November 24, 2025, 02:44:07 PM
Hi Denise,

I think that in 1.6.4 you can't do much more than scale the whole Scribus user interface.
If you want to go in this direction and don't find how to do it, I can look it up.

The development version 1.7.x has a better handing of the icons.
It's up to you, to judge if your skills and situation allows to use a development version.

Finally, on the contrary of the icons in the palettes, the buttons in the toolbar are completely optional.
All of the commands in the toolbars can also be triggered from the menus, many have a good keyboard shortcut, and the other ones can be triggered with the Action search (ctrl-/).
If you are visual impaired (and generally also for other types of impairments), it's probably worth to learn how to do as much as possible with the keyboard.

Once the new user interface for 1.7 is closer to be finished, I guess it would be useful to assess how well it can be used by user impaired.
#89
User Interface / Re: Issues with the v1.7.1.svn...
Last post by amair - November 24, 2025, 12:56:11 PM
Quote from: amair on October 18, 2025, 05:42:02 PMA) scribus-sidebar-missing-background.jpg
The new non-permanent sidebars have no background color set.
I've found a workaround that works for me. I've added this to ~/.config/scribus-9999/stylesheet.css:
ads--CAutoHideDockContainer {
  qproperty-autoFillBackground: 1;
}

Thanks to all who brought the knowledge about stylesheet.css back to my mind!
#90
Text and Typography / Re: How to make this numbering...
Last post by Nermander - November 23, 2025, 08:17:41 PM
I managed to get like this, but there was some glitch where I think I had to save the first style before I could set the second style to level 2.

My Scribus is set to Swedish, but I think it is possible to understand anyway.

bild.png
bild.png
bild.png
bild.png