View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017445 | Scribus | Styles | public | 2025-03-08 10:57 | 2026-07-05 07:32 |
| Reporter | ale | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Summary | 0017445: Use IDs and not names for referencing styles (and allow duplicate names for styles) | ||||
| Description | Generally 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) | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Patch | No | ||||
|
|
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). |