View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017262 | Scribus | Import / Export | public | 2024-08-30 20:11 | 2024-10-23 18:42 |
| Reporter | azwing | Assigned To | cbradney | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Product Version | 1.7.0.svn | ||||
| Target Version | 1.7.0 | Fixed in Version | 1.7.0.svn | ||
| Summary | 0017262: Version interoperability | ||||
| Description | It is not a bug just a wish! Would it be possible to implement the save as to be able to save for previous versions of Scribus | ||||
| Steps To Reproduce | NA | ||||
| Additional Information | NA | ||||
| Tags | No tags attached. | ||||
| Patch | No | ||||
|
|
What is the need for this request? Scribus is free and everyone can use the latest version. From my point of view, there is no need for a backwards compatible mode. If you have files created with a development version like 1.7.0. You can open your file with a text editor and change the document version number. <SCRIBUSUTF8NEW Version="1.7.0.svn"> --> <SCRIBUSUTF8NEW Version="1.6.2"> Each newer document version may have changes that are not supported in older Scribus versions. |
|
|
as complement to what nitramr wrote: ... you can try to modify the version. this will mostly work in the early phases of a development series, but is less and less likely to work with each new feature that the development version gets. all in all: scribus does not have the workforce for implementing a save function into older version. on the other side, there is one thing that could be done in the long term: modify the .sla file format so that it can contain tags and properties that are not known to a specific version of scribus: when opening the .sla file, scribus could then ignore what it does not know, warn that some type of error has happened (maybe with some details about them) and render what it has understood. but even this is something that is highly unlike to be implemented soon. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-08-30 20:11 | azwing | New Issue | |
| 2024-09-01 12:35 | nitramr | Severity | minor => feature |
| 2024-09-01 12:42 | nitramr | Note Added: 0051301 | |
| 2024-09-02 14:35 | ale | Note Added: 0051302 | |
| 2024-10-22 13:15 | nitramr | Relationship added | has duplicate 0017289 |
| 2024-10-22 13:16 | nitramr | Assigned To | => cbradney |
| 2024-10-22 13:16 | nitramr | Status | new => assigned |
| 2024-10-22 13:16 | nitramr | Category | General => Import / Export |
| 2024-10-22 13:16 | nitramr | Fixed in Version | => 1.7.0.svn |
| 2024-10-22 13:16 | nitramr | Target Version | => 1.7.0 |
| 2024-10-22 13:17 | nitramr | Status | assigned => resolved |
| 2024-10-22 13:17 | nitramr | Resolution | open => duplicate |
| 2024-10-23 18:42 | cbradney | Status | resolved => closed |
