View Issue Details

IDProjectCategoryView StatusLast Update
0017445ScribusStylespublic2026-07-05 07:32
Reporterale Assigned To 
PrioritynormalSeverityminorReproducibilityN/A
Status newResolutionopen 
Summary0017445: Use IDs and not names for referencing styles (and allow duplicate names for styles)
DescriptionGenerally speaking, it would be much better if Scribus would not use values that can be edited by the user for internal references.

Concerning the styles, we already have hierarchical styles, but it is not really comfortable to create styles with the same meaning under different styles.
Also, being able to create the same character sub-style would allow a simple interface for applying those styles when bold or italic should be applied (both when importing formatted text and for keyboard shortcuts)
TagsNo tags attached.
Attached Files
same-char-sub-style.png (15,011 bytes)   
same-char-sub-style.png (15,011 bytes)   
PatchNo

Activities

ale

2026-07-05 07:32

manager   ~0053973

I'm currently working on the Styles Browser that will replace the collapsed view of the Style Manager.

The issues I'm currently facing:

- How to keep the collapsed / expanded choice made by the user, when an update comes from the Style Manager?
- How to track changes, when the user changed the name of the style in the Style Manager?
- How to track changes, when the user changed the base style in the Style Manager?

Only a few things that would be easier if each style (and each resource in Scribus!) would have a unique ID that never changes (not because the user renamed something, not because the user switched the UI language).

Issue History

Date Modified Username Field Change
2025-03-08 10:57 ale New Issue
2025-03-08 10:57 ale File Added: same-char-sub-style.png
2026-07-05 07:32 ale Note Added: 0053973