View Single Post
Old 06-05-2020, 12:52 PM   #13
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,856
Karma: 169712582
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by najgori View Post
Let Sigil inform user about crappy code and let him decide if he or she want to wait for program to show it, or to fix it.
That might work if the file opened fast enough that the user doesn't have the opportunity to think the program has crashed. Not to mention once the file is open, the incredible slowness of trying to do anything.

Basically, I did what Turtle91 did and used Notepad++ to add the line breaks (though I did use </p>\r\n), restructured to Sigil Norm and used the RemoveInLineStyles plugin to move the styles to a stylesheet. Some time spent with cleaning up that stylesheet muttering about people who use absolute value and their probable destination, dubious ancestry, repugnant morals, etc.

Last edited by DNSB; 06-05-2020 at 01:03 PM.
DNSB is offline   Reply With Quote