Sigil-0.9.8 Released

[notimp]

Originally Posted by KevinH

You can always compile and include your own tidy html5 library inside your plugin (one plugin author already does this) or you can use Sigil's internal gumbo library. Sigil's gumbo parser is a fork of Google's Gumbo parser that autocorrects using the exact same rules as browsers. Sigil gumbo library is available through the plugin api as well.

FWIW, You also might be better off parsing the file in gumbo first and then doing replacements of the text parts so that you do not break the xhtml syntax by funny search and replaces.

I think there is a simple example of using Sigil's gumbo in the testme plugin that is documented in the latest Plugin framework Developers guide.

Thank you for the clarification - I believe I also caught the switch to gumbo in changelogs several months ago but never saw it do its magic while lets say switching from source view to wysiwyg f.e. (or at least not in the way I needed it - it's been a while since I tested the new parser version) but if its a library I can call - it might work.

I'll also look into plugins other people have written already, as suggested.

I'm afraid the main enemy here is complexity. I'm confident I could hack together a little find/replace regex plugin in python - but calling other modules requires more "learning curve" first...

In any case - I'm doing some pretty freaky replacements (like search for this, followed by whatever, followed by that tag 1 or 3 times, which can also include that other tag 0 or 1 times...) so I'm relying on actually working on the html source and not just "visible text". (Because it turns out - that OCR software outputs have "predictable formating" you can actually take advantage of, if you wan't to modify text thats structured in a certain way - but ignore text that isn't - and the actual formating followed by formating (or not ) isn't something you can do on a text level.

The thing is, that it turns out, that you can pretty much automate ePub production from Finereader>Sigil or Finereader>Atlantis>Sigil (Atlantis = one of the best wordprocessing>epub converters out there) based on "predictable error profiles" that can be automated away by looking for sentence (missing end sign) structure and formating structure at the same time.

Short way of saying - I created a better method to create ePubs from Finereader results than is "available" on the international scene (shared/created it with a german "scenes" (dont ask ) board) in 2012 - that broke once tidy was removed. At which point it was more convenient to just tell everyone to keep using the older versions of Sigil, than to try to get the functionality back myself. The availability of a GUI frontend library for plugins now peaked my interest again.

I'll look into it (this isn't a promise of delivery - for people recognizing my nickname.. ).

[DiapDealer]

Originally Posted by notimp

THe availability of a GUI frontend library for plugins now peaked my interest again.

For the record: a gui frontend for Sigil plugins has always been available. External Python interpreters have always been able to use any GUI frontend that happens to be installed on a system, and Tkinter has been included since the first version of Sigil that came with a bundled Python implementation was released. Sigil v0.9.8 has simply added support for PyQt5 as well.

[notimp]

Again, thanks for the clarification.

[odamizu]

Originally Posted by KevinH

Just so you know, Apple really messed up on this ...

Originally Posted by KevinH

It gets worse ... This truly sucks.

YIKES!!! YIKES!!! YIKES!!! Sorry I opened this can of worms. 0.9.7 is working fine for me. Thank you for all your time and effort.

[blackest]

Originally Posted by odamizu

YIKES!!! YIKES!!! YIKES!!! Sorry I opened this can of worms. 0.9.7 is working fine for me. Thank you for all your time and effort.

Well thank you as that is my problem too on yosemite. I will see if i can build it. Did it before for Lion but that was a long time ago
Actually still have that dev environment on an old macbook probably. this might be harder than i thought. Certainly longer the qt compile part has been running 10 hours now and is around 80% complete...

[blackest]

I managed to get a fair way through the build but cmake failed

CMake Warning at src/CMakeLists.txt:65 (find_package):
Found package configuration file:

/Users/me/Qt56/lib/cmake/Qt5/Qt5Config.cmake

but it set Qt5_FOUND to FALSE so package "Qt5" is considered to be NOT
FOUND. Reason given by package:

Failed to find Qt5 component "WebKit" config file at
"/Users/me/Qt56/lib/cmake/Qt5WebKit/Qt5WebKitConfig.cmake"

Failed to find Qt5 component "WebKitWidgets" config file at
"/Users/me/Qt56/lib/cmake/Qt5WebKitWidgets/Qt5WebKitWidgetsConfig.cmake"

Failed to find Qt5 component "LinguistTools" config file at
"/Users/me/Qt56/lib/cmake/Qt5LinguistTools/Qt5LinguistToolsConfig.cmake"

Any suggestions how to fix this please?

[DiapDealer]

You either have to build a newer version of Qt5 yourself with QtWebKit added back in (Qt5.6 no longer includes it), or you have to use something like Qt5.5.1 (which still has QtWebkit as part of the binary downloads). The detailed instructions to build all of the pieces that Sigil requires can be found in the docs folder. There's several Mac specific documents in there.

As far as Linguist tools being missing from your system Qt5, I can only imagine it's a separate download of some kind (like it is for Linux). Those tools are needed to compile the language dictionaries.

EDIT: this may be moot as I think KevinH just uploaded a new version of 0.9.8 (the usual place) that should work on older versions of OSX.

[KevinH]

All Mac Users:

I just uploaded a new build that I was able to test under OSX 10.11 and 10.12 that should hopefully work under 10.10 and 10.9 as well. This all assumes that Qt5's "configure" is much better written that Python's configuration tests on Mac OSX when a MACOSX_DEPLOYMENT_TARGET setting is used.

Please give it a try and let me know of any issues or successes. It is available now in our github releases.

I have my fingers crossed.

[KevinH]

For the record ...

I filed a bug with Apple's developer site ...

The following testcase shows that the newly added function in sys/random.h is not in any way detectable as only being available on 10.12.

When compiled with XCode 8 on OSX 10.12

clang -mmacosx-version-min=10.9 -Werror=partial-availability -o testcase testcase.c

will compile and run on 10.12 but will fail with missing symbols on all earlier releases.

testcase.c

#include <sys/types.h>
#include <stdio.h>
#include <sys/random.h>

int main(int argc, char **argv)
{
  unsigned x;
  if (getentropy(&x, sizeof(x)) < 0)
    perror("getentropy");
  else
    printf("%u\n", x);
  return 0;
}

If getentropy in sys/random.h was properly protected by an availability macro such as testcase2.c

testcase2.c

#include <sys/types.h>
#include <stdio.h>
#include <AvailabilityMacros.h>

extern int getentropy(void* buffer, size_t size) AVAILABLE_MAC_OS_X_VERSION_10_12_AND_LATER;

int main(int argc, char **argv)
{
  unsigned x;
  if (getentropy(&x, sizeof(x)) < 0)
    perror("getentropy");
  else
    printf("%u\n", x);
  return 0;
}

The above compile would properly detect that getentropy did not exists in earlier version of OSX.

kbhend$ clang -mmacosx-version-min=10.9 -Werror=partial-availability -o testcase2 testcase2.c
testcase2.c:14:7: error: 'getentropy' is partial: introduced in macOS 10.12 [-Werror,-Wpartial-availability]
  if (getentropy(&x, sizeof(x)) < 0)
      ^
testcase2.c:9:12: note: 'getentropy' has been explicitly marked partial here
extern int getentropy(void* buffer, size_t size) AVAILABLE_MAC_OS_X_VERSION_10_12_AND_LATER;
           ^
testcase2.c:14:7: note: explicitly redeclare 'getentropy' to silence this warning
  if (getentropy(&x, sizeof(x)) < 0)
      ^
1 error generated.

If Apple can fix bugs like this, then we can fix Python's configure.ac/configure to more properly handle this case and not just to claim that it exists just because it is run on OSX 10.12.

Please note that we can NOT use the linker flags -Wl,-no_weak_imports to detect this case at link time as Python properly handles and uses weak symbols with #pragma weak properly used with statvfs, fstatvfs, lchown, and inet_aton so using weak symbols is needed.

Just wanted all of this out there in case in a few months I forget all of this.

[blackest]

Originally Posted by KevinH

All Mac Users:

I just uploaded a new build that I was able to test under OSX 10.11 and 10.12 that should hopefully work under 10.10 and 10.9 as well. This all assumes that Qt5's "configure" is much better written that Python's configuration tests on Mac OSX when a MACOSX_DEPLOYMENT_TARGET setting is used.

Please give it a try and let me know of any issues or successes. It is available now in our github releases.

I have my fingers crossed.

You can uncross your fingers for Yosemite at least its working fine.

[KevinH]

Originally Posted by blackest

You can uncross your fingers for Yosemite at least its working fine.

Wonderful news!

Thanks.

[DiapDealer]

Yay! Way to go, Kevin!

[odamizu]

Originally Posted by KevinH

All Mac Users: I just uploaded a new build that I was able to test under OSX 10.11 and 10.12 that should hopefully work under 10.10 and 10.9 as well ...
Please give it a try and let me know of any issues or successes.

On behalf of myself and my 10.11.6 Mac:

[alban lusitanae]

Hi to all

I was searching for the latest version 0.9.8 Portable version (I travel a lot, it's really needed) and I had a 0.9.7 link so I thought there would be a 0.9.8 Port but I can't find it. Is such a version going to happen and be placed on GitHub?

Best regards

[DiapDealer]

Originally Posted by alban lusitanae

Hi to all

I was searching for the latest version 0.9.8 Portable version (I travel a lot, it's really needed) and I had a 0.9.7 link so I thought there would be a 0.9.8 Port but I can't find it. Is such a version going to happen and be placed on GitHub?

Best regards

We have no connection to those who package portable versions of Sigil. You'll probably need to ask in the PortableApps forums.