From: "'Marek Stepanek' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Index of picture sources in Markdown
Date: Tue, 23 May 2023 18:27:34 +0200 [thread overview]
Message-ID: <51160ACF-4EF8-40A6-97F4-2D287907228B@googlemail.com> (raw)
In-Reply-To: <c19d9830-7623-44b3-94ad-24889e2498cen-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To finish this thread:
I have a dream!
Perhaps there is hope, that this dream comes true!
I make an appeal to all of this savvy mailing-list:
Please make Biblatex or biber savvy too! I am wondering, why there is no possibility to enter the sources of images!!! Or am I missing something? An entry could be like follows:
@pic{pic:tolstoy1873,
artist = {Ivan Kramskoy},
title = {Portrait of Leo Tolstoy},
technic = {<oil>|<chalkdrawing>|<engraving>|<photo>|...},
location = {Tretyakov Gallery, Moscow, Russia},
originalyear = {1873},
reproduction = {<photographer>|<print>|...},
url = {\url{<>}},
urldate = {<last accessed>},
...
}
Or make pandoc a "Killer-App" that it is even cleverer than LaTeX itself: let citeproc create a pictography separated from bibliography. Hope some people feel stimulated in their ambition by this appeal!
greetings to all
marek
prev parent reply other threads:[~2023-05-23 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 15:32 'Marek Stepanek' via pandoc-discuss
[not found] ` <26DA151C-9D95-4558-BC46-8AD1BBC81E19-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2023-05-15 8:32 ` BPJ
[not found] ` <CADAJKhA+DNaqnBEP+JHN8J5eP0OFJjb2cguwDF1LgDGscpcaCg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-05-17 16:45 ` 'Marek Stepanek' via pandoc-discuss
2023-05-18 14:50 ` Bernardo C. D. A. Vasconcelos
[not found] ` <c19d9830-7623-44b3-94ad-24889e2498cen-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-23 16:27 ` 'Marek Stepanek' via pandoc-discuss [this message]
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=51160ACF-4EF8-40A6-97F4-2D287907228B@googlemail.com \
--to=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).