From: Denis Maier <denis.maier.lists-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How to export .md to MS Word (Windows 10) with sidenotes?
Date: Tue, 15 Sep 2020 22:41:45 +0200 [thread overview]
Message-ID: <627b6a91-ef5e-7992-b6a2-417ba5398b32@mailbox.org> (raw)
In-Reply-To: <CALu=v3KLbq3T95Gim03Z3Vu+EYQsxUxEL4kr-mDd8Xv+yxM2+g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Am 13.09.2020 um 21:44 schrieb Leonard Rosenthol:
> Looks like you can -
> https://wordribbon.tips.net/T010668_Adding_Sidebars.html
>
> You can also do text boxes, pull quotes, etc. However, I didn't dig
> into which coudl be done with custom styles and which would require a
> (Lua) filter. But the features are there in DocX if we figure out the
> best way to expose them...
Well, maybe... but, the link above is about Sidebars, which I understand
as adding arbitray content in the margins. That's not the same thing as
sidenotes, maybe a visual approximation, but I think there won't be any
link between those boxes and the text. There even won't be a note number
in the text unless we add one. And the worst part might be placing those
boxes in the margins. There are some LaTeX packages that go at great
lengths to keep the sidenotes close to the calling location, but also
move them around if need arise, e.g. when the note is called near the
end of a page, or if there are to many notes. (Does pandoc even have
access to these details?)
Anyway, all that doesn't fundamentally speak against implementing this.
Just one remark regarding this particular case: The OP wrote he is going
to send his manuscript to his publisher. So I guess the publisher will
do the layout anyway, and I doubt that the typesetter will appreciate a
docx with notes in the margins. (At least I wouldn't.)
Best,
Denis
--
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/627b6a91-ef5e-7992-b6a2-417ba5398b32%40mailbox.org.
next prev parent reply other threads:[~2020-09-15 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 23:05 Alan
[not found] ` <8038ea6e-4d7a-4e0c-aa83-0c028e1cae56n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-13 16:03 ` Leonard Rosenthol
[not found] ` <CALu=v3KtuDwBXg2z+dBJzcKCB8WcTD9pv1JY0J=aGPNFKMxhKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-13 16:20 ` Denis Maier
[not found] ` <01631ad8-bbd1-d17d-e9f7-a2027f829a7c-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-13 19:44 ` Leonard Rosenthol
[not found] ` <CALu=v3KLbq3T95Gim03Z3Vu+EYQsxUxEL4kr-mDd8Xv+yxM2+g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-15 20:41 ` Denis Maier [this message]
[not found] ` <627b6a91-ef5e-7992-b6a2-417ba5398b32-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2021-01-14 10:03 ` Zev Spitz
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=627b6a91-ef5e-7992-b6a2-417ba5398b32@mailbox.org \
--to=denis.maier.lists-cl+vpiynx/1afugrpc6u6w@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).