https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #38 from Thomas Schmitt <scdbac...@gmx.net> --- Hi, > I noticed that when the ISO file is not recognizable, "Burn image" window > shows no info about the file despite burning process is successful > (screenshot). Ahum. My olde Debian K3B shows with real ISO 9660 a "Filesize", some info from the ISO 9660 Primary Volume Descriptor, and an MD5 sum. Maybe "Filesize" stems from the PVD, too. The messages probably come from function createIso9660InfoItems() https://cgit.kde.org/k3b.git/tree/src/misc/k3bimagewritingdialog.cpp?id=0a7848344c470e70a845fa87463317f9c889f5fc#n168 There are more such functions: createCdrecordCloneItems(), createCueBinItems(), createAudioCueItems(). They are all called in slotUpdateImage(), where the confirmation dialog for unknown images is called, too. The message "Md5 sum:" stemms from function calculateMd5Sum(). It is called from slotUpdateImage() for ISO 9660 and some other recognized types. So K3B would need a new function createRawImageItems() which reports similar as e.g. createCdrecordCloneItems(): Detected: Image of unrecognized type Filesize: ... Image file: ... This new function and calculateMd5Sum() would then be called after the line d->foundImageType = IMAGE_RAW; which gets performed when the confirmation dialog has not aborted. Leslie, what do you think about such an augmentation ? Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
