View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017694 | Scribus | Graphics / Image Frames | public | 2025-11-20 18:59 | 2025-11-20 19:01 |
| Reporter | ale | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Product Version | 1.7.1.svn | ||||
| Summary | 0017694: Allow absolute paths for images | ||||
| Description | Often, we have set of images that are used in multiple projects (company logo, ...) and we want to be able to link them with their absolute path. It should then be possible to move the file both on the same computer and to other computers (mostly opening the file on a shared folder with a different computer). Currently, Scribus is using the absolute path while editing the document but stored the paths as relative paths, relative to the .sla file. The idea is to let the user define absolute paths that will stored as is in the .sla file. Those paths can be defined in the preferences or in the document settings. The user should also be able to define named absolute paths. As an example, a user could define that E:\Shared\Company\Assets is defined as ASSETS on a Windows computer but as /mnt/Shared_assets on a Linux computer. The path stored in the .sla would then be something like PATH="::ASSETS/logos/big.tif", where "logos/big.tif" is the relative paths on the shared server. For paths that are not named, the paths is written as is in the .sla file PATH="C:/user/ale/Documents/Assets/logos/big.tif" and the .sla can moved around without the need to duplicate the logo in a sub folder of the project. The paths defined in the preferences are inherited in the document setup, without being editable. The user can add further paths in the Document Setup (in case of name clashes, it's the Document that wins). | ||||
| Tags | No tags attached. | ||||
| Patch | No | ||||