From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/7545 Path: news.gmane.org!not-for-mail From: Nick Bart Newsgroups: gmane.text.pandoc Subject: Re: Decoupling citeproc and highlighting-kate from pandoc Date: Sun, 29 Sep 2013 04:39:24 -0700 (PDT) Message-ID: References: <09c521a8-1f44-474b-8829-60dd95cf0f94@googlegroups.com> <20130928193409.GA45018@Johns-MacBook-Pro.local> <20130928213433.GB45256@Johns-MacBook-Pro.local> <605aad90-4967-42b9-8efe-0aa033c670da@googlegroups.com> <20130928225947.GA45508@Johns-MacBook-Pro.local> <2e3d65a5-01f8-4be5-94b5-2346160886ac@googlegroups.com> <20130929012541.GC45785@Johns-MacBook-Pro.local> <20130929014129.GA45834@Johns-MacBook-Pro.local> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1393_28682036.1380454765056" X-Trace: ger.gmane.org 1380454767 7871 80.91.229.3 (29 Sep 2013 11:39:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 29 Sep 2013 11:39:27 +0000 (UTC) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-X-From: pandoc-discuss+bncBDIPX6WQ4INBB35CUCJAKGQEKLJIXJQ-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Sun Sep 29 13:39:31 2013 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane.org Original-Received: from mail-pb0-f61.google.com ([209.85.160.61]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VQFLV-0001mm-NK for gtp-pandoc-discuss@m.gmane.org; Sun, 29 Sep 2013 13:39:30 +0200 Original-Received: by mail-pb0-f61.google.com with SMTP id jt11sf949232pbb.26 for ; Sun, 29 Sep 2013 04:39:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=Vfm5nt3rEJ8podNEpVfrqP2oZTEfNkOJpGvHj4pZNWU=; b=DpqgjZt7hGSrNay7dwUg4iYT0A9UiTVmp4IUjJpjY+q9pTLek6RJCr2OLSKPzGu9Sf G+Of4IpueQXLJOjELV2nq2PoOTHc7lxtIffUN2Aa1Tz5QKTyOfBirI9TXv77HrpbYQH5 GJ/ZXw/x7566UOOsOpwIA19m7fSg2b5UTENrIguiMzUJIeJu4z/mDTCX8xbjce8x2gAl gAT9W7GeVCKhprNXF9qqjQ7s0sLP1e/JUtaj+kWwlNw5yFOOmHCm5gT0jci9LyQJ1goT Ubm0ONi4GUG/vYS73vfpwkPVvGfcXZqs9d11mXli4tEhP9rApsStJ3Sq43hvAw3abKXw olDA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=Vfm5nt3rEJ8podNEpVfrqP2oZTEfNkOJpGvHj4pZNWU=; b=hhfmJy/qHAS10GI5Zs3PX6z4qMRDG94JdFBAGxJFqfvwQrIw5jxU0vwsxBfeQmh2JB 3xwNHTYcKRMqcjYs0HRfqS54K6uiOh9SahbB5AEgmzc6cU8bqf7g0qWejCqGZjds01H3 wb+fx8hO5mbXx2aqiNTAqo8i/qgGqrZ9B6VsRA6mMGV4K2Wkngjl/QF+TjiEbGQsqoJd uykvOhb8eISVYDlZGbP8Is81xtxRM0uZUtk9Jb2ZA+hZw0WV44VDcF06qpfWwoS44mws 2/zoHh1XmuXl80CLZmE3P7K7dIERhhDnPN45ky+HNtGIfRx4oUnKPrVI82CxjMCUCe66 ECjg== X-Received: by 10.50.23.8 with SMTP id i8mr337895igf.8.1380454768351; Sun, 29 Sep 2013 04:39:28 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 10.50.73.106 with SMTP id k10ls1320161igv.3.gmail; Sun, 29 Sep 2013 04:39:27 -0700 (PDT) X-Received: by 10.50.25.40 with SMTP id z8mr75729igf.15.1380454767173; Sun, 29 Sep 2013 04:39:27 -0700 (PDT) In-Reply-To: <20130929014129.GA45834-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> X-Original-Sender: nickbart1980-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.text.pandoc:7545 Archived-At: ------=_Part_1393_28682036.1380454765056 Content-Type: text/plain; charset=ISO-8859-1 John, you are prefectly right, biblatex uses Babel language terms. In a comprehensive mapping from biblatex to CSL they should surely be implemented, and I can look into this. Still, to get title/sentence case right, it just a question of English vs. other languages, and this seems to work well with the small set of languages included so far. Are you aware of anything CSL/citeproc would actually be doing with entry-specific language information (except for dealing with title/sentence case)? On a related note, how is per-document localization done in pandoc(-citeproc)? On Sunday, 29 September 2013 01:41:30 UTC, fiddlosopher wrote: > > I guess they are Babel language names. > > So here's the list from the Babel manual. We just need to > correlate these with things like en-US: > > Afrikaans afrikaans > Bahasa bahasa > Basque basque > Breton breton > Bulgarian bulgarian > Catalan catalan > Croatian croatian > Czech czech > Danish danish > Dutch dutch > English english, USenglish, american, UKenglish, british, > canadian, australian, newzealand > Esperanto esperanto > Estonian estonian > Finnish finnish > French french, francais, canadien, acadian > Galician galician > German austrian, german, germanb, ngerman, naustrian > Greek greek, polutonikogreek > Hebrew hebrew > Hungarian magyar, hungarian > Icelandic icelandic > Interlingua interlingua > Irish Gaelic irish > Italian italian > Latin latin > Lower Sorbian lowersorbian > North Sami samin > Norwegian norsk, nynorsk > Polish polish > Portuguese portuges, portuguese, brazilian, brazil > Romanian romanian > Russian russian > Scottish Gaelic scottish > Spanish spanish > Slovakian slovak > Slovenian slovene > Swedish swedish > Serbian serbian > Turkish turkish > Ukrainian ukrainian > Upper Sorbian uppersorbian > Welsh welsh > > This page (http://demo.icu-project.org/icu-bin/locexp) has > teh information. > > > +++ John MacFarlane [Sep 28 13 18:25 ]: > > But this only covers English locales. We also want to map > > Spanish to "es-SP" or whatever it is, and so on.... > > > > Is there a list of the valid values for the biblatex > > "hyphenation" field? > > > > I also think it makes more sense to define a function > > > > toLocale :: String -> String > > toLocale "english" = "en" > > toLocale "australian" = "en-AU" > > ...etc... > > > > and then > > > > opt $ getRawField "hyphenation" >>= setRawField "language" . > toLocale > > > > The . is function composition, so this says: apply to toLocale > > function to the value before passing it to setRawField "language". > > > > +++ Nick Bart [Sep 28 13 16:48 ]: > > > OK, this should do the trick: > > > opt $ do > > > val <- getRawField "hyphenation" > > > case val of > > > "english" -> setRawField "language" "en" > > > "american" -> setRawField "language" "en-US" > > > "british" -> setRawField "language" "en-UK" > > > "canadian" -> setRawField "language" "en-CA" > > > "australian" -> setRawField "language" "en-AU" > > > "newzealand" -> setRawField "language" "en-NZ" > > > "USenglish" -> setRawField "language" "en-US" > > > "UKenglish" -> setRawField "language" "en-UK" > > > _ -> setRawField "language" val > > > And remove > > > opt $ getRawField "hyphenation" >>= setRawField "language" > > > On Saturday, September 28, 2013 11:30:24 PM UTC, Nick Bart wrote: > > > > > > On second thoughts, however: Works for me, since I have only > "english" > > > in my hyphenation fields. > > > However, CSL's title cases routine is simply triggered if the CSL > > > language field starts with "en", but not by, e.g., "american"; so > we'll > > > probably have to map hyphenation = american, british, canadian, > > > australian, newzealand, USenglish or UKenglish either all to > "english", > > > or individually to "en-UK", "en-US", etc. > > > On Saturday, September 28, 2013 11:16:42 PM UTC, Nick Bart wrote: > > > > > > I already added this earlier: > > > opt $ getRawField "hyphenation" >>= setRawField "language" > > > Seems to work nicely ... > > > On Saturday, September 28, 2013 10:59:47 PM UTC, fiddlosopher > wrote: > > > > > > OK, I've added this feature. > > > In order to set the "language" variable properly, we need a > mapping > > > from biblatex hyphenation field values to whatever fills the CSL > > > language slot. > > > Can you provide one? > > > +++ Nick Bart [Sep 28 13 15:19 ]: > > > > biblatex database entries may contain a "hyphenation" field, > > > specifying > > > > the language of the bibliographic record, used for > determining > > > > hyphenation patterns and whether title/sentence case > conversion > > > is to > > > > be applied. It must contain exactly one language term. The > > > functional > > > > equivalent in CSL is the "language" variable, also used for > > > determining > > > > whether title/sentence case conversion is to be applied. > > > > biblatex database entries may also contain a "language" > field, > > > which > > > > describes the language or languages of the *content* of the > > > work, e.g. > > > > language = {latin and english}. This has no counterpart in > CSL. > > > > unTitlecase should only be applied to titles in languages > that > > > do > > > > distinguish title from sentence case, and that's as far as I > > > know, and > > > > in line with biblatex's default only English. In other > words, > > > > unTitlecase should only be applied if an entry's hyphenation > > > field > > > > contains one of the terms american, british, canadian, > english, > > > > australian, newzealand, USenglish or UKenglish. > > > > On Saturday, September 28, 2013 9:34:33 PM UTC, fiddlosopher > > > wrote: > > > > > > > > How is the language represented in a biblatex file? Or is > it > > > an > > > > external parameter that comes from the locale or something > > > else? > > > > +++ Nick Bart [Sep 28 13 13:37 ]: > > > > > unTitlecase: Brilliant. > > > > > Forgot one important detail, though: unTitlecase > should > > > only be > > > > applied > > > > > if the language is English, i.e., if an entry's > biblatex > > > > hyphenation > > > > > field is one of american, british, canadian, english, > > > > australian, > > > > > newzealand, USenglish or UKenglish. > > > > > From the biblatex manual (v 2.7a), "4.6.4 > Miscellaneous > > > > Commands", item > > > > > " \MakeSentenceCase": > > > > > > By default, converting to sentence case is enabled > for > > > the > > > > following > > > > > language identifiers: american, british, canadian, > > > english, > > > > australian, > > > > > newzealand as well as the aliases USenglish and > > > UKenglish. > > > > > On Saturday, September 28, 2013 7:34:09 PM UTC, > > > fiddlosopher > > > > wrote: > > > > > > > > > > +++ Nick Bart [Sep 28 13 03:52 ]: > > > > > > A few additional ideas/issues: > > > > > > Title vs. sentence case > > > > > > ======================= > > > > > > bibtex and biblatex expect titles in title > case > > > in the > > > > > database, > > > > > > converting these to sentence case if required > by > > > a > > > > particular > > > > > style, > > > > > > except for strings protected by {}. > > > > > > CSL does the opposite: It expects titles in > > > sentence > > > > case, > > > > > converting > > > > > > these to title case if required, except for > > > certain stop > > > > words. > > > > > > I think it make senses for bibtex2pandoc to > > > convert > > > > > bibtex=biblatex > > > > > > titles to sentence case for further > consumption > > > by CSL; > > > > i.e., > > > > > to lower > > > > > > case, except strings protected by {}. > > > > > > - ex.: > > > > > > title = {{JFK}: The {CIA}, {Vietnam}, and > the > > > Plot > > > > to > > > > > Assassinate > > > > > > {John F. Kennedy}} > > > > > > becomes > > > > > > title: 'JFK: The CIA, Vietnam, and the > plot > > > to > > > > assassinate > > > > > John F. > > > > > > Kennedy' > > > > > > - to be discussed: should strings inside > > > commands be > > > > > converted, > > > > > > too? > > > > > > i.e., should > > > > > > title = {An Analysis of \textit{For Whom > the > > > Bell > > > > Tolls}} > > > > > > become > > > > > > title: 'An Analysis of for whom the > bell > > > > tolls' > > > > > > and only extra protection > > > > > > title = {An Analysis of {\textit{For Whom > > > the Bell > > > > > Tolls}}} > > > > > > would yield > > > > > > title: 'An Analysis of For Whom the > Bell > > > > Tolls' > > > > > I've implemented the unTitlecase transformation. > > > (This > > > > depends on a > > > > > recent patch to pandoc that causes the LaTeX reader > to > > > insert > > > > Span > > > > > when we have a bare group {Like This}.) > > > > > I don't know about the "to be discussed" -- > currently > > > strings > > > > inside > > > > > emphasis, etc., will retain their case. I think > > > that's > > > > probably > > > > > right. > > > > > > Corporate authors > > > > > > ================= > > > > > > Example: author = {{National Aeronautics and > > > Space > > > > > Administration}}, > > > > > > Current bibtex2pandoc output: > > > > > > - author: > > > > > > - family: Aeronautics > > > > > > given: > > > > > > - National > > > > > > - family: Administration > > > > > > given: > > > > > > - Space > > > > > > Expected: > > > > > > - author: > > > > > > - literal: 'National Aeronautics and Space > > > > Administration' > > > > > I've added support for this. > > > > > > Literal and in institution, organization, > > > publisher, > > > > location, > > > > > etc. > > > > > > ============================= > > > > ============================== > > > > > ========== > > > > > > If code includes > > > > > > > > > > > > getLiteralList "publisher" ==> setList > > > "publisher" > > > > > > publisher = {Holt, Rinehart {and} Winston} > > > > > > Current bibtex2pandoc output: > > > > > > publisher: > > > > > > - 'Holt, Rinehart' > > > > > > - Winston > > > > > > Expected: > > > > > > publisher: > > > > > > - 'Holt, Rinehart and Winston' > > > > > > Also noticed, however, that pandoc-citeproc > does > > > not > > > > seem to > > > > > like it > > > > > > when actual multiple publishers occur: > > > > > > publisher: > > > > > > - 'Univ. of Toronto Press' > > > > > > - Routledge > > > > > > throws an error: > > > > > > pandoc-citeproc: Error parsing references: > when > > > > expecting a > > > > > String, > > > > > > encountered Array instead > > > > > > This needs to be checked, but if CSL does not > > > allow > > > > multiple > > > > > > publishers, the code above would need to be > > > changed back > > > > to > > > > > > getField "publisher" ==> setField > "publisher" > > > > > > I see that multiple publishers (and locations) > > > are being > > > > > discussed at > > > > > > various Zotero/CSL/citeproc-js forums, but > don't > > > get a > > > > clear > > > > > picture > > > > > > yet. > > > > > The literal {and} will not cause breaking of author > > > lists or > > > > literal > > > > > lists. > > > > > I'll leave the multiple publishers question open > for > > > now. > > > > Either > > > > > bibtex2pandoc or pandoc-citeproc should be changed, > > > not sure > > > > which. > > > > > > Names > > > > > > ===== > > > > > > Can bibtex2pandoc be expected to distinguish > all > > > five > > > > name > > > > > components > > > > > > (family, given, suffix, non-dropping-particle, > > > > > dropping-particle)? > > > > > > biblatex provides one useful additional bit of > > > info for > > > > name > > > > > parsing > > > > > > via the "useprefix" switch inside the > "options" > > > field: > > > > > > From the biblatex manual (v 2.7a), "3.1.3 > Entry > > > Options" > > > > > > > Whether the name prefix (von, van, of, da, > de, > > > della, > > > > etc.) > > > > > is > > > > > > considered when printing the last name in > > > citations. > > > > This also > > > > > affects > > > > > > the sorting and formatting of the bibliography > as > > > well > > > > as the > > > > > > generation of certain types of labels. If this > > > option is > > > > > enabled, > > > > > > biblatex always precedes the last name with > the > > > prefix. > > > > For > > > > > example, > > > > > > Ludwig van Beethoven would be cited as > Beethoven > > > and > > > > > alphabetized as > > > > > > Beethoven, Ludwig van by default. If this > option > > > is > > > > enabled, he > > > > > is > > > > > > cited as van Beethoven and alphabetized as Van > > > > Beethoven, > > > > > Ludwig > > > > > > instead. With Biber, this option is also > settable > > > on a > > > > per-type > > > > > basis. > > > > > I used a rough-and-ready algorithm, probably not > the > > > same one > > > > biber > > > > > or biblatex uses. Basically, the only time my code > > > gives you > > > > a > > > > > non-dropping particle is when you have a name in > > > format > > > > > B A, D E > > > > > then B is the particle and A the given name. > > > > > I don't have any support now for dropping-particle > or > > > suffix. > > > > > This needs to be improved, but I'd need to know > better > > > what > > > > the > > > > > algorithm is. > > > > > > Inline formatting > > > > > > ================= > > > > > > It probably doesn't play a role for pandoc, > but > > > in the > > > > interest > > > > > of > > > > > > portability, shouldn't inline formatting in a > > > CSL-YAML > > > > file or > > > > > metadata > > > > > > section rather use > > > > > > and for italics > > > > > > and for bold > > > > > > and for subscript > > > > > > and for superscript > > > > > > > and > > > > > > > for > > > > > smallcaps > > > > > > instead of markdown formatting? > > > > > > (see [1][1][1]https://github.com/jgm/ > > > pandoc/issues/931, > > > > > > [2][2][2]https://www.zotero.org/ > > > support/kb/rich_text_ > > > > bibliography) > > > > > No, because the YAML file is standard pandoc > metadata, > > > > formatted in > > > > > markdown. When it is read by pandoc-citeproc, this > > > will be > > > > > converted > > > > > where possible to CSL metadata. > > > > > > Small Caps > > > > > > ========== > > > > > > Speaking of small caps: Any plans to add some > > > > markdownish > > > > > formatting > > > > > > commands for small caps to pandoc? > > > > > No idea what a natural syntax would be. > > > > > > > > > > -- > > > > > 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 [3]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > To post to this group, send email to > > > > [4]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > To view this discussion on the web visit > > > > > [3][5][3]https://groups.google. > > > com/d/msgid/pandoc-discuss/ > > > > a86067ec-6b4a-437b- > > > > > b2f0-3ee666209dae%[6][4]40googlegroups.com. > > > > > For more options, visit [4][7][5] > https://groups.google. > > > com/ > > > > groups/opt_out. > > > > > > > > > > References > > > > > > > > > > 1. [8][6]https://github.com/jgm/pandoc/issues/931 > > > > > 2. [9][7]https://www.zotero.org/support/kb/rich_text_ > > > bibliography > > > > > 3. [10][8]https://groups.google.com/d/ > > > > msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae% > > > > [9]40googlegroups.com > > > > > 4. [11][10]https://groups.google.com/groups/opt_out > > > > > > > > -- > > > > 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 post to this group, send email to > > > pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To view this discussion on the web visit > > > > [12][11]https://groups.google.com/d/msgid/pandoc-discuss/ > > > 605aad90-4967-42b9 > > > > -8efe-0aa033c670da%[12]40googlegroups.com. > > > > For more options, visit [13][13]https://groups.google.com/ > > > groups/opt_out. > > > > > > > > References > > > > > > > > 1. [14]https://github.com/jgm/pandoc/issues/931 > > > > 2. [15] > https://www.zotero.org/support/kb/rich_text_bibliography > > > > 3. javascript:/ > > > > 4. javascript:/ > > > > 5. [16]https://groups.google.com/d/ > > > msgid/pandoc-discuss/a86067ec-6b4a-437b- > > > > 6. [17]http://40googlegroups.com/ > > > > 7. [18]https://groups.google.com/groups/opt_out > > > > 8. [19]https://github.com/jgm/pandoc/issues/931 > > > > 9. [20] > https://www.zotero.org/support/kb/rich_text_bibliography > > > > 10. [21]https://groups.google.com/d/ > > > msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae% > > > 40googlegroups.com > > > > 11. [22]https://groups.google.com/groups/opt_out > > > > 12. [23]https://groups.google.com/d/ > > > msgid/pandoc-discuss/605aad90-4967-42b9-8efe-0aa033c670da% > > > 40googlegroups.com > > > > 13. [24]https://groups.google.com/groups/opt_out > > > > > > -- > > > 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...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org . > > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org. > > > > To view this discussion on the web visit > > > [25] > https://groups.google.com/d/msgid/pandoc-discuss/ebae1a26-c6cb-44c4 > > > -add2-5dc57f620a4c%40googlegroups.com. > > > For more options, visit [26] > https://groups.google.com/groups/opt_out. > > > > > > References > > > > > > 1. https://github.com/jgm/pandoc/issues/931 > > > 2. https://www.zotero.org/support/kb/rich_text_ > > > 3. https://groups.google.com/d/msgid/pandoc-discuss/ > > > 4. http://40googlegroups.com/ > > > 5. https://groups.google.com/ > > > 6. https://github.com/jgm/pandoc/issues/931 > > > 7. https://www.zotero.org/support/kb/rich_text_bibliography > > > 8. https://groups.google.com/d/ > > > 9. http://40googlegroups.com/ > > > 10. https://groups.google.com/groups/opt_out > > > 11. > https://groups.google.com/d/msgid/pandoc-discuss/605aad90-4967-42b9 > > > 12. http://40googlegroups.com/ > > > 13. https://groups.google.com/groups/opt_out > > > 14. https://github.com/jgm/pandoc/issues/931 > > > 15. https://www.zotero.org/support/kb/rich_text_bibliography > > > 16. > https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b- > > > 17. http://40googlegroups.com/ > > > 18. https://groups.google.com/groups/opt_out > > > 19. https://github.com/jgm/pandoc/issues/931 > > > 20. https://www.zotero.org/support/kb/rich_text_bibliography > > > 21. > https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae%40googlegroups.com > > > 22. https://groups.google.com/groups/opt_out > > > 23. > https://groups.google.com/d/msgid/pandoc-discuss/605aad90-4967-42b9-8efe-0aa033c670da%40googlegroups.com > > > 24. https://groups.google.com/groups/opt_out > > > 25. > https://groups.google.com/d/msgid/pandoc-discuss/ebae1a26-c6cb-44c4-add2-5dc57f620a4c%40googlegroups.com > > > 26. https://groups.google.com/groups/opt_out > > > > -- > > 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...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org . > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org. > > > To view this discussion on the web visit > https://groups.google.com/d/msgid/pandoc-discuss/20130929012541.GC45785%40Johns-MacBook-Pro.local. > > > For more options, visit https://groups.google.com/groups/opt_out. > -- 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/fd944048-488f-4d68-a27e-5db0f5d41723%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. ------=_Part_1393_28682036.1380454765056 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
John, you are prefectly right, biblatex uses Babel languag= e terms. In a comprehensive mapping from biblatex to CSL they should surely= be implemented, and I can look into this. Still, to get title/sentence cas= e right, it just a question of English vs. other languages, and this seems = to work well with the small set of languages included so far.

Are yo= u aware of anything CSL/citeproc would actually be doing with entry-specifi= c language information (except for dealing with title/sentence case)?
On a related note, how is per-document localization done in pandoc(-citep= roc)?

On Sunday, 29 September 2013 01:41:30 UTC, fiddlosopher wrot= e:
I guess they are Babel langu= age names.

So here's the list from the Babel manual.  We just need to
correlate these with things like en-US:

Afrikaans afrikaans
Bahasa bahasa
Basque basque
Breton breton
Bulgarian bulgarian
Catalan catalan
Croatian croatian
Czech czech
Danish danish
Dutch dutch
English english, USenglish, american, UKenglish, british,
canadian, australian, newzealand
Esperanto esperanto
Estonian estonian
Finnish finnish
French french, francais, canadien, acadian
Galician galician
German austrian, german, germanb, ngerman, naustrian
Greek greek, polutonikogreek
Hebrew hebrew
Hungarian magyar, hungarian
Icelandic icelandic
Interlingua interlingua
Irish Gaelic irish
Italian italian
Latin latin
Lower Sorbian lowersorbian
North Sami samin
Norwegian norsk, nynorsk
Polish polish
Portuguese portuges, portuguese, brazilian, brazil
Romanian romanian
Russian russian
Scottish Gaelic scottish
Spanish spanish
Slovakian slovak
Slovenian slovene
Swedish swedish
Serbian serbian
Turkish turkish
Ukrainian ukrainian
Upper Sorbian uppersorbian
Welsh welsh

This page (http://demo.icu-project.org/icu-bin/locexp) has
teh information.


+++ John MacFarlane [Sep 28 13 18:25 ]:
> But this only covers English locales.  We also want to map
> Spanish to "es-SP" or whatever it is, and so on....
>=20
> Is there a list of the valid values for the biblatex
> "hyphenation" field?
>=20
> I also think it makes more sense to define a function
>=20
> toLocale :: String -> String
> toLocale "english" =3D "en"
> toLocale "australian" =3D "en-AU"
> ...etc...
>=20
> and then
>=20
>     opt $ getRawField "hyphenation" >>=3D setRawFi= eld "language" . toLocale
>=20
> The . is function composition, so this says:  apply to toLoca= le
> function to the value before passing it to setRawField "language".
>=20
> +++ Nick Bart [Sep 28 13 16:48 ]:
> >    OK, this should do the trick:
> >      opt $ do
> >        val <- getRawField "hyphenation= "
> >        case val of
> >          "english"    ->= ; setRawField "language" "en"
> >          "american"   -> set= RawField "language" "en-US"
> >          "british"    ->= ; setRawField "language" "en-UK"
> >          "canadian"   -> set= RawField "language" "en-CA"
> >          "australian" -> setRawFi= eld "language" "en-AU"
> >          "newzealand" -> setRawFi= eld "language" "en-NZ"
> >          "USenglish"  -> set= RawField "language" "en-US"
> >          "UKenglish"  -> set= RawField "language" "en-UK"
> >          _       &nbs= p;    -> setRawField "language" val
> >    And remove
> >    opt $ getRawField "hyphenation" >>=3D setR= awField "language"
> >    On Saturday, September 28, 2013 11:30:24 PM UTC,= Nick Bart wrote:
> >=20
> >    On second thoughts, however: Works for me, since= I have only "english"
> >    in my hyphenation fields.
> >    However, CSL's title cases routine is simply tri= ggered if the CSL
> >    language field starts with "en", but not by, e.g= ., "american"; so we'll
> >    probably have to map hyphenation =3D american, b= ritish, canadian,
> >    australian, newzealand, USenglish or UKenglish e= ither all to "english",
> >    or individually to "en-UK", "en-US", etc.
> >    On Saturday, September 28, 2013 11:16:42 PM UTC,= Nick Bart wrote:
> >=20
> >    I already added this earlier:
> >      opt $ getRawField "hyphenation" >>= =3D setRawField "language"
> >    Seems to work nicely ...
> >    On Saturday, September 28, 2013 10:59:47 PM UTC,= fiddlosopher wrote:
> >=20
> >      OK, I've added this feature.
> >      In order to set the "language" variable p= roperly, we need a mapping
> >      from biblatex hyphenation field values to= whatever fills the CSL
> >      language slot.
> >      Can you provide one?
> >      +++ Nick Bart [Sep 28 13 15:19 ]:
> >      >    biblatex database entri= es may contain a "hyphenation" field,
> >      specifying
> >      >    the language of the bib= liographic record, used for determining
> >      >    hyphenation patterns an= d whether title/sentence case conversion
> >      is to
> >      >    be applied. It must con= tain exactly one language term. The
> >      functional
> >      >    equivalent in CSL is th= e "language" variable, also used for
> >      determining
> >      >    whether title/sentence = case conversion is to be applied.
> >      >    biblatex database entri= es may also contain a "language" field,
> >      which
> >      >    describes the language = or languages of the *content* of the
> >      work, e.g.
> >      >    language =3D {latin and= english}. This has no counterpart in CSL.
> >      >    unTitlecase should only= be applied to titles in languages that
> >      do
> >      >    distinguish title from = sentence case, and that's as far as I
> >      know, and
> >      >    in line with biblatex's= default only English. In other words,
> >      >    unTitlecase should only= be applied if an entry's hyphenation
> >      field
> >      >    contains one of the ter= ms american, british, canadian, english,
> >      >    australian, newzealand,= USenglish or UKenglish.
> >      >    On Saturday, September = 28, 2013 9:34:33 PM UTC, fiddlosopher
> >      wrote:
> >      >
> >      >      How is the langu= age represented in a biblatex file?  Or is it
> >      an
> >      >      external paramet= er that comes from the locale or something
> >      else?
> >      >      +++ Nick Bart [S= ep 28 13 13:37 ]:
> >      >      >   &nbs= p;unTitlecase: Brilliant.
> >      >      >   &nbs= p;Forgot one important detail, though: unTitlecase should
> >      only be
> >      >      applied
> >      >      >   &nbs= p;if the language is English, i.e., if an entry's biblatex
> >      >      hyphenation
> >      >      >   &nbs= p;field is one of american, british, canadian, english,
> >      >      australian,
> >      >      >   &nbs= p;newzealand, USenglish or UKenglish.
> >      >      >   &nbs= p;From the biblatex manual (v 2.7a), "4.6.4 Miscellaneous
> >      >      Commands", item
> >      >      >   &nbs= p;" \MakeSentenceCase":
> >      >      >   &nbs= p;> By default, converting to sentence case is enabled for
> >      the
> >      >      following
> >      >      >   &nbs= p;language identifiers: american, british, canadian,
> >      english,
> >      >      australian,
> >      >      >   &nbs= p;newzealand as well as the aliases USenglish and
> >      UKenglish.
> >      >      >   &nbs= p;On Saturday, September 28, 2013 7:34:09 PM UTC,
> >      fiddlosopher
> >      >      wrote:
> >      >      >
> >      >      >   &nbs= p;  +++ Nick Bart [Sep 28 13 03:52 ]:
> >      >      >   &nbs= p;  >    A few additional ideas/issues:
> >      >      >   &nbs= p;  >    Title vs. sentence case
> >      >      >   &nbs= p;  >    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D
> >      >      >   &nbs= p;  >    bibtex and biblatex expect titles in title case
> >      in the
> >      >      >   &nbs= p;  database,
> >      >      >   &nbs= p;  >    converting these to sentence case if required by
> >      a
> >      >      particular
> >      >      >   &nbs= p;  style,
> >      >      >   &nbs= p;  >    except for strings protected by {}.
> >      >      >   &nbs= p;  >    CSL does the opposite: It expects titles in
> >      sentence
> >      >      case,
> >      >      >   &nbs= p;  converting
> >      >      >   &nbs= p;  >    these to title case if required, except for
> >      certain stop
> >      >      words.
> >      >      >   &nbs= p;  >    I think it make senses for bibtex2pandoc to
> >      convert
> >      >      >   &nbs= p;  bibtex=3Dbiblatex
> >      >      >   &nbs= p;  >    titles to sentence case for further consumption
> >      by CSL;
> >      >      i.e.,
> >      >      >   &nbs= p;  to lower
> >      >      >   &nbs= p;  >    case, except strings protected by {}.
> >      >      >   &nbs= p;  >        - ex.:
> >      >      >   &nbs= p;  >        title =3D {{JFK}: The {CIA}, {Viet= nam}, and the
> >      Plot
> >      >      to
> >      >      >   &nbs= p;  Assassinate
> >      >      >   &nbs= p;  >    {John F. Kennedy}}
> >      >      >   &nbs= p;  >        becomes
> >      >      >   &nbs= p;  >        title: 'JFK: The CIA, Vietnam, and= the plot
> >      to
> >      >      assassinate
> >      >      >   &nbs= p;  John F.
> >      >      >   &nbs= p;  >    Kennedy'
> >      >      >   &nbs= p;  >        - to be discussed: should strings = inside
> >      commands be
> >      >      >   &nbs= p;  converted,
> >      >      >   &nbs= p;  >    too?
> >      >      >   &nbs= p;  >         i.e., should
> >      >      >   &nbs= p;  >         title =3D {An Analysis of \textit= {For Whom the
> >      Bell
> >      >      Tolls}}
> >      >      >   &nbs= p;  >         become
> >      >      >   &nbs= p;  >         title: 'An Analysis of <i>f= or whom the bell
> >      >      tolls</i>'
> >      >      >   &nbs= p;  >         and only extra protection
> >      >      >   &nbs= p;  >         title =3D {An Analysis of {\texti= t{For Whom
> >      the Bell
> >      >      >   &nbs= p;  Tolls}}}
> >      >      >   &nbs= p;  >         would yield
> >      >      >   &nbs= p;  >         title: 'An Analysis of <i>F= or Whom the Bell
> >      >      Tolls</i>'
> >      >      >   &nbs= p;  I've implemented the unTitlecase transformation.
> >      (This
> >      >      depends on a
> >      >      >   &nbs= p;  recent patch to pandoc that causes the LaTeX reader to
> >      insert
> >      >      Span
> >      >      >   &nbs= p;  when we have a bare group {Like This}.)
> >      >      >   &nbs= p;  I don't know about the "to be discussed" -- currently
> >      strings
> >      >      inside
> >      >      >   &nbs= p;  emphasis, etc., will retain their case.  I think
> >      that's
> >      >      probably
> >      >      >   &nbs= p;  right.
> >      >      >   &nbs= p;  >    Corporate authors
> >      >      >   &nbs= p;  >    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D
> >      >      >   &nbs= p;  >    Example: author =3D {{National Aeronautics and
> >      Space
> >      >      >   &nbs= p;  Administration}},
> >      >      >   &nbs= p;  >    Current bibtex2pandoc output:
> >      >      >   &nbs= p;  >    - author:
> >      >      >   &nbs= p;  >      - family: Aeronautics
> >      >      >   &nbs= p;  >        given:
> >      >      >   &nbs= p;  >        - National
> >      >      >   &nbs= p;  >      - family: Administration
> >      >      >   &nbs= p;  >        given:
> >      >      >   &nbs= p;  >        - Space
> >      >      >   &nbs= p;  >    Expected:
> >      >      >   &nbs= p;  >    - author:
> >      >      >   &nbs= p;  >      - literal: 'National Aeronautics and Spac= e
> >      >      Administration'
> >      >      >   &nbs= p;  I've added support for this.
> >      >      >   &nbs= p;  >    Literal and in institution, organization,
> >      publisher,
> >      >      location,
> >      >      >   &nbs= p;  etc.
> >      >      >   &nbs= p;  >    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >      >      =3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >      >      >   &nbs= p;  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >      >      >   &nbs= p;  >    If code includes
> >      >      >   &nbs= p;  >
> >      >      >   &nbs= p;  >      getLiteralList "publisher" =3D=3D> set= List
> >      "publisher"
> >      >      >   &nbs= p;  >    publisher =3D {Holt, Rinehart {and} Winston}
> >      >      >   &nbs= p;  >    Current bibtex2pandoc output:
> >      >      >   &nbs= p;  >      publisher:
> >      >      >   &nbs= p;  >      - 'Holt, Rinehart'
> >      >      >   &nbs= p;  >      - Winston
> >      >      >   &nbs= p;  >    Expected:
> >      >      >   &nbs= p;  >      publisher:
> >      >      >   &nbs= p;  >      - 'Holt, Rinehart and Winston'
> >      >      >   &nbs= p;  >    Also noticed, however, that pandoc-citeproc does
> >      not
> >      >      seem to
> >      >      >   &nbs= p;  like it
> >      >      >   &nbs= p;  >    when actual multiple publishers occur:
> >      >      >   &nbs= p;  >      publisher:
> >      >      >   &nbs= p;  >      - 'Univ. of Toronto Press'
> >      >      >   &nbs= p;  >      - Routledge
> >      >      >   &nbs= p;  >    throws an error:
> >      >      >   &nbs= p;  >    pandoc-citeproc: Error parsing references: when
> >      >      expecting a
> >      >      >   &nbs= p;  String,
> >      >      >   &nbs= p;  >    encountered Array instead
> >      >      >   &nbs= p;  >    This needs to be checked, but if CSL does not
> >      allow
> >      >      multiple
> >      >      >   &nbs= p;  >    publishers, the code above would need to be
> >      changed back
> >      >      to
> >      >      >   &nbs= p;  >      getField "publisher" =3D=3D> setField = "publisher"
> >      >      >   &nbs= p;  >    I see that multiple publishers (and locations)
> >      are being
> >      >      >   &nbs= p;  discussed at
> >      >      >   &nbs= p;  >    various Zotero/CSL/citeproc-js forums, but don't
> >      get a
> >      >      clear
> >      >      >   &nbs= p;  picture
> >      >      >   &nbs= p;  >    yet.
> >      >      >   &nbs= p;  The literal {and} will not cause breaking of author
> >      lists or
> >      >      literal
> >      >      >   &nbs= p;  lists.
> >      >      >   &nbs= p;  I'll leave the multiple publishers question open for
> >      now.
> >      >      Either
> >      >      >   &nbs= p;  bibtex2pandoc or pandoc-citeproc should be changed,
> >      not sure
> >      >      which.
> >      >      >   &nbs= p;  >    Names
> >      >      >   &nbs= p;  >    =3D=3D=3D=3D=3D
> >      >      >   &nbs= p;  >    Can bibtex2pandoc be expected to distinguish all
> >      five
> >      >      name
> >      >      >   &nbs= p;  components
> >      >      >   &nbs= p;  >    (family, given, suffix, non-dropping-particle,
> >      >      >   &nbs= p;  dropping-particle)?
> >      >      >   &nbs= p;  >    biblatex provides one useful additional bit of
> >      info for
> >      >      name
> >      >      >   &nbs= p;  parsing
> >      >      >   &nbs= p;  >    via the "useprefix" switch inside the "options"
> >      field:
> >      >      >   &nbs= p;  >    From the biblatex manual (v 2.7a), "3.1.3 Entry
> >      Options"
> >      >      >   &nbs= p;  >    > Whether the name prefix (von, van, of, da, = de,
> >      della,
> >      >      etc.)
> >      >      >   &nbs= p;  is
> >      >      >   &nbs= p;  >    considered when printing the last name in
> >      citations.
> >      >      This also
> >      >      >   &nbs= p;  affects
> >      >      >   &nbs= p;  >    the sorting and formatting of the bibliography a= s
> >      well
> >      >      as the
> >      >      >   &nbs= p;  >    generation of certain types of labels. If this
> >      option is
> >      >      >   &nbs= p;  enabled,
> >      >      >   &nbs= p;  >    biblatex always precedes the last name with the
> >      prefix.
> >      >      For
> >      >      >   &nbs= p;  example,
> >      >      >   &nbs= p;  >    Ludwig van Beethoven would be cited as Beethoven
> >      and
> >      >      >   &nbs= p;  alphabetized as
> >      >      >   &nbs= p;  >    Beethoven, Ludwig van by default. If this option
> >      is
> >      >      enabled, he
> >      >      >   &nbs= p;  is
> >      >      >   &nbs= p;  >    cited as van Beethoven and alphabetized as Van
> >      >      Beethoven,
> >      >      >   &nbs= p;  Ludwig
> >      >      >   &nbs= p;  >    instead. With Biber, this option is also settabl= e
> >      on a
> >      >      per-type
> >      >      >   &nbs= p;  basis.
> >      >      >   &nbs= p;  I used a rough-and-ready algorithm, probably not the
> >      same one
> >      >      biber
> >      >      >   &nbs= p;  or biblatex uses.  Basically, the only time my code
> >      gives you
> >      >      a
> >      >      >   &nbs= p;  non-dropping particle is when you have a name in
> >      format
> >      >      >   &nbs= p;     B A, D E
> >      >      >   &nbs= p;  then B is the particle and A the given name.
> >      >      >   &nbs= p;  I don't have any support now for dropping-particle or
> >      suffix.
> >      >      >   &nbs= p;  This needs to be improved, but I'd need to know better
> >      what
> >      >      the
> >      >      >   &nbs= p;  algorithm is.
> >      >      >   &nbs= p;  >    Inline formatting
> >      >      >   &nbs= p;  >    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D
> >      >      >   &nbs= p;  >    It probably doesn't play a role for pandoc, but
> >      in the
> >      >      interest
> >      >      >   &nbs= p;  of
> >      >      >   &nbs= p;  >    portability, shouldn't inline formatting in a
> >      CSL-YAML
> >      >      file or
> >      >      >   &nbs= p;  metadata
> >      >      >   &nbs= p;  >    section rather use
> >      >      >   &nbs= p;  >        <i> and </i> for itali= cs
> >      >      >   &nbs= p;  >        <b> and </b> for bold
> >      >      >   &nbs= p;  >        <sub> and </sub> for s= ubscript
> >      >      >   &nbs= p;  >        <sup> and </sup> for s= uperscript
> >      >      >   &nbs= p;  >        <span style=3D"font-variant:sma= ll-caps;"> and
> >      </span>
> >      >      for
> >      >      >   &nbs= p;  smallcaps
> >      >      >   &nbs= p;  >    instead of markdown formatting?
> >      >      >   &nbs= p;  >    (see [1][1][1]https://github.com/jgm/
> >      pandoc/issues/931,
> >      >      >   &nbs= p;  >    [2][2][2]https://www.zotero.org/
> >      support/kb/rich_text_
> >      >      bibliography)
> >      >      >   &nbs= p;  No, because the YAML file is standard pandoc metadata,
> >      >      formatted in
> >      >      >   &nbs= p;  markdown.  When it is read by pandoc-citeproc, this
> >      will be
> >      >      >   &nbs= p;  converted
> >      >      >   &nbs= p;  where possible to CSL metadata.
> >      >      >   &nbs= p;  >    Small Caps
> >      >      >   &nbs= p;  >    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >      >      >   &nbs= p;  >    Speaking of small caps: Any plans to add some
> >      >      markdownish
> >      >      >   &nbs= p;  formatting
> >      >      >   &nbs= p;  >    commands for small caps to pandoc?
> >      >      >   &nbs= p;  No idea what a natural syntax would be.
> >      >      >
> >      >      >   &nbs= p;--
> >      >      >   &nbs= p;You received this message because you are subscribed to
> >      the
> >      >      Google
> >      >      >   &nbs= p;Groups "pandoc-discuss" group.
> >      >      >   &nbs= p;To unsubscribe from this group and stop receiving emails
> >      from
> >      >      it, send
> >      >      >   &nbs= p;an email to [3]pandoc-discus...@googlegroups.com.
> >      >      >   &nbs= p;To post to this group, send email to
> >      >      [4]pandoc-...= @googlegroups.com.
> >      >      >   &nbs= p;To view this discussion on the web visit
> >      >      >   &nbs= p;[3][5][3]https://grou= ps.google.
> >      com/d/msgid/pandoc-discuss/
> >      >      a86067ec-6b4a-43= 7b-
> >      >      >   &nbs= p;b2f0-3ee666209dae%[6][4]40googlegroups.com.
> >      >      >   &nbs= p;For more options, visit [4][7][5]https://groups.google.
> >      com/
> >      >      groups/opt_out.
> >      >      >
> >      >      > References
> >      >      >
> >      >      >   &nbs= p;1. [8][6]https://github.com/jgm/pandoc/issues/931
> >      >      >   &nbs= p;2. [9][7]https://www.zotero.org/support/kb/rich_text_
> >      bibliography
> >      >      >   &nbs= p;3. [10][8]http= s://groups.google.com/d/
> >      >      msgid/pandoc-dis= cuss/a86067ec-6b4a-437b-b2f0-3ee666209dae%
> >      >      [9]40googlegroups.com
> >      >      >   &nbs= p;4. [11][10]https://groups.google.com/groups/opt_out
> >      >
> >      >    --
> >      >    You received this messa= ge because you are subscribed to the
> >      Google
> >      >    Groups "pandoc-discuss"= group.
> >      >    To unsubscribe from thi= s group and stop receiving emails from
> >      it, send
> >      >    an email to pandoc-d= iscus...@googlegroups.com.
> >      >    To post to this group, = send email to
> >      pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
> >      >    To view this discussion= on the web visit
> >      >    [12][11]https://gr= oups.google.com/d/msgid/pandoc-discuss/
> >      605aad90-4967-42b9
> >      >    -8efe-0aa033c670da%[12]= 40googlegroups= .com.
> >      >    For more options, visit= [13][13]https://g= roups.google.com/
> >      groups/opt_out.
> >      >
> >      > References
> >      >
> >      >    1. [14]https://github.com/j= gm/pandoc/issues/931
> >      >    2. [15]http= s://www.zotero.org/support/kb/rich_text_bibliography
> >      >    3. javascript:/
> >      >    4. javascript:/
> >      >    5. [16]https://groups.google.com/d= /
> >      msgid/pandoc-discuss/a86067ec-6b4a-4= 37b-
> >      >    6. [17]http://40googlegroups.com/
> >      >    7. [18]https://groups.googl= e.com/groups/opt_out
> >      >    8. [19]https://github.com/j= gm/pandoc/issues/931
> >      >    9. [20]http= s://www.zotero.org/support/kb/rich_text_bibliography
> >      >   10. [21]https://groups.google.com/d/
> >      msgid/pandoc-discuss/a86067ec-6b4a-4= 37b-b2f0-3ee666209dae%
> >      40googlegroups.com
> >      >   11. [22]https://groups.google.com= /groups/opt_out
> >      >   12. [23]https://groups.google.com/d/
> >      msgid/pandoc-discuss/605aad90-4967-4= 2b9-8efe-0aa033c670da%
> >      40googlegroups.com
> >      >   13. [24]https://groups.google.com= /groups/opt_out
> >=20
> >    --
> >    You received this message because you are subscr= ibed to the Google
> >    Groups "pandoc-discuss" group.
> >    To unsubscribe from this group and stop receivin= g emails from it, send
> >    an email to pandoc-discus...@googlegr= oups.com.
> >    To post to this group, send email to pando= c-...@googlegroups.com.
> >    To view this discussion on the web visit
> >    [25]https://groups.google= .com/d/msgid/pandoc-discuss/ebae1a26-c6cb-44c4
> >    -add2-5dc57f620a4c%40googlegroups.com.
> >    For more options, visit [26]https://groups.google.co= m/groups/opt_out.
> >=20
> > References
> >=20
> >    1. https://github.com/jgm/pandoc/issues/931
> >    2. https://www.zotero.org/support/kb/rich_t= ext_
> >    3. https://groups.google.com/d/msgid/p= andoc-discuss/
> >    4. http://40googlegroups.com/
> >    5. https://groups.google.com/
> >    6. https://github.com/jgm/pandoc/issues/931
> >    7. https://www.zotero.org/suppo= rt/kb/rich_text_bibliography
> >    8. https://groups.google.com/d/
> >    9. http://40googlegroups.com/
> >   10. https://groups.google.com/groups/opt_out
> >   11. https://groups.google.com/d= /msgid/pandoc-discuss/605aad90-4967-42b9
> >   12. http://40googlegroups.com/
> >   13. https://groups.google.com/groups/opt_out
> >   14. https://github.com/jgm/pandoc/issues/931
> >   15. https://www.zotero.org/support/kb= /rich_text_bibliography
> >   16. https://groups.google.com/= d/msgid/pandoc-discuss/a86067ec-6b4a-437b-
> >   17. http://40googlegroups.com/
> >   18. https://groups.google.com/groups/opt_out
> >   19. https://github.com/jgm/pandoc/issues/931
> >   20. https://www.zotero.org/support/kb= /rich_text_bibliography
> >   21. https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-= 6b4a-437b-b2f0-3ee666209dae%40googlegroups.com
> >   22. https://groups.google.com/groups/opt_out
> >   23. https://groups.google.com/d/msgid/pandoc-discuss/605aad90-= 4967-42b9-8efe-0aa033c670da%40googlegroups.com
> >   24. https://groups.google.com/groups/opt_out
> >   25. https://groups.google.com/d/msgid/pandoc-discuss/ebae1a26-= c6cb-44c4-add2-5dc57f620a4c%40googlegroups.com
> >   26. https://groups.google.com/groups/opt_out
>=20
> --=20
> 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...@googlegroups.com.
> To post to this group, send email to pandoc-...@googlegroups= .com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-d= iscuss/20130929012541.GC45785%40Johns-MacBook-Pro.local.
> For more options, visit https://groups.google.com/groups/opt_out<= /a>.

--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail 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/fd944048-488f-4d68= -a27e-5db0f5d41723%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
------=_Part_1393_28682036.1380454765056--