0.5.901 (0.6.0 beta) avaliable

[crutledge]

I have installed both the win 64bit and 32bit. I usually activate Sigil thru the "send to" menu.

Everything works fine using epub files and looks very nice.


Both versions refuse to load HTML files. Both from the "send to" menu or from a running instance of Sigil, the system reports "program has stopped running,"

I hope I haven't done something dumb.

PS: I'm using Win 7.

[roger64]

Originally Posted by meme

Make sure you turn Tidy to Pretty Print and restart Sigil .

With Pretty Print, everything is OK: no sgc, no artefacts...

@crutledge
Loading html file is OK too.

Linux deb package 64 bits

If it can help testing,I join a deb package for amd64. I use it for Debian. I make no warranty at all of any kind. Just for beta testing purposes. Should not explode though...

To launch Sigil: /usr/local/bin/sigil or create a launcher.
To uninstall: dpkg -r sigil

[DiapDealer]

Is PCRE being compiled in the beta with same options as it was in v0.5.3? As mentioned in another thread, I can't seem to get certain unicode classes to work in the beta like I did in 0.5.3. Namely, stuff like \p{L} or \p{Lu}. Has there been a change, or have I just not configured my build environment properly, or is this a known issue? (building beta from source on ubuntu 11.10 64-bit)

[user_none]

Originally Posted by DiapDealer

Is PCRE being compiled in the beta with same options as it was in v0.5.3?

0.5.901 uses the UTF-16 version with JITing enabled.

[DiapDealer]

Originally Posted by user_none

0.5.901 uses the UTF-16 version with JITing enabled.

But no "--enable-unicode-properties" like with the previous version? I believe that's what gets you the \p{..}, \P{..}, \X support.

[user_none]

Originally Posted by DiapDealer

But no "--enable-unicode-properties" like with the previous version? I believe that's what gets you the \p{..}, \P{..}, \X support.

It wasn't a build option in 0.5.3...

There could be a build system issue here. With 0.5.901 the build system will prefer system version over the bundled version. If you have PCRE development files installed those will be used. You can use the -DFORCE_BUNDLED_COPES=1 to force the use of the bundled versions. Otherwise the bundled version will only be used as a fall back if the system one is not found. Can you re-run cmake with that flag and recompile. This will ensure that it's not a build system issue.

If you're still having the same problem after verifying that you're using the bundled copy can you add:

SET(SUPPORT_UCP 1)

on line 77 (or about) to src/pcre/CMakeLists.txt. Then rebuild and see if it works properly.

[DiapDealer]

I don't have any PCRE dev stuff unstalled on that particular machine, but to be safe, I went ahead and ran cmake with the -DFORCE_BUNDLED_COPIES=1 flag, but unfortunately, once built... the Sigil binary seg-faulted when trying to run. Not sure what was up there. But anyway... compile time messages indicate no local pcre packages were found and it is indeed using the bundled copy.

Anyway... long story short... the SUPPORT_UCP option does need to be enabled for unicode property support to work--including the (*UCP), \p{..}, and \X stuff.

I hope you consider enabling that by default going forward, but at least I learned how to configure it myself if necessary. Thanks for that.

[pwr]

About compiling Sigil -- is there a downloadable version of the Qt libraries for Windows x64 that I haven't been able to find, or do I have to build my own?

[Serpentine]

Originally Posted by pwr

About compiling Sigil -- is there a downloadable version of the Qt libraries for Windows x64 that I haven't been able to find, or do I have to build my own?

The Qt SDK - somewhat obvious

Comes with QtCreator, the IDE which is pretty good these days, however if you're using VS you need to fetch the plugin which makes projects easier to work with.

[pwr]

I did try both the Qt SDK and the Qt libraries. And they both come in x86 (32bit) flavor only. When building Sigil for the x64 platform, I get a LNK1112 linker error at the end, and I suspect it's because of the Qt libraries.

[roger64]

User guide - About standard PNG images

I am still amazed at how tight and efficient your code is for standard PNG images.
I had to try it on a separate book to convince myself there was not any trick...

Spoiler:

<div class="image"><img alt="" src="../Images/numéro01.png" /></div>

and the CSS rules I found (maybe even only the first one here applies)

div.image {
	text-align: center;
	margin-top: 1em;
	margin-bottom: 1em;
	page-break-inside: avoid;
}

img {
	max-width: 100%;
}

I remarked that your images scale very well. I tried with a "standard" png image and it did scale but not so well. Maybe, this is due to the fact that your images are set in some kind of frames? (see third screenshot)
1. - Image properties
Now, in Book view, when double clicking, we can access to the "Properties" of images and modify them. However, I noticed that these fields (width, height, etc.) were not even filled up in your Guide (see screenshots). Could you comment this?

2. - The standard images in your guide are all centered. What would have been your recommended code for a floating one?

[wokavan]

Thanks for all the work on Sigil!

A few things I've noticed in the Beta (on Mac OS 10.6.8)

- Is it no longer possible to apply pure html bold/italic tags in Book View? For example, previously if you used the GUI or CMD-B shortcut Sigil would use < b >, but now it relies on spans and in-line CSS.

- Relatedly, the bold / italic gui buttons don't highlight when inside bold/italic content (whether it's been created with html b/i tags or spans and in-line css).

- Is it no longer possible toggle Tidy on and off?

[JSWolf]

Originally Posted by roger64

- Opening the chapters of the guide, I found inline sgc styles. Current version does not have these sgc styles. See joint images:

In order to not have SGC styles, you'll need to open Sigil with no ePub, turn off Tidy, close Sigil and do not ever turn Tidy back on. Tidy is changing things as it feels you should have everything in styles. So paragraph level codes get converted to SGC styles.

[JSWolf]

Originally Posted by roger64

This is what I mean about dropcaps. Lower down is the difference of display between current and beta.

EDIT Found the reason: On beta version, I left Tidy on. Tidy does not like my dropcaps and decided to put their code in order... On current version, Tidy is off. Sorry for this...

However, the creation of the unwanted inline styles shown above is not due to a Tidy'mischievous action because they stay put even when Tidy is turned off.

They stay put because you've already infested the ePub with them. You have to have Tidy off before loading the ePub and the ePub has to be SGC free.

[roger64]

Originally Posted by JSWolf

In order to not have SGC styles, you'll need to open Sigil with no ePub, turn off Tidy, close Sigil and do not ever turn Tidy back on. Tidy is changing things as it feels you should have everything in styles. So paragraph level codes get converted to SGC styles.

Very clear. As meme advised me, now I am hooked on Pretty Print mode and I do not even look backwards.

Dropcaps

This is to explain what happened about dropcaps.

What Tidy does not like are the two spans let1 and let2. He absolutely wishes to mix them, which totally wreaks the display.