View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012480 | Scribus | General | public | 2014-07-05 13:26 | 2020-05-20 10:31 |
| Reporter | JLuc | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Product Version | 1.5.0svn | ||||
| Summary | 0012480: Afterflight checker : Warn when some image is outside "images" folder | ||||
| Description | A new afterflight checker, or a possible project manager, could warn when some image is outside "images" folder. When doing "prepare ouput and bring images together" ("Fichier" > "Rassembler pour la sortie"), all used images are brought inside "images" subfolder. This has to be done to share the datas or save them for future use. BUT it is still possible to edit the file and change some image, maybe use another image as the one in "images" subfolder. Its not possible to know that, afterward, and this leads to dangerous potential situation where it appears later that a used image has been "lost". [Edit] Since the PDF export is done at least when all is fine (but possibly before), the preflight could a good place to test whether all used images are in "images" subfolder. However, this check is not strictly related to PDF export. That's why this report now mentions a new "afterflight checker" or "Project manager" that would provide this checking function. | ||||
| Additional Information | [Edit 2015-03] Notes of a discussion on IRC : - The life of a document is not ended once printed. It can be stored and later re-printed. This can need some work to be done on the document and thus, user has to be able to restore all links and images, years later. In such situation, its very important that the collect for output operation has been done *after* all image changes or additions have been done in the document. - This feature belong to some "Project manager" or some "Afterflight checker" if that makes sense. | ||||
| Tags | PreflightChecker | ||||
| Patch | No | ||||
|
|
In the meanwhile, here is the command i use to find files where some new images have been inserted since the last "Collect all images for output" :grep -H PFILE= *.sla | grep -v "PFILE=\"images" | sed 's/^\(.*\.sla\).* PFILE="\([^"]*\)".*$/In \1, image has source file outside \/images : \2/' Each resulting line displays the name(s) of a sla file that has to be opened with scribus so as to bring used images in "images" folder, and the source folder of the faulty images. + Since i often split published documents in parts that each are in a subfolder, i have writen a more complex "slacheck" script, based on that grep command. - ATM, it outputs also the embeded images as part of the images that dont have their files in the images/ folder. That is true, but not usefull. |
|
|
Very cool JLuc! |
|
|
basically: very interesting to have an optional "official" images directory... but i'd prefer a way to set/choose it (also) through the document settings and not have to first collect for output to have one... |
|
|
Since i've writen that script, i discover issues in allmost each of the documents (magazine issues) i've archived, which would make their later recovery a problem. Having that option in PDFchecker would be a neat workflow security improvement. |
|
|
Improved script is there https://github.com/JLuc/scribus-project-manager/blob/master/slacheckimages |
|
|
I edited this report, changed the title and added some comments in the description : Notes of a discussion on IRC : - The life of a document is not ended once printed. It can be stored and later re-printed. This can need some work to be done on the document and thus, user has to be able to restore all links and images, years later. In such situation, its very important that the collect for output operation has been done *after* all image changes or additions have been done in the document. - This feature belong to some "Project manager" or some "Afterflight checker" if that makes sense. |
|
|
1) As for the "Use document's preference" hint, its not valid really since there is NO "fonts" pane in that dialog, so its not possible to select which of the used fonts are embeded or vectorized. 2) Even if this feature is not required to export the PDFt, it would feel very ok to fit amongst the preflight checks, in a user POV. Maintenability and long term quality is not to be insured in the last bits of a project, or when its finished. It has to be cared from the start, for example when establishing a well choosen set of documents folders. Hence having that proposed check in the preflight check is correct IMO. |
|
|
Project management and quality reach wider activities than plain PDF export. Let me quote jghali about quality management it : « ... errors are rarely intentional. In a quality managed environment, when errors can be committed, a basic rule says: if you can prevent an error, then prevent it. » In this case, that translates: if you don't want parts of the project to get lost when saving the files, then do warn that there is such a risk. further quotes : « For more information about quality management: https://en.wikipedia.org/wiki/Quality_management https://en.wikipedia.org/wiki/Corrective_and_preventive_action » |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-07-05 13:26 | JLuc | New Issue | |
| 2014-07-10 20:41 | JLuc | Tag Attached: PreflightChecker | |
| 2014-07-22 10:18 | JLuc | Note Added: 0032913 | |
| 2014-07-22 10:39 | JLuc | Note Edited: 0032913 | |
| 2014-07-22 10:43 | JLuc | Note Edited: 0032913 | |
| 2014-07-22 11:06 | JLuc | Note Edited: 0032913 | |
| 2014-07-22 11:11 | JLuc | Note Edited: 0032913 | |
| 2014-07-22 11:28 | Kunda | Note Added: 0032915 | |
| 2014-07-22 11:59 | ale | Note Added: 0032917 | |
| 2014-07-23 08:20 | JLuc | Note Edited: 0032913 | |
| 2014-07-24 09:56 | JLuc | Note Added: 0032959 | |
| 2014-07-24 10:54 | JLuc | Note Edited: 0032913 | |
| 2014-07-24 10:55 | JLuc | Note Edited: 0032959 | |
| 2014-12-08 19:52 | JLuc | Note Added: 0034286 | |
| 2015-02-01 23:57 | Kunda | Patch | => No |
| 2015-02-01 23:57 | Kunda | Summary | Warn when some image is outside "images" folder => Preflight Verifier: Warn when some image is outside "images" folder |
| 2015-02-01 23:58 | Kunda | Relationship added | child of 0012524 |
| 2015-04-09 20:01 | JLuc | Summary | Preflight Verifier: Warn when some image is outside "images" folder => Afterflight checker : Warn when some image is outside "images" folder |
| 2015-04-09 20:01 | JLuc | Description Updated | |
| 2015-04-09 20:01 | JLuc | Additional Information Updated | |
| 2015-04-09 20:03 | JLuc | Note Added: 0034867 | |
| 2015-04-14 07:10 | JLuc | Note Added: 0034923 | |
| 2015-04-14 07:14 | JLuc | Note Edited: 0034923 | |
| 2017-02-27 20:44 | JLuc | Note Added: 0043504 | |
| 2020-02-20 07:21 | JLuc | Relationship added | related to 0014133 |
| 2020-05-20 10:31 | JLuc | Relationship added | related to 0016115 |
