Language after compilation

[austriaka]

This topic has been discussed already, nevertheless I want to bring it up again.
I use Scrivener in German, everything is set to German. But after compilation to docx, the language formatting is set to English (USA).
A few weeks ago @Caithness postet a solution which is based on a Macro in Word - this is great, but I don’t use Word but a different Office Suite which does neat spelling correction as well (Softmaker office). So this does not work for me.
Another solution I found at the Mac Forum considered changing the export conversion in Scrivener > Preferences > Sharing > Conversion (Mac) or Options > Sharing > Conversion (Win). And here is the first glimpse to a solution: When changing export converter “ODT” from Aspose to Scrivener and then compile my manuscript to .odt, the language is compiled correctly. Unfortunately other things like page breaks and page layout are completely destroyed, so this doesn’t work at all.
Changing the export converter “DOC” to “RTF” does not change a thing.

So I would ask if you could make it possible to correct this export conversion when using doc or docx as well? Of course I don’t know if this is possible, but I would guess as long as it is possible with odt, it should work with doc or even better with docx too.
Or perhaps it could be possible to simply add the “language” style property to the compilation styles?

Thanks a lot!
Karin

(if this is part of the 3.1.5 beta, I would be glad to test it!)

[austriaka]

Unfortunately I never got a response to this post. New v3.1.5 still can’t compile correct language.
Any solutions?

[AntoniDol]

For now, there’s no solution but to select all text and change the language setting to your preferred language.

[austriaka]

Or to change it in the format panel of your preferred office tool.
What a shame

[CatharinaSteel]

I recommend updating each of the styles in your word document. If you don’t do this, you will need to keep resetting the language (if you edit/add new sentences).

[austriaka]

v3.1.6 still not working. Why ist this such a problem?

[AmberV]

Is this a different issue from what has already been discussed in this thread?

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 Engli…

[austriaka]

It is the same issue.
Changing Aspose to RTF-based and compiling as docx still did not work. I don’t use Microsoft Word, so I don’t have any other option in export settings.
But what did work (and that is new) is to export it as rtf-Format, no matter if I choose Aspose oder RTF-based. Formerly it “forgot” about some style settings like italic when exporting in rtf Format. Now this seems to do the trick. Thank you!

[AmberV]

Okay! Good to hear you found a solution from the alternatives.

When you select RTF as your “compile for” file type, that is in fact the closest thing to a pure export from Scrivener. That is the format it understands natively, and it requires no conversion to produce it, we have full control over it. So if you can, if the software you do use reads it well (like LibreOffice and Word), then there is rarely any reason to use .docx.

The “RTF-based” option you refer to is something else. Mainly for getting past people that demanded DOC files without realising RTF is just as good in Word.