Quote:
Originally Posted by eggheadbooks1
I don't recall early versions of Sigil doing this, but in any case, I can say from a writer's perspective that it's not a great feature. I have a lengthy book that I am redoing solely as an ebook; it is far quicker to edit the existing ebook in Sigil than to start from scratch in InDesign or Word. Trying to rewrite passages while in code view is taxing. So this feature is one of those things that likely seemed like a good idea from a coder's or book builder's perspective but which did not consider the implications for content creators.
Also, remember that writers often find typos later on after the ebook is built and published, or may wish to make minor revisions. It is far more feasible to work from the ebook itself than the original manuscript and rebuild the ebook from scratch. So if the user is not aware of this feature, and fixes stuff in book view, they are inadvertently creating a problem in their text.
|
It has never really been a goal of Sigil developers to provide an interface for authors to
write their books. And it's not that the implications for content creators was never
considered with regard to Book View and spaces vs nbsps--far from it. It's that it's extremely impractical to provide the functionality you desire. Allowing users to enter "normal" spaces in Sigil's Book View is a recipe for disaster. Always has been. The damage that
will be wreaked on a document by allowing normal spaces to be entered in Book View far outweighs any minimal damage that using nbsps in place of normal spaces in Book View
might cause.