docx writer does not respect yaml toc variable

[tolot27]

The following markdown snippet does not produce a docx with a TOC but a PDF with a TOC:

---
toc: true
toc-title: Inhaltsverzeichnis
...

# Test

Some text.

Only after addint --toc to the command line of pandoc, a TOC is generated in docx but now also with the title defined in the yaml variable toc-title.

[mb21]

Yes, that's due to the fact that the docx writer doesn't use a template. Thus you cannot use metadata to change the writer's behavior.

[tolot27]

I don't understand this explanation. Currently, the docx writer supports the yaml variable toc-title but not toc. What's the difference here? And what is ment by "use a template"?
And does it mean this issue is unfixable?

[mb21]

Currently, the docx writer supports the yaml variable toc-title

Ah yes, the docx writer looks up that variable here. So I guess we could do the same thing for toc... or consider something like #4627...

And what is ment by "use a template"?

see http://pandoc.org/MANUAL.html#templates

[tolot27]

I'd love to see consistency here with other writers like latex. It would be nice if a writer would read command line switches already made available as yaml variable.
In this case here, toc and toc-depth in addition to toc-title.

WRT to templates: Okay, that kind of templates were already known to me. As far as I know, the docx writer uses a default reference.docx. But you are right at that point that this reference.docx does not check variables like the latex template does, because it is simply not possible.

I already considered panzer. Nevertheless, it is a bit confusing, if one writer supports a yaml variable and its corresponding command line switch, but another only the command line switch.

[mb21]

Note: the following produces a toc for latex, but not html and docx:

---
toc:
  - true
---

# Test

but maybe that's okay...

[tolot27]

But does the following work now:

---
toc: true
---

That would be sufficient.

[mb21]

@tolot27 yes it does (current nightly build)