Consider following example:

`MetadataSettings.yaml`:

```

```

with `test.txt` containing text "test" or whatever and with default latex template and command:

```

pandoc --metadata-file=MetadataSettings.yaml -f markdown -s -t latex -o test.tex test.txt

```

produces `test.tex` file, in which key-value options written in metadata file are simply flattened to "true", which wont compile to pdf.

If possible, I would very much prefer setting `geometry` package options (and other packages similarly) via metadata-settings file, which makes them nicely organized. So, how can that be done properly?