|
Why would you go through it one at a time, instead of using search and replace, starting at the point where the bold starts, in code view?
If it is complicated, you can use regex, examples of which are on a sticky. You might want to make sure HTML Tidy is always off, since it can create problems.
It may be a defect with your underlying HTML, especially if it comes out of some word processor which adds many things that are useful to it, but useless otherwise.
Next time, if there is a next time, if you reload and see something is not bolded, perhaps you should look at the underlying code and see what is there already FIRST. Sigil tries to create conforming code. If you try to insert something that can not be put within existing code, Sigil will try its best, but nothing is error proof given sufficiently bad underlying HTML.
I do NOT want autosave. When I am trying to resolve a problem, I often try something which sounds good at the time, but which creates code that is not conforming and just plain wrong. Whether it is a block of HTML or epub, which is very similar, saving a mess does not solve the problem.
What does solve it is a small mouse action to save at the end of each corrected chapter. In your case I would save as epub1, epub2, etc. If you took that extra step, it would be dead simple to look at your last successful version versus the current one and you would know what is going wrong.
If it is Sigil related, the developers have been good about correcting any correctable problem. If it is a spaghetti HTML problem, then you might be better off saving text out of whatever source you are getting your material and save yourself a lot of aggravation.
|