![]() |
New Sigil Release: Sigil-0.8.901
Hi All,
The second (and hopefully final!) in our Sigil pre-release series, Sigil-0.8.901 is now available. This release is primarily a bug-fix release, although a couple of new features have slipped in. This release is much more stable than its predecessor all thanks to your testing and bug reports. If no major showstoppers are found, this pre-release will form the official Sigil 0.9.0 release and we will then start work towards Sigil 1.0 and reasonable epub3 support. As far as new features go, the tool box for plugins that use the embedded Python 3.4 interpreter, has been expanded. The embedded site-packages now include: six, html5lib, lxml, sigil_bs4 (Sigil's version of Beautiful Soup4), Google's Gumbo parser via a sigil_bs4_to_gumbo_adapter, PIL (Pillow image library), regex, cssutils, cssselect, chardet, and our own ctypes interface to the hunspell spell checker. This along with the new epub3 versioned plugin interfaces (see https://www.mobileread.com/forums/sho...8&postcount=95) should provide a quite powerful toolbox for plugin developers. Complete details of what is fixed and how to get is is available from our wordpress site: http://sigil-ebook.com To download binaries for Mac OS X and Windows, please see our github releases page: https://github.com/Sigil-Ebook/Sigil...es/tag/0.8.901 Please note, beginning with the Sigil 0.8.900 release, the process to build from source has changed greatly. Please check new instructions for building on Mac OS X, and Linux available on our github site. See the README.md and docs/ directory for complete instructions. As always, only download Sigil from its official home github site and remember to run a sha 256 checksum on your downloads and compare them against those posted in the release on github to make sure you have downloaded the exact same binary that we have uploaded. When the the next full release build is made, I will be signing the Mac OS X builds with my Mac OS X Developer account (assuming I can figure out how to do that!). Leave it up to Apple to charge volunteer developers just to build and release GPL OpenSource projects! They are indeed clueless. Again, for fastest resolution, please post any bug reports or feedback on this release in this thread in the Sigil forum and we will try our best to address any serious issues in quick follow-up release if needed. Thank you for using Sigil and helping to make it better! KevinH and DiapDealer |
:thumbsup: :thanks:
|
Wonderful!
All seem to work perfectly and faster than before: many thanks. |
W10 X64
:eek: Using a Sigil split marker (loaded by S&R) files, results in a scrambled (splits at the end) book IIRC this was a OLD issue that was fixed S&R status (how many, not found) missing. The lS&R box wobbles like it was trying ;), but nada showed :blink: Crash unfortunately, I can't remember the precise edit function I was performing, only that I had been doing a lot of successful (scan) cleanup before that happened |
I have no earthly idea what you mean by a "wobbling" S&R box! ;)
|
I have an MR download "Bleak House" from HarryT that uses divs instead of p for paragraph classes. Any span within the div gets a lot of whitespace put around it by Prettyprint. This adds spaces into the text. Look for italic spans to see the effect.
--MH |
Quote:
|
Quote:
Regardless of the crazy whitespace added in code view, Pretty-Print results in extra space being rendered after "Matthew Bagnet:" In the third entry ("Matthew Bagnet:*The owner of a music shop;"). That extra spacing isn't there when pretty print is turned off. |
Quote:
-Some attached html -The exact search/replace expression you're using to insert split markers -what you're seeing after you split, and what you think you should be seeing after you split. Keep in mind that you may not be able to use saved expressions/clips that are based on the way the old Sigil pretty-printed code (without tweaking them first). The Gumbo Pretty-print does not produce the exact same thing that the old Sigil Pretty-Print did. I'm still not quite certain what you're describing with regard to the S&R functionality. Quote:
|
Quote:
I don't remember when. But I had the same and with Matches. It displayed nothing and not "Matches found:xx" I think when i haven't any of the Option cheked. |
Hi,
I really and truly need an example ebook and the exact sequence of steps to have any idea what you are talkign about here? I really haven't a clue. So please attach a small epub example and please include a detailed sequence of steps to recreate the issue. None of the4 S&R code was touched in the large change since Sigil 0.8.7, so it should not be broken in any way but perhaps the problem is caused by something outside of the S&R code? I really need an example and specific steps to track it down. Thanks, KevinH |
The Search and Replace part works fine.
in Sigil.8.x there is a status line as Gipsy indicated. That is missing. When it SHOULD appear, the S&R box does some sort of resize/refresh jiggle. Splitting (the same way I do with 0.8.7) I insert the standard: <hr class="sigil_split_marker" /> Manually, or by S&R code into the various HTML files later, I press <F6> to split the whole lot BTW When this happened before (Sigil2?) , valloric could not find it because he only had 1 file being split. I was splitting 4+ (each 240K limit break point of older devices ). All the splits ended up AFTER the last original pre-split file |
Quote:
This source file hasn't been touched since before the 0.8.7 release. |
Quote:
|
Quote:
Sigil 8.7: I extended my desktop so that one monitor (primary) had the preview pane all to itself, the other monitor had Sigil. When I tried to change a S&R option ("This Page" to "All HTML pages") the box just jiggled and did NOT drop down to show the list of options. When I returned the preview pane to it's rightful place (docked on the right side of the window) and went back to displaying only on the secondary monitor...then the problem went away. So, this very well may be a QT5 issue that doesn't have anything to do with 8.901 Cheers, |
Hi,
I think this problem is my fault. The damn tr() function to actually translate text is actually what is returning blanks instead of the message it is supposed to show. I think this is because somehow I have generated a base.ts that seems to be seems to be missing all file info and line numbers. I compared it to the base.ts that was in the Sigil 0.8.X branch and it properly had line numbers and did not display this empty message nonsense. So I have taken a chance and rebuild cleanly base.ts so it now has all of the file info and line numbers in it and will upload it to transifex for translating. Hopefully I have not lost anything by doing that but that was the only way to fix the issue and get the messages back for me. I will check out things tomorrow to make sure I have not messed up any other language translations doing it. I have my fingers crossed. But my what a strange problem! KevinH |
Quote:
|
Quote:
|
Select some text in code view - click to Superscript. Sigil crush.
I try to duplicate it without result. |
Is this with Windows? If so, it may be clipboard related. I have not been able to duplicate this subscript issue on Linux or Mac. If you run into it again please let us know.
KevinH |
Hi All,
Given the very few bug reports, I think we have achieved some sort of stability here. We will wait a few weeks in case anything else shows up and then declare the pre-release series done and release a very slightly updated version (hopefully with working messages in Find/Replace), plus a number of other minor changes) as the official Sigil 0.9.0. Thanks all for your continued use and bug reports. KevinH |
Yes Kevin, in Windows 10
|
In the previously releases when you save and you have something like this...
Code:
<p class="subtitle"> ΠΕΡΙΘΩΡΙΑΚΑCode:
<p class="subtitle">ΠΕΡΙΘΩΡΙΑΚΑ</p>EDIT: Another example Code:
<div class="footnote"> |
Hi,
The change you want makes no sense as it removes whitespace that may in fact be part of the paragraph both before and after the exact text (up to one character of each. Quote:
Yes, pretty print has changed a lot, It will no longer trim whitespace from inside of paragraph tags as it should not since whitespace can be important both before and after any text (at least up to one character's worth). Quote:
I am not sure either of these are bugs. You seem to be asking for the old Tidy approach of a deep clean. I am sorry but those days are pretty much gone. If you want me to modify prettyprint to reduce multiple spaces into one space inside of the p tag, that may be doable, but stripping it all away is simply incorrect. KevinH |
The old days the last example turn to...
Code:
<div class="footnote">Thanks KevinH |
Hi,
So do you think prettyprint should ignore the newline and completely remove it as opposed to replacing it with a single space? See the extra space below: Code:
<div class="footnote">Code:
<p>Code:
<p>Thisisalineoftext.</p>[code] <p>This is a line of text.</p> [/code. So dropping newlines and not replacing them with spaces can lead to nonsense just as easily as it can lead to good things. That is why I try to have prettyprint leave whitespace inside of tags alone as much as possible. KevinH |
My mistake. The pretty in 0.8.7 change it like your code, with a space after "Some text".
And I don't want to completly remove the newline :) But the Code:
<p>Code:
<p>This is a line of text.</p>Code:
<p>This<br/>is<br/>a<br/>line<br/>of<br/>text.</p> |
Hi,
Okay, I can live with changing newlines to spaces and replacing a sequence of multiple spaces with a single space when text is inside a tag like p. I will try to play around with gumbo prettyprint to do that hopefully without breaking anything else. KevinH |
Thanks KevinH,
leave it as is now and focus to other things for the next release :p As I say and before, it's not that important. :thumbsup: |
Hello:
Very nice release guys! I do, however, have a question: Will the next non-beta release rewrite the tags: Quote:
I sometimes start with html from the web, and the initial declaration is sometimes different, so short of copying the snippet to before the <body> tag, is there a more efficient way (perhaps a plugin)? Thanks…. |
Hi,
As far as I can tell, gumbo will happily parse all types of doctypes and return then to their original condition including html5 doctypes !DOCTYPE html. If you find a case where it does not do that, please report it and I will try to track down where things are getting messed up. Take care, Kevin Quote:
|
I installed this latest version today and the ePub I made it in will not display properly in any of my ePub testing apps (ADE, Aldiko), nor my Kobo; it's as if the CSS cannot be read. Yet it displays properly in Sigil, and I can convert the file to Kindle using Kindlegen and the ebook displays as coded.
All my ePubs built using earlier versions display properly in my ePub apps. I have compared the header code and Content.opf code between the old ebooks and this new one and cannot find anything amiss. Any ideas? |
Quote:
|
Quote:
Right-click on the CSS in the Book browser: Validate with W3C (the red ones) |
Yep. Looks fine using WebKit, but not with ADE/RMSDK = CSS syntax error. Nine times out of ten. The tenth time = an embedded font that's incompatible with ADE/RMSDK. ;)
|
Quote:
Thanks for the tip to validate with W3C. Will try that next time I run into a problem. |
Quote:
FWIW, calibre preserves whitespace entirely, on the rationale that when using <pre>, whitespace matters. IIRC, only whitespace outside a block-level tag gets reformatted when pretty-printing. Sigil may or may not wish to follow the same approach. :) ... Seems like an unwise (and unlikely) thing to use, IMHO, but I'd hate to be responsible for Sigil breaking a book because of this. :D |
Hi eschwartz,
Yes, I agree. That is why we moved away from Tidy (it cleaned too much and did not fully support all html5 tags, svg tags, and math tags). Regular gumbo serialization, changes no whitespace whatsoever. gumbo prettyprinting will now condense multiple whitespace on any allowed tag (and that is quite a specific list to prevent problems) and will trim leading and trailing whitespace from inside p tags only. All other places, people will just have to live with it or edit it by hand. I am thinking of creating a "Clean-and-Sanitize" plugin using the html5lib's parser and sanitize code and a few things like that just to give people the option of "heavy cleaning" if they end up starting with heaping piles of crap html code (ie. read that they have unpacked an entire mobi7 book to one huge html file with lots of out of date html 3.2 pieces flying around. Thanks! KevinH |
I'm think that in the future (not immediate mind you ;) ), we may want to add a new pretty-print plugin type. One that can be used in the"traditional" PluginRunner dialog setting (for debugging purposes), but can also be "assigned" via the clean source settings using a combobox populated with installed pretty-print plugins.
I've been mulling the idea around in my head for a bit. And it'll probably mull a little longer. The bottom line is: Sigil's not overly concerned with making your code look "pretty" any more. It's more concerned with not breaking anything. We are, however, dedicated to providing a framework that offers users a way to manipulate their code in any way they see fit--through a robust plugin system. My two cents anyway. |
Windows 10, 32-bit.
Sigil crashes repeatedly a) at uploading a cover image (in "Tools"->add cover, not at uploading other Images in the respective Folder of the book browser)), b) when trying to create TOC via Tools->TOC->create Toc. No Problem when I add a cover/TOC in a different program and open the epub afterwards in Sigil. Am I the only concerned Person? |
| All times are GMT -4. The time now is 08:14 PM. |
Powered by: vBulletin
Copyright ©2000 - 3.8.5, Jelsoft Enterprises Ltd.
MobileRead.com is a privately owned, operated and funded community.