View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003951 | Scribus | Import / Export | public | 2006-06-29 23:11 | 2025-11-08 17:19 |
| Reporter | christoph_s | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | any | OS | any | OS Version | any |
| Product Version | 1.3 | ||||
| Summary | 0003951: Add an option to export a PDF file containing all data relevant for production | ||||
| Description | It would be fine if Scribus could offer an option to export an additional PDF file that contains all data relevant for production, e.g.: Fonts (embedded/not embedded), solid colours/spot colours, colour space, profiles, PDF creator, image resolution settings etc. The file would be named like the PDF exported from the document, but with an addition "-profile" (can this be made multilingual?). Of course these data can be retrieved with prepress tools, but IMHO it would be a benefit to and quite handy for the printer to receive the data in such an easily accessible way. | ||||
| Tags | prepress | ||||
| Patch | |||||
|
|
OK, so what you're after is a summary of all the resources used in the document (presuably along with key information such as the resolution and colour depth of images, etc). Sounds interesting. Rather than exporting a PDF, though, would there be any problem with just making this resource summary available as plain text? It'd be quite a bit simpler to do that way, as Scribus's PDF export capabilities are currently _tightly_ integrated with its document structure etc, and probably do the job just as well. |
|
|
Exporting plain text would be enough -- in principle. Unfortunately, Unix/linux, OS X and Win32 handle plain text differently, so that informations could get lost after transfer from one system to another. That's why I was thinking about PDF. |
|
|
Makes sense. Most mailers will convert line endings automatically though, and most editors handle all platform's line endings. Anyway, a simple HTML file wouldn't be much harder. Doing PDF right now would involve creating a new Scribus doc with the details programatically, then exporting that. Not too pretty really; much nicer to output a companion file in another format. In fact, I wonder about xml+css .... output a generic XML doc summary with the right xslt+css to render in a browser. It could be fun ;-) |
|
|
Cezary's suggestions for a warning about images that are compressed less than the original could be integrated into this ticket (see 0011784) |
|
|
ah, twenty years later, the output should probably be json (or in the worst case yaml) some more notes: - in the scripter there is scribus.savePDFOptions('/tmp/test.xml'): it can be used as a base for the implementation of a native export or for creating an export script that exports many more details. (the scripter commands seems to miss a few settings but covers most part of the export settings). - we need to export a list of the fonts used in the document - we need to export several characteristics of the document setup |
|
|
Also add data that is relevant for debugging (or add a second command for it): - List of items that are set as not printed / exported |
|
|
A usefull output might be a .zip or a .gz with all ressources included, not only their names. = An autonomous file that scribus could open, whose opening would never throw eg a "missing image file". = A single file that could be easily moved and transfered as are .doc files. It could become the prefered format for many usecases. And it might quickly bring an end to newcomer's awe and to a steady flow of reports on the bugtracker. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-06-29 23:11 | christoph_s | New Issue | |
| 2006-06-29 23:15 | christoph_s | Relationship added | related to 0003328 |
| 2006-07-02 20:00 |
|
Note Added: 0011756 | |
| 2006-07-02 20:06 | christoph_s | Note Added: 0011758 | |
| 2006-07-02 20:57 |
|
Note Added: 0011767 | |
| 2006-10-05 23:15 | christoph_s | Relationship added | related to 0003876 |
| 2007-08-02 20:52 | christoph_s | Relationship added | related to 0006056 |
| 2016-03-05 21:15 | Kunda | Tag Attached: prepress | |
| 2025-05-17 19:59 | ale | Relationship added | related to 0011784 |
| 2025-05-17 20:00 | ale | Note Added: 0052598 | |
| 2025-05-20 16:40 | ale | Note Added: 0052627 | |
| 2025-05-20 17:20 | ale | Note Edited: 0052627 | |
| 2025-11-08 11:22 | ale | Note Added: 0053185 | |
| 2025-11-08 17:18 | JLuc | Note Added: 0053188 | |
| 2025-11-08 17:19 | JLuc | Note Edited: 0053188 | |
| 2025-11-08 17:19 | JLuc | Note Edited: 0053188 |