If you put any kind of punctuation after e.g. it will be flagged as misspelt; if you "correct" it using the right-mouse button in-context menu, Scrivener inserts "e.g." in addition to the existing full-stop after g, so you get e.g.. (plus your original punctuation), which Scrive...

May I add that Scrivener is using extended RTF format and RTF keywords. Editing the RTF files within your project with an external editor should be done ONLY in critical situations (you should only Open and Copy text, or Open and use Save As), or you might lose Inspector notes, styles, etc. in your...

Just a quick PS to my previous comment: Scrivener stores all your text as simple RTF files, which can be edited by almost any word processor. So, as long as you have backups, you're most unlikely to lose anything you've written. (Although actually sorting all those RTF files back into a book would b...

I'm just a user, but I've written over 100,000 words of my current book using the beta. Haven't had a serious problem of any kind. Most of the remaining issues seem to be related to compiling or cosmetic. But, obviously, L&L are officially saying "wait for the final version". So, you'r...

This has been reported before. I don't know if a fix is planned (I have no connection to L&L), but the problem is caused by the fact that the apostrophe may be a straight "typewriter" quote or a smart (curly) one; typically, if you type into a dialogue box you will type a straight quot...

I feel as if I'm being really stupid here: I have noticed people celebrating the arrival of quick reference windows, but I find them useless because I can't figure out how to open a new document in a QR window without losing my main one. e.g. I have my draft open in the main editor, and use the spli...

This isn't new, but I've been meaning to report it for a while. If i type a few words, then paste something, and realise that I've pasted the wrong thing, I hit "undo" (using the Ctrl-Z shortcut). I would expect that to "undo" the last command (the paste), but it always undoes th...

In the next build Inspector Footnote anchors will never be decorated as links, when exported to RTF/Word. Great improvement; thanks. Also, just in case @narrsd is struggling to find the RTF compatibility option; you have to use a custom compile format (you can't edit the supplied ones). So, save on...

May I also point out that the compiling default to US spelling also happens—and has always happened in my experience—with the Mac version. I'd always assumed it was something to do with the OS and beyond Keith's—or in your case LAP and Tiho_D's—control. You may indeed; thanks for the info (I've nev...

Well, it was not to insult anybody, so sorry if it happened to touch you. Anyway, so far as you had some time to give me an advice on my tone, could you frame any objections or comments on what I said? Well, I don't want to escalate this, but I just felt that "senseless advice" was a bit ...

What is much more disappointing for me, even unbelievable, is the fact that the developers have not seen [snip] Please may I suggest that everyone takes a minute to think about their tone before they post (here, or anywhere else online)? The whole world is feeling stressed and anxious right now, fo...

1) Check RTF Compatibilty "Ensure hyperlinks are colored and underlined" 2) Not sure what you mean by that. 3) Check the compile format "Footnotes & Comments" > Override font. Thanks for the helpful info. I was using the "default" compile output style, which you ca...

First time I've compiled anything for a long while (but I finished my fourth chapter!). A couple of problems: ⋅ Footnotes are rendered as hyperlinks (in blue and underlined), which looks awful. Not too hard to fix, but it would be nice to have an option to format them as ordinary text. &sd...

Every couple of days someone posts a question along the lines of "why do we have to keep updating the beta", "please can I just pay for it now", "why can't I just license the beta and not have to update it", etc., etc. Every time someone from L&L has to take a break...

I've seen the answer be "no" for quite a long time now... however, I have another solution: Make the in-program updater work even on expired betas, so that people who miss the expiration date can update more easily... and test the updater while they're at it. I have no connection with L&a...