187 karma · joined November 18, 2015
i don't see it that way. i especially don't see it as involving "willpower". i see it more as a specific skill.
now, as i said quite clearly, some people lack the skill. and some of those people will be totally unable to learn it. the most unfortunate ones should adopt your 2-stage workflow.
but most people can learn to drop the procrastination habit and pick up the skill of simultaneous writing and layout.
plus, on the other side, some people thrive on that method. not just do they not "have a problem" with it, to any degree, but they actually perform better when they work in that way.
> It's (sadly) not usually feasible in large orgs, given that there are separate teams with separate skillsets
i agree that such organizations won't change their workflow.
but i'm not really all that interested in empowering _them_.
> iBooks Author
> It's honestly a shame that the EPUB 3.0 standard
it's much better if i don't get started on either of those topics... :+)
and i like the simplicity and flexibility and freedom of plain-text as my format of choice. but if you or anybody else prefers something different, i urge you to take that path.
light-markup will never do everything ms-word does.
nor should it.
but typical light-markup systems these days handle all of the features needed for the vast majority of long-form documents which are now being produced -- books, annual reports, scientific articles, etc. -- and do it with an eye toward mounting on the web.
whereas ms-word is still stuck in a page mentality, and creates .html output which is rather horrendous.
but i agree that ms-word is still valuable to many.
and i no longer feel it necessary to bludgeon word for being the "de facto default" out in the world, where everybody uses it because everybody uses it, and nobody can use anything else because "conform".
so if someone needs one of the "does more" things where ms-word does more, i'm glad they have word. it's a tool in their chest, no reason to begrudge. i'm happy, even, that word has true fans like you.
i'm also glad the rest of us can move on now to something that we think is better. it's about time.
a plain-text light-markup file -- easily read, parsed, and rewritten when necessary by a plethora of apps (text-editors, spell-checkers, grammar-checkers, link-checkers, sanitizers, validators, on and on) -- is a big advantage (gargantuan!) over a complex xml-format document stored in a .zip container.
and editing and ease-of-use (and re-use and repurposability) is much friendlier as well.
ms-word can support those things as well, but only when you bring its proprietary format into its proprietary, closed-source app, which is not free of cost. the silo only looks better when you are locked inside it.
it's fine to prefer ms-word. prefer whatever you like. but think clearly and fairly if you start to bring up objective comparative advantage.
here's what prompted that:
> when I'm out for a walk or a long drive, I'll start thinking about fiction ideas. Before too long, my wandering mind drills down to what I think is an actual internal monologue of prose. In my head, it flows smoothly and sounds compelling. I always mean to start writing it down when I get home but never seem to find the time or discipline or whatever to do so.
the main reason they do it that way is because they have different people doing the writing and the layout tasks.
but the writers of today and tomorrow are much more likely to be self-publishers, who are pricing their work such that they don't have the margin to employ others to do layout.
now, it's true that some people are incapable of doing both tasks at once, and find themselves procrastinating by doing one task when they should be doing the other.
those people will have to learn how to fix that bad habit.
but it is equally true that other people are quite capable of doing both tasks at the same time, and they'll typically do the complete job in much faster time doing both at once.
and they often end up doing a much better job too, because they're working with a tight feedback loop between the tasks.
now, i do agree with you that a light-markup editor can enhance such a feedback loop. a 2-pane setup, a la the ghost interface, requires the entry of clean text and couples it with a display that lets a writer confirm they will get the output they want.
(indesign is outdated. if you need a .pdf today, repurpose your .html using prince, renting it on a monthly basis via docraptor. that way, a single input creates .html, .epub, .mobi, and .pdf.)
i think many observers say that reader preferences are trending to a more conversational style these days anyway.
and, if you have an iphone, you can use the dictate command on the keyboard to input into the notes app. you need to do a fair bit of editing, it's true, but many first drafts require that anyway.
so all in all, i think that dictating your first draft is a pretty smart idea, especially if these conversational flashes happen to you during a walk, and also if you are prone to forgetting them before you get them down.
for instance, i dictated the first draft of this comment on my walk just now, and then emailed it to myself to post it here. i cleaned it up, of course, but if you want to see the original, as is, i posted it here:
it was also a bit slow to load, on my machine anyway, maybe due to my typical dozens of tabs in dozens of windows... but i'd explore whether the .svg approach was the offender.
of course, lethargy won't have any impact in the course of actually presenting the thing to an audience, but there is much value to be gained by the after-the-fact mounting of a presentation on the web for later consumption by others, who will thumb through the slideshow at a much faster pace.
this is also why a presentation full of bullet-point slides, void of the accompanying speech, is not very compelling.
so even if your show does end up being a little bit slower, i think that's offset completely by your step-up in design.
you really can't call a .json structure like that "markdown", because the formatting isn't nearly intuitive enough -- for instance, i threw a single-quote in to do a contraction, and that was enough to make it fail -- so that needs work, but overall i'd call it a very good effort, worth pursuing.
except markdown also makes me feel a bit icky -- too many inconsistencies in the various flavors.
markdown's redeeming value is that it's "popular".
which is also why it's so frightening now, since it desperately needs to be replaced. (it cannot be improved, because xkcd 927.)
speaking of "popular", that's how you describe the showdown converter that your plug-in uses.
one reason it's popular is because it was fast -- the fastest converter, at one time, it claimed.
note the past-tense "was"...
because that time has now passed.
other converters, also coded in javascript (the other big reason showdown got popular) are now much faster and far more powerful.
without getting into all the surrounding drama, i'd recommend that you use markdown-it instead: it's blazingly fast, and has much functionality.
> https://github.com/markdown-it/markdown-it
(functionality is now a better differentiator of the worth of a markdown converter than speed.)
mavo's choice of converter is more consequential than it might appear at the first glance because follow-on effects of differential functionalities will surely impact the success of a mavo project, as will the inconsistencies that will bite users.
all this aside, mavo is a fascinating little tool. :+)
i'm creating a mavo project right now and i wanna use a simple textarea as a mavo field. (tinymce makes me feel a little icky inside.) but i didn't see anything in the documentation about how i would do that. can i? if so, how?
edit: oh hey. i just acted like it would work, tried it out, and bingo! hey, that makes me happy...
everyone thinks merely putting stuff on github is sufficient.
i think that's silly. but it seems to be what people think.
but my opinion is quite different.
i've been active in the e-book sphere for a long time, and i've studied e-book authoring quite extensively, even programming some systems myself, and i think leanpub is quite good. i liked it better when you didn't have to make a lump-sum payment in advance, but even now, i think it's one of the best systems around, especially for people who don't want to code their own solution. and leanpub gives you access to a customer-base that's more than large enough to warrant the small percentage they skim off your sales.
as for html-to-markdown conversion, http://markdownrules.com is good.
i think it started out being free for everybody, but now a free account is available only for public slide-decks. (when it was free for everyone, i think all decks were public, so it's not as if they ripped back functionality.)
but you're just talking about _reading_...
when it comes to typing, and especially _editing,_ all that markup cruft becomes a distraction (at best), and usually much more like an irritating obstacle. and you glossed over the ’ which needs to sit in the middle of every contraction. like this:
“if you don’t have it, you’ll still have something...”
ick. no thank you.and that's just from an "easy on the eyes" standpoint.
when i also think about actually typing all those unnecessary angle-brackets, i break out in hives. it's not "difficult". but it's terribly tedious.
but you should stick with what you like... :+)
programs are self-contained entities, whereas prose often drags in multitudes of real-world context involving assumptions, motives, and other considerations.
a diff might inform you of an edit in chapter 2 where you changed a man's status from "divorced" to "widowed" (to make him appear more sympathetic), but it won't also remind you that you need to rewrite that section in chapter 25 where the man gets a phone-call from his former wife.
this type of thing happens a lot, in ways that are much more subtle than that silly example. and it's usually because the arc of the story is greater than (and different from) a simple sum of its pieces.
in the same way that one-sentence-per-line
gives you much more fine-grained diffs than
one-paragraph-per-line, notching it down to
one-phrase-per-line gives the best results.
a simple javascript routine can do that split,
and then rejoin the lines after you do a diff.
i've written this up extensively, to no notice.
http://zenmagiclove.com/simple/breaker.html
https://github.com/bbirdiman/breakerbreaker
***
i've since found that a dozen changes suffice:
replace ". " -- with -- ". \n"
replace ", " -- with -- ", \n"
replace "? " -- with -- "? \n"
replace "! " -- with -- "! \n"
replace ": " -- with -- ": \n"
replace "; " -- with -- "; \n"
replace ") " -- with -- ") \n"
replace "] " -- with -- "] \n"
replace "} " -- with -- "} \n"
replace "-- " -- with -- "-- \n"
replace "' " -- with -- "' \n"
replace '" ' -- with -- '" \n'
***
and, of course, to revert those changes,
you simply change " \n" to " " and boom.by the way, i don't know how they compare with each other, but the speed of commonmark.js is blazing fast these days.
that's why they're installing fascist governments worldwide.
so i think a violent revolution would be a very bad idea.
i think a non-violent evolution (no-r) is smarter and better.