New Sigil Release: Sigil-0.8.901

[eschwartz]

http://www.regular-expressions.info/

[theducks]

Originally Posted by Notjohn

Would you point me to that simple guide? Gosh knows, I need one!

MR members Pablo and Manichean, both wrote tutorials quite a while back (early 201x's).


Manichean's was the first and the one that got thru my thick skull

[DiapDealer]

We're drifting a bit from the purpose of this thread again. This is not the thread for learning how to use features long present in Sigil. If you don't understand a particular feature of Sigil (that wasn't introduced in 0.8.901) please start a separate thread about it.

New feature requests should also have their own threads.

Thanks

[Arios]

Hi Kevin and Diap,

Sorry, but I found an error in Sigil 0.8.901.0 (win 7, HP 64 b).

I was playing with a new crutledge's epub (Shawnee's Warning, The, here: https://www.mobileread.com/forums/sho...d.php?t=266762). By habit I made a SanityCheck which has barked with the following message:

Embedded Python Error

Traceback (most recent call last):

  File "F:/Sigil89/python3lib\sanitycheck.py", line 290, in perform_sanity_check
    has_error, errlist = p.check()

  File "F:/Sigil89/python3lib\sanitycheck.py", line 61, in check
    for text, tp, tname, ttype, tattr in self.parse_iter():

  File "F:/Sigil89/python3lib\sanitycheck.py", line 213, in parse_iter
    tname, ttype, tattr = self.parsetag(tag)

  File "F:/Sigil89/python3lib\sanitycheck.py", line 97, in parsetag
    error_msg = 'Tag name not properly delimited: "' + self.s[b:p] + '"'

AttributeError: 'SanityCheck' object has no attribute 's'

No problem with the message, but after that Sigil doesn't close, the process must be killed.

PS Sigil 8.6 has no problem nor epubcheck 4.

[DiapDealer]

Originally Posted by Arios

Sorry, but I found an error in Sigil 0.8.901.0 (win 7, HP 64 b).

No need to apologize, by the way. Even if it HAD been a heretofore unmentioned bug.

[KevinH]

Hi,

Actually that is still an unfixed bug. It just no longer gets hit. The self.s[b:p] should really be s[b:p].

I will fix this now and commit the fix to master.

So I am very happy you submitted the bug report!

KevinH

Originally Posted by Arios

Hi Kevin and Diap,

Sorry, but I found an error in Sigil 0.8.901.0 (win 7, HP 64 b).

I was playing with a new crutledge's epub (Shawnee's Warning, The, here: https://www.mobileread.com/forums/sho...d.php?t=266762). By habit I made a SanityCheck which has barked with the following message:

Embedded Python Error

Traceback (most recent call last):

  File "F:/Sigil89/python3lib\sanitycheck.py", line 290, in perform_sanity_check
    has_error, errlist = p.check()

  File "F:/Sigil89/python3lib\sanitycheck.py", line 61, in check
    for text, tp, tname, ttype, tattr in self.parse_iter():

  File "F:/Sigil89/python3lib\sanitycheck.py", line 213, in parse_iter
    tname, ttype, tattr = self.parsetag(tag)

  File "F:/Sigil89/python3lib\sanitycheck.py", line 97, in parsetag
    error_msg = 'Tag name not properly delimited: "' + self.s[b:p] + '"'

AttributeError: 'SanityCheck' object has no attribute 's'

No problem with the message, but after that Sigil doesn't close, the process must be killed.

PS Sigil 8.6 has no problem nor epubcheck 4.

[Arios]

Thanks Kevin,

This is my first bug report without any bugs, I would have been devastated if it had been for nothing...

And the incriminating crutledge's epub could now be renamed: Arios's Warning, The

PS To Doitsu and DiapDealer: I feel sorry (a little ) because I think as a writer for whom a spelling mistake is horrible and not as a programmer for whom a dead bug mean an app more lively... something like that

[sinclair]

Hi everyone,

Sorry if this has already been reported elsewhere, but I seem to have found a serious bug that is making Sigil pretty much unusable for producing a clean epub. I'm using version 0.8.901 on Windows 10 and it keeps messing up the html escape characters in my html documents. For example, when I open my html file in Sigil it changes an emdash ( &mdash into — Unfortunately it's also doing the same to single double quotes and basically every html escape I have in my html file.
If I go into 'Preferences' and then 'Clean Source' and untick both the 'Open' and 'Save' boxes for automatically cleaning the html source, it makes no difference. If I correct the html escape codes and then save and close the epub, when I reopen it, it once again messes up all the html escape characters. Similarly, if I add all the html escape characters to the 'Preserve Entities' box that doesn't seem to make any difference either. Hope this information is helpful.

Paul

[KevinH]

Hi sinclair,

I simply can not recreate this at all. mdash and nbsp seem to be working well and no duplication or anything else.

That said, if your html is not well formed ie. missing an opening < or closing > or /> , the gumbo parser will do strange things to try and prevent removal of your data. So please load up a copy of your file and run SanityCheck (the checkmark) on it. Please let me know what it tells you.

KevinH

Originally Posted by sinclair

Hi everyone,

Sorry if this has already been reported elsewhere, but I seem to have found a serious bug that is making Sigil pretty much unusable for producing a clean epub. I'm using version 0.8.901 on Windows 10 and it keeps messing up the html escape characters in my html documents. For example, when I open my html file in Sigil it changes an emdash ( &mdash into &amp;amp;mdash; Unfortunately it's also doing the same to single double quotes and basically every html escape I have in my html file.
If I go into 'Preferences' and then 'Clean Source' and untick both the 'Open' and 'Save' boxes for automatically cleaning the html source, it makes no difference. If I correct the html escape codes and then save and close the epub, when I reopen it, it once again messes up all the html escape characters. Similarly, if I add all the html escape characters to the 'Preserve Entities' box that doesn't seem to make any difference either. Hope this information is helpful.

Paul

[DiapDealer]

Entering the entities you wish to preserve in the Preserve Entities prefernces certainly works for quite a few people (myself included). There are some rare entities that it doesn't work for, but emdash is certainly one that works for me and many others.

For the record, the gumbo parser does not speak "entity," so unless the entities are properly entered in the Preserve Entities list first, they will all be converted to their unicode characters equivalents. This is just how Sigil works now.

But this is this first I've ever heard of entities being re-"entitied." The only time I've ever seen anything like that is if someone tries to type (or paste) an html entity/tag into Book View. If that's the case, then Sigil is correct in changing &mdash; to &amp;mdash; in Code View. Just like a typing an html tag (like <h2>) in Book view will result in &lth;2;&gt; in Code View.

Can you provide a small sample (non-copyrighted) epub and the documented steps to reproduce what you're seeing? That would be very helpful. Thanks.

Originally Posted by sinclair

Hi everyone,

Sorry if this has already been reported elsewhere, but I seem to have found a serious bug that is making Sigil pretty much unusable for producing a clean epub. I'm using version 0.8.901 on Windows 10 and it keeps messing up the html escape characters in my html documents. For example, when I open my html file in Sigil it changes an emdash ( &mdash;) into &amp;amp;mdash; Unfortunately it's also doing the same to single double quotes and basically every html escape I have in my html file.
If I go into 'Preferences' and then 'Clean Source' and untick both the 'Open' and 'Save' boxes for automatically cleaning the html source, it makes no difference. If I correct the html escape codes and then save and close the epub, when I reopen it, it once again messes up all the html escape characters. Similarly, if I add all the html escape characters to the 'Preserve Entities' box that doesn't seem to make any difference either. Hope this information is helpful.

Paul

[sinclair]

Hi KevinH and DiapDealer,

Thanks for your kind advice, which seems to have solved the problem.

I added the latest Sanitychecker plugin to Sigil and opened the html file. I manually fixed all the messed up html escape entities using find and replace and then ran Sanitychecker. It then came up with the message 'No problems found!'.

Then I went to the Preserve Entities preferences and deleted the entities I had and then re-entered them. After closing the html file without saving it and re-opening it Sigil stopped messing up the Escape entities. Not sure what exactly happened there, but perhaps I had entered one or more of those html entities incorrectly. Anyway, it seems to be working properly now. Many thanks again for your help.

Paul

[KevinH]

Hi sinclair,

Glad to hear it! FYI: SanityCheck is now built in to Sigil-0.8.901 under the Checkmark symbol that used to run FlightCrew. So no need to add the plugin to run SanityCheck any more in recent versions of Sigil.

Take care,

Kevin

Originally Posted by sinclair

Hi KevinH and DiapDealer,

Thanks for your kind advice, which seems to have solved the problem.

I added the latest Sanitychecker plugin to Sigil and opened the html file. I manually fixed all the messed up html escape entities using find and replace and then ran Sanitychecker. It then came up with the message 'No problems found!'.

Then I went to the Preserve Entities preferences and deleted the entities I had and then re-entered them. After closing the html file without saving it and re-opening it Sigil stopped messing up the Escape entities. Not sure what exactly happened there, but perhaps I had entered one or more of those html entities incorrectly. Anyway, it seems to be working properly now. Many thanks again for your help.

Paul

[jugaor]

Hi.
Thank you very much for keeping alive the Sigil project!

1. I think I've found a serious problem with Pretty Print Gumbo (0.8.901, Win7-x64): it joins contiguous labels, creating false "long" words.
Ex:

<p><u>Prueba</u> <i>de</i> <b>texto</b> <span class="nosep">junto</span></p>

becames

<p><u>Prueba</u><i>de</i><b>texto</b><span class="nosep">junto</span></p>

It reads: Pruebadetextojunto.
(Besides the use of deprecated < u > tags )
BTW, the Google Gumbo-Parser is fine (although I don't want changes to the code --as I understand it is equivalent to the previous HTML Tidy).

2. It's possible maintain two versions of Sigil, with independent Preferences folders? I prefer to keep active the 0.87 Pretty Print Tidy option for the daily work, but launching 0.89 it becomes the now erroneous PPGumbo.


Thank you very much!
(and sorry for my terrible English.)

[DiapDealer]

Originally Posted by jugaor

BTW, the Google Gumbo-Parser is fine (although I don't want changes to the code --as I understand it is equivalent to the previous HTML Tidy)

No. Google Gumbo-Parser is not the equivalent of HTML Tidy. In fact, Google Gumbo-Parser is the option you want to select if you want Sigil to make the very least changes to your code possible. Pretty-Print is the more intrusive option.

Originally Posted by jugaor

2. It's possible maintain two versions of Sigil, with independent Preferences folders? I prefer to keep active the 0.87 Pretty Print Tidy option for the daily work, but launching 0.89 it becomes the now erroneous PPGumbo.

I'm afraid this isn't very likely to happen. If you wish to run two different versions of Sigil on the same machine, I would recommend using something like Portable Apps' version of Sigil for the older version.

Originally Posted by jugaor

1. I think I've found a serious problem with Pretty Print Gumbo (0.8.901, Win7-x64): it joins contiguous labels, creating false "long" words.
Ex:

<p><u>Prueba</u> <i>de</i> <b>texto</b> <span class="nosep">junto</span></p>

becames

<p><u>Prueba</u><i>de</i><b>texto</b><span class="nosep">junto</span></p>

It reads: Pruebadetextojunto.
(Besides the use of deprecated < u > tags )

I can confirm what you're experiencing here. The problem is really exacerbated when the only "text" outside of inline tags (inside a block-level tag) is whitespace. Recommendation for now is to exclusively use the Pretty Print Gumbo clean source setting. At least until we move Pretty Print to a plugin (or at least a feature separate from the clean source settings) where it belongs.

[KevinH]

Arrggh ... that prettyprint bug will need to be fixed before any Sigil-0.9.0 release.
I'll take a shot at it later this afternoon to see if I can track down where single whitespace inside a p tag is being lost.

Thanks for your bug report!

KevinH