From: Stephan Boltzmann <stephan2boltzmann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: citeproc: Missing indentation in DOCX output of list of references
Date: Tue, 11 Jul 2023 07:58:54 -0700 (PDT) [thread overview]
Message-ID: <778adde0-a246-417e-9dc7-57b31a810273n@googlegroups.com> (raw)
In-Reply-To: <2a000ffa-6d52-46a6-813e-f05ff3bcbe67n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2066 bytes --]
Thinking and searching hard for a solution, the closest I got was to use a
DOCX template file with an enumeration in the references.
A disadvantage of this solution is that it is no longer possible to use the
same CSL file for all output formats (because this would cause duplicate
numbers in DOCX output; in this case it is necessary to remove the numbers).
There was a discription the same problem on
https://community.rstudio.com/t/csl-style-is-not-recognized-when-output-in-word/143064.
I think it would be nice to have a fix for beginners.
Stephan Boltzmann schrieb am Freitag, 16. Juni 2023 um 13:00:07 UTC+2:
> Hello everybody out there using Pandoc-citeproc,
>
> Generating a numbered list of references from Markdown with
> Pandoc-citeproc for LaTeX output works great and there is a nice
> indentation after each (sequential) number for all references.
> This indentation is missing when generating DOCX (Word) documents for any
> citation style (CSL file) I have tried so far.
> Each reference is displayed in according to
> 1. First author, second author: A long title with
> a linebreak. Journal, Issue, Date, etc.
> whereas I would prefere
> 1. First author, second author: A long title with
> a linebreak. Journal, Issue, Date, etc.
> Is it possible to have this kind of indentation for list of references in
> DOCX documents?
> Surprisingly, I could not find any solution about this issue by web search.
>
> I made sure that the CSL files I use really included suitable indentation
> tags and also tried to adjust them but so for without success.
> Are there additional diagnostics I could run to pin down the problem?
>
--
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/778adde0-a246-417e-9dc7-57b31a810273n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2955 bytes --]
next prev parent reply other threads:[~2023-07-11 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 11:00 Stephan Boltzmann
[not found] ` <2a000ffa-6d52-46a6-813e-f05ff3bcbe67n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-11 14:58 ` Stephan Boltzmann [this message]
[not found] ` <778adde0-a246-417e-9dc7-57b31a810273n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-11 15:04 ` Stephan Boltzmann
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=778adde0-a246-417e-9dc7-57b31a810273n@googlegroups.com \
--to=stephan2boltzmann-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).