From: jcr <ffi.appdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to get \section[Short title]{Long title} in LaTeX output
Date: Wed, 30 Jun 2021 02:54:30 -0700 (PDT) [thread overview]
Message-ID: <bc3ac76b-306d-4ab4-9a33-6acdd2d2a38fn@googlegroups.com> (raw)
In-Reply-To: <yh480ktulgs0oj.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2890 bytes --]
I did this with LaTeX and memoir: in my case, I only wanted a shorter title
in the page headings. I kept the full title in the table of contents. These
are the relevant functions from my filter:
-- Print a formatted warning to stderr
function warnf (...)
io.stderr:write(string.format(...))
end
function Header (el)
-- Replace heading with raw LaTeX if pageheading is used to specify a
-- shorter form of the title to use in page headers.
if el.attributes.pageheading then
local commands = {'chapter', 'section', 'subsection'}
if el.level > #commands then
warnf('pageheading attribute not supported for level %d headings',
el.level)
return el
end
-- Produce LaTeX like pandoc does, but with two additional arguments
-- to specify a short for of the page heading to memoir.
local title = pandoc.utils.stringify(el)
local latexStr = string.format('\\%s[%s][%s]{%s}', commands[el.level],
title, el.attributes.pageheading, title)
local label = string.format('\\label{%s}', el.identifier)
-- wrap in hypertarget
latexStr = string.format('\\hypertarget{%s}{%%\n%s%s}', el.identifier,
latexStr, label)
return pandoc.RawBlock('latex', latexStr)
end
end
On Wednesday, June 30, 2021 at 1:37:00 AM UTC+2 John MacFarlane wrote:
>
> Not easy. You could write a filter that builds the
> relevant section command, but that might break other
> things because the LaTeX writer won't see a heading
> there (not sure).
>
> It might be a good idea to have pandoc do this automatically.
>
> "'Nick Bart' via pandoc-discuss"
> <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> writes:
>
> > Is there any way to have pandoc output LaTeX code like
> >
> > \section[Short Section Title]{Long Section Title}
> >
> > from pandoc markdown containing both versions as in the following (but
> not necessarily given in this exact syntax)?
> >
> > # Long Section Title {short_title="Short Section Title"}
> >
> > --
> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/4p2Sx0e_CqUgNm9ZcXR064fya9gybYYDVBTVMMIL9p1m2ynHgBzs30shkkVJnu0l2RqSKghQo5oi10jSV33BS6IBsvIhBhtyoExu-d3p3Kc%3D%40protonmail.com
> .
>
--
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/bc3ac76b-306d-4ab4-9a33-6acdd2d2a38fn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4472 bytes --]
next prev parent reply other threads:[~2021-06-30 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 15:33 'Nick Bart' via pandoc-discuss
2021-06-29 23:36 ` John MacFarlane
[not found] ` <yh480ktulgs0oj.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-06-30 6:53 ` 'Nick Bart' via pandoc-discuss
2021-06-30 9:54 ` jcr [this message]
[not found] ` <bc3ac76b-306d-4ab4-9a33-6acdd2d2a38fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-30 12:29 ` 'Nick Bart' via pandoc-discuss
2021-06-30 15:04 ` jcr
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=bc3ac76b-306d-4ab4-9a33-6acdd2d2a38fn@googlegroups.com \
--to=ffi.appdev-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).