MobileRead Forums - View Single Post - Found two bugs -- Related?

DiapDealer · 11-17-2016, 09:34 PM

1) Not a bug. That's by design. The file isn't getting "renamed," that's the file's id property in the manifest (and the idref property in the opf spine) that's being generated for the newly-created file from the split. It's a perfectly valid id. In fact, the "x" was prepended to the uuid generated starting with this latest version (0.9.7) so that it would always be valid. The uuid id is also only generated under very specific conditions (and only when using the "Split at Cursor" feature). It happens when the preferred id Sigil wants to use for the split file is already in use.

2) I've seen that on Windows. I don't see it on Linux. But I've never seen any functionality problems because of it. I assume it's a new cosmetic-only Qt quirk.

I'm not able to recreate the Python error when merging files, but I'll keep trying.

11-17-2016, 09:34 PM	#2
DiapDealer Grand Sorcerer Posts: 28,664 Karma: 205039118 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	1) Not a bug. That's by design. The file isn't getting "renamed," that's the file's id property in the manifest (and the idref property in the opf spine) that's being generated for the newly-created file from the split. It's a perfectly valid id. In fact, the "x" was prepended to the uuid generated starting with this latest version (0.9.7) so that it would always be valid. The uuid id is also only generated under very specific conditions (and only when using the "Split at Cursor" feature). It happens when the preferred id Sigil wants to use for the split file is already in use. 2) I've seen that on Windows. I don't see it on Linux. But I've never seen any functionality problems because of it. I assume it's a new cosmetic-only Qt quirk. I'm not able to recreate the Python error when merging files, but I'll keep trying. Last edited by DiapDealer; 11-17-2016 at 09:55 PM.