Possible Bug in Sigil 0.8.7 - Page 2

dragon reader · 10-23-2015, 10:21 PM

it is font specific; very strange.

dragon reader · 10-23-2015, 10:26 PM

it is font specific; but also seems tied with the size of font. Very strange.

dragon reader · 10-23-2015, 10:57 PM

could the font problem be connected with the number of css entries you have and if you are using a secondary css while getting rid of the garbage in code view in main part of book.

KevinH · 10-23-2015, 11:07 PM

Hi,
No its just a broken font.

Simply google: consolas font metrics broken

dragon reader · 10-24-2015, 10:30 AM

You could set Liberation Font and replace Consolas, especially since Liberation is free source. The Calibre Editor is also using them.

Liberation is not available as an alternate in css or code view. But is available in book view and preview.

KevinH · 10-24-2015, 10:44 AM

Any monospaced font should work.

That default font was changed early on, but for people using old Sigil ini files, some still get Consolas. I use Courier New.

KevinH · 10-24-2015, 11:54 AM

Hi,
I checked the commit history of Sigil and all traces of Consolas have been replaced by Courier New in settings and things early in the Sigil 0.8 series. The only reason you are still defaulting to Consolas is because your Sigil.ini settings file was created before the change took place. So either choose Courier New yourself in tha Appearance settings or after backing up your old Sigil.ini file, remove it, and on next launch a more sane set of defaults will be created. Newer users will never see this issue, as Consolas is never used anymore.

KevinH

jugaor · 11-01-2015, 09:59 AM

Quote:

Originally Posted by DiapDealer

If you're going to stick with an older version of Sigil, I'd go with 0.8.6 -- as 0.8.7 had known issues.

Hi, DiapDealer.
Please, could you briefly explain these issues of 0.87?
I use it daily, bc I read it's a 'bug-fix release' of 0.86 ... what is the advantage of keeping this one?

TIA!

eschwartz · 11-01-2015, 10:12 AM

More bugfixes.

And the 0.8.901 changelog: https://github.com/Sigil-Ebook/Sigil.../ChangeLog.txt

jugaor · 11-01-2015, 09:38 PM

Quote:

Originally Posted by jugaor

Hi, DiapDealer.
Please, could you briefly explain these issues of 0.87?
I use it daily, bc I read it's a 'bug-fix release' of 0.86 ... what is the advantage of keeping this one?

Quote:

Originally Posted by eschwartz

More bugfixes.

And the 0.8.901 changelog: https://github.com/Sigil-Ebook/Sigil.../ChangeLog.txt

Thank you for your reply, eschwartz.
I'll try to be clearer

:

Those who wish to remain with the 0.8x branch, at the moment, why choose 0.86 versus 0.87? What are the "known issues" that prevent use 0.87? (as DiapDealer said).

eschwartz · 11-01-2015, 09:56 PM

Hmm, I don't know.

Comparing the versions in git shows me three commits, two of which affect building Sigil on OSX only, and the third updates the text in the credits.

As the Changelog says:

Update links
Try to work around clang compiler issues with older C++ cdebase

...

Well, maybe the version of Qt5 it was built against was different. But I'd expect later versions of Sigil to build against later versions of Qt5, which if anything would get rid of bugs...

KevinH · 11-02-2015, 06:11 AM

One change related to fixing the source for clang compiler issues was incorrect and under some circumstances can cause bugs. Reverting that change brings us effectively back to Sigil 0.8.6. So using Sigil 0.8.6 is recommended over Sigil 0.8.7.

KevinH

DiapDealer · 11-02-2015, 07:51 AM

Thanks Kevin. I couldn't remember exactly what the problem was with 0.8.7, but I knew there was something.

KevinH · 11-02-2015, 08:01 AM

Here is me reverting the change after the Sigil -0.8.7 release.

https://github.com/Sigil-Ebook/Sigil...18640a7987f111

It caused some signals to not be properly attached to some slots in MainWindow causing even some primary buttons to stop working seemingly randomly, and lots of hard to detect issues. So again, I strongly recommend using the latest Sigil (especially the forthcoming Sigil-0.9.0) but if that is not possible then use Sigil 0.8.6 over any earlier releases.

Hope this helps,

KevinH

KevinH · 11-02-2015, 10:15 AM

Quick question.

Once we decide to strip out PrettyPrint and make-it a plugin, would anyone be interested in a Tidy pretty-print plugin? I should be able to extract the Tidy code out of the Sigil-0.8.X series into its own github project and create a plugin from it if anyone truly misses Tidy.

Kevin

11-01-2015, 09:56 PM	#26
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	Hmm, I don't know. Comparing the versions in git shows me three commits, two of which affect building Sigil on OSX only, and the third updates the text in the credits. As the Changelog says: Update links Try to work around clang compiler issues with older C++ cdebase ... Well, maybe the version of Qt5 it was built against was different. But I'd expect later versions of Sigil to build against later versions of Qt5, which if anything would get rid of bugs... Last edited by eschwartz; 11-01-2015 at 10:03 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Sigil 0.8.6 and CSS cleanup tool bug	steven522	Sigil	18	07-16-2015 01:57 AM
Table of Content click-bug inside Sigil	steven522	Sigil	6	12-30-2014 03:33 PM
Sigil on Nook vs Sigil on Kobo vs Sigil on iBook	rosshalde	Sigil	12	11-13-2014 09:34 AM
possible h1 bug in Sigil 0.6.1?	michaelbr	Sigil	2	12-04-2012 07:56 PM
Jumping Tocs (Bug Sigil 0.3.1)	pedoll	Sigil	1	11-09-2010 05:31 AM

10-23-2015, 10:21 PM	#16
dragon reader Member Posts: 15 Karma: 10 Join Date: Oct 2015 Device: none	it is font specific; very strange.

10-23-2015, 10:26 PM	#17
dragon reader Member Posts: 15 Karma: 10 Join Date: Oct 2015 Device: none	it is font specific; but also seems tied with the size of font. Very strange.

10-23-2015, 10:57 PM	#18
dragon reader Member Posts: 15 Karma: 10 Join Date: Oct 2015 Device: none	could the font problem be connected with the number of css entries you have and if you are using a secondary css while getting rid of the garbage in code view in main part of book.

10-23-2015, 11:07 PM	#19
KevinH Sigil Developer Posts: 8,489 Karma: 5703586 Join Date: Nov 2009 Device: many	Hi, No its just a broken font. Simply google: consolas font metrics broken

10-24-2015, 10:30 AM	#20
dragon reader Member Posts: 15 Karma: 10 Join Date: Oct 2015 Device: none	You could set Liberation Font and replace Consolas, especially since Liberation is free source. The Calibre Editor is also using them. Liberation is not available as an alternate in css or code view. But is available in book view and preview.

10-24-2015, 10:44 AM	#21
KevinH Sigil Developer Posts: 8,489 Karma: 5703586 Join Date: Nov 2009 Device: many	Any monospaced font should work. That default font was changed early on, but for people using old Sigil ini files, some still get Consolas. I use Courier New.

10-24-2015, 11:54 AM	#22
KevinH Sigil Developer Posts: 8,489 Karma: 5703586 Join Date: Nov 2009 Device: many	Hi, I checked the commit history of Sigil and all traces of Consolas have been replaced by Courier New in settings and things early in the Sigil 0.8 series. The only reason you are still defaulting to Consolas is because your Sigil.ini settings file was created before the change took place. So either choose Courier New yourself in tha Appearance settings or after backing up your old Sigil.ini file, remove it, and on next launch a more sane set of defaults will be created. Newer users will never see this issue, as Consolas is never used anymore. KevinH

11-01-2015, 10:12 AM	#24
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	More bugfixes. And the 0.8.901 changelog: https://github.com/Sigil-Ebook/Sigil.../ChangeLog.txt

11-02-2015, 06:11 AM	#27
KevinH Sigil Developer Posts: 8,489 Karma: 5703586 Join Date: Nov 2009 Device: many	One change related to fixing the source for clang compiler issues was incorrect and under some circumstances can cause bugs. Reverting that change brings us effectively back to Sigil 0.8.6. So using Sigil 0.8.6 is recommended over Sigil 0.8.7. KevinH

11-02-2015, 07:51 AM	#28
DiapDealer Grand Sorcerer Posts: 28,368 Karma: 203720150 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Thanks Kevin. I couldn't remember exactly what the problem was with 0.8.7, but I knew there was something.

Advert

Advert

11-02-2015, 08:01 AM	#29
KevinH Sigil Developer Posts: 8,489 Karma: 5703586 Join Date: Nov 2009 Device: many	Here is me reverting the change after the Sigil -0.8.7 release. https://github.com/Sigil-Ebook/Sigil...18640a7987f111 It caused some signals to not be properly attached to some slots in MainWindow causing even some primary buttons to stop working seemingly randomly, and lots of hard to detect issues. So again, I strongly recommend using the latest Sigil (especially the forthcoming Sigil-0.9.0) but if that is not possible then use Sigil 0.8.6 over any earlier releases. Hope this helps, KevinH

11-02-2015, 10:15 AM	#30
KevinH Sigil Developer Posts: 8,489 Karma: 5703586 Join Date: Nov 2009 Device: many	Quick question. Once we decide to strip out PrettyPrint and make-it a plugin, would anyone be interested in a Tidy pretty-print plugin? I should be able to extract the Tidy code out of the Sigil-0.8.X series into its own github project and create a plugin from it if anyone truly misses Tidy. Kevin