1.0.0

mrmikel · 01-18-2020, 09:54 AM

If epub lacks toc.ncx, says it must close. Previouis version creates one for you. This is opening epub created with this new version.

Went back to 0.09.18 and said it lacked one and created it for me.

In working with a long html file seemed to work slower than before.

This is under Windows 10 64 bit.

mrmikel · 01-18-2020, 10:21 AM

Further: ABBYY reader created an html file with 60,000 lines to accomodate statistical tables. When saved as an epub it used a mere 8,000 lines which Sigil found more digestible.

KevinH · 01-18-2020, 10:28 AM

The bug where you directly import an html file as its own epub in Sigil, and therefore the required ncx did not exist (under epub2), has been fixed in master and will be in the next Sigil release.

If you have trouble because an html file uses huge run-on lines with no line breaks (that slows any line based editor with syntax highlighting to a crawl) simply run Sigil's mend on it and proper linefeeds will be inserted to make the line editing capability of Sigil work better and make the file much more editable and readable.

Large numbers of short lines should not be a problem for Sigil given you have enough memory and reasonable performance on the machine you use to live edit it.

DiapDealer · 01-18-2020, 10:28 AM

Even further: I have no idea what your second post is trying to say. Can you explain a little more clearly/completely?

DiapDealer · 01-18-2020, 10:35 AM

Quote:

Originally Posted by KevinH

The bug where you directly import an html file as its own epub in Sigil, and therefore the required ncx did not exist (under epub2), has been fixed in master and will be in the next Sigil release.

I checked, and an epub2 with no ncx does indeed pop that error. But it appears to be (somewhat) cosmetic only. When dismissed, Sigil doesn't close and the default ncx is created. This is with the latest build of the Sigil master branch.

DiapDealer · 01-18-2020, 10:38 AM

Quote:

Originally Posted by mrmikel

This is opening epub created with this new version.

How did you create an epub2 with no ncx with Sigil 1.0.0?

mrmikel · 01-19-2020, 06:42 AM

I imported an html file from ABBYY reader.

The point of the second post was the first file was extremely long.

The file was not likely to be fixed with the mend command because it contained a series of tables. A different format produced a more manageable file.

exaltedwombat · 01-19-2020, 06:52 AM

Yes, recent versions of ABBYY reader have become very useful tools! We're approaching the one-click PDF > EPUB conversion. (So that's me out of a job

)

KevinH · 01-19-2020, 08:21 AM

Again table rows that are properly separated with linefeed characters do not cause any additional performance penalty for line based editors other than the implications driven by file size alone.

KevinH · 01-19-2020, 08:47 AM

In fact, if you hide Preview (so the browser-like window is not reloading the page with every edit), you should be able to run mend and then insert split markers and convert the single html file into proper chapters. Once mended and split you should be able to re-enable Preview and get reasonable performance.

01-18-2020, 09:54 AM	#1
mrmikel Color me gone Posts: 2,089 Karma: 1445295 Join Date: Apr 2008 Location: Central Oregon Coast Device: PRS-300	1.0.0 If epub lacks toc.ncx, says it must close. Previouis version creates one for you. This is opening epub created with this new version. Went back to 0.09.18 and said it lacked one and created it for me. In working with a long html file seemed to work slower than before. This is under Windows 10 64 bit.

01-18-2020, 10:21 AM	#2
mrmikel Color me gone Posts: 2,089 Karma: 1445295 Join Date: Apr 2008 Location: Central Oregon Coast Device: PRS-300	Further: ABBYY reader created an html file with 60,000 lines to accomodate statistical tables. When saved as an epub it used a mere 8,000 lines which Sigil found more digestible.

01-18-2020, 10:28 AM	#3
KevinH Sigil Developer Posts: 9,071 Karma: 6361556 Join Date: Nov 2009 Device: many	The bug where you directly import an html file as its own epub in Sigil, and therefore the required ncx did not exist (under epub2), has been fixed in master and will be in the next Sigil release. If you have trouble because an html file uses huge run-on lines with no line breaks (that slows any line based editor with syntax highlighting to a crawl) simply run Sigil's mend on it and proper linefeeds will be inserted to make the line editing capability of Sigil work better and make the file much more editable and readable. Large numbers of short lines should not be a problem for Sigil given you have enough memory and reasonable performance on the machine you use to live edit it.

01-18-2020, 10:28 AM	#4
DiapDealer Grand Sorcerer Posts: 28,880 Karma: 207000000 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Even further: I have no idea what your second post is trying to say. Can you explain a little more clearly/completely?

01-19-2020, 06:42 AM	#7
mrmikel Color me gone Posts: 2,089 Karma: 1445295 Join Date: Apr 2008 Location: Central Oregon Coast Device: PRS-300	I imported an html file from ABBYY reader. The point of the second post was the first file was extremely long. The file was not likely to be fixed with the mend command because it contained a series of tables. A different format produced a more manageable file.

01-19-2020, 06:52 AM	#8
exaltedwombat Guru Posts: 878 Karma: 2457540 Join Date: Nov 2011 Device: none	Yes, recent versions of ABBYY reader have become very useful tools! We're approaching the one-click PDF > EPUB conversion. (So that's me out of a job )

01-19-2020, 08:21 AM	#9
KevinH Sigil Developer Posts: 9,071 Karma: 6361556 Join Date: Nov 2009 Device: many	Again table rows that are properly separated with linefeed characters do not cause any additional performance penalty for line based editors other than the implications driven by file size alone.

01-19-2020, 08:47 AM	#10
KevinH Sigil Developer Posts: 9,071 Karma: 6361556 Join Date: Nov 2009 Device: many	In fact, if you hide Preview (so the browser-like window is not reloading the page with every edit), you should be able to run mend and then insert split markers and convert the single html file into proper chapters. Once mended and split you should be able to re-enable Preview and get reasonable performance.

Advert

Advert