View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013453 | Scribus | General | public | 2015-10-22 12:37 | 2015-10-22 15:58 |
| Reporter | htgoebel | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 1.5.0 | ||||
| Summary | 0013453: Consider using a nested XML structure in .sla | ||||
| Description | I know, I'm opening a new barrel (German proverb) by requesting yet another file format change. Please consider changing the file-format again and using a more structured approach. I had search bugs in the XML file and it is very hard to spot relevant portions since most elements are flat. The structure of ODT could be a guideline to follow. So something like this would be much more easier to understand by human: Dokument - Settings .... group the current "Document" attributes into some xml-elements like pages, text, pictures - CheckProfiles -- container for all <Checkprofile> elements - CheckProfile - Printer - Pagesets ... - Styles - CharStyles -- container for CHARSTYLE - TableStyles -- container for table style ...and so on - Sections - Pages - Page - PageObject ... - Page - PageObjects ... ... | ||||
| Additional Information | This can be implemented with less effort using this trick: - When writing the XML, write according to the structure. - When reading, *ignore* the structure and process only based on the (old) tag-name. | ||||
| Tags | No tags attached. | ||||
| Patch | No | ||||
