I tried the search function but didn’t find anything, so sorry if this was already answered.
I have an issue with Scrivener for Windows (latest version, but this was also happening before, I believe). I write in french, and everytime I use quotation marks, the paragraph spacing changes for the paragraph which has the quote. Sometimes, it’s the wole paragraph, sometimes, it’s a few lines, but it always happens, and is persistent through compilation.
Yes it is. I tried switching around those settings too, but to no avail. I selected all the text and put it in the same style, but it still happens. It also happens to a friend of mine, who’s also writing in French.
Yes it does. As soon as there’s a quotation mark, the whole paragraph changes its line spacing, although in the settings, it still shows the same spacing.
Weirdly enough, some paragraphs aren’t entirely affected : only a part of them changes, while the rest stays the same. Here’s an example of that :
I tried different situations and it seems pretty inconsistent. I can’t get a solid grasp of what’s happening and why. It’s just weird, and my friend has exactly the same. :')
No it doesn’t, so you gave me an idea which I tried : I changed the “narrow non-breaking space” into a regular non-breaking space, and now the line spacing stays the same. So it seems it has something to do with the narrow non-breaking space. Maybe that particular character is higher than the others?
EDIT : it’s definitely the space itself. When I type in the quotation mark and remove it, the interspace won’t come back to the regular one unless I also remove the additional non-breaking space that was added.
I do wonder what the difference is between narrow and regular, and why the narrow one is the default.
Le narrow est plus étroit, c’est la seule différence à ce que je sache.
C’est le standard en Français. La fonction est seulement disponible si celle pour utiliser les guillemets Français est activée. Ce qui tombe sous le sens.
Mais moi je n’utilise jamais ça. Je ne mets pas d’espace, ça me fais moi d’édits à faire au besoin. Ou encore que ça élimine le risque inutile d’en avoir qui traînent, oubliés derrière, puisque dans Scrivener on ne les voit pas spécialement (ils peuvent saboter la mise en page finale ou un ebook, alors je veux être sûr de ne pas en faire l’erreur).
Je laisse Antidote s’en charger à la correction finale.
Merci pour l’essai, je continue en anglais pour le reste de l’audience !
That’s weird indeed. I have no idea what’s causing this. But at least I know a workaround, if not a fix. Any idea how I can retroactively replace all narrow non-breaking spaces into regular ones? :')
Project replace.
Copy the narrow non-break space and the (normal)non-break space from your editor to the search and replace fields.
They will be invisible, but it should work. [EDIT] Sadly, it doesn’t.
Yeah I tried that, but it didn’t work. I just copied every chapter onto Libreoffice, used Grammalecte’s text formatter option on it and then copied it back. It took a bit more time but it was still fairly fast.
Thanks a lot for taking the time to help !
I wonder if other people have the same issue now, besides my friend and I…
Something else you might try is using a different kind of line spacing, instead of the basic one that multiplies the height based on the tallest character in the line:
Put your cursor in one of the paragraphs with unusual height, and use the Format ▸ Paragraph ▸ Line and Paragraph Spacing... tool.
Change the Line spacing dropdown to “Exactly”.
Type in the an amount in points based on how much line height you would normally get on a line without quotes. As a rough guide, if you use a 12pt font and 1.2 line-height, to emulate that you would want 14.4pts of line height. Not every font may work the same though—some have more leading than others built into the font itself, so you may want to experiment a bit.
The downside of using Exactly type line-heights is that it will always be exactly that tall, of course. This can cause weird results if you try to make the font a lot bigger, the text may overlap with the line before it, and if you put inline images into the line they may also overlap. But that kind of result is often the best answer for some things, like superscript numbers.
The downside of doing that is that you likely lost all of your styles assignation…
Likely most if not all of your formatting too.
If for some reason @AmberV’s proposed solution doesn’t do it for you, perhaps then have a look at this thread/post:
(Just replace “Antidote” with “Grammalecte”.)