Imagine the engine of your car starts to fail. You call the garage, tell them what it sounds like in the hope that they can tell you what’s wrong and how to fix it yourself. They ask you to bring the car round to have a closer look. Instead you offer to put your phone near the engine to prove that it is indeed acting up.
Consider bringing the car round (a sample project), so someone can peek under the hood.
I bet that is your problem… you’ve given every paragraph in your project a style (as you would in Word), with the result that when you compile they are all formatted in the paragraph style, which doesn’t include italics, so strips them out.
All your main text paragraphs in Scrivener should be “No Style”, which becomes “body” or “Normal”—whatever the base style is called in Word (I don’t use Word or DOCX)—but doesn’t override the italics as you have discovered in that one paragraph.
In Scrivener, only paragraphs that differ from the main text style, like headings or block quotes should be given a style. All main text should be “No Style”.
I understand what the problem is, and in multiple threads it has been said it was fixed in a previous update, which is why I have continued to do it, because it’s far more convenient for me to hit a couple of shortcut keys to change specific paragraphs than to adjust my formatting manually.
So I guess the bottom line is that there is no way to prevent this manuscript from losing all of its italics. I appreciate your time.
@xiamenese : I bet that is your problem… you’ve given every paragraph in your project a style (as you would in Word), with the result that when you compile they are all formatted in the paragraph style, which doesn’t include italics, so strips them out.
That latter part was the original bug that was being reported, in that what you describe shouldn’t happen. The compiler should have special exemptions for direct formatting that is placed on top of styled text, so that it doesn’t get nuked when compiling. In older builds, it was getting nuked, but we fixed that and it should now be working as intended.
In practical usage the matter goes beyond body paragraph formatting. Say you want to italicise three words in a caption? (Yes, best practices would have one create a “Proper Noun” character style that uses italics to present itself, and apply that to the text rather than just messing around with font variants directly—but not everyone writes to best practices, clearly, or this thread wouldn’t exist, so we need to anticipate that in the design.)
While I do agree that the practice of applying a body style to all text, in a program like Scrivener, is needless and makes using the software more complicated than it should be—it’s still a supported way of working, and critical capabilities like making some text italic shouldn’t be mysteriously lost.
Here is a sample project that demonstrates several different combinations of settings:
Each of the three items in this test have two test paragraphs with italics in them. One is not styled and the other is. The styles used are the most impactful possible: font family and size are changed, and character formatting as well as paragraph formatting.
The third item’s C-03 paragraph uses a different style (same configuration). We use two different “Body” styles so that we can test whether when the compiler overwrites the style design that makes a difference.
The “Body” style in B-03 is passed through the compiler without modification, which can be evidenced by the fact that all of the formatting around that paragraph changes, while it sticks to what we see in the editor.
The “Body Temp” style in C-03 has a rule in the Styles compile format pane that reformats the font family and size to match the rest of the text around it. I also added a little indent to help illustrate that this text is being manipulated specially.
All italic ranges are also highlighted for ease of referencing in the output.
All six italic ranges are preserved in output, whether the Section Layout reformats the paragraph, or the style is exempting the paragraph from reformatting, or the style is being reformatted itself.
While that is useful for demonstrating what works, the problem is that these are only six of many different ways to set things up.
Absolutely. It took me a couple of months following the release of Scriv 3 for Mac to realise that I was best off not styling all paragraphs word processor style, and have read so often on the forum of people running into problems compiling from having done so, that I didn’t realise that the italics/bold problem in styled paragraphs had been resolved. I’m glad it has, but why @NJDamschroder is still encountering it, I hope you will be able to ascertain.
Yes, your sample project works fine, and it encouraged me to investigate setting up flexible ‘emphasis’ or ‘strong’ character styles… I hadn’t tried turning off Font Family and Font Size, assuming erroneously that they were necessary in a Character style.
So thanks for that, and for all the other help and support you give to us all.
Either you can send an email with an attachment, or can click on my avatar here on the forum and then the big Message button, which will send a private message. Just drag and drop the .zipped copy of the project into the composition area to upload. Or if it is too big, a share link from a cloud service is fine as well.
If you want to make a trimmed down version that’s ideal. You can use File ▸ Save As... to make a throw-away copy and purge everything but a section or two that demonstrates the problem (probably some with paragraphs that work too). But if you’re nervous about doing that we can work with whatever.
For anyone else having this issue, in case deleting the styles is not viable (say you have captions with italics, or headings), there are actually two potential fixes we found.
For both fixes, I recommend creating a backup of your current project, via the File ▸ Back Up ▸ Back Up To... menu command. Both of these steps are “destructive” in the sense that they have the potential to broadly change large amounts of your project. They are not destructive in the sense that you should lose any formatting, however it never hurts to play it safe with tools that work so broadly.
This involves simply setting the font family on the styles to something else, and then switching them back to what you prefer, which seems to be enough to reset the formatting and get rid of the glitch.
Select any paragraph using one of the styles that doesn’t have italics in it.
Change the font to something else. I used Times New Roman.
With the cursor in the modified paragraph, use the Format ▸ Style ▸ Redefine Style from Selection ▸ (style name).
If the Include font family checkbox is not enabled, tick it so that your adjustment will take effect.
This will go through the whole thing and update the entire manuscript with the new font. Double-check to make sure none of the italics were lost.
As this point, you can follow the same procedure to set the font back to one of your choosing, and if you had to tick Include font family, you might also want to do a third run to clear that setting. You do need to leave it on for the two main font swaps though, otherwise this fix won’t actually change the formatting in the way we need it to.
The second method also works, and that is to simply delete the Self-Pub and Self-Pub First styles from the project. Deleting a style does not disturb the original formatting at all—it just strips the style tags out of the document. This will be a viable approach if you don’t really need the styles (like “body” paragraph styles, which have little use in Scrivener).
I’ve managed to slove this problem for myself, and I hope this works for others. In the end it was incredibly simple.
Choose a paragraph in the style you wish to keep.
Italicise a couple of words.
Select the whole paragraph.
Open the Styles panel in the paragraph box.
Click on the … at the bottom and click on “Redefine paragraph style from selection”.
If you’re starting from scratch, include every potential variant in your intial paragraph style.