Word proofing language is always US English on compiled docs

Every time I compile my story into docx, the resulting Word document’s proofing language is always US English. My Win 10 PC is set up to use UK English as the only language, having deleted US English in Windows, and Word is also set up to use English (UK) also as the only language. However, when my compiled documents open, my English words are underlined as spelling errors because the Proofing Language (Review, Language, Set Proofing Language) is English (United States). When I the select English (UK) and Set As Default, the language changes but does not persist to the next Word session. On documents not created by the Scrivener compiler, the proofing language is UK English.

Obviously, I now know how to circumvent the problem, but it would be good if I didn’t have to, so I’ve filed this as a bug.

Thanks!

4 Likes

One thing you could try is going through the various Export converters for DOCX files under File > Options > Sharing > Conversion and see if any of them fix the issue.

1 Like

Hello amickie

I had no idea that there was any choice in the selection of export or import convertors! DOCX and DOC were set to the default converter, Aspose. The only alternative to DOCX was Microsoft Office, so I’ve changed to that and the compiled stories now appear in a Word document which is set to use UK English.

Is Aspose’s language configurable?

Many thanks for your good advice!

Yay! Glad that worked. Basically, Scrivener generates DOCX files by creating an RTF file and then piping it through a third-party converter, so I’m thinking this is something that would need to be fixed by Aspose. We’ll certainly keep it under the bug tag for now though so one of the developers can look into it.

Wonderful. Why did I only just find this? Opting for Microsoft Word as the Docx export converter has done the trick.

Hi there,

I have Scrivener Windows, latest version, Office 365, latest version, and Windows, latest version.

I have Scrivener set up as English UK. At least, I think I do. I’ve been using Scrivener a while but I wouldn’t call myself an expert.

All is good, until I compile the manuscript into a Word document.

The document is fine, but Word opens it and thinks it is an English US document. This affects the dictionaries Word uses, plus, I’ve found, the voices it uses to read, etc. Maybe other stuff, too.

I was wondering, does anybody know the process taking place, here? Does Scrivener hardwire “US” as the document language? Does Scrivener set a default to US, which I can override somewhere? Has Word scanned the inbound document on the fly, and wrongly decided “US”, all on its own? Nothing to do with Scrivener? Something else?

Just wondering. Thanks.

1 Like

I’ve merged your query with a recent thread on the same topic. Please review the above for how to get this working better.

2 Likes

I always have better luck with Scrivener->RTF and then open that document into Word. From there, save-as into DOCX if needed. Avoids going through any third party converters.

1 Like

Yes, using RTF is the best output Scrivener can make, however in this particular case, setting the conversion engine to a locally installed copy of Microsoft Office is about as first-party as you can get (unless you’re being super technical about it and considering Scrivener the first-party), and should in theory be the same as opening in Word and saving as DOCX.

But, if you don’t have it installed, that is the way to go.

3 Likes

Thanks Amber. I wasn’t aware that Scrivener used plugins for this but it seems like a good idea.
Using the Office converter seemed to do the trick as far as I can see. It’ll take me a few days to verify that the entire document is good. But certainly lang = eng uk.

2 Likes

This solution has seemed to work for me too.
@jacquot, I don’t suppose you noticed any funnies with the resulting document, using this new converter, did you? Thanks.

As far as I can remember, the resulting documents were fine.

1 Like

The result should be fine. Scrivener’s native format is RTF, so compiling to RTF in Scrivener is quick and straightforward and trouble-free as no converters are involved.

RTF was created by Microsoft and DOCX is their format, so if anyone knows how to convert between the two, it must be Microsoft.

If I used Word (which I don’t), I would still compile to RTF and open that in Word rather than using any of the DOCX compile routines provided by Scrivener.

:slight_smile:
Mark

3 Likes

Cheers, Mark. Yes I’ve been working with the new converter for a few days and it looks fine.

I’m using Word to generate proofs (a) for me, editing, and (b) for Alpha readers.

Also, it has one big advantage over Scrivener. I can have it read things back to me. My eyesight is crap so an aural check is invaluable - it’ll spot “is” versus “in” more reliably than any pair of eyes.

Pete

1 Like

Oh, WOW, it works for compiling as well. Nice!

I noticed that the spelling check inside Scrivener is “English”, but not which version of English.
My computer is set to English UK and that is what I want to use in Scrivener as well. However, Scrivener gives me the English USA spelling check. I don’t want that.

How can I fix that?

Just to make clear: I’m not talking about what gets exported. I’m talking about the documents INSIDE Scrivener :slight_smile:

Thanks for the help!

Hello Sherizira - In Scriv, select File → Options → Corrections → Spelling, and you’ll find yourself in the place where you can specify which dictionary to use. Download Eglish (United Kingdom) if necessary, then select it, the click on Apply.

2 Likes

Ah, thanks so much! I had been looking in the wrong place :smiley: