Ricardo Berlasso wrote: > El jue., 4 oct. 2018 a las 2:21, John Kane (<jrkrid...@gmail.com>) > escribió: > >> Lovely book. I am up to about page 53 and it has remind me of things I >> have forgotten and taught me a number of new things. >> >> I second Steve Litt's comment about the language. Very easy to read and >> does not--at least so far need any English editing. It would be nice if >> 90% of the native English speakers I know wrote as well. >> > > Thanks John! I was worried about the language, now I'm starting to feel > proud of myself! :) > > Regards, > Ricardo > > > >> On Wed, 3 Oct 2018 at 14:54, Steve Litt <sl...@troubleshooters.com> >> wrote: >> >>> On Wed, 3 Oct 2018 11:19:05 -0400 >>> Scott Kostyshak <skost...@lyx.org> wrote: >>> >>> > On Wed, Oct 03, 2018 at 03:59:44AM -0400, Steve Litt wrote: >>> > >>> > > but LyX' html and xhtml exporters >>> > > export pidgeon xhtml and html that requires all sorts of human >>> > > intervention and garbage removal. >>> > >>> > Have you reported bugs for this or are all of the bugs covered by >>> > existing reports? LyX HTML export is slowly improving, especially when >>> > bugs with minimal examples are reported. >>> >>> I reported them on this list, many, many times, and was shouted down as >>> people priortized just-right rendering of Apple Retina Displays over >>> any sane way of LyX authoring 21st century flowing text books (ePub, >>> for instance) without repeated human intervention. >>> >>> I was told that the xhtml and html export mechanisms were "just fine" >>> for ePub. They use different styles for the first paragraph after a >>> heading, for gosh sakes. They almost completely converted styles to >>> inline appearance codes so I couldn't customize my ePubs via CSS. The >>> HTML they put out wasn't WYSIWYM, it was 100% pure fingerpainting. The >>> files were therefore HUGE. >>> >>> Understanding that xhtml/html exports would never be adequate for ePub, >>> I begged for the transition of LyX's language to well-formed XML to be >>> completed so I could write my own LyX to ePub converter. No. Too much >>> work. >>> >>> After years of begging and pleading, I created Stylz to author both PDF >>> and ePub. I am writing two different books written in Stylz. >>> It's not easy for one developer to develop an authoring tool and write >>> books at the same time, but I'm doing it. Stylz already renders HTML >>> beautifully, does ePub pretty darn well, but its rendering in PDF is >>> defective and needs several repairs. >>> >>> I had given up on LyX, because it's important I be able to have one >>> document render both PDF and *high quality* ePub, without human >>> intervention. If lwarp can *correctly and semantically* export LyX to >>> HTML5 *as XML*, I might write the HTML5 to ePub converter and return to >>> the LyX fold. >>> >>> But if you're asking me to report the inadequacies of LyX' html and >>> xhtml exports for the purpose of ePub, I've done my time. And nobody >>> cared. And I've moved on. >>> >>> SteveT >>> >>> Steve Litt >>> September 2018 featured book: Quit Joblessness: Start Your Own Business >>> http://www.troubleshooters.com/startbiz >>> >> >> >> -- >> John Kane >> Kingston ON Canada >>
Enjoyed reading this, thanks! 1 minor comment: My procedure for inserting graphics is usually to choose scale to 100% columnwidth (or textwidth) for an article. Usually for beamer I'll scale to 85% of textheight, unless there's other text on the page, in which case I'll choose perhaps 75% textheight. I've never used scaling to fixed dimensions. Although your procedure to automatically center graphics is more automatic, I simply choose paragraph setting centered before inserting the graphic (and if scaled 100% textwidth doesn't matter if it's centered anyway).
