View Single Post
Old 01-09-2022, 11:32 AM   #111
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,915
Karma: 6120478
Join Date: Nov 2009
Device: many
I just tested this in master under Qt6. I took an epub, restructured it to Sigil norm, then renamed the content.opf to package.opf and saved it.
When I loaded up that just saved test epub, it was detected as non-standard properly.

I then Restructured it to Sigil norm again (which changed package.opf back to content.opf) and it properly detected and added the [std] to the Window title.

So based on this, the bug you reported must exist only in the arm64 version of Qt or Sigil.

Until I get an arm64 machine tracking this one down is going to be impossible.

Sorry.


Quote:
Originally Posted by KevinH View Post
The [std] indicator is updated after every File/Resource addition, deletion, or move so it catches every standardize test I tried.

Thinking about it more now, that does leave out rename, but the only two names that mean anything to standardization are the opf name and the ncx name (if it exists). So could the only things that were not standard in bug test case be "content.opf" or "toc.ncx" before you standardized it?

If so, let me know and I will see if there are signals for renaming both that I can hook to somehow to detect when to update the Window title bar.

KevinH
KevinH is offline   Reply With Quote