Recent posts

#1
General Discussion / Casino Marriott Warsaw w telef...
Last post by StevenPaRty - February 20, 2026, 09:38:18 PM
Cześć! Testowałem aplikację Kasyno Warszawa kilka tygodni.
 
Co działa:
 
- Atmosfera Marriott Warszawa
- 3000+ gier - sloty, ruletka, kasyno Warszawa poker
- Krupierzy PL 4K HD
- Cashout 15 min - 24h (moja: 780 PLN w 17h)
- Bonus 100% do 4000 PLN + 200 FS
- BLIK instant, min 10 PLN
- 50 MB - lekka app
 
Minusy:
 
- Wagering 35x
- Brak crash games
 
Legalna, bezpieczna (TLS 1.3, EU license). Live casino z Warszawy - czat PL!
 
Stats miesiąc: wpłaty 1200 PLN, wypłaty 1580 PLN = +380 PLN
 
Recommend dla miłośników luksusowych kasyn i aplikacje mobilne kasyno. Graj odpowiedzialnie!
#2
Beginner Talk / Re: Single Line Drop Caps
Last post by utnik - February 20, 2026, 08:49:51 PM
hi rvodden

try to reduce the font size of the style for the drop caps to something below the value of the baseline grid.

utnik
#3
Beginner Talk / Re: Single Line Drop Caps
Last post by AdmFubar - February 20, 2026, 08:13:54 PM
Looks like an issue with the font. I noticed that you are using different fonts in your examples. Try a different one for the problematic drop cap and see if that clears it up.
#4
Beginner Talk / Single Line Drop Caps
Last post by rvodden - February 20, 2026, 05:51:27 PM
I'm having a strange problem with DropCaps. I have a 2 line dropcap selected, and the drop cap has appeared 3 lines deep with only a single line following it:

https://drive.google.com/file/d/1Cj9ZPhGygOEC_ZD_kKtwJCuRaTQjqiT5

In other places it works fine though:

https://drive.google.com/file/d/1xuTT1fQSm81CfSbT9SUu65L2JiDk-fcB

Does anyone have any idea what is going?
#6
Scripts and Plugins / Re: Utility script for book ty...
Last post by Lynn - February 17, 2026, 10:59:51 PM
Oh, honestly, I hadn't imagined Scribus would implement any of this natively; at least certainly not any time soon. For one thing, typesetting norms vary by language/region/medium and I have no idea whether these rules are applicable outside english-language book typesetting. I don't get the impression many people use Scribus for books, though I think it can work very well for it.

Out of the list, the only one I think is likely universal is preventing the last word of a paragraph from being automatically hyphenated. Perhaps it'd be possible to have a "don't hyphenate within X lines of the end of a paragraph"? Both Affinity and InDesign have toggles for this in their hyphenation settings.

But I know there's certainly bigger Scribus priorities, hence writing a script to automate that task in my projects. (I would definitely rank these fiddly bits way below style-based running headers.)

The initial reason I wrote my script to work with the XML instead of within Scribus directly is that I didn't see a method in the API to edit text that isn't visible on a page in Scribus. When doing book projects, I add pages in chunks as I finalize the text and unlink the text chain at each chapter break. That prevents ever having a really long text chain visible on-screen, and reduces lag when doing 200+ page projects. If I could only edit visible pages, I would have to remember to run the script four or six times per project rather than all at once at the beginning.
#7
Scripts and Plugins / Re: Utility script for book ty...
Last post by a.l.e - February 17, 2026, 08:01:17 PM
Very interesting summary.

Personally, I have a hard time believing that Scribus will be able to add all or even any of the rules you mention.

The main hurdle I see: adding an algorithm that is somehow performant and that will manage to never produce a really bad result. In one pass.

... And this with the limited number of contributors currently active in Scribus...

But, what I think might be possible, is to get Scribus to give information about the possible and enhancing the scripter API to allow a more or less automatic enhancement of the text flow through Python scripts.
A bit like what you are doing with your script, but with interactions with the document's frames and not by tweaking the XML in the .sla.

What do you think about it?
#8
Scripts and Plugins / Utility script for book typese...
Last post by Lynn - February 15, 2026, 09:18:25 PM
There's been a few requests scattered throughout the forum from folks looking for ways to implement certain book typesetting norms:
  • The last word of a paragraph should never be hyphenated
  • According to some sources, the penultimate line of the paragraph shouldn't be hyphenated
  • If the last word of a paragraph breaks to its own line, it should be longer than a certain minimum length. Short last lines are called "stubs" or "runts"
  • Words that are already hyphenated, like "pell-mell" shouldn't be given additionally hyphenated by the software
  • Chapters generally begin after a frame break

I implemented all that in one script, plus an extra feature to apply a character style the first X characters/words or up to a delimiter at the beginning of a selected paragraph style (handy for when you want each chapter to start with a few words in small caps, though I suspect I'd probably end up manually adjusting them).

https://github.com/notwhelmedyet/ScribusTypesetting/blob/main/runtsAndStuff.py

Since there's no way to mark in a Scribus XML file (yet, waiting on Ale's patch to get accepted) that a word shouldn't be hyphenated, the script needs to be run after the whole document has hyphenation applied. It will selectively go through and remove the unwanted hyphens.

There's also no "frame break right" option in Scribus so the script only inserts one frame break. If you needed each chapter to start on the right, you'd still need to add an extra break as needed while cleaning up your file. The script assumes you've already applied the style for chapter titles because I always import my text with that pre-styled; if you have a different workflow you could just toggle that option off and do your frame breaks later.

It saves a copy of the file so there's no worries about it corrupting anything & has variant code so it works in 1.7.1+ and 1.5-1.6 versions of Scribus.

As is my typical style, the script opens a series of menus where you can pick the operations it will run; if you hate menus you could save a copy where you remove those dialogs and hard code the settings.
#9
User Interface / Re: Automatic Fraction Generat...
Last post by a.l.e - February 15, 2026, 08:23:59 PM
  • That type of fraction only works when the font does support it. You see it in the "Open Type Features" section of the content palette.
  • Concerning the palettes: the current implementation will be replaced "soon" by a different implementation
    https://bugs.scribus.net/view.php?id=17432
#10
User Interface / Automatic Fraction Generation ...
Last post by Portreve - February 15, 2026, 06:48:30 PM
Using: Scribus 1.7.2 Flatpak, openSUSE Tumbleweed / Gnome 49

Scribus has a capability for turning a pair of numbers into a superscript/subscript formatted fraction. For example, you can type in a 1, then a 2, click in between, and then insert the "Solidus" character (a solidus is basically a specific type of slash also known as a fraction bar).

What should happen is that the first number (using the example above, the "1") should be superscripted, and the second number should be subscripted, and one should have a proper-looking fraction.

What actually does happen is that you have to change fonts to something else after doing it, and some fonts don't do anything at all.

For example, if I switch to Tekton Pro, it will automatically make it a fraction. If I switch to Helvetica LT, nothing happens.

I don't believe this is a font feature issue because it doesn't replace the 1, the solidus, and the 2 with a single fraction character, though maybe it is and I'm wrong.

The other issue is when you start moving Pallets around, they become unwieldy. They will shift around, or they will completely undock, and sometimes when they undock they lose their title bar so suddenly they cannot be moved at all.

EDIT: One other thing, related to fractions, and this is something I've experienced across multiple versions of Scribus (1.4, 1.5, 1.6, and 1.7) is that when you set all your superscript and subscript settings, if you manually make a fraction, the numerator will not appear at the correct height, but if you take the document and export it (as a PDF, for example) it shows correctly there.