Quote:
Originally Posted by st_albert
Thanks for sharing your workflow. It was an eye-opener to me!
As my post right above yours suggests, my experience has been almost the opposite of yours. I do 90+% of my work (which is book interior design) for a single publisher whose authors and editors almost exclusively use Word or an equivalent. Only after the final edits are complete do I get a .doc file for placement into InDesign and/or conversion to epub and other formats.
Your authors must be much more tech-savvy than the ones I work with. I can only imagine the chaos which would ensue if we asked our authors to use Sigil as a word processor!
So it seems there's a whole other world out there that I had been unaware of. Horses for courses, eh?
Albert
|
Yes, I was thinking the same thing. If we asked our clients ("our" authors, for lack of a better way to phrase it) to work in Sigil...well, that wouldn't be pretty. Our clients have difficulty in downloading files from the browser interface (we have browser-based SAS), much less downloading and installing Sigil.
We have myriad tools prior to using Sigil, but even with the fairly endless revision cycles we do, we're not working in BV. When we edit, we edit in HTML, whether that's a single HTML file (usually a section or chapter of a book), or in Sigil. I am a huge fan of Sigil, but I never use BV; I use Preview when I need it.
Offered solely FWIW. As Albert said, different horses.
Hitch