Compile to Docx Mishandles Font

[xiamenese]

Ahem, in your other thread,

Font Naming Misfire in Compiled Output

I have run into a problem whereby Scrivener seems to deliver out the wrong font name on compile resulting in the font setting not being recognized further down the road (InDesign). DETAILS: I have a compile layout aimed at producing docx files set in Adobe Garamond Pro. But when the result is opened in Word, Words toolbar widget shows the font name as: AGaramondPro-Regular Now, when I place this docx file into my InDesign project, InDesign says it can’t find that font and substitutes the d…

on 23rd April, Xiamenese wrote:

EDIT: I’ve just tried compiling a bit of one of my projects to DOCX, using KB’s new internal converter, and as far as I can see at a quick look, AGP is correctly there with its italics, semibold, etc., Margin comments have come across properly, but this text has no footnotes … I should try putting in a couple of footnotes.

Perhaps I wasn’t explicit about turning off the Enhanced Converters completely!

Mark