From: iandol <iandol-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to set margin for Typst?
Date: Fri, 8 Dec 2023 18:01:33 -0800 (PST) [thread overview]
Message-ID: <76d39afe-f9c9-4f2e-8a08-d79627538e5bn@googlegroups.com> (raw)
In-Reply-To: <e815ceb0-4056-43bb-afef-51faff7ddf67n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]
In YAML metadata: margin: {x: 1.75cm, y: 2cm} works with the Typst
template, however I assume given the docmentation for the -M option:
> Values will be parsed as YAML boolean or string values
Suggests that YAML lists cannot be passed via the command line. In which
case the solution is to use a metadata or a defaults file to pass these
options?
Cheers, Ian
On Thursday 7 December 2023 at 23:33:03 UTC+8 Cerdo wrote:
> Hi,
>
> I am trying to set the margins when converting a Markdown file to a PDF
> with Typst.
> According to the documentation
> <https://pandoc.org/MANUAL.html#variables-for-typst>, this should be
> possible by setting the variable *margin *as
> *dictionary with the fields defined in the Typst documentation: x, y, top,
> bottom, left, right.*
>
> How do I define the dictionary?
> As far, I have tried:
>
> - -V margin=top:1mm
> -
> - -V margin="top:1mm"
> - -V margin="(top:1mm)"
> - -V margin="{\"top\":"1mm"}"
> - and many other combinations
>
> What is the correct way to provide this "dictionary"?
>
> Best,
> Cerdo
>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/76d39afe-f9c9-4f2e-8a08-d79627538e5bn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 8094 bytes --]
next prev parent reply other threads:[~2023-12-09 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 15:33 Cerdo
[not found] ` <e815ceb0-4056-43bb-afef-51faff7ddf67n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-12-09 2:01 ` iandol [this message]
[not found] ` <76d39afe-f9c9-4f2e-8a08-d79627538e5bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-12-12 11:47 ` Cerdo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76d39afe-f9c9-4f2e-8a08-d79627538e5bn@googlegroups.com \
--to=iandol-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).