public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Björn Ekström" <eksbjo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Markdown syntax can't handle BibLaTeX formatting
Date: Thu, 2 Nov 2017 00:53:16 -0700 (PDT)	[thread overview]
Message-ID: <5fdd83a6-e681-42bf-91b5-1216e605f76b@googlegroups.com> (raw)
In-Reply-To: <cfc702fb-7389-4b78-88c8-0ec235ffa481-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

Also, why wouldn't 

What do you think about the theory of [@smith2000?]?


be valid formatting? 

 


Den torsdag 2 november 2017 kl. 08:39:29 UTC+1 skrev Björn Ekström:
>
> Hello,
>
> Thanks for your replies. I could of course change the bibkeys. But since I 
> am generating them through export from Zotero I would like to do so now and 
> again when adding citations to a text, not having to edit each and every 
> faulty bibkey each time this export process is done.
>
> Albert Krewinkel: This script seems handy. Where do I place it? As a file 
> by itself or inside the Markdown file? I tried the latter but I didn't seem 
> to get it right.
>
> Den onsdag 1 november 2017 kl. 21:41:48 UTC+1 skrev Albert Krewinkel:
>>
>> If, for some reason, the bib keys cannot be changed, the combination of 
>> spans and filters might come in handy: 
>>
>> Write citations as a markdown span 
>>
>>     [statute._2014/foo:bar_title_????]{.cite} 
>>
>> and use a filter like the following to convert the span into a citation. 
>>
>>     function Span(elem) 
>>       if elem.classes[1] == "cite" then 
>>         local citeId = elem.content[1].text 
>>         local citeMode = pandoc.AuthorInText 
>>         local citation = pandoc.Citation(citeId, citeMode) 
>>         return pandoc.Cite(elem.content, {citation}) 
>>       end 
>>     end 
>>     
>> It is not a pretty solution, but you might find it useful regardless. 
>>
>>
>> distantflag <eks...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: 
>>
>> > I have an issue where the Markdown syntax for referring to 
>> bibliographical sources can't treat direct links to the entries in an 
>> BibLaTeX file. 
>> > 
>> > For instance, the BibLaTeX file looks like this: 
>> > 
>> > @online{statute._2014/foo:bar_title_????, 
>> > title = {Title}, 
>> > author = {{Statute. 2014/Foo:Bar}}, 
>> > langid = {swedish} 
>> > } 
>> > 
>> > @report{author_report:_2014, 
>> > location = {Foobar}, 
>> > title = {Report: Foo (Bar)}, 
>> > url = {http://foo.bar}, 
>> > author = {{Author}}, 
>> > urldate = {2017-11-01}, 
>> > date = {2014} 
>> > } 
>> > 
>> > The Markdown formatting for referring to this would be 
>> > 
>> > [@statute._2014/foo:bar_title_????] 
>> > 
>> > and 
>> > 
>> > [@author_report:_2014] 
>> > 
>> > However, the question marks and the colon messes up the syntax 
>> formatting and the sources cannot be converted to plain text using pandoc. 
>> > 
>> > What can be done about this? 
>>
>> -- 
>> Albert Krewinkel 
>> GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124 
>>
>

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/5fdd83a6-e681-42bf-91b5-1216e605f76b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

  parent reply	other threads:[~2017-11-02  7:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 13:25 distantflag
     [not found] ` <90e14ff2-6cec-4dfe-9236-0998cf317b6c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-01 16:40   ` John MACFARLANE
2017-11-01 20:40   ` Albert Krewinkel
     [not found]     ` <87tvyd4trv.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2017-11-02  7:39       ` distantflag
     [not found]         ` <cfc702fb-7389-4b78-88c8-0ec235ffa481-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-02  7:53           ` Björn Ekström [this message]
     [not found]             ` <5fdd83a6-e681-42bf-91b5-1216e605f76b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-02 19:22               ` John MACFARLANE
2017-11-02 20:02           ` Albert Krewinkel
     [not found]             ` <87po904ffv.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2017-11-02 20:22               ` John MACFARLANE
2017-11-02 21:22                 ` Albert Krewinkel
     [not found]                   ` <87k1z84bpy.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2017-11-02 22:19                     ` John MACFARLANE
2017-11-03  9:37                       ` Björn Ekström
     [not found]                         ` <1de89ee9-9064-4020-8419-4bcf7755cf9b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-03  9:56                           ` Björn Ekström
     [not found]                             ` <219efc35-d812-4b40-addd-adaed55955d8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-03 18:51                               ` Albert Krewinkel
     [not found]                                 ` <87bmkj42mv.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2017-11-04  7:04                                   ` Björn Ekström

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=5fdd83a6-e681-42bf-91b5-1216e605f76b@googlegroups.com \
    --to=eksbjo-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).