public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Pa Sc <ideas-and-peanutbutter-zqRNUXuvxA0b1SvskN2V4Q@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Citations/References using Pandoc (via LaTeX) to export to PDF from Obsidian (markdown): How to have Pandoc just use my text for citations
Date: Thu, 8 Dec 2022 02:21:58 -0800 (PST)	[thread overview]
Message-ID: <3e527a2b-41b2-4421-bfc9-b34b3fbac067n@googlegroups.com> (raw)
In-Reply-To: <a8b8c8eea2f04a908cb6090a3c5b674a-NSENcxR/0n0@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2505 bytes --]

Via a plugin (https://github.com/phillipjohnston/obsidian-pandoc). I just 
figured out that you can use @citekey to cite via the plugin, but not how 
to use the correct style. therefore I think it would still be easier if 
Pandoc could just pass that text along to LaTeX, i.e. ignore it. How would 
I do this?


denis...-NSENcxR/0n0@public.gmane.org schrieb am Donnerstag, 8. Dezember 2022 um 11:12:42 UTC+1:

> How does Obsidian call pandoc ?
>
>  
>
> *Von:* pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> *Im 
> Auftrag von *Pa Sc
> *Gesendet:* Mittwoch, 7. Dezember 2022 21:58
> *An:* pandoc-discuss <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
> *Betreff:* Citations/References using Pandoc (via LaTeX) to export to PDF 
> from Obsidian (markdown): How to have Pandoc just use my text for citations
>
>  
>
> The source are markdown files created in Obsidian.
>
> I would like to use Pandoc and LaTeX to automatically cite my sources. I 
> have the bib file all set up, and the LaTeX part too, and directly in a 
> LaTeX editor I can use \cite{Smith2020}to reference a source, and it is 
> then rendered as Smith 2020.
>
> Now I’d just like to be able to include that type of citation in my 
> markdown files so I can then export those to PDF via LaTeX.
>
> Right now when I export this kind of citation it just outputs the citekey 
> itself, with no change.
>
> How can I fix this?
>
> Thank you!
>
> -- 
> 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/5d9e027d-f905-4cb6-a070-873d87c74428n%40googlegroups.com 
> <https://groups.google.com/d/msgid/pandoc-discuss/5d9e027d-f905-4cb6-a070-873d87c74428n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/3e527a2b-41b2-4421-bfc9-b34b3fbac067n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 4547 bytes --]

  parent reply	other threads:[~2022-12-08 10:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AQHZCn6SQ5QglEnCFE604mbixJdi8K5jxiSA///x6QCAAce2kA==>
     [not found] ` <AQHZCn6SQ5QglEnCFE604mbixJdi8K5jxiSA>
2022-12-07 20:57   ` Pa Sc
     [not found]     ` <5d9e027d-f905-4cb6-a070-873d87c74428n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-08 10:12       ` AW: " denis.maier-NSENcxR/0n0
     [not found]         ` <a8b8c8eea2f04a908cb6090a3c5b674a-NSENcxR/0n0@public.gmane.org>
2022-12-08 10:21           ` Pa Sc [this message]
     [not found]             ` <3e527a2b-41b2-4421-bfc9-b34b3fbac067n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-09 12:38               ` denis.maier-NSENcxR/0n0
     [not found]                 ` <975010e9280d4b2a9a100a09a5ddfc96-NSENcxR/0n0@public.gmane.org>
2022-12-09 14:47                   ` Pa Sc

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=3e527a2b-41b2-4421-bfc9-b34b3fbac067n@googlegroups.com \
    --to=ideas-and-peanutbutter-zqrnuxuvxa0b1svskn2v4q@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).