* Decoupling citeproc and highlighting-kate from pandoc @ 2013-08-25 19:15 John MacFarlane [not found] ` <20130825191545.GA80583-9Rnp8PDaXcZ2EAH53EmH34tHsfhOvSUSZkel5v8DVj8@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-08-25 19:15 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Pandoc currently includes built-in support for citation processing (using citeproc-hs) and syntax highlighting (using highlighting-kate). This is not ideal, since many users don't use either of these features, and few, I would imagine, use both. Both citeproc-hs and highlighting-kate are big libraries, which bloat the pandoc binary. So I am moving towards decoupling these components from core pandoc. As noted earlier, I've added a --filter flag to pandoc, which makes it easy to run JSON filters. So, to process citations, you'll now do pandoc --filter pandoc-citeproc input.txt and specify the bibliography and csl file in the document's metadata. Similarly, to highlight source code using highlighting kate, you'll do pandoc --filter pandoc-highlight input.txt (Highlighting style will be specified in the metadata rather than on the command line.) Both pandoc-citeproc and pandoc-highlight will be optional add-ons. The packages that provide them will also provide Haskell libraries for processing citations and doing code highlighting in pandoc documents, for those who use pandoc as a library. I have already made the citations change; I have not yet made the highlighting change, and could still back down if there is a lot of protest. The main drawback I can see is that performance will be a *little* worse -- but the difference is pretty negligible. The command line will also be a bit longer for those who use highlighting. But I think this change makes a lot of sense. It will also make it easier for users to use their own highlighting libraries; they just need to write a simple filter. Another nice feature I'm adding is inline references. Instead of putting your bibliographic references in an external file, you can now include them directly in the document, in a YAML metadata block. (This can occur at the end of the document if you like.) This makes the document more self-contained. The YAML format is basically a YAML representation of the JSON format used by citeproc-js. Here's an example: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Some claim [fenner12a]. --- csl: tests/mhra.csl references: - id: fenner12a title: One-click science marketing author: family: Fenner given: [Martin] container-title: Nature Materials volume: 11 url: 'http://dx.doi.org/10.1038/nmat3283' doi: '10.1038/nmat3283' issue: 4 publisher: Nature Publishing Group page: 261-263 type: article-journal issued: year: 2012 month: 3 ... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Of course, you can also store the YAML bibliography in a separate file, and provide it to pandoc on the command line with the main file. The pandoc-citations package will include an executable, biblio2yaml, that translates from common bibliographic formats (e.g. bibtex) into this YAML format. I'm pretty excited about these changes, which I would like to include in the 1.12 release. The release has been held up waiting for Andrea to release citeproc-hs. I haven't heard from Andrea in a long time, so I now have a contingency plan. I will simply include the code from citeproc-hs, including a couple of bug fixes, in the pandoc-citations package. When Andrea comes back, as I hope he does, I'll remove this and depend once more on citeproc-hs. But at least this will let us go ahead with the release. If you want to play with the new pandoc-citations stuff, it's on github: http://github.com/jgm/pandoc-citations It assumes you've installed a very recent dev version of pandoc and pandoc-types. John ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130825191545.GA80583-9Rnp8PDaXcZ2EAH53EmH34tHsfhOvSUSZkel5v8DVj8@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130825191545.GA80583-9Rnp8PDaXcZ2EAH53EmH34tHsfhOvSUSZkel5v8DVj8@public.gmane.org> @ 2013-08-26 15:23 ` Joseph Reagle [not found] ` <521B730A.50901-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> 2013-08-27 13:18 ` Nick Bart ` (5 subsequent siblings) 6 siblings, 1 reply; 283+ messages in thread From: Joseph Reagle @ 2013-08-26 15:23 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: John MacFarlane On 08/25/2013 03:15 PM, John MacFarlane wrote: > and specify the bibliography and csl file in the document's metadata. Does using the filter require this? Is it because one can't pass arguments to the filter? I often already specify CSL in the metadata using my wrapper/build utilities so that's fine by me. For instance: ~~~~ Title: DRAFT: The Obligation to Know Author: Joseph Reagle Date: 20130601 md_opts: --toc --style-csl apa --british-punctuation ~~~~ However, I am concerned with having the bibfile in the metadata because I generate those dynamically and temporarily to deal with the problem of my larger bibtex file (~3MB) and pandoc/hs-citeproc's slow processing. (I extract the keys from the markdown file then use that to generate a specific and per-document bibtex file.) ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <521B730A.50901-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <521B730A.50901-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> @ 2013-08-27 12:16 ` BP Jonsson 0 siblings, 0 replies; 283+ messages in thread From: BP Jonsson @ 2013-08-27 12:16 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2735 bytes --] I've been meaning to start using the citation feature for quite some time and this change might actually get me going. When working on other people's documents as I do quite a bit I usually get a ready-formatted bibliography section so then the need hardly arises. As for using either syntax highlighting or citations but not both it kindof applies in that I hardly would use both with the same document, but I might well use them both at different times. Anyway I'm not opposed to the change. Like Joseph I'm wondering whether it is or will be possible to pass arguments to filters? /bpj Den måndagen den 26:e augusti 2013 skrev Joseph Reagle: > On 08/25/2013 03:15 PM, John MacFarlane wrote: > > and specify the bibliography and csl file in the document's metadata. > > Does using the filter require this? Is it because one can't pass > arguments to the filter? > > I often already specify CSL in the metadata using my wrapper/build > utilities so that's fine by me. For instance: > > ~~~~ > > Title: DRAFT: The Obligation to Know > Author: Joseph Reagle > Date: 20130601 > md_opts: --toc --style-csl apa --british-punctuation > > ~~~~ > > However, I am concerned with having the bibfile in the metadata because > I generate those dynamically and temporarily to deal with the problem of > my larger bibtex file (~3MB) and pandoc/hs-citeproc's slow processing. > (I extract the keys from the markdown file then use that to generate a > specific and per-document bibtex file.) > > -- > 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:;>. > To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:;> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/pandoc-discuss/521B730A.50901%40reagle.org > . > For more options, visit https://groups.google.com/groups/opt_out. > -- /BP -- 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/CAFC_yuR_8EKbhs8LwzwzNXANmS6%3Dxs7m3JtFR1vYXhmqbuwi3Q%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3704 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130825191545.GA80583-9Rnp8PDaXcZ2EAH53EmH34tHsfhOvSUSZkel5v8DVj8@public.gmane.org> 2013-08-26 15:23 ` Joseph Reagle @ 2013-08-27 13:18 ` Nick Bart [not found] ` <d479b8cf-95f2-4182-bc16-8dca53420eb8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-08-30 15:41 ` Bruce D'Arcus ` (4 subsequent siblings) 6 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-08-27 13:18 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 958 bytes --] On Sunday, August 25, 2013 9:15:45 PM UTC+2, fiddlosopher wrote: > > > The pandoc-citations package will include an executable, biblio2yaml, > that translates from common bibliographic formats (e.g. bibtex) into > this YAML format. > "biblio2yaml" sounds exciting. Could it be used as a filter, too, converting external biblio databases at runtime, and replacing bibutils? -- 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/d479b8cf-95f2-4182-bc16-8dca53420eb8%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1373 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <d479b8cf-95f2-4182-bc16-8dca53420eb8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <d479b8cf-95f2-4182-bc16-8dca53420eb8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-08-27 13:53 ` John MacFarlane [not found] ` <20130827135349.GB4394-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-08-27 13:53 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ Nick Bart [Aug 27 13 06:18 ]: > On Sunday, August 25, 2013 9:15:45 PM UTC+2, fiddlosopher wrote: > > The pandoc-citations package will include an executable, > biblio2yaml, > that translates from common bibliographic formats (e.g. bibtex) into > this YAML format. > > "biblio2yaml" sounds exciting. Could it be used as a filter, too, > converting external biblio databases at runtime, and replacing > bibutils? Yes, I've set it up so it will work as a pipe -- I'm not sure if that's what you meant. Note that it uses the bibutils library behind the scenes. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130827135349.GB4394-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130827135349.GB4394-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-08-27 15:46 ` John MacFarlane 2013-08-30 15:24 ` Nick Bart 1 sibling, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-08-27 15:46 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ John MacFarlane [Aug 27 13 06:53 ]: > +++ Nick Bart [Aug 27 13 06:18 ]: > > On Sunday, August 25, 2013 9:15:45 PM UTC+2, fiddlosopher wrote: > > > > The pandoc-citations package will include an executable, > > biblio2yaml, > > that translates from common bibliographic formats (e.g. bibtex) into > > this YAML format. > > > > "biblio2yaml" sounds exciting. Could it be used as a filter, too, > > converting external biblio databases at runtime, and replacing > > bibutils? > > Yes, I've set it up so it will work as a pipe -- I'm not sure if > that's what you meant. > Note that it uses the bibutils library behind the scenes. Note that you can also just include bibliography: mybib.bib in the metadata, and it will grab the bibliography from a bibtex or biblatex file. (Other formats can also be used.) ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130827135349.GB4394-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-08-27 15:46 ` John MacFarlane @ 2013-08-30 15:24 ` Nick Bart 1 sibling, 0 replies; 283+ messages in thread From: Nick Bart @ 2013-08-30 15:24 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1680 bytes --] That's what I wanted to know, thank you. If bibutils is used, I'm curious how the conversion step from MODS to "YAML representation of CSL variables in the JSON format" is done? If the existing citeproc-hs routines are used, please note that these still contain a number of bugs, and I’d be very happy if these could be ironed out at this opportunity. On Tuesday, 27 August 2013 16:53:49 UTC+3, fiddlosopher wrote: > > +++ Nick Bart [Aug 27 13 06:18 ]: > > On Sunday, August 25, 2013 9:15:45 PM UTC+2, fiddlosopher wrote: > > > > The pandoc-citations package will include an executable, > > biblio2yaml, > > that translates from common bibliographic formats (e.g. bibtex) > into > > this YAML format. > > > > "biblio2yaml" sounds exciting. Could it be used as a filter, too, > > converting external biblio databases at runtime, and replacing > > bibutils? > > Yes, I've set it up so it will work as a pipe -- I'm not sure if > that's what you meant. > Note that it uses the bibutils library behind the scenes. > > -- 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/049d081f-6a1a-479b-9b44-c36c8967cf6c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2204 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130825191545.GA80583-9Rnp8PDaXcZ2EAH53EmH34tHsfhOvSUSZkel5v8DVj8@public.gmane.org> 2013-08-26 15:23 ` Joseph Reagle 2013-08-27 13:18 ` Nick Bart @ 2013-08-30 15:41 ` Bruce D'Arcus [not found] ` <28ef090f-b33e-4fd1-91cb-5da1eadf386b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-09 20:42 ` Joseph Reagle ` (3 subsequent siblings) 6 siblings, 1 reply; 283+ messages in thread From: Bruce D'Arcus @ 2013-08-30 15:41 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 4649 bytes --] Sounds good. One minor thing: we put together that CSL JSON input schema fairly informally, and I've long thought we ought to look again at a few details (like, say, how dates are represented). Just to say it may not be 100% stable. On Sunday, August 25, 2013 3:15:45 PM UTC-4, fiddlosopher wrote: > > Pandoc currently includes built-in support for citation processing > (using citeproc-hs) and syntax highlighting (using highlighting-kate). > This is not ideal, since many users don't use either of these features, > and few, I would imagine, use both. Both citeproc-hs and > highlighting-kate are big libraries, which bloat the pandoc binary. > > So I am moving towards decoupling these components from core pandoc. > As noted earlier, I've added a --filter flag to pandoc, which makes it > easy to run JSON filters. So, to process citations, you'll now do > > pandoc --filter pandoc-citeproc input.txt > > and specify the bibliography and csl file in the document's metadata. > Similarly, to highlight source code using highlighting kate, you'll do > > pandoc --filter pandoc-highlight input.txt > > (Highlighting style will be specified in the metadata rather than on > the command line.) Both pandoc-citeproc and pandoc-highlight will be > optional add-ons. The packages that provide them will also provide > Haskell libraries for processing citations and doing code highlighting > in pandoc documents, for those who use pandoc as a library. > > I have already made the citations change; I have not yet made the > highlighting change, and could still back down if there is a lot of > protest. The main drawback I can see is that performance will be a > *little* worse -- but the difference is pretty negligible. The > command line will also be a bit longer for those who use highlighting. > But I think this change makes a lot of sense. It will also make it > easier for users to use their own highlighting libraries; they just need > to write a simple filter. > > Another nice feature I'm adding is inline references. Instead of > putting your bibliographic references in an external file, you can > now include them directly in the document, in a YAML metadata block. > (This can occur at the end of the document if you like.) > This makes the document more self-contained. The YAML format is > basically a YAML representation of the JSON format used by citeproc-js. > Here's an example: > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Some claim [fenner12a]. > > --- > csl: tests/mhra.csl > references: > - id: fenner12a > title: One-click science marketing > author: > family: Fenner > given: [Martin] > container-title: Nature Materials > volume: 11 > url: 'http://dx.doi.org/10.1038/nmat3283' > doi: '10.1038/nmat3283' > issue: 4 > publisher: Nature Publishing Group > page: 261-263 > type: article-journal > issued: > year: 2012 > month: 3 > ... > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Of course, you can also store the YAML bibliography in a separate file, > and provide it to pandoc on the command line with the main file. > > The pandoc-citations package will include an executable, biblio2yaml, > that translates from common bibliographic formats (e.g. bibtex) into > this YAML format. > > I'm pretty excited about these changes, which I would like to include > in the 1.12 release. The release has been held up waiting for Andrea > to release citeproc-hs. I haven't heard from Andrea in a long time, so > I now have a contingency plan. I will simply include the code from > citeproc-hs, including a couple of bug fixes, in the pandoc-citations > package. When Andrea comes back, as I hope he does, I'll remove this > and depend once more on citeproc-hs. But at least this will let us > go ahead with the release. > > If you want to play with the new pandoc-citations stuff, it's on github: > http://github.com/jgm/pandoc-citations > It assumes you've installed a very recent dev version of pandoc and > pandoc-types. > > John > > -- 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/28ef090f-b33e-4fd1-91cb-5da1eadf386b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 5621 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <28ef090f-b33e-4fd1-91cb-5da1eadf386b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <28ef090f-b33e-4fd1-91cb-5da1eadf386b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-08-30 16:56 ` Rintze Zelle 2013-08-30 19:36 ` Joseph Reagle 1 sibling, 0 replies; 283+ messages in thread From: Rintze Zelle @ 2013-08-30 16:56 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1033 bytes --] (I commented at http://blog.martinfenner.org/2013/08/08/csl-is-more-than-citation-styles/ about the current state of Citeproc JSON) On Friday, August 30, 2013 11:41:13 AM UTC-4, Bruce D'Arcus wrote: > > Sounds good. > > One minor thing: we put together that CSL JSON input schema fairly > informally, and I've long thought we ought to look again at a few details > (like, say, how dates are represented). > > Just to say it may not be 100% stable. > -- 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/aa3f83b9-9e91-4cc0-ae03-e872dda16d9d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1574 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <28ef090f-b33e-4fd1-91cb-5da1eadf386b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-08-30 16:56 ` Rintze Zelle @ 2013-08-30 19:36 ` Joseph Reagle [not found] ` <5220F425.5050002-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Joseph Reagle @ 2013-08-30 19:36 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: John MacFarlane On 08/30/2013 11:41 AM, Bruce D'Arcus wrote: > One minor thing: we put together that CSL JSON input schema fairly > informally, and I've long thought we ought to look again at a few details > (like, say, how dates are represented). On this point, as I consider moving from mostly biblatex/latex to mostly CSL/HTML I've been looking at some of the mappings. My data is kept in mindmaps and can be output to biblatex, bibtex, or Wikipedia. If I add a YAML output (to feed directly into pandoc so as to avoid bibutils, its bugs, and too many conversions) it also might be worthwhile moving to that schema as well. I've briefly looked more closely at which fields are making it into pandoc and comparing the input and output of `biblio2yaml`. 1. It appears the biblatex field 'original-date' is disappearing (even though there is a CSL original-date). 2. In biblatex we have a 'series' field. It appears the equivalent in CSL is 'collection-title'? This seems to go missing as well. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <5220F425.5050002-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <5220F425.5050002-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> @ 2013-08-30 20:16 ` Jorge Peña 2013-08-31 14:19 ` Nick Bart 1 sibling, 0 replies; 283+ messages in thread From: Jorge Peña @ 2013-08-30 20:16 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: John MacFarlane [-- Attachment #1: Type: text/plain, Size: 2610 bytes --] I'm not entirely sure I completely understand the proposal, but I think it's relevant to me and my use case, which might help one of you to come to a conclusion. I am one such user. I don't use either the citation or the built-in highlighting features. What I do instead is that I created an AST transformer that collects CodeBlocks and runs the contents through Pygments (backed by some caching to speed things up a bit) and embeds the resulting html in a RawBlock; I'm not sure if there's a better way. When you say that you'd add a filter for highlighting, for example, would that basically be an AST transformer like mine, except using highlighting-kate? And so the highlighting would be decoupled in that manner, where users can run the filter/transformer if they want to (rather than by default, hence no longer requiring highlighting-kate as a dependency)? If so, I take it my kind of setup will not be affected? On Friday, August 30, 2013 12:36:05 PM UTC-7, Joseph wrote: > > On 08/30/2013 11:41 AM, Bruce D'Arcus wrote: > > One minor thing: we put together that CSL JSON input schema fairly > > informally, and I've long thought we ought to look again at a few > details > > (like, say, how dates are represented). > > On this point, as I consider moving from mostly biblatex/latex to mostly > CSL/HTML I've been looking at some of the mappings. My data is kept in > mindmaps and can be output to biblatex, bibtex, or Wikipedia. If I add a > YAML output (to feed directly into pandoc so as to avoid bibutils, its > bugs, and too many conversions) it also might be worthwhile moving to > that schema as well. I've briefly looked more closely at which fields > are making it into pandoc and comparing the input and output of > `biblio2yaml`. > > 1. It appears the biblatex field 'original-date' is disappearing (even > though there is a CSL original-date). > 2. In biblatex we have a 'series' field. It appears the equivalent in > CSL is 'collection-title'? This seems to go missing as well. > -- 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/242ec07d-4cfa-4599-b324-b2ad4e367fa6%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3086 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <5220F425.5050002-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> 2013-08-30 20:16 ` Jorge Peña @ 2013-08-31 14:19 ` Nick Bart [not found] ` <b00f2f74-ae3a-4a4b-9f3e-a6ce2a5e5e04-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-08-31 14:19 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: John MacFarlane [-- Attachment #1: Type: text/plain, Size: 1651 bytes --] On Friday, 30 August 2013 22:36:05 UTC+3, Joseph wrote: > > 1. It appears the biblatex field 'original-date' is disappearing (even > though there is a CSL original-date). > 2. In biblatex we have a 'series' field. It appears the equivalent in > CSL is 'collection-title'? This seems to go missing as well. > So it would seem that biblio2yaml indeed uses the existing buggy citeproc-hs routines for converting MODS to CSL. Both bugs you describe have been reported at http://code.google.com/p/citeproc-hs/issues a long time ago. Note that proper mapping of the biblatex series field (to CSL 'collection-title', that's correct) depends on proper handling of the whole title/booktitle/maintitle/series complex. I proposed a solution of how to implement this in MODS, and both bibutils and citeproc-hs have begun implementing this, but there have been no attempts at fixing the remaining bugs for a long time. Again, I'd be very happy if a fresh attempt could be made to convince the citeproc-hs and bibutils maintainers that these really need to be fixed. -- 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/b00f2f74-ae3a-4a4b-9f3e-a6ce2a5e5e04%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2080 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <b00f2f74-ae3a-4a4b-9f3e-a6ce2a5e5e04-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <b00f2f74-ae3a-4a4b-9f3e-a6ce2a5e5e04-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-08-31 15:23 ` John MacFarlane [not found] ` <20130831152309.GA39551-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-08-31 15:23 UTC (permalink / raw) To: Nick Bart; +Cc: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ Nick Bart [Aug 31 13 07:19 ]: > On Friday, 30 August 2013 22:36:05 UTC+3, Joseph wrote: > > 1. It appears the biblatex field 'original-date' is disappearing > (even > though there is a CSL original-date). > 2. In biblatex we have a 'series' field. It appears the equivalent > in > CSL is 'collection-title'? This seems to go missing as well. > > So it would seem that biblio2yaml indeed uses the existing buggy > citeproc-hs routines for converting MODS to CSL. Both bugs you describe > have been reported at http://code.google.com/p/citeproc-hs/issues a > long time ago. > Note that proper mapping of the biblatex series field (to CSL > 'collection-title', that's correct) depends on proper handling of the > whole title/booktitle/maintitle/series complex. I proposed a solution > of how to implement this in MODS, and both bibutils and citeproc-hs > have begun implementing this, but there have been no attempts at fixing > the remaining bugs for a long time. > Again, I'd be very happy if a fresh attempt could be made to convince > the citeproc-hs and bibutils maintainers that these really need to be > fixed. I have not heard from Andrea Rossato in months, which is one reason I've taken the citeproc-hs code as the basis for a new package, pandoc-citeproc, which I can modify. I hope that Andrea will come back to the project, in which case I can depend on hs-bibutils again. In any case, I can try to fix the bugs, but my time is limited. Probably best to get the bibutils side working first. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130831152309.GA39551-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130831152309.GA39551-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-08-31 18:25 ` Nick Bart [not found] ` <b423b3ba-5a81-4d16-aa32-83131b6c441b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-08-31 18:25 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: Nick Bart [-- Attachment #1: Type: text/plain, Size: 2463 bytes --] On Saturday, August 31, 2013 6:23:09 PM UTC+3, fiddlosopher wrote: > > I have not heard from Andrea Rossato in months, which is one reason > I've taken the citeproc-hs code as the basis for a new package, > pandoc-citeproc, which I can modify. I hope that Andrea will come > back to the project, in which case I can depend on hs-bibutils again. > In any case, I can try to fix the bugs, but my time is limited. > Probably best to get the bibutils side working first. > Well, the bibutils author has not reacted for a long time either. Maybe it would help if you, the pandoc author, underlined this message on bibutils issues on the bibutils forum. To clarify what's still buggy: For mapping title/booktitle/maintitle/series to MODS, nested <relatedItem type="host"> elements are used. The bibutils author has opted for a rigid system that always has three levels (top-level element plus two nested <relatedItem type="host"> elements) for "book", "collection", etc. entry types and four levels for "inbook", "incollection", etc. entry types. Currently, this works ok for some types, but levels are missing, or biblatex fields end up on the wrong level for others. (See http://sourceforge.net/p/bibutils/discussion/general/thread/d5909c51/). IMHO, the fix would be easy, it's just that the schema that has been introduced has to be used consistently. In addition, MODS offers nice <genre> elements to further specify levels. bibutils, however, only uses <genre authority="marcgt">book</genre> or <genre authority="marcgt">collection</genre> one the first, resp. second level. To avoid errors, it would probably be better to use <genre authority="marcgt">multivolume monograph</genre> and <genre authority="marcgt">series</genre> on the appropriate levels as well, but bibutils currently does not. There hasn't even been any reaction when I suggested this. -- 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/b423b3ba-5a81-4d16-aa32-83131b6c441b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3411 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <b423b3ba-5a81-4d16-aa32-83131b6c441b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <b423b3ba-5a81-4d16-aa32-83131b6c441b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-01 4:07 ` Nick Bart [not found] ` <03d50535-8cba-4844-958d-2a8fc1ee77b1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-01 4:07 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: Nick Bart [-- Attachment #1: Type: text/plain, Size: 959 bytes --] What I'm meaning to say is that since it's clear what is required, the citeproc-hs and biblio2yaml bugs could easily be fixed even before bibutils is ready. For some entry types, MODS generated by bibutils is ok, but citeproc-hs doesn't do the right thing, e.g., it does not set "collection-title" even if a MODS element corresponding to the biblatex series field is present. -- 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/03d50535-8cba-4844-958d-2a8fc1ee77b1%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1218 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <03d50535-8cba-4844-958d-2a8fc1ee77b1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <03d50535-8cba-4844-958d-2a8fc1ee77b1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-02 15:57 ` John MacFarlane [not found] ` <20130902155711.GB31156-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-02 15:57 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I'm open to fixing these bugs. The code base is a bit forbidding, but I'm starting to understand it better. +++ Nick Bart [Aug 31 13 21:07 ]: > What I'm meaning to say is that since it's clear what is required, the > citeproc-hs and biblio2yaml bugs could easily be fixed even before > bibutils is ready. For some entry types, MODS generated by bibutils is > ok, but citeproc-hs doesn't do the right thing, e.g., it does not set > "collection-title" even if a MODS element corresponding to the biblatex > series field is present. > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/03d50535-8cba-4844- > 958d-2a8fc1ee77b1%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/03d50535-8cba-4844-958d-2a8fc1ee77b1%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130902155711.GB31156-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130902155711.GB31156-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-02 18:43 ` Matthias Hüning 2013-09-03 7:42 ` Nick Bart 1 sibling, 0 replies; 283+ messages in thread From: Matthias Hüning @ 2013-09-02 18:43 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 720 bytes --] Am Montag, 2. September 2013 17:57:11 UTC+2 schrieb fiddlosopher: > > I'm open to fixing these bugs. > That would be great!! Matthias -- 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/10c1dd20-c44b-46b3-8fea-89406bbb941c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1143 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130902155711.GB31156-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-09-02 18:43 ` Matthias Hüning @ 2013-09-03 7:42 ` Nick Bart [not found] ` <4d09f924-b9ca-4f29-8c64-de355407a90a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-03 7:42 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2697 bytes --] On Monday, 2 September 2013 17:57:11 UTC+2, fiddlosopher wrote: > > I'm open to fixing these bugs. The code base is a bit forbidding, but > I'm starting to understand it better. > Brilliant. This is much appreciated. Here's my summary of how title / (booktitle) / maintitle / series should be mapped to MODS and then to CSL variables: book, collection, proceedings, etc.: biblatex MODS CSL --------- --------- ------------------------------------ title top level if maintitle non-empty: volume-title if maintitle empty: title maintitle level +1 if non-empty: title series level +2 collection-title inbook etc.: biblatex MODS CSL --------- --------- ------------------------------------ title top level title booktitle level +1 if maintitle non-empty: volume-title if maintitle empty: container-title maintitle level +2 if non-empty: container-title series level +3 collection-title Notes: - MODS "levels" refer to nested <relatedItem type="host"> elements - "maintitle", if non-empty, will be mapped to the CSL variables "title" (for books etc.) or "container-title" (for inbook etc.) and will be included in the output by all current CSL styles. - volume-title (i.e., title of a single volume within a multi-volume monograph) has been proposed (https://github.com/ajlyon/zotero-bits/issues/54) but is not an official CSL variable yet. Still, I see no harm in starting to implement it now, even if currently only customized CSL styles will be able to use it. Standard CSL styles will not include this information in their output (yet), but the title of the whole multivolume monograph will be (plus volume number, if provided), so while not ideal, this is perfectly acceptable; much better in any case than to provide nothing but the the single-volume title. As to other citeproc-hs bugs identified so far, I think most are described rather fully on https://github.com/jgm/pandoc/issues. If you need any further information, or assistance that I might be able provide, please let me know. -- 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/4d09f924-b9ca-4f29-8c64-de355407a90a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3757 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <4d09f924-b9ca-4f29-8c64-de355407a90a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <4d09f924-b9ca-4f29-8c64-de355407a90a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-03 11:54 ` Joseph Reagle [not found] ` <5225CDE2.2090109-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> 2013-09-03 14:54 ` Bruce D'Arcus 2013-09-03 15:20 ` John MacFarlane 2 siblings, 1 reply; 283+ messages in thread From: Joseph Reagle @ 2013-09-03 11:54 UTC (permalink / raw) To: Nick Bart; +Cc: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw On 09/03/2013 03:42 AM, Nick Bart wrote: > Here's my summary of how title / (booktitle) / maintitle / series should be > mapped to MODS and then to CSL variables: I've been trying to wrap my head around biblatex <-> CSL/yaml as I hope to make the transition myself. Sections 2.1 and 2.2 of the biblatex documentation have a really nice description of the entry types and fields (i.e., for each type, what are the required and optional/expected fields). Does anyone know if something similar exists for CSL? The CSL JSON schema [2] is syntactical only. The best sense of this that I've gotten is from a zotero doc. [1]: http://mirrors.rit.edu/CTAN/macros/latex/contrib/biblatex/doc/biblatex.pdf [2]: https://github.com/citation-style-language/schema/blob/master/csl-data.json [3]: http://aurimasv.github.io/z2csl/typeMap.xml ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <5225CDE2.2090109-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <5225CDE2.2090109-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> @ 2013-09-03 17:36 ` Nick Bart 0 siblings, 0 replies; 283+ messages in thread From: Nick Bart @ 2013-09-03 17:36 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: Nick Bart [-- Attachment #1: Type: text/plain, Size: 1665 bytes --] http://citationstyles.org/downloads/specification.html#appendix-iv-variables contains a list of all CSL variables, each with a brief explanation. On Tuesday, 3 September 2013 13:54:10 UTC+2, Joseph wrote: > > On 09/03/2013 03:42 AM, Nick Bart wrote: > > Here's my summary of how title / (booktitle) / maintitle / series should > be > > mapped to MODS and then to CSL variables: > > I've been trying to wrap my head around biblatex <-> CSL/yaml as I hope > to make the transition myself. Sections 2.1 and 2.2 of the biblatex > documentation have a really nice description of the entry types and > fields (i.e., for each type, what are the required and optional/expected > fields). Does anyone know if something similar exists for CSL? The CSL > JSON schema [2] is syntactical only. The best sense of this that I've > gotten is from a zotero doc. > > [1]: > http://mirrors.rit.edu/CTAN/macros/latex/contrib/biblatex/doc/biblatex.pdf > [2]: > https://github.com/citation-style-language/schema/blob/master/csl-data.json > [3]: http://aurimasv.github.io/z2csl/typeMap.xml > -- 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/ff6335de-a8cd-44e9-88e0-d95167fc8c9e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2414 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <4d09f924-b9ca-4f29-8c64-de355407a90a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-03 11:54 ` Joseph Reagle @ 2013-09-03 14:54 ` Bruce D'Arcus [not found] ` <CAF-FPGNwUX9rSnJoBFbTp-od3nmJ6jo-i_=xh+DL1KEOL60RKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2013-09-03 15:20 ` John MacFarlane 2 siblings, 1 reply; 283+ messages in thread From: Bruce D'Arcus @ 2013-09-03 14:54 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I don't have time to think again about the details, but note: that proposal for a "volume-title" variable is for zotero; not CSL. The variables in CSL tend to be a little more abstract. Bruce On Tue, Sep 3, 2013 at 3:42 AM, Nick Bart <nickbart1980-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > On Monday, 2 September 2013 17:57:11 UTC+2, fiddlosopher wrote: >> >> I'm open to fixing these bugs. The code base is a bit forbidding, but >> I'm starting to understand it better. > > > Brilliant. This is much appreciated. > > Here's my summary of how title / (booktitle) / maintitle / series should be > mapped to MODS and then to CSL variables: > > book, collection, proceedings, etc.: > > biblatex MODS CSL > --------- --------- ------------------------------------ > title top level if maintitle non-empty: volume-title > if maintitle empty: title > maintitle level +1 if non-empty: title > series level +2 collection-title > > > inbook etc.: > > biblatex MODS CSL > --------- --------- ------------------------------------ > title top level title > booktitle level +1 if maintitle non-empty: volume-title > if maintitle empty: container-title > maintitle level +2 if non-empty: container-title > series level +3 collection-title > > Notes: > > - MODS "levels" refer to nested <relatedItem type="host"> elements > > - "maintitle", if non-empty, will be mapped to the CSL variables "title" > (for books etc.) or "container-title" (for inbook etc.) and will be included > in the output by all current CSL styles. > > - volume-title (i.e., title of a single volume within a multi-volume > monograph) has been proposed > (https://github.com/ajlyon/zotero-bits/issues/54) but is not an official CSL > variable yet. Still, I see no harm in starting to implement it now, even if > currently only customized CSL styles will be able to use it. Standard CSL > styles will not include this information in their output (yet), but the > title of the whole multivolume monograph will be (plus volume number, if > provided), so while not ideal, this is perfectly acceptable; much better in > any case than to provide nothing but the the single-volume title. > > As to other citeproc-hs bugs identified so far, I think most are described > rather fully on https://github.com/jgm/pandoc/issues. > > If you need any further information, or assistance that I might be able > provide, please let me know. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "pandoc-discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/pandoc-discuss/-SajbqoPX8k/unsubscribe. > To unsubscribe from this group and all its topics, 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/4d09f924-b9ca-4f29-8c64-de355407a90a%40googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <CAF-FPGNwUX9rSnJoBFbTp-od3nmJ6jo-i_=xh+DL1KEOL60RKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <CAF-FPGNwUX9rSnJoBFbTp-od3nmJ6jo-i_=xh+DL1KEOL60RKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2013-09-03 15:46 ` Nick Bart [not found] ` <9703dae4-9816-4508-a1cd-8272c0c6ea0c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-03 15:46 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1468 bytes --] On Tuesday, 3 September 2013 16:54:01 UTC+2, Bruce D'Arcus wrote: > > I don't have time to think again about the details, but note: that > proposal for a "volume-title" variable is for zotero; not CSL. The > variables in CSL tend to be a little more abstract. > > Bruce > The proposal in https://github.com/ajlyon/zotero-bits/issues/54 is both for a new Zotero field "Volume Title" *and* a new CSL variable "volume-title". "Proposal: add a field "Volume Title" to Book and Book Section, map it to new CSL variable "volume-title"" I think such a variable is definitely necessary: CMoS requires the distinction between single volumes and multivolume monographs (and series, which is again something different). biblatex has it, MODS has it … and CSL should introduce it, too. How exactly are decisions on introduction of new CSL variables being made? -- 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/9703dae4-9816-4508-a1cd-8272c0c6ea0c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1906 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <9703dae4-9816-4508-a1cd-8272c0c6ea0c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <9703dae4-9816-4508-a1cd-8272c0c6ea0c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-03 15:56 ` Bruce D'Arcus [not found] ` <CAF-FPGOjxF=8vDBOtL3RY5dRO-zetra3EXvddNgKZMf8tiEB-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Bruce D'Arcus @ 2013-09-03 15:56 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Decisions: I'd call it a loose consensus process. So someone proposes something (ideally on the github issue tracker, maybe with a note on the ML), and if sufficient implementers support it, without significant objection, then it gets adopted. Otherwise, it doesn't. But admittedly, variables are an easier conversation than other types of proposals. On the substance, that may well be the solution, except that it needs to fit logically into the current title, container-title, collection-title logic, which is fairly abstract. As I said, I haven't thought about the details in awhile. On Tue, Sep 3, 2013 at 11:46 AM, Nick Bart <nickbart1980-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > On Tuesday, 3 September 2013 16:54:01 UTC+2, Bruce D'Arcus wrote: >> >> I don't have time to think again about the details, but note: that >> proposal for a "volume-title" variable is for zotero; not CSL. The >> variables in CSL tend to be a little more abstract. >> >> Bruce > > > The proposal in https://github.com/ajlyon/zotero-bits/issues/54 is both for > a new Zotero field "Volume Title" *and* a new CSL variable "volume-title". > > "Proposal: add a field "Volume Title" to Book and Book Section, map it to > new CSL variable "volume-title"" > > I think such a variable is definitely necessary: CMoS requires the > distinction between single volumes and multivolume monographs (and series, > which is again something different). biblatex has it, MODS has it … and CSL > should introduce it, too. > > How exactly are decisions on introduction of new CSL variables being made? > > -- > You received this message because you are subscribed to a topic in the > Google Groups "pandoc-discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/pandoc-discuss/-SajbqoPX8k/unsubscribe. > To unsubscribe from this group and all its topics, 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/9703dae4-9816-4508-a1cd-8272c0c6ea0c%40googlegroups.com. > > 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/CAF-FPGOjxF%3D8vDBOtL3RY5dRO-zetra3EXvddNgKZMf8tiEB-A%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <CAF-FPGOjxF=8vDBOtL3RY5dRO-zetra3EXvddNgKZMf8tiEB-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <CAF-FPGOjxF=8vDBOtL3RY5dRO-zetra3EXvddNgKZMf8tiEB-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2013-09-03 17:51 ` Nick Bart [not found] ` <1ae7a028-9095-4365-a874-179cabf6b702-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-03 20:44 ` Joseph Reagle 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-03 17:51 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3683 bytes --] Thank you for the clarification. So far, I took the proposal in https://github.com/ajlyon/zotero-bits/issues/54 to be directed at both Zotero and CSL developers. If I understand you correctly, however, proposals concerning CSL should rather be made on https://github.com/citation-style-language/styles/issues and the xbiblio-devel mailing list. Introducing "volume-title" has indeed not been proposed there yet. Would it help if I did this, or would you want to do it yourself? Nick On Tuesday, 3 September 2013 17:56:28 UTC+2, Bruce D'Arcus wrote: > > Decisions: I'd call it a loose consensus process. So someone proposes > something (ideally on the github issue tracker, maybe with a note on > the ML), and if sufficient implementers support it, without > significant objection, then it gets adopted. Otherwise, it doesn't. > > But admittedly, variables are an easier conversation than other types > of proposals. > > On the substance, that may well be the solution, except that it needs > to fit logically into the current title, container-title, > collection-title logic, which is fairly abstract. As I said, I haven't > thought about the details in awhile. > > On Tue, Sep 3, 2013 at 11:46 AM, Nick Bart <nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org<javascript:>> > wrote: > > On Tuesday, 3 September 2013 16:54:01 UTC+2, Bruce D'Arcus wrote: > >> > >> I don't have time to think again about the details, but note: that > >> proposal for a "volume-title" variable is for zotero; not CSL. The > >> variables in CSL tend to be a little more abstract. > >> > >> Bruce > > > > > > The proposal in https://github.com/ajlyon/zotero-bits/issues/54 is both > for > > a new Zotero field "Volume Title" *and* a new CSL variable > "volume-title". > > > > "Proposal: add a field "Volume Title" to Book and Book Section, map it > to > > new CSL variable "volume-title"" > > > > I think such a variable is definitely necessary: CMoS requires the > > distinction between single volumes and multivolume monographs (and > series, > > which is again something different). biblatex has it, MODS has it … and > CSL > > should introduce it, too. > > > > How exactly are decisions on introduction of new CSL variables being > made? > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "pandoc-discuss" group. > > To unsubscribe from this topic, visit > > https://groups.google.com/d/topic/pandoc-discuss/-SajbqoPX8k/unsubscribe. > > > To unsubscribe from this group and all its topics, send an email to > > pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/pandoc-discuss/9703dae4-9816-4508-a1cd-8272c0c6ea0c%40googlegroups.com. > > > > > 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/1ae7a028-9095-4365-a874-179cabf6b702%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 4860 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <1ae7a028-9095-4365-a874-179cabf6b702-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <1ae7a028-9095-4365-a874-179cabf6b702-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-03 17:53 ` Bruce D'Arcus 2013-09-04 18:38 ` Rintze Zelle 1 sibling, 0 replies; 283+ messages in thread From: Bruce D'Arcus @ 2013-09-03 17:53 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 4890 bytes --] Sure; feel free to propose yourself. CSL is closely connected to Zotero, but independent. On Sep 3, 2013 1:51 PM, "Nick Bart" <nickbart1980-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > Thank you for the clarification. So far, I took the proposal in > https://github.com/ajlyon/**zotero-bits/issues/54<https://github.com/ajlyon/zotero-bits/issues/54>to be directed at both Zotero and CSL developers. > > If I understand you correctly, however, proposals concerning CSL should > rather be made on https://github.com/citation-style-language/styles/issuesand the xbiblio-devel mailing list. > > Introducing "volume-title" has indeed not been proposed there yet. Would > it help if I did this, or would you want to do it yourself? > > Nick > > On Tuesday, 3 September 2013 17:56:28 UTC+2, Bruce D'Arcus wrote: >> >> Decisions: I'd call it a loose consensus process. So someone proposes >> something (ideally on the github issue tracker, maybe with a note on >> the ML), and if sufficient implementers support it, without >> significant objection, then it gets adopted. Otherwise, it doesn't. >> >> But admittedly, variables are an easier conversation than other types >> of proposals. >> >> On the substance, that may well be the solution, except that it needs >> to fit logically into the current title, container-title, >> collection-title logic, which is fairly abstract. As I said, I haven't >> thought about the details in awhile. >> >> On Tue, Sep 3, 2013 at 11:46 AM, Nick Bart <nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: >> > On Tuesday, 3 September 2013 16:54:01 UTC+2, Bruce D'Arcus wrote: >> >> >> >> I don't have time to think again about the details, but note: that >> >> proposal for a "volume-title" variable is for zotero; not CSL. The >> >> variables in CSL tend to be a little more abstract. >> >> >> >> Bruce >> > >> > >> > The proposal in https://github.com/ajlyon/**zotero-bits/issues/54<https://github.com/ajlyon/zotero-bits/issues/54>is both for >> > a new Zotero field "Volume Title" *and* a new CSL variable >> "volume-title". >> > >> > "Proposal: add a field "Volume Title" to Book and Book Section, map it >> to >> > new CSL variable "volume-title"" >> > >> > I think such a variable is definitely necessary: CMoS requires the >> > distinction between single volumes and multivolume monographs (and >> series, >> > which is again something different). biblatex has it, MODS has it … and >> CSL >> > should introduce it, too. >> > >> > How exactly are decisions on introduction of new CSL variables being >> made? >> > >> > -- >> > You received this message because you are subscribed to a topic in the >> > Google Groups "pandoc-discuss" group. >> > To unsubscribe from this topic, visit >> > https://groups.google.com/d/**topic/pandoc-discuss/-** >> SajbqoPX8k/unsubscribe<https://groups.google.com/d/topic/pandoc-discuss/-SajbqoPX8k/unsubscribe>. >> >> > To unsubscribe from this group and all its topics, 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-discuss/9703dae4-** >> 9816-4508-a1cd-8272c0c6ea0c%**40googlegroups.com<https://groups.google.com/d/msgid/pandoc-discuss/9703dae4-9816-4508-a1cd-8272c0c6ea0c%40googlegroups.com>. >> >> > >> > For more options, visit https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>. >> >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "pandoc-discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/pandoc-discuss/-SajbqoPX8k/unsubscribe. > To unsubscribe from this group and all its topics, 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/1ae7a028-9095-4365-a874-179cabf6b702%40googlegroups.com > . > 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/CAF-FPGM19xs%2B9xipOMSa3wEXgumqBE3ro841cN%3DvBe-j6fz4Pg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 6597 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <1ae7a028-9095-4365-a874-179cabf6b702-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-03 17:53 ` Bruce D'Arcus @ 2013-09-04 18:38 ` Rintze Zelle 1 sibling, 0 replies; 283+ messages in thread From: Rintze Zelle @ 2013-09-04 18:38 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2120 bytes --] On Tuesday, September 3, 2013 1:51:34 PM UTC-4, Nick Bart wrote: > Thank you for the clarification. So far, I took the proposal in > https://github.com/ajlyon/zotero-bits/issues/54 to be directed at both > Zotero and CSL developers. > > If I understand you correctly, however, proposals concerning CSL should > rather be made on https://github.com/citation-style-language/styles/issuesand the xbiblio-devel mailing list. > The xbiblio-devel mailing list is the most central location to discuss CSL development. We also use the GitHub issue trackers of the CSL project, but not everybody follows those, so it's not the best place for any decision making. If any significant proposals develop on GitHub, we usually crosspost to xbiblio-devel to inform all stakeholders and to seek consensus approval. The zotero-bits repository was started by several Zotero power users in anticipation of a long-promised redesign of Zotero's data model. We have been using it to keep track of changes to the Zotero data model that users have requested, as well as the changes that would be required in CSL to accomodate those. The data model redesign is still pretty far ahead on the horizon, and many of the proposals in the zotero-bits tracker still have to be vetted by the Zotero developers. When that time comes, any desired changes on the CSL side of things should be discussed on xbiblio-devel. (the fact that most CSL contributors are Zotero users might explain some of the apparent chaos in this communication arrangement) Rintze -- 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/e770d4d1-14ad-4f08-8c32-add1aef89279%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2781 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <CAF-FPGOjxF=8vDBOtL3RY5dRO-zetra3EXvddNgKZMf8tiEB-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2013-09-03 17:51 ` Nick Bart @ 2013-09-03 20:44 ` Joseph Reagle [not found] ` <52264A45.3000909-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Joseph Reagle @ 2013-09-03 20:44 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: Bruce D'Arcus On 09/03/2013 11:56 AM, Bruce D'Arcus wrote: > On the substance, that may well be the solution, except that it needs > to fit logically into the current title, container-title, > collection-title logic, which is fairly abstract. As I said, I haven't Nick pointed to the CSL variables in an appendix of the spec, but this is one of the things I haven't been able to figure out. What is the logic between collection vs. container? -- Regards, Joseph Reagle http://reagle.org/joseph/ (Perhaps using speech recognition, sorry for any speakos.) ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <52264A45.3000909-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <52264A45.3000909-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> @ 2013-09-03 21:07 ` Bruce D'Arcus 2013-09-04 9:02 ` Nick Bart 1 sibling, 0 replies; 283+ messages in thread From: Bruce D'Arcus @ 2013-09-03 21:07 UTC (permalink / raw) To: Joseph Reagle; +Cc: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Take a book chapter and an article: they share the characteristic that they are discrete items within a larger, autonomous, item. So an edited book is a container for the former, and a series is the collection. For the latter, the journal is the container. Now if you're paying attention, you're saying that's not so consistent, and somewhat arbitrary. Why isn't a journal issue the container, and the journal itself the collection? And, apropos Nick's point here, what about things like multi-volumed works? There's no good reason: I think I/we just designed the spec to cover as much as we could as easily as possible. It seemed sensible at the time, but am not so sure it does now. Think I need to add this to the new ticket Nick added. Bruce On Tue, Sep 3, 2013 at 4:44 PM, Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> wrote: > On 09/03/2013 11:56 AM, Bruce D'Arcus wrote: >> On the substance, that may well be the solution, except that it needs >> to fit logically into the current title, container-title, >> collection-title logic, which is fairly abstract. As I said, I haven't > > Nick pointed to the CSL variables in an appendix of the spec, but this > is one of the things I haven't been able to figure out. What is the > logic between collection vs. container? > > > -- > Regards, > Joseph Reagle http://reagle.org/joseph/ > (Perhaps using speech recognition, sorry for any speakos.) ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <52264A45.3000909-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> 2013-09-03 21:07 ` Bruce D'Arcus @ 2013-09-04 9:02 ` Nick Bart [not found] ` <83ebfc01-27a8-4f45-a3f8-3ee4378e66e2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-04 9:02 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: Bruce D'Arcus [-- Attachment #1: Type: text/plain, Size: 2753 bytes --] I think it's rather straightforward: From http://citationstyles.org/downloads/specification.html#appendix-iv-variables: *collection-title* title of the collection holding the item (e.g. the series title for a book) *container-title* title of the container holding the item (e.g. the book title for a book chapter, the journal title for a journal article) "container-title" contains the title of the whole book or the journal in types such as book chapters, articles, etc. It corresponds to biblatex's "booktitle" or "journal". According to the "volume-title" proposal, "container-title" would always hold the title of the whole book, even if it consists of multiple volumes (such as "Collected Works", "Handbook of Psychology"), and "volume-title" would hold the title of a single volume ("Tragedies", "Clinical Psychology", etc.). "collection-title" on the other hand contains the title of a book series in the sense of CMoS 6e 14.128, e.g., "Johns Hopkins Jewish Studies", "Studies in Illinois Archaeology 6", which is not italicized, and may even "be omitted to save space". 1. Gershon David Hundert, *The Jews in a Polish Private Town: The Case of Opatów in the Eighteenth Century,* Johns Hopkins Jewish Studies (Baltimore: Johns Hopkins University Press, 1992). Fowler, Melvin L. *The Cahokia Atlas: A Historical Atlas of Cahokia Archaeology.* Studies in Illinois Archaeology 6. Springfield: Illinois Historic Preservation Agency, 1989. Grenier, Roger. *Les larmes d’Ulysse.* Collection l’un et l’autre. Paris: Gallimard, 1998. Wauchope, Robert. *A Tentative Sequence of Pre-Classic Ceramics in Middle America.* Middle American Research Records, vol. 1, no. 14. New Orleans, LA: Tulane University, 1950. Since I have not been able to spot any other use, I imagine "collection-title" might just as well be renamed to "series-title". On Tuesday, September 3, 2013 10:44:53 PM UTC+2, Joseph wrote: > > Nick pointed to the CSL variables in an appendix of the spec, but this > is one of the things I haven't been able to figure out. What is the > logic between collection vs. container? > -- 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/83ebfc01-27a8-4f45-a3f8-3ee4378e66e2%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3300 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <83ebfc01-27a8-4f45-a3f8-3ee4378e66e2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <83ebfc01-27a8-4f45-a3f8-3ee4378e66e2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-04 11:00 ` Bruce D'Arcus [not found] ` <CAF-FPGOb+h48xYH9S04gNi-hZ3m7Hph9gdWLzBFcZHc6-qoUbw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Bruce D'Arcus @ 2013-09-04 11:00 UTC (permalink / raw) To: Nick Bart; +Cc: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3088 bytes --] Yeah, I'm saying that a journal is (should be) really a collection, as is a book series, a legal code, etc. But let's move this to the CSL venues. On Sep 4, 2013 5:02 AM, "Nick Bart" <nickbart1980-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > I think it's rather straightforward: From > http://citationstyles.org/downloads/specification.html#appendix-iv-variables > : > > *collection-title* > title of the collection holding the item (e.g. the series title for a book) > *container-title* > title of the container holding the item (e.g. the book title for a book > chapter, the journal title for a journal article) > > "container-title" contains the title of the whole book or the journal in > types such as book chapters, articles, etc. It corresponds to biblatex's > "booktitle" or "journal". > > According to the "volume-title" proposal, "container-title" would always > hold the title of the whole book, even if it consists of multiple volumes > (such as "Collected Works", "Handbook of Psychology"), and "volume-title" > would hold the title of a single volume ("Tragedies", "Clinical > Psychology", etc.). > > "collection-title" on the other hand contains the title of a book series > in the sense of CMoS 6e 14.128, e.g., "Johns Hopkins Jewish Studies", > "Studies in Illinois Archaeology 6", which is not italicized, and may even > "be omitted to save space". > > 1. Gershon David Hundert, *The Jews in a Polish Private Town: The Case of > Opatów in the Eighteenth Century,* Johns Hopkins Jewish Studies (Baltimore: > Johns Hopkins University Press, 1992). > > Fowler, Melvin L. *The Cahokia Atlas: A Historical Atlas of Cahokia > Archaeology.* Studies in Illinois Archaeology 6. Springfield: Illinois > Historic Preservation Agency, 1989. > > Grenier, Roger. *Les larmes d’Ulysse.* Collection l’un et l’autre. Paris: > Gallimard, 1998. > > Wauchope, Robert. *A Tentative Sequence of Pre-Classic Ceramics in Middle > America.* Middle American Research Records, vol. 1, no. 14. New Orleans, > LA: Tulane University, 1950. > > Since I have not been able to spot any other use, I imagine > "collection-title" might just as well be renamed to "series-title". > > On Tuesday, September 3, 2013 10:44:53 PM UTC+2, Joseph wrote: >> >> Nick pointed to the CSL variables in an appendix of the spec, but this >> is one of the things I haven't been able to figure out. What is the >> logic between collection vs. container? >> > -- 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/CAF-FPGOb%2Bh48xYH9S04gNi-hZ3m7Hph9gdWLzBFcZHc6-qoUbw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 4161 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <CAF-FPGOb+h48xYH9S04gNi-hZ3m7Hph9gdWLzBFcZHc6-qoUbw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <CAF-FPGOb+h48xYH9S04gNi-hZ3m7Hph9gdWLzBFcZHc6-qoUbw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2013-09-05 7:01 ` Nick Bart [not found] ` <b1c9a0f2-11af-4e30-bb26-57cfb5503571-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-05 7:01 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: Nick Bart [-- Attachment #1: Type: text/plain, Size: 918 bytes --] Continued at the xbiblio-devel ML (see http://sourceforge.net/mailarchive/forum.php?forum_name=xbiblio-devel) On Wednesday, 4 September 2013 13:00:47 UTC+2, Bruce D'Arcus wrote: > > Yeah, I'm saying that a journal is (should be) really a collection, as is > a book series, a legal code, etc. > > But let's move this to the CSL venues. > -- 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/b1c9a0f2-11af-4e30-bb26-57cfb5503571%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1334 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <b1c9a0f2-11af-4e30-bb26-57cfb5503571-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <b1c9a0f2-11af-4e30-bb26-57cfb5503571-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-05 7:12 ` Nick Bart 0 siblings, 0 replies; 283+ messages in thread From: Nick Bart @ 2013-09-05 7:12 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: Nick Bart [-- Attachment #1: Type: text/plain, Size: 1579 bytes --] So, thu upshot for pandoc/citeproc-hs so far seems to be that the proposal for a new CSL variable, "volume-title" is on the table, but it's not so clear if and when a consensus might be achieved. In the meantime, pandoc/citeproc-hs could fix the issues concerning the series field, and also (a) implement "volume-title" as I suggested earlier in this thread, or (b) map the content of the biblatex maintitle field, if non-empty, or else the content of the title field (for type book etc.) or the content of the booktitle field (for type inbook etc.) to the CSL variable "container-title"; if the maintitle field is non-empty, the content of the title field (for type book etc.) or the content of the booktitle field (for type inbook etc.) will have to be discarded. (b) is tolerable. It would still output, e.g., "Collected Works, vol. 7", which is much better than just "Tragedies", or even "Tragedies, vol. 7" which would be just plain wrong. Still, I'd be happier if it'd be (a) ... -- 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/6f1be56f-1995-4e54-84ed-201881300237%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1867 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <4d09f924-b9ca-4f29-8c64-de355407a90a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-03 11:54 ` Joseph Reagle 2013-09-03 14:54 ` Bruce D'Arcus @ 2013-09-03 15:20 ` John MacFarlane [not found] ` <20130903152008.GC45840-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-03 15:20 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Just don't expect anything too soon... +++ Nick Bart [Sep 03 13 00:42 ]: > On Monday, 2 September 2013 17:57:11 UTC+2, fiddlosopher wrote: > > I'm open to fixing these bugs. The code base is a bit forbidding, > but > I'm starting to understand it better. > > Brilliant. This is much appreciated. > Here's my summary of how title / (booktitle) / maintitle / series > should be mapped to MODS and then to CSL variables: > book, collection, proceedings, etc.: > biblatex MODS CSL > --------- --------- ------------------------------------ > title top level if maintitle non-empty: volume-title > if maintitle empty: title > maintitle level +1 if non-empty: title > series level +2 collection-title > inbook etc.: > biblatex MODS CSL > --------- --------- ------------------------------------ > title top level title > booktitle level +1 if maintitle non-empty: volume-title > if maintitle empty: container-title > maintitle level +2 if non-empty: container-title > series level +3 collection-title > Notes: > - MODS "levels" refer to nested <relatedItem type="host"> elements > - "maintitle", if non-empty, will be mapped to the CSL variables > "title" (for books etc.) or "container-title" (for inbook etc.) and > will be included in the output by all current CSL styles. > - volume-title (i.e., title of a single volume within a multi-volume > monograph) has been proposed > (https://github.com/ajlyon/zotero-bits/issues/54) but is not an > official CSL variable yet. Still, I see no harm in starting to > implement it now, even if currently only customized CSL styles will be > able to use it. Standard CSL styles will not include this information > in their output (yet), but the title of the whole multivolume monograph > will be (plus volume number, if provided), so while not ideal, this is > perfectly acceptable; much better in any case than to provide nothing > but the the single-volume title. > As to other citeproc-hs bugs identified so far, I think most are > described rather fully on https://github.com/jgm/pandoc/issues. > If you need any further information, or assistance that I might be able > provide, please let me know. > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/4d09f924-b9ca-4f29- > 8c64-de355407a90a%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/4d09f924-b9ca-4f29-8c64-de355407a90a%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130903152008.GC45840-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130903152008.GC45840-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-07 17:16 ` John MacFarlane [not found] ` <20130907171630.GA66328-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-07 17:16 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Just for kicks, I made a little bibtex -> pandoc yaml converter that doesn't depend on bibutils. It's bibtex.hs in the pandoc-citeproc repository, and can be compiled with 'ghc --make bibtex' (you'll need to 'cabal install bibtex split' and also pandoc-citeproc itself). It's very limited, only supports bibtex fields so far, and probably doesn't properly support even then. It uses pandoc's LaTeX reader to parse bibtex fields, so that all latex will be properly interpreted. (Including math.) Perhaps this is one way forward... ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130907171630.GA66328-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130907171630.GA66328-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-11 17:38 ` Joseph Reagle 2013-09-12 8:57 ` Nick Bart 1 sibling, 0 replies; 283+ messages in thread From: Joseph Reagle @ 2013-09-11 17:38 UTC (permalink / raw) To: John MacFarlane; +Cc: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw On 09/07/2013 01:16 PM, John MacFarlane wrote: > Just for kicks, I made a little bibtex -> pandoc yaml converter > that doesn't depend on bibutils. It's bibtex.hs in the pandoc-citeproc > repository, and can be compiled with 'ghc --make bibtex' (you'll need > to 'cabal install bibtex split' and also pandoc-citeproc itself). I was curious how it'd handle fragment identifiers in URLs and it looks to be escaping them with a backslash. That doesn't seem to cause any problem in generated HTML, but neither does not having the slash... ~~~~ @online{Winer2007uvp, author = {Winer, Dave}, custom2 = {01-intro.mm}, day = {01}, keyword = {comment}, month = {01}, organization = {Scripting News}, title = {{The} Unedited Voice of a Person}, url = {http://scripting.com/2007/01/01.html#theUneditedVoiceOfAPerson}, urldate = {2013-02-15}, year = {2007}, } ~~~~ ~~~~ --- references: - author: - family: Winer given: - - Dave id: Winer2007uvp issued: month: 01 year: 2007 title: The Unedited Voice of a Person type: 'no-type' url: 'http://scripting.com/2007/01/01.html\#theUneditedVoiceOfAPerson' ... ~~~~ ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130907171630.GA66328-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-09-11 17:38 ` Joseph Reagle @ 2013-09-12 8:57 ` Nick Bart [not found] ` <fd109d63-2add-4956-b1f3-dbaf706634fb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-12 8:57 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1671 bytes --] Interesting. It chokes on uppercase chars in bibtex field names, though: "author={Doe, John}" works; "Author={Doe, John}" doesn't. Also, just calling it "bibtex" might not be ideal - what about bibtex2pandocyaml or so? And of course pure bibtex doesn't cover a number of common types - @online, e.g., is converted to "type: 'no-type' " (see post by Joseph in this thread) … so I'm looking forward to biblatex support … On Saturday, 7 September 2013 19:16:30 UTC+2, fiddlosopher wrote: > > Just for kicks, I made a little bibtex -> pandoc yaml converter > that doesn't depend on bibutils. It's bibtex.hs in the pandoc-citeproc > repository, and can be compiled with 'ghc --make bibtex' (you'll need > to 'cabal install bibtex split' and also pandoc-citeproc itself). > > It's very limited, only supports bibtex fields so far, and probably > doesn't properly support even then. > > It uses pandoc's LaTeX reader to parse bibtex fields, so that all > latex will be properly interpreted. (Including math.) > > Perhaps this is one way forward... > > -- 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/fd109d63-2add-4956-b1f3-dbaf706634fb%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2083 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <fd109d63-2add-4956-b1f3-dbaf706634fb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <fd109d63-2add-4956-b1f3-dbaf706634fb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-12 18:19 ` John MacFarlane 2013-09-13 6:24 ` John MacFarlane 1 sibling, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-09-12 18:19 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ Nick Bart [Sep 12 13 01:57 ]: > Interesting. It chokes on uppercase chars in bibtex field names, > though: "author={Doe, John}" works; "Author={Doe, John}" doesn't. Fixed. > Also, > just calling it "bibtex" might not be ideal - what about > bibtex2pandocyaml or so? Provisionally renamed to bibtex2yaml. Of course this is just experimental at this point. > And of course pure bibtex doesn't cover a number of common types - > @online, e.g., is converted to "type: 'no-type' " (see post by Joseph > in this thread) so I'm looking forward to biblatex support Sure. Should just be a matter of toil to add these. In fact I may try to make the code clear enough that a non-Haskell speaker could do it. John ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <fd109d63-2add-4956-b1f3-dbaf706634fb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-12 18:19 ` John MacFarlane @ 2013-09-13 6:24 ` John MacFarlane [not found] ` <20130913062445.GA95508-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-13 6:24 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I've renamed to bibtex2pandoc.hs and made several improvements, including parsing of non-dropping-particles. I've added all the biblatex entry types, and I've started adding support for biblatex data fields. (In the biblatex list of data fields, 2.2.2 of http://www.math.upenn.edu/tex_docs/latex/biblatex/biblatex.pdf, I've gotten as far as 'annotation'.) Nick, if you (or others) want to work on this, it should be pretty self-explanatory how to add to the code, even if you don't know Haskell. (Find the part of the code with all the arrows. ==> means the field is to be interpreted as latex; --> means it's a raw string; *=> is an author list.) Recompile with 'ghc --make bibtex2pandoc.hs' John ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130913062445.GA95508-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130913062445.GA95508-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-13 14:26 ` Nick Bart [not found] ` <b01350cd-72e7-49e5-aa50-6c25382376f6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-13 14:26 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 4747 bytes --] Fantastic. I'm amazed by your energy. And, yes, I'd love to contribute. Time to learn a little Haskell after all, I guess. Still, a few questions first: 1. Would it make sense to cleanly separate code for bibtex vs. code for biblatex? Handling of dates, and a number of other things, see below, differs a lot. 2. (How) can the bibtex and biblatex "crossref" mechanism for inheritance be implemented? (biblatex has introduced an alternative cross-referencing mechanism using the xref field, but I'm not sure how many people have actually started using this. I haven't seen any advantage in using this instead of crossref yet.) 3. Some fields will have to be concatenated, - title + subtitle + titleaddon (same for booktitle, maintitle), and journal/journaltitle + journalsubtitle. How will this be handled? (titleaddon etc. are supposed to be printed "in a different font", i.e., unitalicized or outside of speech marks, but this currently does not seem to be possible in CSL.) - note + addendum. biblatex has addendum at the end of an entry, and note somewhere in front of that, but in CSL there's only one suitable field: note. – Differs from biblatex "annotation" (and its alias "annote") which map to CSL "annote", and contain reader's notes. 4. Some fields have to be omitted if some certain other/newer field(s) are present: In biblatex, "date", if present, is used instead of "year", "month", and "day"; "location" instead of "address", etc. How will this be handled? 5. Proper mapping of some fields or entry types is conditional upon either the existence or the content of other fields. How can this be made to work? - for @book, @collection, @proceedings: title ==> title, unless maintitle exists, in which case maintitle ==> title (and, once consensus on new CSL variables is reached, title ==> volume-title; as discussed earlier in this thread), - for @inbook, @incollection, @proceedings: booktitle ==> container-title, unless maintitle exists, in which case maintitle ==> container-title (and booktitle ==> volume-title), - mapping of editor, editora, editorb, editorc depends on the content of editortype, editoratype, editorbtype, editorctype, - An entrysubtype of "magazine" should change the CSL type from "article-journal" to "article-magazine" (this is not from biblatex itself but from biblatex-chicago, but I think it'd be very useful to borrow certain bits from this package; an entrysubtype of "newspaper" could of course map to CSL "article-newspaper"). - series maps to CSL collection-title, except for @article (and @periodical?), in which case it should appear after the journal title (the only solution in CSL is probably to concatenate the two fields). 6. "keys" are used liberally in biblatex fields, as shorthands, and for localization (see biblatex manual 4.9). These should be translated to natural language terms. Let's focus on English first - but what about localization …? 7. In addition to "name lists" (authors etc.), biblatex has "literal lists" with elements separated by "and", too: institution, location, organization, origlocation, origpublisher, publisher, list[a-f], address, school. Will routines used for names work unmodified? On Friday, 13 September 2013 08:24:45 UTC+2, fiddlosopher wrote: > > I've renamed to bibtex2pandoc.hs and made several improvements, > including parsing of non-dropping-particles. > > I've added all the biblatex entry types, and I've started adding support > for biblatex data fields. (In the biblatex list of data fields, > 2.2.2 of http://www.math.upenn.edu/tex_docs/latex/biblatex/biblatex.pdf, > I've gotten as far as 'annotation'.) > > Nick, if you (or others) want to work on this, it should be pretty > self-explanatory how to add to the code, even if you don't know Haskell. > (Find the part of the code with all the arrows. ==> means the field is > to be interpreted as latex; --> means it's a raw string; *=> is an > author list.) > > Recompile with 'ghc --make bibtex2pandoc.hs' > > John > -- 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/b01350cd-72e7-49e5-aa50-6c25382376f6%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 5387 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <b01350cd-72e7-49e5-aa50-6c25382376f6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <b01350cd-72e7-49e5-aa50-6c25382376f6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-13 14:36 ` John MacFarlane [not found] ` <20130913143645.GF95716-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-09-13 14:44 ` Bruce D'Arcus 2013-09-27 18:26 ` John MacFarlane 2 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-13 14:36 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw You raise some good points. All of this is possible, but I think I'd like to work a bit on the underlying framework to make it all easier to implement. +++ Nick Bart [Sep 13 13 07:26 ]: > Fantastic. I'm amazed by your energy. And, yes, I'd love to contribute. > Time to learn a little Haskell after all, I guess. > Still, a few questions first: > 1. Would it make sense to cleanly separate code for bibtex vs. code for > biblatex? Handling of dates, and a number of other things, see below, > differs a lot. Since so much is the same, the thing to do is probably to add an ifBibTeX conditional. > 2. (How) can the bibtex and biblatex "crossref" mechanism for > inheritance be implemented? (biblatex has introduced an alternative > cross-referencing mechanism using the xref field, but I'm not sure how > many people have actually started using this. I haven't seen any > advantage in using this instead of crossref yet.) I don't know. Can you give an example of the use of crossref? > 3. Some fields will have to be concatenated, > - title + subtitle + titleaddon (same for booktitle, maintitle), > and journal/journaltitle + journalsubtitle. How will this be handled? > (titleaddon etc. are supposed to be printed "in a different font", > i.e., unitalicized or outside of speech marks, but this currently does > not seem to be possible in CSL.) > - note + addendum. biblatex has addendum at the end of an entry, > and note somewhere in front of that, but in CSL there's only one > suitable field: note. Differs from biblatex "annotation" (and its alias > "annote") which map to CSL "annote", and contain reader's notes. > 4. Some fields have to be omitted if some certain other/newer field(s) > are present: In biblatex, "date", if present, is used instead of > "year", "month", and "day"; "location" instead of "address", etc. How > will this be handled? > 5. Proper mapping of some fields or entry types is conditional upon > either the existence or the content of other fields. How can this be > made to work? > - for @book, @collection, @proceedings: title ==> title, unless > maintitle exists, in which case maintitle ==> title (and, once > consensus on new CSL variables is reached, title ==> volume-title; as > discussed earlier in this thread), > - for @inbook, @incollection, @proceedings: booktitle ==> > container-title, unless maintitle exists, in which case maintitle ==> > container-title (and booktitle ==> volume-title), > - mapping of editor, editora, editorb, editorc depends on the > content of editortype, editoratype, editorbtype, editorctype, > - An entrysubtype of "magazine" should change the CSL type from > "article-journal" to "article-magazine" (this is not from biblatex > itself but from biblatex-chicago, but I think it'd be very useful to > borrow certain bits from this package; an entrysubtype of "newspaper" > could of course map to CSL "article-newspaper"). > - series maps to CSL collection-title, except for @article (and > @periodical?), in which case it should appear after the journal title > (the only solution in CSL is probably to concatenate the two fields). > 6. "keys" are used liberally in biblatex fields, as shorthands, and for > localization (see biblatex manual 4.9). These should be translated to > natural language terms. Let's focus on English first - but what about > localization ? > 7. In addition to "name lists" (authors etc.), biblatex has "literal > lists" with elements separated by "and", too: institution, location, > organization, origlocation, origpublisher, publisher, list[a-f], > address, school. Will routines used for names work unmodified? No, because this routine includes code for dividing a single name into given, last, and prefix. But it will be easy to write something that will work for these. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130913143645.GF95716-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130913143645.GF95716-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-13 15:34 ` Nick Bart 2013-09-24 13:11 ` Nick Bart 1 sibling, 0 replies; 283+ messages in thread From: Nick Bart @ 2013-09-13 15:34 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1859 bytes --] Example: @incollection{item1, Author = {Doe, John}, Crossref = {item2}, Pages = {12-34}, Title = {The Incollection Title}} @collection{item2, Date = {2012}, Editor = {Editor, Ed}, Location = {Location}, Publisher = {Publisher}, Title = {The Collection Title}} item1 should inherit all missing fields from item2. The bibtex program used to do this in a rather simple fashion, and required an additional "Booktitle = {The Collection Title}" in item2. biblatex in combination with the biber program provides a much better solution: it remaps field names of item2, e.g., title -> booktitle, according to a set of cross-referencing rules. See biblatex manual, §§ 2.4.1 and 4.5.9, and Appendix B. On Friday, 13 September 2013 16:36:45 UTC+2, fiddlosopher wrote: > > > 2. (How) can the bibtex and biblatex "crossref" mechanism for > > inheritance be implemented? (biblatex has introduced an alternative > > cross-referencing mechanism using the xref field, but I'm not sure > how > > many people have actually started using this. I haven't seen any > > advantage in using this instead of crossref yet.) > > I don't know. Can you give an example of the use of crossref? > -- 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/2513322d-2156-40f2-9546-64eb2cce12bf%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2491 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130913143645.GF95716-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-09-13 15:34 ` Nick Bart @ 2013-09-24 13:11 ` Nick Bart [not found] ` <73c9fc49-d61e-457e-9304-cb42ca1ccac7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-24 13:11 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 23243 bytes --] For what it's worth, this is my list of mappings from all biblatex fields (as listed in the biblatex manual, §§ 2.2.2–2.2.5) to matching CSL variables, with a few comments thrown in. I hope it's useful both for developing bibtex2pandoc and for testing existing conversion routines such as biblatex -> MODS -> CSL. Feedback on content and formatting is welcome, and maybe some improved version could even be integrated into the general pandoc documentation. 2.2.2 Data Fields | biblatex field | biblatex field type | CSL | comment | |:----------------|:---------------------------|:-------------------------|:------------------------------------------------| | abstract | field (literal) | abstract | ! | | addendum | field (literal) | note | concat w/ note | | afterword | list (name) | --- | no corresp. CSL var | | annotation | field (literal) | annote | ! | | annotator | list (name) | --- | no corresp. CSL var | | author | list (name) | author | ! | | authortype | field (key) | --- | no corresp. CSL var | | bookauthor | list (name) | container-author | ! | | bookpagination | field (key) | ? | no corresp. CSL var (?), but check CSL locators | | booksubtitle | field (literal) | (container-title) | concat w/ booktitle | | booktitle | field (literal) | container-title | or volume-title if maintitle exists | | booktitleaddon | field (literal) | (container-title) | concat w/ booktitle | | chapter | field (literal) | chapter-number | at least if numeric | | commentator | list (name) | --- | no corresp. CSL var | | date | field (date) | issued | ! | | doi | field (verbatim) | DOI | ! | | edition | field (integer or literal) | --- | --- | | editor | list (name) | editor, or other type | depending on editortype: CSL has composer, | | editora | list (name) | editor, or other type | director, editorial-director, illustrator, | | editorb | list (name) | editor, or other type | interviewer, recipient | | editorc | list (name) | editor, or other type | | | editortype | field (key) | --- | determines editor's CSL type | | editoratype | field (key) | --- | determines editora's CSL type | | editorbtype | field (key) | --- | determines editorb's CSL type | | editorctype | field (key) | --- | determines editorc's CSL type | | eid | field (literal) | --- | --- | | entrysubtype | field (literal) | --- | may modify entry type of @article | | eprint | field (verbatim) | PMID | only if eprinttype = {pubmed} ... | | eprintclass | field (literal) | --- | ... other eprinttypes have no CSL counterpart | | eprinttype | field (literal) | --- | | | eventdate | field (date) | event-date | ! | | eventtitle | field (literal) | event | ! | | file | field (verbatim) | --- | no corresp. CSL var | | foreword | list (name) | --- | no corresp. CSL var | | holder | list (name) | --- | no corresp. CSL var | | howpublished | field (literal) | publisher | h.+p. never co-occur; h.+orga. do * | | indextitle | field (literal) | --- | --- | | institution | list (literal) | publisher | i. + p. never co-occur * | | introduction | list (name) | --- | no corresp. CSL var | | isan | field (literal) | --- | no corresp. CSL var | | isbn | field (literal) | ISBN | ! | | ismn | field (literal) | --- | no corresp. CSL var | | isrn | field (literal) | --- | no corresp. CSL var | | issn | field (literal) | ISSN | ! | | issue | field (literal) | issue | can issue + number co-occur? | | issuesubtitle | field (literal) | --- | concat after issuetitle | | issuetitle | field (literal) | --- | CSL var proposed: volume-title/issue-title | | iswc | field (literal) | --- | --- | | journalsubtitle | field (literal) | (container-title) | concat after journaltitle | | journaltitle | field (literal) | container-title | ! | | label | field (literal) | citation-label (?) | (???) | | language | list (key) | --- | no corresp. CSL var (!!!) | | library | field (literal) | call-number | [at least close] | | location | list (literal) | publisher-place | ! | | mainsubtitle | field (literal) | (title/container-title) | concat w/ maintitle | | maintitle | field (literal) | title/container-title | ! | | maintitleaddon | field (literal) | (title/container-title) | concat w/ maintitle | | month | field (integer) | --- | see date (?) | | nameaddon | field (literal) | --- | no corresp. CSL var | | note | field (literal) | note | concat w/ addendum | | number | field (literal) | issue | if in @article (?) | | | | number | if in @report (?) | | | | collection-number | all other types, at least if series exists | | organization | list (literal) | --- | * | | origdate | field (date) | original-date | ! | | origlanguage | field (key) | --- | no corresp. CSL var | | origlocation | list (literal) | original-publisher-place | ! | | origpublisher | list (literal) | original-publisher | ! | | origtitle | field (literal) | original-title | ! | | pages | field (range) | page | ! | | pagetotal | field (literal) | number-of-pages | ! | | pagination | field (key) | ? | no corresp. CSL var (?), but check locators | | part | field (literal) | ? | concat w/ volume (?) | | publisher | list (literal) | publisher | ! * | | pubstate | field (key) | status | ! (translate localization keys!) | | reprinttitle | field (literal) | --- | "BibTeX only"=obsolete? | | series | field (literal) | collection-title | if @article, concat after container-title | | shortauthor | list (name) | --- | no corresp. CSL var | | shorteditor | list (name) | --- | no corresp. CSL var | | shorthand | field (literal) | --- | no corresp. CSL var | | shorthandintro | field (literal) | --- | no corresp. CSL var | | shortjournal | field (literal) | container-title-short | ! | | shortseries | field (literal) | --- | no corresp. CSL var | | shorttitle | field (literal) | title-short | ! | | subtitle | field (literal) | (title) | concat after title | | title | field (literal) | title | ! | | titleaddon | field (literal) | (title) | concat after title+subtitle (not optimal) | | translator | list (name) | translator | ! | | type | field (key) | genre | ! | | url | field (uri) | URL | ! | | urldate | field (date) | accessed | ! | | venue | field (literal) | event-place | ! | | version | field (literal) | version | ! | | volume | field (literal) | volume | ! | | volumes | field (literal) | number-of-volumes | ! | | year | field (literal) | issued | ! only use if date empty | ! means straightforward mapping is possible * Some entry types may contain two biblatex fields, for both of which only mapping to CSL publisher seems to make sense: howpublished + organization co-occur in @misc; organization + publisher co-occur in @manual, @proceedings, @mvproceedings, @inproceedings. Maybe simply always concat institution + organization + howpublished + publisher to CSL publisher, no matter what the entry type is? 2.2.3 Special Fields | biblatex field | biblatex field type | CSL | comment | |:---------------|:-----------------------------------------------------------|:---------|:-------------------------------------| | crossref | field (entry key) | | field for cross-referencing entries | | entryset | field (comma-separated values) | | | | execute | field (code) | | | | gender | field (Pattern matching one of sf, sm, sn, pf, pm, pn, pp) | --- | no corresp. CSL var | | hyphenation | field (identifier) | language | ! | | ids | field (comma-separated list of entrykeys (biber only)) | ? | YAML entries w/ >=1 id allowed? | | indexsorttitle | field (literal) | | | | keywords | field (comma-separated values) | keyword | ! | | options | field (comma-separated \keyval options) | | at least a subset of options could | | | | | prob. be used, e.g., url=false to | | | | | suppress the URL | | presort | field (string) | | | | related | field (comma-separated values) | | | | relatedoptions | field (comma-separated values (biber only)) | | | | relatedtype | field (identifier (biber only)) | | | | relatedstring | field (literal) (biber only) | | | | sortkey | field (literal) (biber only) | | | | sortname | list (name) | | | | sortshorthand | field (literal) (biber only) | | | | sorttitle | field (literal) | | | | sortyear | field (literal) | | | | xdata | field (comma-separated list of entrykeys (biber only)) | | | | xref | field (entry key) | | field for cross-referencing entries | 2.2.4 Custom Fields | biblatex field | biblatex field type | CSL | comment | |:---------------|:--------------------|:----|:--------| | name[a-c] | list (name) | | | | name[a-c]type | field (key) | | | | list[a-f] | list (literal) | | | | user[a-c] | field (literal) | | | | verb[a-c] | field (literal) | | | 2.2.5 Field Aliases | biblatex field | biblatex field type | CSL | comment | |:---------------|:--------------------|:----------------|:-----------------------| | address | list (literal) | publisher-place | alias for location | | annote | field (literal) | annote | alias for annotation | | archiveprefix | field (literal) | | | | journal | field (literal) | container-title | alias for journaltitle | | key | field (literal) | | | | pdf | field (verbatim) | | | | primaryclass | field (literal) | | | | school | list (literal) | publisher | alias for publisher | On Friday, September 13, 2013 2:36:45 PM UTC, fiddlosopher wrote: > > You raise some good points. All of this is possible, but I think > I'd like to work a bit on the underlying framework to make it all easier > to implement. > > +++ Nick Bart [Sep 13 13 07:26 ]: > > Fantastic. I'm amazed by your energy. And, yes, I'd love to > contribute. > > Time to learn a little Haskell after all, I guess. > > Still, a few questions first: > > 1. Would it make sense to cleanly separate code for bibtex vs. code > for > > biblatex? Handling of dates, and a number of other things, see below, > > differs a lot. > > Since so much is the same, the thing to do is probably to add an > ifBibTeX conditional. > > > 2. (How) can the bibtex and biblatex "crossref" mechanism for > > inheritance be implemented? (biblatex has introduced an alternative > > cross-referencing mechanism using the xref field, but I'm not sure > how > > many people have actually started using this. I haven't seen any > > advantage in using this instead of crossref yet.) > > I don't know. Can you give an example of the use of crossref? > > > 3. Some fields will have to be concatenated, > > - title + subtitle + titleaddon (same for booktitle, maintitle), > > and journal/journaltitle + journalsubtitle. How will this be handled? > > (titleaddon etc. are supposed to be printed "in a different font", > > i.e., unitalicized or outside of speech marks, but this currently > does > > not seem to be possible in CSL.) > > - note + addendum. biblatex has addendum at the end of an entry, > > and note somewhere in front of that, but in CSL there's only one > > suitable field: note. Differs from biblatex "annotation" (and its > alias > > "annote") which map to CSL "annote", and contain reader's notes. > > 4. Some fields have to be omitted if some certain other/newer > field(s) > > are present: In biblatex, "date", if present, is used instead of > > "year", "month", and "day"; "location" instead of "address", etc. How > > will this be handled? > > 5. Proper mapping of some fields or entry types is conditional upon > > either the existence or the content of other fields. How can this be > > made to work? > > - for @book, @collection, @proceedings: title ==> title, unless > > maintitle exists, in which case maintitle ==> title (and, once > > consensus on new CSL variables is reached, title ==> volume-title; as > > discussed earlier in this thread), > > - for @inbook, @incollection, @proceedings: booktitle ==> > > container-title, unless maintitle exists, in which case maintitle ==> > > container-title (and booktitle ==> volume-title), > > - mapping of editor, editora, editorb, editorc depends on the > > content of editortype, editoratype, editorbtype, editorctype, > > - An entrysubtype of "magazine" should change the CSL type from > > "article-journal" to "article-magazine" (this is not from biblatex > > itself but from biblatex-chicago, but I think it'd be very useful to > > borrow certain bits from this package; an entrysubtype of "newspaper" > > could of course map to CSL "article-newspaper"). > > - series maps to CSL collection-title, except for @article (and > > @periodical?), in which case it should appear after the journal title > > (the only solution in CSL is probably to concatenate the two fields). > > 6. "keys" are used liberally in biblatex fields, as shorthands, and > for > > localization (see biblatex manual 4.9). These should be translated to > > natural language terms. Let's focus on English first - but what about > > localization ? > > 7. In addition to "name lists" (authors etc.), biblatex has "literal > > lists" with elements separated by "and", too: institution, location, > > organization, origlocation, origpublisher, publisher, list[a-f], > > address, school. Will routines used for names work unmodified? > > No, because this routine includes code for dividing a single name into > given, last, and prefix. But it will be easy to write something that > will work for these. > > -- 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/73c9fc49-d61e-457e-9304-cb42ca1ccac7%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 67950 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <73c9fc49-d61e-457e-9304-cb42ca1ccac7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <73c9fc49-d61e-457e-9304-cb42ca1ccac7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-24 14:05 ` Bruce D'Arcus 2013-09-25 16:36 ` John MacFarlane 2013-09-25 17:25 ` Joseph Reagle 2 siblings, 0 replies; 283+ messages in thread From: Bruce D'Arcus @ 2013-09-24 14:05 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I will just emphasize, I view the biblatex and csl models as both a superset of bibtex. E.g. bibtex isn't a great target format. On Tue, Sep 24, 2013 at 9:11 AM, Nick Bart <nickbart1980-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > For what it's worth, this is my list of mappings from all biblatex fields > (as listed in the biblatex manual, §§ 2.2.2–2.2.5) to matching CSL > variables, with a few comments thrown in. I hope it's useful both for > developing bibtex2pandoc and for testing existing conversion routines such > as biblatex -> MODS -> CSL. > > Feedback on content and formatting is welcome, and maybe some improved > version could even be integrated into the general pandoc documentation. > > 2.2.2 Data Fields > > | biblatex field | biblatex field type | CSL | > comment | > |:----------------|:---------------------------|:-------------------------|:------------------------------------------------| > | abstract | field (literal) | abstract | > ! | > | addendum | field (literal) | note | > concat w/ note | > | afterword | list (name) | --- | > no corresp. CSL var | > | annotation | field (literal) | annote | > ! | > | annotator | list (name) | --- | > no corresp. CSL var | > | author | list (name) | author | > ! | > | authortype | field (key) | --- | > no corresp. CSL var | > | bookauthor | list (name) | container-author | > ! | > | bookpagination | field (key) | ? | > no corresp. CSL var (?), but check CSL locators | > | booksubtitle | field (literal) | (container-title) | > concat w/ booktitle | > | booktitle | field (literal) | container-title | > or volume-title if maintitle exists | > | booktitleaddon | field (literal) | (container-title) | > concat w/ booktitle | > | chapter | field (literal) | chapter-number | > at least if numeric | > | commentator | list (name) | --- | > no corresp. CSL var | > | date | field (date) | issued | > ! | > | doi | field (verbatim) | DOI | > ! | > | edition | field (integer or literal) | --- | > --- | > | editor | list (name) | editor, or other type | > depending on editortype: CSL has composer, | > | editora | list (name) | editor, or other type | > director, editorial-director, illustrator, | > | editorb | list (name) | editor, or other type | > interviewer, recipient | > | editorc | list (name) | editor, or other type | > | > | editortype | field (key) | --- | > determines editor's CSL type | > | editoratype | field (key) | --- | > determines editora's CSL type | > | editorbtype | field (key) | --- | > determines editorb's CSL type | > | editorctype | field (key) | --- | > determines editorc's CSL type | > | eid | field (literal) | --- | > --- | > | entrysubtype | field (literal) | --- | > may modify entry type of @article | > | eprint | field (verbatim) | PMID | > only if eprinttype = {pubmed} ... | > | eprintclass | field (literal) | --- | > ... other eprinttypes have no CSL counterpart | > | eprinttype | field (literal) | --- | > | > | eventdate | field (date) | event-date | > ! | > | eventtitle | field (literal) | event | > ! | > | file | field (verbatim) | --- | > no corresp. CSL var | > | foreword | list (name) | --- | > no corresp. CSL var | > | holder | list (name) | --- | > no corresp. CSL var | > | howpublished | field (literal) | publisher | > h.+p. never co-occur; h.+orga. do * | > | indextitle | field (literal) | --- | > --- | > | institution | list (literal) | publisher | > i. + p. never co-occur * | > | introduction | list (name) | --- | > no corresp. CSL var | > | isan | field (literal) | --- | > no corresp. CSL var | > | isbn | field (literal) | ISBN | > ! | > | ismn | field (literal) | --- | > no corresp. CSL var | > | isrn | field (literal) | --- | > no corresp. CSL var | > | issn | field (literal) | ISSN | > ! | > | issue | field (literal) | issue | > can issue + number co-occur? | > | issuesubtitle | field (literal) | --- | > concat after issuetitle | > | issuetitle | field (literal) | --- | > CSL var proposed: volume-title/issue-title | > | iswc | field (literal) | --- | > --- | > | journalsubtitle | field (literal) | (container-title) | > concat after journaltitle | > | journaltitle | field (literal) | container-title | > ! | > | label | field (literal) | citation-label (?) | > (???) | > | language | list (key) | --- | > no corresp. CSL var (!!!) | > | library | field (literal) | call-number | > [at least close] | > | location | list (literal) | publisher-place | > ! | > | mainsubtitle | field (literal) | (title/container-title) | > concat w/ maintitle | > | maintitle | field (literal) | title/container-title | > ! | > | maintitleaddon | field (literal) | (title/container-title) | > concat w/ maintitle | > | month | field (integer) | --- | > see date (?) | > | nameaddon | field (literal) | --- | > no corresp. CSL var | > | note | field (literal) | note | > concat w/ addendum | > | number | field (literal) | issue | > if in @article (?) | > | | | number | > if in @report (?) | > | | | collection-number | > all other types, at least if series exists | > | organization | list (literal) | --- | > * | > | origdate | field (date) | original-date | > ! | > | origlanguage | field (key) | --- | > no corresp. CSL var | > | origlocation | list (literal) | original-publisher-place | > ! | > | origpublisher | list (literal) | original-publisher | > ! | > | origtitle | field (literal) | original-title | > ! | > | pages | field (range) | page | > ! | > | pagetotal | field (literal) | number-of-pages | > ! | > | pagination | field (key) | ? | > no corresp. CSL var (?), but check locators | > | part | field (literal) | ? | > concat w/ volume (?) | > | publisher | list (literal) | publisher | > ! * | > | pubstate | field (key) | status | > ! (translate localization keys!) | > | reprinttitle | field (literal) | --- | > "BibTeX only"=obsolete? | > | series | field (literal) | collection-title | > if @article, concat after container-title | > | shortauthor | list (name) | --- | > no corresp. CSL var | > | shorteditor | list (name) | --- | > no corresp. CSL var | > | shorthand | field (literal) | --- | > no corresp. CSL var | > | shorthandintro | field (literal) | --- | > no corresp. CSL var | > | shortjournal | field (literal) | container-title-short | > ! | > | shortseries | field (literal) | --- | > no corresp. CSL var | > | shorttitle | field (literal) | title-short | > ! | > | subtitle | field (literal) | (title) | > concat after title | > | title | field (literal) | title | > ! | > | titleaddon | field (literal) | (title) | > concat after title+subtitle (not optimal) | > | translator | list (name) | translator | > ! | > | type | field (key) | genre | > ! | > | url | field (uri) | URL | > ! | > | urldate | field (date) | accessed | > ! | > | venue | field (literal) | event-place | > ! | > | version | field (literal) | version | > ! | > | volume | field (literal) | volume | > ! | > | volumes | field (literal) | number-of-volumes | > ! | > | year | field (literal) | issued | > ! only use if date empty | > > > ! means straightforward mapping is possible > > * Some entry types may contain two biblatex fields, for both of which only > mapping to CSL publisher seems to make sense: > howpublished + organization co-occur in @misc; > organization + publisher co-occur in @manual, @proceedings, > @mvproceedings, @inproceedings. > Maybe simply always concat institution + organization + howpublished + > publisher to CSL publisher, no matter what the entry type is? > > > 2.2.3 Special Fields > > | biblatex field | biblatex field type > | CSL | comment | > |:---------------|:-----------------------------------------------------------|:---------|:-------------------------------------| > | crossref | field (entry key) > | | field for cross-referencing entries | > | entryset | field (comma-separated values) > | | | > | execute | field (code) > | | | > | gender | field (Pattern matching one of sf, sm, sn, pf, pm, pn, > pp) | --- | no corresp. CSL var | > | hyphenation | field (identifier) > | language | ! | > | ids | field (comma-separated list of entrykeys (biber only)) > | ? | YAML entries w/ >=1 id allowed? | > | indexsorttitle | field (literal) > | | | > | keywords | field (comma-separated values) > | keyword | ! | > | options | field (comma-separated \keyval options) > | | at least a subset of options could | > | | > | | prob. be used, e.g., url=false to | > | | > | | suppress the URL | > | presort | field (string) > | | | > | related | field (comma-separated values) > | | | > | relatedoptions | field (comma-separated values (biber only)) > | | | > | relatedtype | field (identifier (biber only)) > | | | > | relatedstring | field (literal) (biber only) > | | | > | sortkey | field (literal) (biber only) > | | | > | sortname | list (name) > | | | > | sortshorthand | field (literal) (biber only) > | | | > | sorttitle | field (literal) > | | | > | sortyear | field (literal) > | | | > | xdata | field (comma-separated list of entrykeys (biber only)) > | | | > | xref | field (entry key) > | | field for cross-referencing entries | > > 2.2.4 Custom Fields > > | biblatex field | biblatex field type | CSL | comment | > |:---------------|:--------------------|:----|:--------| > | name[a-c] | list (name) | | | > | name[a-c]type | field (key) | | | > | list[a-f] | list (literal) | | | > | user[a-c] | field (literal) | | | > | verb[a-c] | field (literal) | | | > > 2.2.5 Field Aliases > > | biblatex field | biblatex field type | CSL | comment > | > |:---------------|:--------------------|:----------------|:-----------------------| > | address | list (literal) | publisher-place | alias for > location | > | annote | field (literal) | annote | alias for > annotation | > | archiveprefix | field (literal) | | > | > | journal | field (literal) | container-title | alias for > journaltitle | > | key | field (literal) | | > | > | pdf | field (verbatim) | | > | > | primaryclass | field (literal) | | > | > | school | list (literal) | publisher | alias for > publisher | > > > > On Friday, September 13, 2013 2:36:45 PM UTC, fiddlosopher wrote: >> >> You raise some good points. All of this is possible, but I think >> I'd like to work a bit on the underlying framework to make it all easier >> to implement. >> >> +++ Nick Bart [Sep 13 13 07:26 ]: >> > Fantastic. I'm amazed by your energy. And, yes, I'd love to >> > contribute. >> > Time to learn a little Haskell after all, I guess. >> > Still, a few questions first: >> > 1. Would it make sense to cleanly separate code for bibtex vs. code >> > for >> > biblatex? Handling of dates, and a number of other things, see below, >> > differs a lot. >> >> Since so much is the same, the thing to do is probably to add an >> ifBibTeX conditional. >> >> > 2. (How) can the bibtex and biblatex "crossref" mechanism for >> > inheritance be implemented? (biblatex has introduced an alternative >> > cross-referencing mechanism using the xref field, but I'm not sure >> > how >> > many people have actually started using this. I haven't seen any >> > advantage in using this instead of crossref yet.) >> >> I don't know. Can you give an example of the use of crossref? >> >> > 3. Some fields will have to be concatenated, >> > - title + subtitle + titleaddon (same for booktitle, maintitle), >> > and journal/journaltitle + journalsubtitle. How will this be handled? >> > (titleaddon etc. are supposed to be printed "in a different font", >> > i.e., unitalicized or outside of speech marks, but this currently >> > does >> > not seem to be possible in CSL.) >> > - note + addendum. biblatex has addendum at the end of an entry, >> > and note somewhere in front of that, but in CSL there's only one >> > suitable field: note. Differs from biblatex "annotation" (and its >> > alias >> > "annote") which map to CSL "annote", and contain reader's notes. >> > 4. Some fields have to be omitted if some certain other/newer >> > field(s) >> > are present: In biblatex, "date", if present, is used instead of >> > "year", "month", and "day"; "location" instead of "address", etc. How >> > will this be handled? >> > 5. Proper mapping of some fields or entry types is conditional upon >> > either the existence or the content of other fields. How can this be >> > made to work? >> > - for @book, @collection, @proceedings: title ==> title, unless >> > maintitle exists, in which case maintitle ==> title (and, once >> > consensus on new CSL variables is reached, title ==> volume-title; as >> > discussed earlier in this thread), >> > - for @inbook, @incollection, @proceedings: booktitle ==> >> > container-title, unless maintitle exists, in which case maintitle ==> >> > container-title (and booktitle ==> volume-title), >> > - mapping of editor, editora, editorb, editorc depends on the >> > content of editortype, editoratype, editorbtype, editorctype, >> > - An entrysubtype of "magazine" should change the CSL type from >> > "article-journal" to "article-magazine" (this is not from biblatex >> > itself but from biblatex-chicago, but I think it'd be very useful to >> > borrow certain bits from this package; an entrysubtype of "newspaper" >> > could of course map to CSL "article-newspaper"). >> > - series maps to CSL collection-title, except for @article (and >> > @periodical?), in which case it should appear after the journal title >> > (the only solution in CSL is probably to concatenate the two fields). >> > 6. "keys" are used liberally in biblatex fields, as shorthands, and >> > for >> > localization (see biblatex manual 4.9). These should be translated to >> > natural language terms. Let's focus on English first - but what about >> > localization ? >> > 7. In addition to "name lists" (authors etc.), biblatex has "literal >> > lists" with elements separated by "and", too: institution, location, >> > organization, origlocation, origpublisher, publisher, list[a-f], >> > address, school. Will routines used for names work unmodified? >> >> No, because this routine includes code for dividing a single name into >> given, last, and prefix. But it will be easy to write something that >> will work for these. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "pandoc-discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/pandoc-discuss/-SajbqoPX8k/unsubscribe. > To unsubscribe from this group and all its topics, 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/73c9fc49-d61e-457e-9304-cb42ca1ccac7%40googlegroups.com. > > 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/CAF-FPGPULneZLmjD9qC5W%2BnxiXzU4mGQCA6V%2BUfSkHTBSEPkmg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <73c9fc49-d61e-457e-9304-cb42ca1ccac7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-24 14:05 ` Bruce D'Arcus @ 2013-09-25 16:36 ` John MacFarlane 2013-09-25 17:25 ` Joseph Reagle 2 siblings, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-09-25 16:36 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Nick, This is going to be very helpful. I've tinkered a bit more with bibtex2pandoc.hs. My goal is to make it possible for you to work on the source yourself, with minimal Haskell knowledge. I'm getting closer, but I still have a view things left. In the end, this should be made part of pandoc-citeproc, and it should replace bibutils for reading bibtex and biblatex files. John +++ Nick Bart [Sep 24 13 06:11 ]: > For what it's worth, this is my list of mappings from all biblatex > fields (as listed in the biblatex manual, 2.2.22.2.5) to matching CSL > variables, with a few comments thrown in. I hope it's useful both for > developing bibtex2pandoc and for testing existing conversion routines > such as biblatex -> MODS -> CSL. > Feedback on content and formatting is welcome, and maybe some improved > version could even be integrated into the general pandoc documentation. ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <73c9fc49-d61e-457e-9304-cb42ca1ccac7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-24 14:05 ` Bruce D'Arcus 2013-09-25 16:36 ` John MacFarlane @ 2013-09-25 17:25 ` Joseph Reagle 2 siblings, 0 replies; 283+ messages in thread From: Joseph Reagle @ 2013-09-25 17:25 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw On 09/24/2013 09:11 AM, Nick Bart wrote: > For what it's worth, this is my list of mappings from all biblatex fields > (as listed in the biblatex manual, §§ 2.2.2–2.2.5) to matching CSL > variables, with a few comments thrown in. I hope it's useful both for > developing bibtex2pandoc and for testing existing conversion routines such > as biblatex -> MODS -> CSL. > > Feedback on content and formatting is welcome, and maybe some improved > version could even be integrated into the general pandoc documentation. Do you have a Web page or something for this? I was working on something similar for my own purposes (as I likely extend and migrate my data model towards CSL). http://reagle.org/joseph/2013/08/bib-mapping.html -- 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/52431C6C.1070003%40reagle.org. For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <b01350cd-72e7-49e5-aa50-6c25382376f6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-13 14:36 ` John MacFarlane @ 2013-09-13 14:44 ` Bruce D'Arcus 2013-09-27 18:26 ` John MacFarlane 2 siblings, 0 replies; 283+ messages in thread From: Bruce D'Arcus @ 2013-09-13 14:44 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Worth noting that the design of bibutils involves a common target format, that might be analogous to something like pandocs native format. It then has different readers and writers for the different bib formats. This makes it easy to add new formats, and edit existing ones (the C code has a bunch of simple mapping tables). It seems a design like that would make sense here as well? FWIW, I once tried to operationalize this idea in this effort to use some simple json config files to set up the mapping: https://github.com/bdarcus/bibmaps But I never got very far, and am not sure how practical that is (it might be; the tricky part would be how to configure parsing routines for different name and date formats). On Fri, Sep 13, 2013 at 10:26 AM, Nick Bart <nickbart1980-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > Fantastic. I'm amazed by your energy. And, yes, I'd love to contribute. Time > to learn a little Haskell after all, I guess. > > Still, a few questions first: > > 1. Would it make sense to cleanly separate code for bibtex vs. code for > biblatex? Handling of dates, and a number of other things, see below, > differs a lot. > > 2. (How) can the bibtex and biblatex "crossref" mechanism for inheritance be > implemented? (biblatex has introduced an alternative cross-referencing > mechanism using the xref field, but I'm not sure how many people have > actually started using this. I haven't seen any advantage in using this > instead of crossref yet.) > > 3. Some fields will have to be concatenated, > > - title + subtitle + titleaddon (same for booktitle, maintitle), and > journal/journaltitle + journalsubtitle. How will this be handled? > (titleaddon etc. are supposed to be printed "in a different font", i.e., > unitalicized or outside of speech marks, but this currently does not seem to > be possible in CSL.) > > - note + addendum. biblatex has addendum at the end of an entry, and > note somewhere in front of that, but in CSL there's only one suitable field: > note. – Differs from biblatex "annotation" (and its alias "annote") which > map to CSL "annote", and contain reader's notes. > > 4. Some fields have to be omitted if some certain other/newer field(s) are > present: In biblatex, "date", if present, is used instead of "year", > "month", and "day"; "location" instead of "address", etc. How will this be > handled? > > 5. Proper mapping of some fields or entry types is conditional upon either > the existence or the content of other fields. How can this be made to work? > > - for @book, @collection, @proceedings: title ==> title, unless > maintitle exists, in which case maintitle ==> title (and, once consensus on > new CSL variables is reached, title ==> volume-title; as discussed earlier > in this thread), > > - for @inbook, @incollection, @proceedings: booktitle ==> > container-title, unless maintitle exists, in which case maintitle ==> > container-title (and booktitle ==> volume-title), > > - mapping of editor, editora, editorb, editorc depends on the content of > editortype, editoratype, editorbtype, editorctype, > > - An entrysubtype of "magazine" should change the CSL type from > "article-journal" to "article-magazine" (this is not from biblatex itself > but from biblatex-chicago, but I think it'd be very useful to borrow certain > bits from this package; an entrysubtype of "newspaper" could of course map > to CSL "article-newspaper"). > > - series maps to CSL collection-title, except for @article (and > @periodical?), in which case it should appear after the journal title (the > only solution in CSL is probably to concatenate the two fields). > > 6. "keys" are used liberally in biblatex fields, as shorthands, and for > localization (see biblatex manual 4.9). These should be translated to > natural language terms. Let's focus on English first - but what about > localization …? > > 7. In addition to "name lists" (authors etc.), biblatex has "literal lists" > with elements separated by "and", too: institution, location, organization, > origlocation, origpublisher, publisher, list[a-f], address, school. Will > routines used for names work unmodified? > > > > On Friday, 13 September 2013 08:24:45 UTC+2, fiddlosopher wrote: >> >> I've renamed to bibtex2pandoc.hs and made several improvements, >> including parsing of non-dropping-particles. >> >> I've added all the biblatex entry types, and I've started adding support >> for biblatex data fields. (In the biblatex list of data fields, >> 2.2.2 of http://www.math.upenn.edu/tex_docs/latex/biblatex/biblatex.pdf, >> I've gotten as far as 'annotation'.) >> >> Nick, if you (or others) want to work on this, it should be pretty >> self-explanatory how to add to the code, even if you don't know Haskell. >> (Find the part of the code with all the arrows. ==> means the field is >> to be interpreted as latex; --> means it's a raw string; *=> is an >> author list.) >> >> Recompile with 'ghc --make bibtex2pandoc.hs' >> >> John > > -- > You received this message because you are subscribed to a topic in the > Google Groups "pandoc-discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/pandoc-discuss/-SajbqoPX8k/unsubscribe. > To unsubscribe from this group and all its topics, 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/b01350cd-72e7-49e5-aa50-6c25382376f6%40googlegroups.com. > > 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/CAF-FPGN4OCOGUY%2BzfcAAZmobp%3Da2YemLtkvppGPmWdW-KOiu1w%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <b01350cd-72e7-49e5-aa50-6c25382376f6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-13 14:36 ` John MacFarlane 2013-09-13 14:44 ` Bruce D'Arcus @ 2013-09-27 18:26 ` John MacFarlane [not found] ` <20130927182634.GA37542-0VdLhd/A9Pm0ooXD8Eul3deFUF7NV0gRTVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> 2 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-27 18:26 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Nick, I've made some more improvements to bibtex2pandoc.hs, including a kind of monadic domain-specific language for doing the actual mapping. This occurs in the function itemToMetaValue, which you can find in the source. I've tried to set this up so you can modify it without knowing much Haskell. (To compile, you'll need to make sure you've cabal installed pandoc and pandoc-citeproc, and also the bibtex package and perhaps some others. Then: ghc --make bibtex2pandoc) Answers to questions below: +++ Nick Bart [Sep 13 13 07:26 ]: > Fantastic. I'm amazed by your energy. And, yes, I'd love to contribute. > Time to learn a little Haskell after all, I guess. > > Still, a few questions first: > > 1. Would it make sense to cleanly separate code for bibtex vs. code for > biblatex? Handling of dates, and a number of other things, see below, > differs a lot. itemToMetaValue has a boolean parameter 'bibtex' which you can test for in places where we need to distinguish. Example: unless bibtex $ do getField "addendum" ==> appendField "note" (Space:) > 2. (How) can the bibtex and biblatex "crossref" mechanism for inheritance > be implemented? (biblatex has introduced an alternative cross-referencing > mechanism using the xref field, but I'm not sure how many people have > actually started using this. I haven't seen any advantage in using this > instead of crossref yet.) I have implemented this (including the biblatex mappings, if --bibtex isn't used.) > 3. Some fields will have to be concatenated, > > - title + subtitle + titleaddon (same for booktitle, maintitle), and > journal/journaltitle + journalsubtitle. How will this be handled? > (titleaddon etc. are supposed to be printed "in a different font", i.e., > unitalicized or outside of speech marks, but this currently does not seem > to be possible in CSL.) > > - note + addendum. biblatex has addendum at the end of an entry, and > note somewhere in front of that, but in CSL there's only one suitable > field: note. – Differs from biblatex "annotation" (and its alias "annote") > which map to CSL "annote", and contain reader's notes. There's an 'appendField' function. It takes as parameters the target field name and a function of type [Inline] -> [Inline] that says how to transform the thing you're appending (adding a colon, a space, putting it in parentheses, etc.). You can see how this is used in the lines for "subtitle" and "titleaddon" and "addendum". > 4. Some fields have to be omitted if some certain other/newer field(s) are > present: In biblatex, "date", if present, is used instead of "year", > "month", and "day"; "location" instead of "address", etc. How will this be > handled? If you use setField, it will overwrite an existing value. So, for example, if you want "maintitle" to override "title" in setting the "title" value: getField "title" ==> setField "title" getField "maintitle" ==> setField "title" If "maintitle" is not found, the earlier value (from "title") will persist. So we can handle these issues of priority by ordering. > 5. Proper mapping of some fields or entry types is conditional upon either > the existence or the content of other fields. How can this be made to work? > > - for @book, @collection, @proceedings: title ==> title, unless > maintitle exists, in which case maintitle ==> title (and, once consensus on > new CSL variables is reached, title ==> volume-title; as discussed earlier > in this thread), See above for this one. > - for @inbook, @incollection, @proceedings: booktitle ==> > container-title, unless maintitle exists, in which case maintitle ==> > container-title (and booktitle ==> volume-title), hasMaintitle <- isPresent "maintitle" getField "booktitle" ==> setField (if hasMaintitle && et `elem` ["book","collection","proceedings"] then "volume-title" else "container-title") > - mapping of editor, editora, editorb, editorc depends on the content > of editortype, editoratype, editorbtype, editorctype, > > - An entrysubtype of "magazine" should change the CSL type from > "article-journal" to "article-magazine" (this is not from biblatex itself > but from biblatex-chicago, but I think it'd be very useful to borrow > certain bits from this package; an entrysubtype of "newspaper" could of > course map to CSL "article-newspaper"). getRawField "magazine" ==> setRawField "type" "article-magazine" > - series maps to CSL collection-title, except for @article (and > @periodical?), in which case it should appear after the journal title (the > only solution in CSL is probably to concatenate the two fields). getField "series" ==> if et == "article" || et == "periodical" then appendField "title" inParens else setField "collection-title" > 6. "keys" are used liberally in biblatex fields, as shorthands, and for > localization (see biblatex manual 4.9). These should be translated to > natural language terms. Let's focus on English first - but what about > localization …? I'm ignoring this for now. citeproc-hs has its own localization. > 7. In addition to "name lists" (authors etc.), biblatex has "literal lists" > with elements separated by "and", too: institution, location, organization, > origlocation, origpublisher, publisher, list[a-f], address, school. Will > routines used for names work unmodified? These are supported getLiteralList getAuthorList Why don't you try adding to it and see what you can do? John -- 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/20130927182634.GA37542%40dhcp-128-32-252-11.lips.berkeley.edu. For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130927182634.GA37542-0VdLhd/A9Pm0ooXD8Eul3deFUF7NV0gRTVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130927182634.GA37542-0VdLhd/A9Pm0ooXD8Eul3deFUF7NV0gRTVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> @ 2013-09-27 22:38 ` Nick Bart [not found] ` <cfd2f13e-48f4-4b0e-8415-a68597649e17-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-27 22:38 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 13459 bytes --] Brilliant. But quite a challenge, too. Still, here's a diff with some of the more straightforward stuff hacked in. Other comments and questions below. $ diff -u ../pandoc-citeproc/bibtex2pandoc.hs bibtex2pandoc.hs --- ../pandoc-citeproc/bibtex2pandoc.hs 2013-09-27 23:05:15.000000000 +0200 +++ bibtex2pandoc.hs 2013-09-28 00:11:42.000000000 +0200 @@ -240,7 +240,7 @@ "inproceedings" -> setType "paper-conference" "manual" -> setType "book" "mastersthesis" -> setType "thesis" >> - setRawField "genre" "Ph.D. thesis" + setRawField "genre" "Master’s thesis" "misc" -> setType "no-type" "mvbook" -> setType "book" "mvcollection" -> setType "book" @@ -265,12 +265,24 @@ getRawField "type" ==> setRawField "genre" getField "title" ==> setField "title" getField "subtitle" ==> appendField "title" addColon - getField "titleaddon" ==> appendField "title" inParens + getField "titleaddon" ==> appendField "title" addPeriod + getField "maintitle" ==> setField "container-title" + getField "mainsubtitle" ==> appendField "container-title" addColon + getField "maintitleaddon" ==> appendField "container-title" addPeriod hasMaintitle <- isPresent "maintitle" getField "booktitle" ==> setField (if hasMaintitle && - et `elem` ["book","collection","proceedings"] + et `elem` ["inbook","incollection","inproceedings"] then "volume-title" else "container-title") + getField "booksubtitle" ==> appendField (if hasMaintitle && + et `elem` ["inbook","incollection","inproceedings"] + then "volume-title" + else "container-title") addColon + getField "booktitleaddon" ==> appendField (if hasMaintitle && + et `elem` ["inbook","incollection","inproceedings"] + then "volume-title" + else "container-title") addPeriod + getField "shorttitle" ==> setField "title-short" getField "series" ==> setField "collection-title" getField "pages" ==> setField "page" getField "volume" ==> setField "volume" @@ -280,23 +292,53 @@ getField "note" ==> setField "note" getRawField "url" ==> setRawField "url" getField "journal" ==> setField "container-title" + getField "journaltitle" ==> setField "container-title" + getField "journalsubtitle" ==> appendField "container-title" addColon + getField "shortjournal" ==> setField "container-title-short" + getField "howpublished" ==> setField "publisher" getField "school" ==> setField "publisher" - getLiteralList "institution" ==> setList "publisher" + unless bibtex $ do + getLiteralList "institution" ==> setList "publisher" + getField "publisher" ==> setField "publisher" getField "address" ==> setField "publisher-place" + unless bibtex $ do + getField "location" ==> setField "publisher-place" getAuthorList "author" ==> setList "author" getAuthorList "editor" ==> setList "editor" - getField "howpublished" ==> setField "note" getField "abstract" ==> setField "abstract" unless bibtex $ do getField "addendum" ==> appendField "note" (Space:) getField "annotation" ==> setField "annote" + getField "annote" ==> setField "annote" getField "year" ==> setSubField "issued" "year" getField "month" ==> setSubField "issued" "month" - + getAuthorList "translator" ==> setList "translator" + getAuthorList "bookauthor" ==> setList "container-author" + getField "abstract" ==> setField "abstract" + getField "keywords" ==> setField "keyword" + getField "eventdate" ==> setField "event-date" + getField "eventtitle" ==> setField "event" + getLiteralList "venue" ==> setList "event-place" + getRawField "doi" ==> setRawField "DOI" + getRawField "isbn" ==> setRawField "ISBN" + getRawField "issn" ==> setRawField "ISSN" + getField "origdate" ==> setField "original-date" + getLiteralList "origlocation" ==> setList "original-publisher-place" + getLiteralList "origpublisher" ==> setList "original-publisher" + getField "origtitle" ==> setField "original-title" + getField "pagetotal" ==> setField "number-of-pages" + getField "pubstate" ==> setField "status" + getField "urldate" ==> setField "accessed" + getField "version" ==> setField "version" + getField "volumes" ==> setField "number-of-volumes" + getRawField "hyphenation" ==> setRawField "language" addColon :: [Inline] -> [Inline] addColon xs = [Str ":",Space] ++ xs +addPeriod :: [Inline] -> [Inline] +addPeriod xs = [Str ".",Space] ++ xs + inParens :: [Inline] -> [Inline] inParens xs = [Space, Str "("] ++ xs ++ [Str ")"] On Friday, 27 September 2013 18:26:34 UTC, fiddlosopher wrote: > > Nick, > > I've made some more improvements to bibtex2pandoc.hs, including a kind > of monadic domain-specific language for doing the actual mapping. > This occurs in the function itemToMetaValue, which you can find in > the source. I've tried to set this up so you can modify it without > knowing much Haskell. > > (To compile, you'll need to make sure you've cabal installed pandoc > and pandoc-citeproc, and also the bibtex package and perhaps some > others. Then: ghc --make bibtex2pandoc) > > Answers to questions below: > > +++ Nick Bart [Sep 13 13 07:26 ]: > > Fantastic. I'm amazed by your energy. And, yes, I'd love to contribute. > > Time to learn a little Haskell after all, I guess. > > > > Still, a few questions first: > > > > 1. Would it make sense to cleanly separate code for bibtex vs. code for > > biblatex? Handling of dates, and a number of other things, see below, > > differs a lot. > > itemToMetaValue has a boolean parameter 'bibtex' which you can test > for in places where we need to distinguish. Example: > > unless bibtex $ do > getField "addendum" ==> appendField "note" (Space:) > > > 2. (How) can the bibtex and biblatex "crossref" mechanism for > inheritance > > be implemented? (biblatex has introduced an alternative > cross-referencing > > mechanism using the xref field, but I'm not sure how many people have > > actually started using this. I haven't seen any advantage in using this > > instead of crossref yet.) > > I have implemented this (including the biblatex mappings, if --bibtex > isn't used.) > > Hmm, my bib(la)tex crossref example from earlier in this thread gives: --- references: - editor: - family: Editor given: - Ed id: item2 publisher: Publisher publisher-place: Location title: The Collection Title type: book - author: - family: Doe given: - John editor: - family: Editor given: - Ed id: item1 page: '12-34' publisher: Publisher publisher-place: Location title: The Incollection Title type: chapter ... i.e., no container-title in item2. Can't quite see why not ... > > 3. Some fields will have to be concatenated, > > > > - title + subtitle + titleaddon (same for booktitle, maintitle), and > > journal/journaltitle + journalsubtitle. How will this be handled? > > (titleaddon etc. are supposed to be printed "in a different font", i.e., > > unitalicized or outside of speech marks, but this currently does not > seem > > to be possible in CSL.) > > > > - note + addendum. biblatex has addendum at the end of an entry, and > > note somewhere in front of that, but in CSL there's only one suitable > > field: note. – Differs from biblatex "annotation" (and its alias > "annote") > > which map to CSL "annote", and contain reader's notes. > > There's an 'appendField' function. It takes as parameters the > target field name and a function of type [Inline] -> [Inline] that > says how to transform the thing you're appending (adding a colon, > a space, putting it in parentheses, etc.). You can see how this is used > in the lines for "subtitle" and "titleaddon" and "addendum". > > > 4. Some fields have to be omitted if some certain other/newer field(s) > are > > present: In biblatex, "date", if present, is used instead of "year", > > "month", and "day"; "location" instead of "address", etc. How will this > be > > handled? > > If you use setField, it will overwrite an existing value. So, > for example, if you want "maintitle" to override "title" in setting > the "title" value: > > getField "title" ==> setField "title" > getField "maintitle" ==> setField "title" > > If "maintitle" is not found, the earlier value (from "title") will > persist. > So we can handle these issues of priority by ordering. > Fine, have to come to grips with this logic ... > > > 5. Proper mapping of some fields or entry types is conditional upon > either > > the existence or the content of other fields. How can this be made to > work? > > > > - for @book, @collection, @proceedings: title ==> title, unless > > maintitle exists, in which case maintitle ==> title (and, once consensus > on > > new CSL variables is reached, title ==> volume-title; as discussed > earlier > > in this thread), > > See above for this one. > > > - for @inbook, @incollection, @proceedings: booktitle ==> > > container-title, unless maintitle exists, in which case maintitle ==> > > container-title (and booktitle ==> volume-title), > > hasMaintitle <- isPresent "maintitle" > getField "booktitle" ==> setField (if hasMaintitle && > et `elem` > ["book","collection","proceedings"] > then "volume-title" > else "container-title") > Has to be "inbook" etc. here. books never have booktitles. > > > - mapping of editor, editora, editorb, editorc depends on the > content > > of editortype, editoratype, editorbtype, editorctype, > > > > - An entrysubtype of "magazine" should change the CSL type from > > "article-journal" to "article-magazine" (this is not from biblatex > itself > > but from biblatex-chicago, but I think it'd be very useful to borrow > > certain bits from this package; an entrysubtype of "newspaper" could of > > course map to CSL "article-newspaper"). > > getRawField "magazine" ==> setRawField "type" "article-magazine" > Not sure I get this right: It would be @article{key, entrysubtype={magazine}, ... } > > > - series maps to CSL collection-title, except for @article (and > > @periodical?), in which case it should appear after the journal title > (the > > only solution in CSL is probably to concatenate the two fields). > > getField "series" ==> if et == "article" || et == "periodical" > then appendField "title" inParens > else setField "collection-title" > > > 6. "keys" are used liberally in biblatex fields, as shorthands, and for > > localization (see biblatex manual 4.9). These should be translated to > > natural language terms. Let's focus on English first - but what about > > localization …? > > I'm ignoring this for now. citeproc-hs has its own localization. > Yes, but this is about, e.g., pubstate={inpress}, where the "inpress" should be transformed to 'in press'. > > > 7. In addition to "name lists" (authors etc.), biblatex has "literal > lists" > > with elements separated by "and", too: institution, location, > organization, > > origlocation, origpublisher, publisher, list[a-f], address, school. Will > > routines used for names work unmodified? > > These are supported > > getLiteralList > > getAuthorList > > Why don't you try adding to it and see what you can do? > > John > > More questions: - One of the most urgent issues is probably date handling. Currently only "year" works. bibtex has, e.g., year={1990}, month=aug, biblatex prefers the "date" field, and uses year and month only if no date is found. Format is YYYY-MM-DD, YYYY-MM or YYYY. Date ranges are specified by YYYY-MM-DD/YYYY-MM-DD. (CSL specs mention date ranges, but I don't know about the JSON or YAML format.) Partial dates are valid if date components are omitted at the end only. Open ended date ranges have the range separator but no end date (e. g., YYYY/). Again, thanks, and I'll continue to see what I can do. Nick -- 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/cfd2f13e-48f4-4b0e-8415-a68597649e17%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 19374 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <cfd2f13e-48f4-4b0e-8415-a68597649e17-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <cfd2f13e-48f4-4b0e-8415-a68597649e17-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-28 7:16 ` John MacFarlane [not found] ` <20130928071616.GA42338-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-28 7:16 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Excellent. I've merged in your patch. +++ Nick Bart [Sep 27 13 15:38 ]: > Brilliant. But quite a challenge, too. Still, here's a diff with some > of the more straightforward stuff hacked in. Other comments and > questions below. > Hmm, my bib(la)tex crossref example from earlier in this thread gives: > --- > references: > - editor: > - family: Editor > given: > - Ed > id: item2 > publisher: Publisher > publisher-place: Location > title: The Collection Title > type: book > - author: > - family: Doe > given: > - John > editor: > - family: Editor > given: > - Ed > id: item1 > page: '12-34' > publisher: Publisher > publisher-place: Location > title: The Incollection Title > type: chapter > ... > i.e., no container-title in item2. Can't quite see why not ... I'll look into this. > getRawField "magazine" ==> setRawField "type" "article-magazine" > > Not sure I get this right: It would be > @article{key, > entrysubtype={magazine}, > ... > } Yes. I was assumnig that anything with entrysubtype = "magazine" is a magazine article, hence did not check et (entryType). But it could be checked too in a conditional. > > Yes, but this is about, e.g., pubstate={inpress}, where the "inpress" > should be transformed to 'in press'. So how does it work? Is it just a list of strings that are to be expanded macro-like before further processing? > More questions: > - One of the most urgent issues is probably date handling. Currently > only "year" works. > bibtex has, e.g., > year={1990}, > month=aug, > biblatex prefers the "date" field, and uses year and month only if no > date is found. > Format is YYYY-MM-DD, YYYY-MM or YYYY. > Date ranges are specified by YYYY-MM-DD/YYYY-MM-DD. > (CSL specs mention date ranges, but I don't know about the JSON or YAML > format.) > Partial dates are valid if date components are omitted at the end only. > Open ended date ranges have the range separator but no end date (e. g., > YYYY/). I can add something for this, but I'd need to know more about how citeproc dates ("issued") works. Is there any way to indicate a range there? John ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130928071616.GA42338-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130928071616.GA42338-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-28 7:40 ` John MacFarlane [not found] ` <20130928074012.GA42449-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-09-28 9:38 ` Nick Bart 1 sibling, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-28 7:40 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ John MacFarlane [Sep 28 13 00:16 ]: > Excellent. I've merged in your patch. > > +++ Nick Bart [Sep 27 13 15:38 ]: > > Brilliant. But quite a challenge, too. Still, here's a diff with some > > of the more straightforward stuff hacked in. Other comments and > > questions below. > > > Hmm, my bib(la)tex crossref example from earlier in this thread gives: > > --- > > references: > > - editor: > > - family: Editor > > given: > > - Ed > > id: item2 > > publisher: Publisher > > publisher-place: Location > > title: The Collection Title > > type: book > > - author: > > - family: Doe > > given: > > - John > > editor: > > - family: Editor > > given: > > - Ed > > id: item1 > > page: '12-34' > > publisher: Publisher > > publisher-place: Location > > title: The Incollection Title > > type: chapter > > ... > > i.e., no container-title in item2. Can't quite see why not ... > > I'll look into this. There was a typo in the code which I fixed. But it didn't affect this. Looking at Appendix A of the biblatex manual, I'm not seeing a rule for source = book, target = chapter. (Rather, we have source = book, target = inbook, bookinbook, or suppbook.) Am I misunderstanding something? ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130928074012.GA42449-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130928074012.GA42449-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-28 8:43 ` Nick Bart [not found] ` <35b0f493-82e9-486b-838d-09aa3b48a618-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-28 10:52 ` Nick Bart 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-28 8:43 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2502 bytes --] crossref ======== Do you mean "Appendix B: Default Inheritance Setup" (biblatex manual Version 2.7a)? I think you're right, for source type "book" and target type = "inbook, bookinbook, or suppbook"; source field "title" becomes target field "booktitle". Now in my example, item1 should inherit "title" from item2 with the field designation changed to "booktitle". "chapter" is not a biblatex field name, but just the CSL variable corresponding to inbook, bookinbook, suppbook, but also incollection and a few other in-s and supp-s. Dates ===== As to dates, including date ranges, and their format in what appears to be JSON, see the citeproc-js docs: http://gsl-nagoya-u.net/http/pub/citeproc-doc.html#dates magazine ======== If I insert getRawField "magazine" ==> setRawField "type" "article-magazine" I get the following error message: $ ghc --make bibtex2pandoc [1 of 1] Compiling Main ( bibtex2pandoc.hs, bibtex2pandoc.o ) bibtex2pandoc.hs:267:30: Couldn't match type `RWST T () (M.Map String MetaValue) Maybe ()' with `String -> BibM ()' Expected type: String -> BibM () Actual type: BibM () In the return type of a call of `setRawField' Probable cause: `setRawField' is applied to too many arguments In the second argument of `(==>)', namely `setRawField "type" "article-magazine"' In a stmt of a 'do' block: getRawField "magazine" ==> setRawField "type" "article-magazine" Strictly speaking, it should be IF biblatex type is article (or periodical) AND entrysubtype is magazine THEN CSL type becomes article-magazine. One could probably get away with just checking the entrysubtype since it's not so likely entrysubtype=magazine will be used in other types, but stricter checking might be preferable. So far I haven't figured out how to test for multiple criteria using the bibtex2pandoc code though: is that possible? -- 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/35b0f493-82e9-486b-838d-09aa3b48a618%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3213 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <35b0f493-82e9-486b-838d-09aa3b48a618-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <35b0f493-82e9-486b-838d-09aa3b48a618-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-28 17:52 ` John MacFarlane [not found] ` <20130928175258.GA42972-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-28 17:52 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ Nick Bart [Sep 28 13 01:43 ]: > crossref > ======== > Do you mean "Appendix B: Default Inheritance Setup" (biblatex manual > Version 2.7a)? > I think you're right, for source type "book" and target type = "inbook, > bookinbook, > or suppbook"; source field "title" becomes target field "booktitle". > Now in my example, item1 should inherit "title" from item2 with the > field designation changed to "booktitle". > "chapter" is not a biblatex field name, but just the CSL variable > corresponding to inbook, bookinbook, suppbook, but also incollection > and a few other in-s and supp-s. I was confused about a few things, but with the latest code, crossrefs should be working (at least your example works). > Dates > ===== > As to dates, including date ranges, and their format in what appears to > be JSON, see the citeproc-js docs: > http://gsl-nagoya-u.net/http/pub/citeproc-doc.html#dates OK, I see. That's a bit different than I thought. > magazine > ======== > If I insert > getRawField "magazine" ==> setRawField "type" "article-magazine" > I get the following error message: > $ ghc --make bibtex2pandoc > [1 of 1] Compiling Main ( bibtex2pandoc.hs, bibtex2pandoc.o > ) > bibtex2pandoc.hs:267:30: > Couldn't match type `RWST T () (M.Map String MetaValue) Maybe ()' > with `String -> BibM ()' > Expected type: String -> BibM () > Actual type: BibM () > In the return type of a call of `setRawField' > Probable cause: `setRawField' is applied to too many arguments > In the second argument of `(==>)', namely > `setRawField "type" "article-magazine"' > In a stmt of a 'do' block: > getRawField "magazine" ==> setRawField "type" "article-magazine" > Strictly speaking, it should be IF biblatex type is article (or > periodical) AND entrysubtype is magazine THEN CSL type becomes > article-magazine. One could probably get away with just checking the > entrysubtype since it's not so likely entrysubtype=magazine will be > used in other types, but stricter checking might be preferable. So far > I haven't figured out how to test for multiple criteria using the > bibtex2pandoc code though: is that possible? I think I may have made things overly complicated by trying to make them simpler with the artificial ==> operator. Let me think about how to simplify this so it's easier to do conditional logic. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130928175258.GA42972-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130928175258.GA42972-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-28 18:35 ` John MacFarlane [not found] ` <20130928183516.GA43235-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-28 18:35 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ John MacFarlane [Sep 28 13 10:52 ]: > I think I may have made things overly complicated by trying to make > them simpler with the artificial ==> operator. Let me think about > how to simplify this so it's easier to do conditional logic. OK, I've removed the ==> operator. Now we just use the standard monadic bind >>=, together with an 'opt' function. Let me explain with a couple examples: getField "foo" >>= setField "bar" will attempt to get the value of the "foo" field from the bibtex entry. If "foo" is not set, the action will fail, causing the whole conversion to fail (so, this entry will not be translated). If "foo" is set, the value is passed to the function setField "bar" setField takes two arguments, a field name and a value, so setField "bar" takes one argument, the value. Normally we don't want the conversion to fail if the field is not found (though there are exceptions, like the identifier). So normally we'll put the whole combined action under the 'opt' function (opt for optional). opt $ getField "foo" >>= setField "bar" will attempt to get the "foo" field and set the "bar" field of the new entry to its value, but if "foo" is not set, it will just pass on silently rather than causing the whole conversion to fail. Note that $ is just a way of avoiding parentheses: we could have equivalently written opt (getField "foo" >>= setField "bar") We could have also used "do" notation: opt $ do val <- getField "foo" setField "bar" val And you may want to use 'do' notation for things that have complex logic. So, opt $ do val <- getField "foo" if val == "zeb" || bibtex then setField "bar" val else do setField "baz" val getField "zim" >>= setField "zam" Another operator that is useful to know about is ">>". This is sort of like ">>=", but it doesn't "feed" the output of the first operand to the second one. You might use this when you just want to test for a value's presence. So, opt $ getField "foo" >> getField "bar" >>= setField "baz" would set the "baz" field in the pandoc entry to the value of the "bar" field in the bibtex entry, IF the "foo" field is set; otherwise pass on. In 'do' notation this would be opt $ do getField "foo" val <- getField "bar" setField "baz" val Hope this makes things easier. John ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130928183516.GA43235-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130928183516.GA43235-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-28 20:09 ` Nick Bart [not found] ` <93ff8b26-a132-4da8-a75a-09924f725d34-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-28 20:09 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3954 bytes --] Thanks a lot for the rundown. Seems I could try my hand at this now. Still, when I insert opt $ do val <- getField "entrysubtype" if val == "magazine" then setType "article-magazine" else setType "article-journal" into bibtex2pandoc.hs, ghc --make bibtex2pandoc returns the error: [1 of 1] Compiling Main ( bibtex2pandoc.hs, bibtex2pandoc.o ) bibtex2pandoc.hs:277:15: Couldn't match expected type `MetaValue' with actual type `[Char]' In the second argument of `(==)', namely `"magazine"' In the expression: val == "magazine" In a stmt of a 'do' block: if val == "magazine" then setType "article-magazine" else setType "article-journal" Any idea what would be wrong here? On Saturday, September 28, 2013 6:35:16 PM UTC, fiddlosopher wrote: > > +++ John MacFarlane [Sep 28 13 10:52 ]: > > I think I may have made things overly complicated by trying to make > > them simpler with the artificial ==> operator. Let me think about > > how to simplify this so it's easier to do conditional logic. > > OK, I've removed the ==> operator. Now we just use the standard > monadic bind >>=, together with an 'opt' function. > > Let me explain with a couple examples: > > getField "foo" >>= setField "bar" > > will attempt to get the value of the "foo" field from the bibtex > entry. If "foo" is not set, the action will fail, causing the > whole conversion to fail (so, this entry will not be translated). > If "foo" is set, the value is passed to the function > > setField "bar" > > setField takes two arguments, a field name and a value, so > > setField "bar" > > takes one argument, the value. > > Normally we don't want the conversion to fail if the field is > not found (though there are exceptions, like the identifier). > So normally we'll put the whole combined action under the 'opt' > function (opt for optional). > > opt $ getField "foo" >>= setField "bar" > > will attempt to get the "foo" field and set the "bar" field > of the new entry to its value, but if "foo" is not set, it will > just pass on silently rather than causing the whole conversion to > fail. > > Note that $ is just a way of avoiding parentheses: we could have > equivalently written > > opt (getField "foo" >>= setField "bar") > > We could have also used "do" notation: > > opt $ do > val <- getField "foo" > setField "bar" val > > And you may want to use 'do' notation for things that have complex logic. > So, > > opt $ do > val <- getField "foo" > if val == "zeb" || bibtex > then setField "bar" val > else do > setField "baz" val > getField "zim" >>= setField "zam" > > Another operator that is useful to know about is ">>". This is > sort of like ">>=", but it doesn't "feed" the output of the first > operand to the second one. You might use this when you just want > to test for a value's presence. So, > > opt $ getField "foo" >> getField "bar" >>= setField "baz" > > would set the "baz" field in the pandoc entry to the value of the "bar" > field in the bibtex entry, IF the "foo" field is set; otherwise pass > on. > > In 'do' notation this would be > > opt $ do > getField "foo" > val <- getField "bar" > setField "baz" val > > Hope this makes things easier. > > John > > -- 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/93ff8b26-a132-4da8-a75a-09924f725d34%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 5259 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <93ff8b26-a132-4da8-a75a-09924f725d34-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <93ff8b26-a132-4da8-a75a-09924f725d34-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-28 21:33 ` John MacFarlane 0 siblings, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-09-28 21:33 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw There are two problems with your code. First, you need: setType "article-journal" val not setType "article-journal" Note: the following are completely equivalent: (1) do val <- getField "foo" setField "bar" val (2) getField "foo" >>= setField "bar" In the second case you don't need the second parameter on setField, because it is "piped in" by the >>= operator. Second problem (and this is what the message refers to). getField returns a MetaValue, not a string. IF you want a string -- as you must if you want to compare it to a string "magazine" -- then use getRawField instead. +++ Nick Bart [Sep 28 13 13:09 ]: > Thanks a lot for the rundown. Seems I could try my hand at this now. > Still, when I insert > opt $ do > val <- getField "entrysubtype" > if val == "magazine" > then setType "article-magazine" > else setType "article-journal" > into bibtex2pandoc.hs, > ghc --make bibtex2pandoc > returns the error: > [1 of 1] Compiling Main ( bibtex2pandoc.hs, bibtex2pandoc.o > ) > bibtex2pandoc.hs:277:15: > Couldn't match expected type `MetaValue' with actual type `[Char]' > In the second argument of `(==)', namely `"magazine"' > In the expression: val == "magazine" > In a stmt of a 'do' block: > if val == "magazine" then > setType "article-magazine" > else > setType "article-journal" > Any idea what would be wrong here? > On Saturday, September 28, 2013 6:35:16 PM UTC, fiddlosopher wrote: > > +++ John MacFarlane [Sep 28 13 10:52 ]: > > I think I may have made things overly complicated by trying to > make > > them simpler with the artificial ==> operator. Let me think about > > how to simplify this so it's easier to do conditional logic. > OK, I've removed the ==> operator. Now we just use the standard > monadic bind >>=, together with an 'opt' function. > Let me explain with a couple examples: > getField "foo" >>= setField "bar" > will attempt to get the value of the "foo" field from the bibtex > entry. If "foo" is not set, the action will fail, causing the > whole conversion to fail (so, this entry will not be translated). > If "foo" is set, the value is passed to the function > setField "bar" > setField takes two arguments, a field name and a value, so > setField "bar" > takes one argument, the value. > Normally we don't want the conversion to fail if the field is > not found (though there are exceptions, like the identifier). > So normally we'll put the whole combined action under the 'opt' > function (opt for optional). > opt $ getField "foo" >>= setField "bar" > will attempt to get the "foo" field and set the "bar" field > of the new entry to its value, but if "foo" is not set, it will > just pass on silently rather than causing the whole conversion to > fail. > Note that $ is just a way of avoiding parentheses: we could have > equivalently written > opt (getField "foo" >>= setField "bar") > We could have also used "do" notation: > opt $ do > val <- getField "foo" > setField "bar" val > And you may want to use 'do' notation for things that have complex > logic. So, > opt $ do > val <- getField "foo" > if val == "zeb" || bibtex > then setField "bar" val > else do > setField "baz" val > getField "zim" >>= setField "zam" > Another operator that is useful to know about is ">>". This is > sort of like ">>=", but it doesn't "feed" the output of the first > operand to the second one. You might use this when you just want > to test for a value's presence. So, > opt $ getField "foo" >> getField "bar" >>= setField "baz" > would set the "baz" field in the pandoc entry to the value of the > "bar" > field in the bibtex entry, IF the "foo" field is set; otherwise pass > on. > In 'do' notation this would be > opt $ do > getField "foo" > val <- getField "bar" > setField "baz" val > Hope this makes things easier. > John > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/93ff8b26-a132-4da8- > a75a-09924f725d34%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/93ff8b26-a132-4da8-a75a-09924f725d34%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130928074012.GA42449-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-09-28 8:43 ` Nick Bart @ 2013-09-28 10:52 ` Nick Bart [not found] ` <09c521a8-1f44-474b-8829-60dd95cf0f94-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-28 10:52 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 4825 bytes --] 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 <i>for whom the bell tolls</i>' and only extra protection title = {An Analysis of {\textit{For Whom the Bell Tolls}}} would yield title: 'An Analysis of <i>For Whom the Bell Tolls</i>' 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' 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. 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. 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 <i> and </i> for italics <b> and </b> for bold <sub> and </sub> for subscript <sup> and </sup> for superscript <span style="font-variant:small-caps;"> and </span> for smallcaps instead of markdown formatting? (see https://github.com/jgm/pandoc/issues/931, https://www.zotero.org/support/kb/rich_text_bibliography) Small Caps ========== Speaking of small caps: Any plans to add some markdownish formatting commands for small caps to pandoc? -- 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/09c521a8-1f44-474b-8829-60dd95cf0f94%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 5781 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <09c521a8-1f44-474b-8829-60dd95cf0f94-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <09c521a8-1f44-474b-8829-60dd95cf0f94-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-28 17:56 ` John MacFarlane 2013-09-28 19:34 ` John MacFarlane 1 sibling, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-09-28 17:56 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw This is tricky. Right now I'm just using pandoc's latex reader to read the contents of the bibtex/biblatex fields. But this means that '{A}b' and 'Ab' get translated exactly the same way, as Str "Ab", so I can't distinguish between them. One possible solution would be to change the latex reader so that it parses groups as Span elements -- that would not change visible output in any format, but it would allow us to do the "untitlecase" transformation. A bit worried about the cart leading the horse here, though. John +++ 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 <i>for whom the bell tolls</i>' > and only extra protection > title = {An Analysis of {\textit{For Whom the Bell Tolls}}} > would yield > title: 'An Analysis of <i>For Whom the Bell Tolls</i>' > 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' > 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. > 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. > 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 > <i> and </i> for italics > <b> and </b> for bold > <sub> and </sub> for subscript > <sup> and </sup> for superscript > <span style="font-variant:small-caps;"> and </span> for smallcaps > instead of markdown formatting? > (see https://github.com/jgm/pandoc/issues/931, > https://www.zotero.org/support/kb/rich_text_bibliography) > Small Caps > ========== > Speaking of small caps: Any plans to add some markdownish formatting > commands for small caps to pandoc? > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/09c521a8-1f44-474b- > 8829-60dd95cf0f94%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/09c521a8-1f44-474b-8829-60dd95cf0f94%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <09c521a8-1f44-474b-8829-60dd95cf0f94-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-28 17:56 ` John MacFarlane @ 2013-09-28 19:34 ` John MacFarlane [not found] ` <20130928193409.GA45018-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-28 19:34 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ 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 <i>for whom the bell tolls</i>' > and only extra protection > title = {An Analysis of {\textit{For Whom the Bell Tolls}}} > would yield > title: 'An Analysis of <i>For Whom the Bell Tolls</i>' 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 > <i> and </i> for italics > <b> and </b> for bold > <sub> and </sub> for subscript > <sup> and </sup> for superscript > <span style="font-variant:small-caps;"> and </span> for smallcaps > instead of markdown formatting? > (see https://github.com/jgm/pandoc/issues/931, > 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. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130928193409.GA45018-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130928193409.GA45018-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-28 20:37 ` Nick Bart [not found] ` <a86067ec-6b4a-437b-b2f0-3ee666209dae-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-28 21:47 ` Decoupling citeproc and highlighting-kate from pandoc Nick Bart 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-28 20:37 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 7373 bytes --] 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 <i>for whom the bell tolls</i>' > > and only extra protection > > title = {An Analysis of {\textit{For Whom the Bell Tolls}}} > > would yield > > title: 'An Analysis of <i>For Whom the Bell Tolls</i>' > > 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 > > <i> and </i> for italics > > <b> and </b> for bold > > <sub> and </sub> for subscript > > <sup> and </sup> for superscript > > <span style="font-variant:small-caps;"> and </span> for smallcaps > > instead of markdown formatting? > > (see https://github.com/jgm/pandoc/issues/931, > > 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 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/a86067ec-6b4a-437b-b2f0-3ee666209dae%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 9995 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <a86067ec-6b4a-437b-b2f0-3ee666209dae-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <a86067ec-6b4a-437b-b2f0-3ee666209dae-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-28 21:34 ` John MacFarlane [not found] ` <20130928213433.GB45256-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-28 21:34 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw 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 <i>for whom the bell tolls</i>' > > and only extra protection > > title = {An Analysis of {\textit{For Whom the Bell > Tolls}}} > > would yield > > title: 'An Analysis of <i>For Whom the Bell Tolls</i>' > 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 > > <i> and </i> for italics > > <b> and </b> for bold > > <sub> and </sub> for subscript > > <sup> and </sup> for superscript > > <span style="font-variant:small-caps;"> and </span> for > smallcaps > > instead of markdown formatting? > > (see [1]https://github.com/jgm/pandoc/issues/931, > > [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 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 > [3]https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b- > b2f0-3ee666209dae%40googlegroups.com. > For more options, visit [4]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_bibliography > 3. https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae%40googlegroups.com > 4. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130928213433.GB45256-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130928213433.GB45256-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-28 22:19 ` Nick Bart [not found] ` <605aad90-4967-42b9-8efe-0aa033c670da-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-28 22:19 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 10873 bytes --] 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 <i>for whom the bell tolls</i>' > > > and only extra protection > > > title = {An Analysis of {\textit{For Whom the Bell > > Tolls}}} > > > would yield > > > title: 'An Analysis of <i>For Whom the Bell Tolls</i>' > > 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 > > > <i> and </i> for italics > > > <b> and </b> for bold > > > <sub> and </sub> for subscript > > > <sup> and </sup> for superscript > > > <span style="font-variant:small-caps;"> and </span> for > > smallcaps > > > instead of markdown formatting? > > > (see [1]https://github.com/jgm/pandoc/issues/931, > > > [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 pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [3] > https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b- > > b2f0-3ee666209dae%40googlegroups.com. > > For more options, visit [4]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_bibliography > > 3. > https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae%40googlegroups.com > > 4. 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/605aad90-4967-42b9-8efe-0aa033c670da%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 17417 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <605aad90-4967-42b9-8efe-0aa033c670da-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <605aad90-4967-42b9-8efe-0aa033c670da-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-28 22:59 ` John MacFarlane [not found] ` <20130928225947.GA45508-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-28 22:59 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw 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 <i>for whom the bell > tolls</i>' > > > and only extra protection > > > title = {An Analysis of {\textit{For Whom the Bell > > Tolls}}} > > > would yield > > > title: 'An Analysis of <i>For Whom the Bell > Tolls</i>' > > 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 > > > <i> and </i> for italics > > > <b> and </b> for bold > > > <sub> and </sub> for subscript > > > <sup> and </sup> for superscript > > > <span style="font-variant:small-caps;"> and </span> > for > > smallcaps > > > instead of markdown formatting? > > > (see [1][1]https://github.com/jgm/pandoc/issues/931, > > > [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]https://groups.google.com/d/msgid/pandoc-discuss/ > a86067ec-6b4a-437b- > > b2f0-3ee666209dae%[6]40googlegroups.com. > > For more options, visit [4][7]https://groups.google.com/ > groups/opt_out. > > > > References > > > > 1. [8]https://github.com/jgm/pandoc/issues/931 > > 2. [9]https://www.zotero.org/support/kb/rich_text_bibliography > > 3. [10]https://groups.google.com/d/ > msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae% > 40googlegroups.com > > 4. [11]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 > [12]https://groups.google.com/d/msgid/pandoc-discuss/605aad90-4967-42b9 > -8efe-0aa033c670da%40googlegroups.com. > For more options, visit [13]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_bibliography > 3. javascript:/ > 4. javascript:/ > 5. https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b- > 6. http://40googlegroups.com/ > 7. https://groups.google.com/groups/opt_out > 8. https://github.com/jgm/pandoc/issues/931 > 9. https://www.zotero.org/support/kb/rich_text_bibliography > 10. https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae%40googlegroups.com > 11. https://groups.google.com/groups/opt_out > 12. https://groups.google.com/d/msgid/pandoc-discuss/605aad90-4967-42b9-8efe-0aa033c670da%40googlegroups.com > 13. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130928225947.GA45508-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130928225947.GA45508-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-28 23:16 ` Nick Bart [not found] ` <b268960d-ddc1-4346-8535-f90124e1e890-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-28 23:16 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 14861 bytes --] 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 <i>for whom the bell > > tolls</i>' > > > > and only extra protection > > > > title = {An Analysis of {\textit{For Whom the Bell > > > Tolls}}} > > > > would yield > > > > title: 'An Analysis of <i>For Whom the Bell > > Tolls</i>' > > > 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 > > > > <i> and </i> for italics > > > > <b> and </b> for bold > > > > <sub> and </sub> for subscript > > > > <sup> and </sup> for superscript > > > > <span style="font-variant:small-caps;"> and </span> > > for > > > smallcaps > > > > instead of markdown formatting? > > > > (see [1][1]https://github.com/jgm/pandoc/issues/931, > > > > [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]https://groups.google.com/d/msgid/pandoc-discuss/ > > a86067ec-6b4a-437b- > > > b2f0-3ee666209dae%[6]40googlegroups.com. > > > For more options, visit [4][7]https://groups.google.com/ > > groups/opt_out. > > > > > > References > > > > > > 1. [8]https://github.com/jgm/pandoc/issues/931 > > > 2. [9]https://www.zotero.org/support/kb/rich_text_bibliography > > > 3. [10]https://groups.google.com/d/ > > msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae% > > 40googlegroups.com > > > 4. [11]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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [12] > https://groups.google.com/d/msgid/pandoc-discuss/605aad90-4967-42b9 > > -8efe-0aa033c670da%40googlegroups.com. > > For more options, visit [13]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_bibliography > > 3. javascript:/ > > 4. javascript:/ > > 5. > https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b- > > 6. http://40googlegroups.com/ > > 7. https://groups.google.com/groups/opt_out > > 8. https://github.com/jgm/pandoc/issues/931 > > 9. https://www.zotero.org/support/kb/rich_text_bibliography > > 10. > https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae%40googlegroups.com > > 11. https://groups.google.com/groups/opt_out > > 12. > https://groups.google.com/d/msgid/pandoc-discuss/605aad90-4967-42b9-8efe-0aa033c670da%40googlegroups.com > > 13. 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/b268960d-ddc1-4346-8535-f90124e1e890%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 27719 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <b268960d-ddc1-4346-8535-f90124e1e890-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <b268960d-ddc1-4346-8535-f90124e1e890-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-28 23:30 ` Nick Bart [not found] ` <2e3d65a5-01f8-4be5-94b5-2346160886ac-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-28 23:30 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 15718 bytes --] 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 <i>for whom the bell >> > tolls</i>' >> > > > and only extra protection >> > > > title = {An Analysis of {\textit{For Whom the >> Bell >> > > Tolls}}} >> > > > would yield >> > > > title: 'An Analysis of <i>For Whom the Bell >> > Tolls</i>' >> > > 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 >> > > > <i> and </i> for italics >> > > > <b> and </b> for bold >> > > > <sub> and </sub> for subscript >> > > > <sup> and </sup> for superscript >> > > > <span style="font-variant:small-caps;"> and >> </span> >> > for >> > > smallcaps >> > > > instead of markdown formatting? >> > > > (see [1][1]https://github.com/jgm/pandoc/issues/931, >> > > > [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]https://groups.google.com/d/msgid/pandoc-discuss/ >> > a86067ec-6b4a-437b- >> > > b2f0-3ee666209dae%[6]40googlegroups.com. >> > > For more options, visit [4][7]https://groups.google.com/ >> > groups/opt_out. >> > > >> > > References >> > > >> > > 1. [8]https://github.com/jgm/pandoc/issues/931 >> > > 2. [9] >> https://www.zotero.org/support/kb/rich_text_bibliography >> > > 3. [10]https://groups.google.com/d/ >> > msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae% >> > 40googlegroups.com >> > > 4. [11]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] >> https://groups.google.com/d/msgid/pandoc-discuss/605aad90-4967-42b9 >> > -8efe-0aa033c670da%40googlegroups.com. >> > For more options, visit [13]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_bibliography >> > 3. javascript:/ >> > 4. javascript:/ >> > 5. >> https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b- >> > 6. http://40googlegroups.com/ >> > 7. https://groups.google.com/groups/opt_out >> > 8. https://github.com/jgm/pandoc/issues/931 >> > 9. https://www.zotero.org/support/kb/rich_text_bibliography >> > 10. >> https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae%40googlegroups.com >> > 11. https://groups.google.com/groups/opt_out >> > 12. >> https://groups.google.com/d/msgid/pandoc-discuss/605aad90-4967-42b9-8efe-0aa033c670da%40googlegroups.com >> > 13. 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/2e3d65a5-01f8-4be5-94b5-2346160886ac%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 28209 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <2e3d65a5-01f8-4be5-94b5-2346160886ac-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <2e3d65a5-01f8-4be5-94b5-2346160886ac-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-28 23:48 ` Nick Bart [not found] ` <ebae1a26-c6cb-44c4-add2-5dc57f620a4c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-28 23:48 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 16856 bytes --] 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 <i>for whom the bell >>> > tolls</i>' >>> > > > and only extra protection >>> > > > title = {An Analysis of {\textit{For Whom the >>> Bell >>> > > Tolls}}} >>> > > > would yield >>> > > > title: 'An Analysis of <i>For Whom the Bell >>> > Tolls</i>' >>> > > 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 >>> > > > <i> and </i> for italics >>> > > > <b> and </b> for bold >>> > > > <sub> and </sub> for subscript >>> > > > <sup> and </sup> for superscript >>> > > > <span style="font-variant:small-caps;"> and >>> </span> >>> > for >>> > > smallcaps >>> > > > instead of markdown formatting? >>> > > > (see [1][1]https://github.com/jgm/pandoc/issues/931, >>> > > > [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]https://groups.google.com/d/msgid/pandoc-discuss/ >>> > a86067ec-6b4a-437b- >>> > > b2f0-3ee666209dae%[6]40googlegroups.com. >>> > > For more options, visit [4][7]https://groups.google.com/ >>> > groups/opt_out. >>> > > >>> > > References >>> > > >>> > > 1. [8]https://github.com/jgm/pandoc/issues/931 >>> > > 2. [9] >>> https://www.zotero.org/support/kb/rich_text_bibliography >>> > > 3. [10]https://groups.google.com/d/ >>> > msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae% >>> > 40googlegroups.com >>> > > 4. [11]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] >>> https://groups.google.com/d/msgid/pandoc-discuss/605aad90-4967-42b9 >>> > -8efe-0aa033c670da%40googlegroups.com. >>> > For more options, visit [13] >>> 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_bibliography >>> > 3. javascript:/ >>> > 4. javascript:/ >>> > 5. >>> https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b- >>> > 6. http://40googlegroups.com/ >>> > 7. https://groups.google.com/groups/opt_out >>> > 8. https://github.com/jgm/pandoc/issues/931 >>> > 9. https://www.zotero.org/support/kb/rich_text_bibliography >>> > 10. >>> https://groups.google.com/d/msgid/pandoc-discuss/a86067ec-6b4a-437b-b2f0-3ee666209dae%40googlegroups.com >>> > 11. https://groups.google.com/groups/opt_out >>> > 12. >>> https://groups.google.com/d/msgid/pandoc-discuss/605aad90-4967-42b9-8efe-0aa033c670da%40googlegroups.com >>> > 13. 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/ebae1a26-c6cb-44c4-add2-5dc57f620a4c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 29539 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <ebae1a26-c6cb-44c4-add2-5dc57f620a4c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <ebae1a26-c6cb-44c4-add2-5dc57f620a4c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-29 1:25 ` John MacFarlane [not found] ` <20130929012541.GC45785-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-29 1:25 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw 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 <i>for whom the bell > > tolls</i>' > > > > and only extra protection > > > > title = {An Analysis of {\textit{For Whom > the Bell > > > Tolls}}} > > > > would yield > > > > title: 'An Analysis of <i>For Whom the Bell > > Tolls</i>' > > > 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 > > > > <i> and </i> for italics > > > > <b> and </b> for bold > > > > <sub> and </sub> for subscript > > > > <sup> and </sup> for superscript > > > > <span style="font-variant:small-caps;"> and > </span> > > 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-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 > [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 ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130929012541.GC45785-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130929012541.GC45785-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-29 1:41 ` John MacFarlane [not found] ` <20130929014129.GA45834-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-29 1:41 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw 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 <i>for whom the bell > > > tolls</i>' > > > > > and only extra protection > > > > > title = {An Analysis of {\textit{For Whom > > the Bell > > > > Tolls}}} > > > > > would yield > > > > > title: 'An Analysis of <i>For Whom the Bell > > > Tolls</i>' > > > > 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 > > > > > <i> and </i> for italics > > > > > <b> and </b> for bold > > > > > <sub> and </sub> for subscript > > > > > <sup> and </sup> for superscript > > > > > <span style="font-variant:small-caps;"> and > > </span> > > > 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-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 > > [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-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/20130929012541.GC45785%40Johns-MacBook-Pro.local. > For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130929014129.GA45834-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130929014129.GA45834-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-29 11:39 ` Nick Bart [not found] ` <fd944048-488f-4d68-a27e-5db0f5d41723-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-29 22:58 ` Rintze Zelle 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-29 11:39 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 25814 bytes --] 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 <i>for whom the > bell > > > > tolls</i>' > > > > > > and only extra protection > > > > > > title = {An Analysis of {\textit{For Whom > > > the Bell > > > > > Tolls}}} > > > > > > would yield > > > > > > title: 'An Analysis of <i>For Whom the > Bell > > > > Tolls</i>' > > > > > 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 > > > > > > <i> and </i> for italics > > > > > > <b> and </b> for bold > > > > > > <sub> and </sub> for subscript > > > > > > <sup> and </sup> for superscript > > > > > > <span style="font-variant:small-caps;"> > and > > > </span> > > > > 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 <javascript:>. > > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > > 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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > 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. [-- Attachment #2: Type: text/html, Size: 50928 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <fd944048-488f-4d68-a27e-5db0f5d41723-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <fd944048-488f-4d68-a27e-5db0f5d41723-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-29 14:49 ` John MacFarlane [not found] ` <20130929144959.GD1060-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-29 14:49 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ Nick Bart [Sep 29 13 04:39 ]: > 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)? That may be true, but it seems worth doing it right; otherwise we end up with 'language' fields that are invalid. > On a related note, how is per-document localization done in > pandoc(-citeproc)? I'm going to look into this more, but I think it just takes the locale from the environment, and uses it to find appropriate terms for things like "editor". (These can be overridden, I believe, in the CSL files.) In any case, the per-entry 'language' field wouldn't be used for this; rather, we'd want the language for the document containing the bibliography. John ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130929144959.GD1060-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130929144959.GD1060-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-29 17:02 ` John MacFarlane [not found] ` <20130929170210.GA24069-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-09-29 20:49 ` Nick Bart 1 sibling, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-29 17:02 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw On localization keys in biblatex: I looked at the manual. Most of the keys look like things that are handled automatically by citeproc-hs. For example: editor. So we really need to focus on keys that might be used as shorthand in fields. Perhaps things like 'inpreparation' qualify. Nick, could you come up with a list of the keys that are likely to be used in this way, which we must support? ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130929170210.GA24069-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130929170210.GA24069-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-29 20:33 ` Nick Bart [not found] ` <2e05de82-6208-49bf-be01-1f5f710c89de-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-29 20:33 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3590 bytes --] These are the biblatex fields specified as "field(key)", each with possible values - authortype - bookpagination - page - column - line - verse - section - paragraph - editortype - editor - compiler - founder - continuator - redactor - reviser - collaborator - editoratype - see editortype - editorbtype - see editortype - editorctype - see editortype - language - langamerican langbrazilian langcatalan langcroatian langczech langdanish langdutch langenglish langfinnish langfrench langgerman langgreek langitalian langlatin langnorwegian langpolish langportuguese langrussian langspanish langswedish - origlanguage - see language - pagination - page - column - line - verse - section - paragraph - pubstate - inpreparation -> 'in preparation' - submitted -> 'submitted' - forthcoming -> 'forthcoming' - inpress -> 'in press' - prepublished -> 'pre-published' - type - mathesis -> ‘Master’s thesis’ - phdthesis -> ‘PhD thesis’ - candthesis -> ‘Candidate thesis’ - techreport -> ‘technical report’ - resreport -> ‘research report’ - software -> ‘computer software’ - datacd -> ‘data CD’ - audiocd -> audio CD - name[a–c]type What does this mean? - authortype, name[a–c]type are not used in standard styles. - editortype is to be used for determining the CSL item type, though straightforward mapping is mostly difficult; CSL has only "editor", "editorial-director", "director", "composer", "illustrator", "interviewer", or "series editor" (some are rather types of author, though) - pagination, bookpagination: CSL has similar "locator" terms, but I have neither seen them used nor been able to figure out how they work yet. - language, origlanguage describe language(s) of content; have no counterpart in CSL - they are independent of the biblatex field hyphenation which, confusingly, needs to be mapped to the CSL "language" variable and specifies the language (exactly one) of the bibliographic record. - language can describe multilingual works, e.g., language = {langlatin and langgerman}, - In a pinch, bibtex2pandoc could append language and origlanguage info to the note field, but I'm not sure it's worth it. - pubstate and type should be mapped as indicated -- however, unless it is possible to map to a CSL "term" which in turn can be localized (currently CSL offers only "forthcoming", and "in press"), this will be a solution that is limited to English only. Still, short of providing bibtex2pandoc with a language switch and having it produce localized output I have no better idea. Anyway, English only it still better than to have a key such as "mathesis" appear as is in your printed output. On Sunday, 29 September 2013 17:02:10 UTC, fiddlosopher wrote: > > On localization keys in biblatex: > -- 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/2e05de82-6208-49bf-be01-1f5f710c89de%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 4782 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <2e05de82-6208-49bf-be01-1f5f710c89de-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <2e05de82-6208-49bf-be01-1f5f710c89de-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-30 2:51 ` John MacFarlane [not found] ` <20130930025139.GA1405-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-09-30 2:51 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I've added some preliminary support for keys, doing the two translations you indicate below. The code has a hook for locale (which is read from the LANG environment variable), but currently only values for en-US are given (and those are used for unknown locales). +++ Nick Bart [Sep 29 13 13:33 ]: > These are the biblatex fields specified as "field(key)", each with > possible values > - authortype > - bookpagination > - page > - column > - line > - verse > - section > - paragraph > - editortype > - editor > - compiler > - founder > - continuator > - redactor > - reviser > - collaborator > - editoratype - see editortype > - editorbtype - see editortype > - editorctype - see editortype > - language > - langamerican langbrazilian langcatalan langcroatian langczech > langdanish langdutch langenglish langfinnish langfrench langgerman > langgreek langitalian langlatin langnorwegian langpolish langportuguese > langrussian langspanish langswedish > - origlanguage > - see language > - pagination > - page > - column > - line > - verse > - section > - paragraph > - pubstate > - inpreparation -> 'in preparation' > - submitted -> 'submitted' > - forthcoming -> 'forthcoming' > - inpress -> 'in press' > - prepublished -> 'pre-published' > - type > - mathesis -> Masters thesis > - phdthesis -> PhD thesis > - candthesis -> Candidate thesis > - techreport -> technical report > - resreport -> research report > - software -> computer software > - datacd -> data CD > - audiocd -> audio CD > - name[ac]type > What does this mean? > - authortype, name[ac]type are not used in standard styles. > - editortype is to be used for determining the CSL item type, > though straightforward mapping is mostly difficult; CSL has only > "editor", "editorial-director", "director", "composer", "illustrator", > "interviewer", or "series editor" (some are rather types of author, > though) > - pagination, bookpagination: CSL has similar "locator" terms, but > I have neither seen them used nor been able to figure out how they work > yet. > - language, origlanguage describe language(s) of content; have no > counterpart in CSL > - they are independent of the biblatex field hyphenation which, > confusingly, needs to be mapped to the CSL "language" variable and > specifies the language (exactly one) of the bibliographic record. > - language can describe multilingual works, e.g., language = > {langlatin and langgerman}, > - In a pinch, bibtex2pandoc could append language and > origlanguage info to the note field, but I'm not sure it's worth it. > - pubstate and type should be mapped as indicated -- however, > unless it is possible to map to a CSL "term" which in turn can be > localized (currently CSL offers only "forthcoming", and "in press"), > this will be a solution that is limited to English only. Still, short > of providing bibtex2pandoc with a language switch and having it produce > localized output I have no better idea. Anyway, English only it still > better than to have a key such as "mathesis" appear as is in your > printed output. > > On Sunday, 29 September 2013 17:02:10 UTC, fiddlosopher wrote: > > On localization keys in biblatex: > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/2e05de82-6208-49bf- > be01-1f5f710c89de%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/2e05de82-6208-49bf-be01-1f5f710c89de%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20130930025139.GA1405-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20130930025139.GA1405-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-09-30 15:48 ` Nick Bart [not found] ` <e39a1944-d7c8-46d1-80ce-1ee66b8c12bd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-30 15:48 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 12375 bytes --] Here's another patch. Thank you, Rintze, for the link to the CSL language codes. I've added or fixed code for - series, number, and issue fields, - article with entrysubtype= magazine - editortype (unfortunately, the overlap between biblatex and CSL is minimal here; editoratype, editorbtype, editorctype would look exactly the same and can be added easily) - language codes --- ../pandoc-citeproc/bibtex2pandoc.hs 2013-09-30 07:08:21.000000000 +0100 +++ bibtex2pandoc.hs 2013-09-30 16:42:20.000000000 +0100 @@ -241,6 +241,69 @@ where go (Str ys) = Str $ map toLower ys go z = z +toLocale :: String -> String +toLocale "english" = "en-US" -- "en-EN" unavailable in CSL +toLocale "USenglish" = "en-US" +toLocale "american" = "en-US" +toLocale "british" = "en-GB" +toLocale "UKenglish" = "en-GB" +toLocale "canadian" = "en-US" -- "en-CA" unavailable in CSL +toLocale "australian" = "en-GB" -- "en-AU" unavailable in CSL +toLocale "newzealand" = "en-GB" -- "en-NZ" unavailable in CSL +toLocale "afrikaans" = "af-ZA" +toLocale "arabic" = "ar-AR" +toLocale "basque" = "eu" +toLocale "bulgarian" = "bg-BG" +toLocale "catalan" = "ca-AD" +toLocale "croatian" = "hr-HR" +toLocale "czech" = "cs-CZ" +toLocale "danish" = "da-DK" +toLocale "dutch" = "nl-NL" +toLocale "estonian" = "et-EE" +toLocale "finnish" = "fi-FI" +toLocale "canadien" = "fr-CA" +toLocale "acadian" = "fr-CA" +toLocale "french" = "fr-FR" +toLocale "francais" = "fr-FR" +toLocale "austrian" = "de-AT" +toLocale "naustrian" = "de-AT" +toLocale "german" = "de-DE" +toLocale "germanb" = "de-DE" +toLocale "ngerman" = "de-DE" +toLocale "greek" = "el-GR" +toLocale "polutonikogreek" = "el-GR" +toLocale "hebrew" = "he-IL" +toLocale "hungarian" = "hu-HU" +toLocale "icelandic" = "is-IS" +toLocale "italian" = "it-IT" +toLocale "japanese" = "ja-JP" +toLocale "Khmer" = "km-KH" +toLocale "latvian" = "lv-LV" +toLocale "lithuanian" = "lt-LT" +toLocale "magyar" = "hu-HU" +toLocale "mongolian" = "mn-MN" +toLocale "norsk" = "nb-NO" +toLocale "nynorsk" = "nn-NO" +toLocale "Persian" = "fa-IR" +toLocale "polish" = "pl-PL" +toLocale "brazil" = "pt-BR" +toLocale "brazilian" = "pt-BR" +toLocale "portugues" = "pt-PT" +toLocale "portuguese" = "pt-PT" +toLocale "romanian" = "ro-RO" +toLocale "russian" = "ru-RU" +toLocale "serbian" = "sr-RS" +toLocale "serbianc" = "sr-RS" +toLocale "slovak" = "sk-SK" +toLocale "slovene" = "sl-SL" +toLocale "spanish" = "es-ES" +toLocale "swedish" = "sv-SE" +toLocale "thai" = "th-TH" +toLocale "turkish" = "tr-TR" +toLocale "ukrainian" = "uk-UA" +toLocale "vietnamese" = "vi-VN" +toLocale _ = "" + itemToMetaValue :: Lang -> Bool -> T -> MetaValue itemToMetaValue lang bibtex = bibItem $ do getId >>= setRawField "id" @@ -282,6 +345,14 @@ "unpublished" -> setType "manuscript" "www" -> setType "webpage" _ -> setType "no-type" + + opt $ do + val <- getRawField "entrysubtype" + if et == "article" && val == "magazine" then + setType "article-magazine" + else + return () + opt $ getRawField "type" >>= setRawField "genre" . resolveKey lang hyphenation <- getRawField "hyphenation" <|> return "english" let processTitle = if (map toLower hyphenation) `elem` @@ -317,7 +388,13 @@ opt $ getField "series" >>= setField "collection-title" . processTitle opt $ getField "pages" >>= setField "page" opt $ getField "volume" >>= setField "volume" - opt $ getField "number" >>= setField "number" + opt $ getField "number" >>= + setField (if et `elem` ["report"] + then "number" + else if et `elem` ["article", "periodical"] + then "issue" + else "collection-number") + opt $ getField "issue" >>= appendField "issue" addComma opt $ getField "chapter" >>= setField "chapter-number" opt $ getField "edition" >>= setField "edition" opt $ getField "note" >>= setField "note" @@ -334,8 +411,36 @@ opt $ getField "address" >>= setField "publisher-place" unless bibtex $ do opt $ getField "location" >>= setField "publisher-place" + opt $ getAuthorList "author" >>= setList "author" - opt $ getAuthorList "editor" >>= setList "editor" + opt $ do + val <- getRawField "editortype" + getAuthorList "editor" >>= setList ( + case val of + "" -> "editor" -- from here on biblatex & CSL + "editor" -> "editor" + "compiler" -> "editor" -- from here on biblatex only + "founder" -> "editor" + "continuator" -> "editor" + "redactor" -> "editor" + "reviser" -> "editor" + "collaborator" -> "editor" + "director" -> "director" -- from here on biblatex-chicago & CSL +-- "conductor" -> "" -- from here on biblatex-chicago only +-- "producer" -> "" +-- "none" -> "" -- = performer +-- "" -> "editorial-director" -- from here on CSL only +-- "" -> "composer" +-- "" -> "illustrator" +-- "" -> "interviewer" +-- "" -> "collection-editor" + _ -> "editor") + +-- FIXME: add same for editora, editorb, editorc + + opt $ getAuthorList "director" >>= setList "director" + -- director from biblatex-apa, which has also producer, writer, execproducer (FIXME?) + opt $ getField "abstract" >>= setField "abstract" unless bibtex $ do opt $ getField "addendum" >>= appendField "note" (Space:) @@ -363,11 +468,14 @@ opt $ getField "urldate" >>= setField "accessed" opt $ getField "version" >>= setField "version" opt $ getField "volumes" >>= setField "number-of-volumes" - opt $ getRawField "hyphenation" >>= setRawField "language" + opt $ getRawField "hyphenation" >>= setRawField "language" . toLocale addColon :: [Inline] -> [Inline] addColon xs = [Str ":",Space] ++ xs +addComma :: [Inline] -> [Inline] +addComma xs = [Str ",",Space] ++ xs + addPeriod :: [Inline] -> [Inline] addPeriod xs = [Str ".",Space] ++ xs @@ -440,7 +548,7 @@ "forthcoming" -> "forthcoming" "inpress" -> "in press" "prepublished" -> "pre-published" - "mathesis" -> "Masters thesis" + "mathesis" -> "Master’s thesis" "phdthesis" -> "PhD thesis" "candthesis" -> "Candidate thesis" "techreport" -> "technical report" On Monday, September 30, 2013 2:51:39 AM UTC, fiddlosopher wrote: > > I've added some preliminary support for keys, doing the two translations > you indicate below. The code has a hook for locale (which is read from > the LANG environment variable), but currently only values for en-US > are given (and those are used for unknown locales). > > +++ Nick Bart [Sep 29 13 13:33 ]: > > These are the biblatex fields specified as "field(key)", each with > > possible values > > - authortype > > - bookpagination > > - page > > - column > > - line > > - verse > > - section > > - paragraph > > - editortype > > - editor > > - compiler > > - founder > > - continuator > > - redactor > > - reviser > > - collaborator > > - editoratype - see editortype > > - editorbtype - see editortype > > - editorctype - see editortype > > - language > > - langamerican langbrazilian langcatalan langcroatian langczech > > langdanish langdutch langenglish langfinnish langfrench langgerman > > langgreek langitalian langlatin langnorwegian langpolish > langportuguese > > langrussian langspanish langswedish > > - origlanguage > > - see language > > - pagination > > - page > > - column > > - line > > - verse > > - section > > - paragraph > > - pubstate > > - inpreparation -> 'in preparation' > > - submitted -> 'submitted' > > - forthcoming -> 'forthcoming' > > - inpress -> 'in press' > > - prepublished -> 'pre-published' > > - type > > - mathesis -> Masters thesis > > - phdthesis -> PhD thesis > > - candthesis -> Candidate thesis > > - techreport -> technical report > > - resreport -> research report > > - software -> computer software > > - datacd -> data CD > > - audiocd -> audio CD > > - name[ac]type > > What does this mean? > > - authortype, name[ac]type are not used in standard styles. > > - editortype is to be used for determining the CSL item type, > > though straightforward mapping is mostly difficult; CSL has only > > "editor", "editorial-director", "director", "composer", > "illustrator", > > "interviewer", or "series editor" (some are rather types of author, > > though) > > - pagination, bookpagination: CSL has similar "locator" terms, > but > > I have neither seen them used nor been able to figure out how they > work > > yet. > > - language, origlanguage describe language(s) of content; have no > > counterpart in CSL > > - they are independent of the biblatex field hyphenation > which, > > confusingly, needs to be mapped to the CSL "language" variable and > > specifies the language (exactly one) of the bibliographic record. > > - language can describe multilingual works, e.g., language = > > {langlatin and langgerman}, > > - In a pinch, bibtex2pandoc could append language and > > origlanguage info to the note field, but I'm not sure it's worth it. > > - pubstate and type should be mapped as indicated -- however, > > unless it is possible to map to a CSL "term" which in turn can be > > localized (currently CSL offers only "forthcoming", and "in press"), > > this will be a solution that is limited to English only. Still, short > > of providing bibtex2pandoc with a language switch and having it > produce > > localized output I have no better idea. Anyway, English only it still > > better than to have a key such as "mathesis" appear as is in your > > printed output. > > > > On Sunday, 29 September 2013 17:02:10 UTC, fiddlosopher wrote: > > > > On localization keys in biblatex: > > > > -- > > 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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [1] > https://groups.google.com/d/msgid/pandoc-discuss/2e05de82-6208-49bf- > > be01-1f5f710c89de%40googlegroups.com. > > For more options, visit [2]https://groups.google.com/groups/opt_out. > > > > References > > > > 1. > https://groups.google.com/d/msgid/pandoc-discuss/2e05de82-6208-49bf-be01-1f5f710c89de%40googlegroups.com > > 2. 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/e39a1944-d7c8-46d1-80ce-1ee66b8c12bd%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 19826 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <e39a1944-d7c8-46d1-80ce-1ee66b8c12bd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <e39a1944-d7c8-46d1-80ce-1ee66b8c12bd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-30 16:07 ` John MacFarlane 2013-09-30 18:59 ` Benct Philip jonsson 1 sibling, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-09-30 16:07 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Applied, thanks. ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <e39a1944-d7c8-46d1-80ce-1ee66b8c12bd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-09-30 16:07 ` John MacFarlane @ 2013-09-30 18:59 ` Benct Philip jonsson [not found] ` <5249C9FC.4010603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Benct Philip jonsson @ 2013-09-30 18:59 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw 2013-09-30 17:48, Nick Bart skrev: > +toLocale "Persian" = "fa-IR" Is uppercase 'P' a typo here? All the codes except 'USenglish', 'UKenglish', 'Khmer' and 'Persian' are all-lowercase. /bpj ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <5249C9FC.4010603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <5249C9FC.4010603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> @ 2013-09-30 20:04 ` Nick Bart [not found] ` <f61e532e-8d2b-4264-83ce-41e15ca2adea-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-30 20:04 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: bpj-J3H7GcXPSITLoDKTGw+V6w [-- Attachment #1: Type: text/plain, Size: 6420 bytes --] Another patch. Thank you, bpj, for catching the typo: should be "farsi". And Khmer is known to CSL, but not to babel. Other fixes: - fixed editortype routine which did not reliably set CSL editor variable if editortype was nonexistent. (If there's a simpler way, please fix.) - doi, isbn, issn are shown uppercase in http://citationstyles.org/downloads/specification.html#appendix-iv-variables, but didn't work unless lowercase here. - decided to try concatenating school, institution, organization, howpublished, publisher (which all go to CSL "publisher"). Most don't co-occur, but a few do, and if so, no info will be lost. Comments on whether this works well in the wild are welcome. --- ../pandoc-citeproc/bibtex2pandoc.hs 2013-09-30 18:04:12.000000000 +0100 +++ bibtex2pandoc.hs 2013-09-30 20:51:48.000000000 +0100 @@ -277,14 +277,13 @@ toLocale "icelandic" = "is-IS" toLocale "italian" = "it-IT" toLocale "japanese" = "ja-JP" -toLocale "Khmer" = "km-KH" toLocale "latvian" = "lv-LV" toLocale "lithuanian" = "lt-LT" toLocale "magyar" = "hu-HU" toLocale "mongolian" = "mn-MN" toLocale "norsk" = "nb-NO" toLocale "nynorsk" = "nn-NO" -toLocale "Persian" = "fa-IR" +toLocale "farsi" = "fa-IR" toLocale "polish" = "pl-PL" toLocale "brazil" = "pt-BR" toLocale "brazilian" = "pt-BR" @@ -403,45 +402,56 @@ opt $ getField "journaltitle" >>= setField "container-title" opt $ getField "journalsubtitle" >>= appendField "container-title" addColon opt $ getField "shortjournal" >>= setField "container-title-short" - opt $ getField "howpublished" >>= setField "publisher" - opt $ getField "school" >>= setField "publisher" - unless bibtex $ do - opt $ getLiteralList "institution" >>= setList "publisher" - opt $ getField "publisher" >>= setField "publisher" + +-- opt $ getField "school" >>= setField "publisher" +-- opt $ getField "institution" >>= setField "publisher" +-- opt $ getField "organization" >>= setField "publisher" +-- opt $ getField "howpublished" >>= setField "publisher" +-- opt $ getField "publisher" >>= setField "publisher" + + opt $ getField "school" >>= appendField "publisher" addComma + opt $ getField "institution" >>= appendField "publisher" addComma + opt $ getField "organization" >>= appendField "publisher" addComma + opt $ getField "howpublished" >>= appendField "publisher" addComma + opt $ getField "publisher" >>= appendField "publisher" addComma + opt $ getField "address" >>= setField "publisher-place" unless bibtex $ do opt $ getField "location" >>= setField "publisher-place" opt $ getAuthorList "author" >>= setList "author" - opt $ do - val <- getRawField "editortype" - getAuthorList "editor" >>= setList ( - case val of - "" -> "editor" -- from here on biblatex & CSL - "editor" -> "editor" - "compiler" -> "editor" -- from here on biblatex only - "founder" -> "editor" - "continuator" -> "editor" - "redactor" -> "editor" - "reviser" -> "editor" - "collaborator" -> "editor" - "director" -> "director" -- from here on biblatex-chicago & CSL --- "conductor" -> "" -- from here on biblatex-chicago only --- "producer" -> "" --- "none" -> "" -- = performer --- "" -> "editorial-director" -- from here on CSL only --- "" -> "composer" --- "" -> "illustrator" --- "" -> "interviewer" --- "" -> "collection-editor" - _ -> "editor") + hasEditortype <- isPresent "editortype" + if hasEditortype then + opt $ do + val <- getRawField "editortype" + getAuthorList "editor" >>= setList ( + case val of + "editor" -> "editor" -- from here on biblatex & CSL + "compiler" -> "editor" -- from here on biblatex only + "founder" -> "editor" + "continuator" -> "editor" + "redactor" -> "editor" + "reviser" -> "editor" + "collaborator" -> "editor" + "director" -> "director" -- from here on biblatex-chicago & CSL + -- "conductor" -> "" -- from here on biblatex-chicago only + -- "producer" -> "" + -- "none" -> "" -- = performer + -- "" -> "editorial-director" -- from here on CSL only + -- "" -> "composer" + -- "" -> "illustrator" + -- "" -> "interviewer" + -- "" -> "collection-editor" + _ -> "editor") + else + getAuthorList "editor" >>= setList "editor" + -- FIXME: add same for editora, editorb, editorc opt $ getAuthorList "director" >>= setList "director" -- director from biblatex-apa, which has also producer, writer, execproducer (FIXME?) - opt $ getField "abstract" >>= setField "abstract" unless bibtex $ do opt $ getField "addendum" >>= appendField "note" (Space:) opt $ getField "annotation" >>= setField "annote" @@ -455,9 +465,9 @@ opt $ getField "eventdate" >>= setField "event-date" opt $ getField "eventtitle" >>= setField "event" opt $ getLiteralList "venue" >>= setList "event-place" - opt $ getRawField "doi" >>= setRawField "DOI" - opt $ getRawField "isbn" >>= setRawField "ISBN" - opt $ getRawField "issn" >>= setRawField "ISSN" + opt $ getRawField "doi" >>= setRawField "doi" + opt $ getRawField "isbn" >>= setRawField "isbn" + opt $ getRawField "issn" >>= setRawField "issn" opt $ getField "origdate" >>= setField "original-date" opt $ getLiteralList "origlocation" >>= setList "original-publisher-place" -- 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/f61e532e-8d2b-4264-83ce-41e15ca2adea%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 11122 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <f61e532e-8d2b-4264-83ce-41e15ca2adea-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <f61e532e-8d2b-4264-83ce-41e15ca2adea-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-09-30 21:31 ` Nick Bart [not found] ` <66a61c32-a3b4-45c2-b548-442592eab56d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-09-30 21:31 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw; +Cc: bpj-J3H7GcXPSITLoDKTGw+V6w [-- Attachment #1: Type: text/plain, Size: 790 bytes --] Note that in the patch above, hasEditortype <- isPresent "editortype" if hasEditortype then opt $ do should read: hasEditortype <- isPresent "editortype" opt $ if hasEditortype then do Apologies. -- 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/66a61c32-a3b4-45c2-b548-442592eab56d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1126 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <66a61c32-a3b4-45c2-b548-442592eab56d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <66a61c32-a3b4-45c2-b548-442592eab56d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-01 2:49 ` John MacFarlane [not found] ` <20131001024928.GA24084-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-01 2:49 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Thanks, patch applied. I'm beginning to rethink the general approach a bit. Currently bibtex2pandoc reads the bibtex file, converts it to a pandoc 'MetaValue', and uses the markdown writer to write it out as YAML metadata. This is fairly nice if you want to convert a bibtex file to a format in which it can be used inline in pandoc, but it makes less sense if you're using an external bibtex file as your bibliography. For that, it would make more sense to convert directly to a list of citeproc Reference objects. We've defined ToJSON and FromJSON instances for these, so it's easy to convert to JSON or YAML (that's what biblio2yaml does). However, the YAML produced will be slightly different: it will have <i>this</i> kind of emphasis instead of *standard markdown* emphasis, for example. It seems that ultimately we're going to want to integrate the code we're writing into pandoc-citeproc itself, so that we can avoid the bibutils conversion step when using bibtex/biblatex bibliographies. That suggests targeting [Reference] rather than MetaValue. (So, we'd fold the code into a new module in pandoc-citeproc library, and biblio2yaml could be used for the conversion.) Thoughts? +++ Nick Bart [Sep 30 13 14:31 ]: > Note that in the patch above, > hasEditortype <- isPresent "editortype" > if hasEditortype then > opt $ do > should read: > hasEditortype <- isPresent "editortype" > opt $ if hasEditortype > then do > Apologies. > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/66a61c32-a3b4-45c2- > b548-442592eab56d%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/66a61c32-a3b4-45c2-b548-442592eab56d%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131001024928.GA24084-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131001024928.GA24084-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-01 9:24 ` Nick Bart [not found] ` <15bfac5e-d7df-476c-8a42-193962e6bca3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-01 9:24 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 4062 bytes --] Sounds very good. Ideally, I feel, bibtex2pandoc would do three things: (1) convert biblatex/bibtex to YAML metadata ready for insertion into a pandoc document (as it currently does), (2) convert biblatex/bibtex to YAML written to a file that can be read in again by, e.g., `pandoc --bibliography bibfile.yaml`, and (3) convert biblatex/bibtex to "a list of citeproc Reference objects" fit for immediate consumption by pandoc-citeproc. Except for file headers etc., I imagine all of these could use essentially the very same format. As to inline formatting, I would not mind having <i>emph</i> instead of *emph* in these data at all. One suggestion, though: Readability would improve if (1) empty lines could be added between entries and (2) id, title, author, editor, and date could be moved to the top of each entry. And a command line option could be added for suppressing fields such as abstract, keywords, annote/annotation which are usually not needed for formatting bibliographies (except annotated ones, that is). Apart from that, at this stage a few issues remain that I cannot fix alone: - date handling (date, urldate, etc. are essential fields in biblatex; many biblatex users do not even use "year" fields any longer). - handling of name prefixes and suffixes (I'll see what I can contribute) - handling of multiple publishers, locations, and other "literal list" field components: Having "getLiteralList", as intended, split such fields into components would be the cleanest solution, but pandoc-citeproc currently does not accept arrays (thus I've mostly replaced "getLiteralList" by "getField" for now), so it would have to be modified. In addition, I came across two issues that are most likely pandoc-citeproc issues: - Extra strings such as "Edited & translated by." in pandoc output. This has been reported here in detail: https://code.google.com/p/citeproc-hs/issues/detail?id=92 - Very long titles in non-English languages: Spanish (French, German, too): Linebreak after title, before '.”' $ cat vlt-es.md Foo [@item1, p. 12]. # References --- references: - author: - family: Author given: - Al container-title: 'Journaltitle' id: item1 issue: 3 issued: year: 2012 language: 'es-ES' page: 'S12-S34' title: | A very very very very very very very very very very very very very very very long title type: 'article-journal' volume: 5 ... $ pandoc --filter pandoc-citeproc vlt-es.md -t markdown-citations Foo (Author 2012, 12). <div class="references"> References ========== Author, Al. 2012. “A very very very very very very very very very very very very very very very long title .” *Journaltitle* 5 (3): S12–S34. </div> English: no such linebreak $ cat vlt-en.md Foo [@item1, p. 12]. # References --- references: - author: - family: Author given: - Al container-title: 'Journaltitle' id: item1 issue: 3 issued: year: 2012 language: 'en-EN' page: 'S12-S34' title: | A very very very very very very very very very very very very very very very long title type: 'article-journal' volume: 5 ... $ pandoc --filter pandoc-citeproc vlt-en.md -t markdown-citations Foo (Author 2012, 12). <div class="references"> References ========== Author, Al. 2012. “A Very Very Very Very Very Very Very Very Very Very Very Very Very Very Very Long Title.” *Journaltitle* 5 (3): S12–S34. </div> -- 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/15bfac5e-d7df-476c-8a42-193962e6bca3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 4544 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <15bfac5e-d7df-476c-8a42-193962e6bca3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <15bfac5e-d7df-476c-8a42-193962e6bca3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-01 11:06 ` Nick Bart [not found] ` <f93e4825-005b-42e0-85f1-e7964da2887d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-05 5:19 ` fiddlosopher 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-01 11:06 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1756 bytes --] Issue: Term “vols.” after number-of-volumes missing ============================================ This might be a pandoc-citeproc issue: $ cat test.md Foo [@item1, p. 12]. # References --- references: - author: - family: Author given: - Al id: item1 issued: year: 2013 language: 'en-US' number-of-volumes: 5 publisher: Publisher publisher-place: Location title: Title of the Book type: book ... $ pandoc -S --filter pandoc-citeproc -t markdown-citations test.md Foo (Author 2013, 12). <div class="references"> References ========== Author, Al. 2013. *Title of the Book*. 5. Location: Publisher. </div> Expected output is: Author, Al. 2013. *Title of the Book*. 5 vols. Location: Publisher. Same effect with other CSL style files. Does work as expected in Zotero. chicago-author-date.csl contains the following, which looks ok: <number variable="number-of-volumes" form="numeric"/> <text term="volume" form="short" prefix=" " plural="true"/> By the way, I've been wondering, is it intentional that <div class="references"> ... </div> appears in the markdown output format? -- 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/f93e4825-005b-42e0-85f1-e7964da2887d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2248 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <f93e4825-005b-42e0-85f1-e7964da2887d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <f93e4825-005b-42e0-85f1-e7964da2887d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-01 14:19 ` Nick Bart 2013-10-01 14:21 ` Nick Bart 2013-10-05 5:23 ` fiddlosopher 2 siblings, 0 replies; 283+ messages in thread From: Nick Bart @ 2013-10-01 14:19 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3967 bytes --] On name parsing (2013-10-01 15:33) =============================== First, the target format. CSL gives the following specs, see <http://citationstyles.org/downloads/specification.html>: >Personal names require a "family" name-part, and may also contain "given", "suffix", "non-dropping-particle" and "dropping-particle" name-parts. These name-parts are defined as: >- "family" - surname minus any particles and suffixes >- "given" - given names, either full ("John Edward") or initialized ("J. E.") >- "suffix" - name suffix, e.g. "Jr." in "John Smith Jr." and "III" in "Bill Gates III" >- "non-dropping-particle" - name particles that are not dropped when only the surname is shown ("de" in the Dutch surname "de Koning") but which may be treated separately from the family name, e.g. for sorting >- "dropping-particle" - name particles that are dropped when only the surname is shown ("van" in "Ludwig van Beethoven", which becomes "Beethoven") Second, bibtex. Its name parsing algorithms are described rather fully in “Tame the BeaST”, <http://mirrors.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf>. In a nutshell, valid formats are: - First von Last - von Last, First - von Last, Jr, First ... which can be identified by counting the number of commas. It seems that an uppercase "von" part, or prefix is recognized as a prefix if it is enclosed in curly braces, or at least its first letter(s) are -- Example: `author = "{D}e {L}a Cruz, Maria"` where `{D}e {L}a` is the prefix (“Tame the BeaST”, § 13.2) It appears - though I must admit I haven't really checked - that biblatex uses the same algorithms. The only extension for biblatex appears to be that it has one additional way of specifying the character of the prefix in the "options" field. From the biblatex manual (v 2.7a): > useprefix=true, false default: false > Whether the name prefix (von, van, of, da, de, della, etc.) is considered when printing the last name in citations. [...] 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. I take this to mean that if a biblatex entry contains `options={useprefix=false}`, the "von part" should be considered to be a "dropping-particle"; if it contains `options={useprefix=true}`, the "von part" should be considered to be a "non-dropping-particle". In addition, biblatex’s `sortname` field might contain some useful information as well: For example, `author={Jean de La Fontaine}` would be parsed into - First = "Jean" - von = "de" - Last = "La Fontaine" However, assuming this particular entry also contained `sortname={Fontaine}`, the conclusion could be drawn that the "La" from "La Fontaine" is to be understood as a "non-dropping-particle". The useprefix option is of course set per entry, so it cannot be expected to handle - hopefully rare - cases with two or more authors with conflicting prefix requirements. Neither would the sortname heuristic work for any name except for the first one, but then again, the others would not be used for sorting anyway. Comments are welcome! -- 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/6e1172e2-04e5-43e2-b77a-baca29fc5d88%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 4281 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <f93e4825-005b-42e0-85f1-e7964da2887d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-01 14:19 ` Nick Bart @ 2013-10-01 14:21 ` Nick Bart 2013-10-05 5:23 ` fiddlosopher 2 siblings, 0 replies; 283+ messages in thread From: Nick Bart @ 2013-10-01 14:21 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3923 bytes --] On name parsing =============== First, the target format. CSL gives the following specs, see <http://citationstyles.org/downloads/specification.html>: >Personal names require a "family" name-part, and may also contain "given", "suffix", "non-dropping-particle" and "dropping-particle" name-parts. These name-parts are defined as: >- "family" - surname minus any particles and suffixes >- "given" - given names, either full ("John Edward") or initialized ("J. E.") >- "suffix" - name suffix, e.g. "Jr." in "John Smith Jr." and "III" in "Bill Gates III" >- "non-dropping-particle" - name particles that are not dropped when only the surname is shown ("de" in the Dutch surname "de Koning") but which may be treated separately from the family name, e.g. for sorting >- "dropping-particle" - name particles that are dropped when only the surname is shown ("van" in "Ludwig van Beethoven", which becomes "Beethoven") Second, bibtex. Its name parsing algorithms are described rather fully in “Tame the BeaST”, <http://mirrors.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf>. In a nutshell, valid formats are: - First von Last - von Last, First - von Last, Jr, First ... which can be identified by counting the number of commas. It seems that an uppercase "von" part, or prefix is recognized as a prefix if it is enclosed in curly braces, or at least its first letter(s) are -- Example: `author = "{D}e {L}a Cruz, Maria"` where `{D}e {L}a` is the prefix (“Tame the BeaST”, § 13.2) It appears - though I must admit I haven't really checked - that biblatex uses the same algorithms. The only extension for biblatex appears to be that it has one additional way of specifying the character of the prefix in the "options" field. From the biblatex manual (v 2.7a): > useprefix=true, false default: false > Whether the name prefix (von, van, of, da, de, della, etc.) is considered when printing the last name in citations. [...] 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. I take this to mean that if a biblatex entry contains `options={useprefix=false}`, the "von part" should be considered to be a "dropping-particle"; if it contains `options={useprefix=true}`, the "von part" should be considered to be a "non-dropping-particle". In addition, biblatex’s `sortname` field might contain some useful information as well: For example, `author={Jean de La Fontaine}` would be parsed into - First = "Jean" - von = "de" - Last = "La Fontaine" However, assuming this particular entry also contained `sortname={Fontaine}`, the conclusion could be drawn that the "La" from "La Fontaine" is to be understood as a "non-dropping-particle". The useprefix option is of course set per entry, so it cannot be expected to handle - hopefully rare - cases with two or more authors with conflicting prefix requirements. Neither would the sortname heuristic work for any name except for the first - but then gain, these would not be used for sorting anyway. Comments are welcome! -- 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/fa1df90f-6ca5-43f2-a0d8-ec413aab1bb8%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 4237 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <f93e4825-005b-42e0-85f1-e7964da2887d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-01 14:19 ` Nick Bart 2013-10-01 14:21 ` Nick Bart @ 2013-10-05 5:23 ` fiddlosopher [not found] ` <d52d9518-9832-45c3-96a0-c3d5b9de3090-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2 siblings, 1 reply; 283+ messages in thread From: fiddlosopher @ 2013-10-05 5:23 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1859 bytes --] On Tuesday, October 1, 2013 4:06:40 AM UTC-7, Nick Bart wrote: > > Issue: Term “vols.” after number-of-volumes missing > ============================================ > > This might be a pandoc-citeproc issue: > > $ cat test.md > Foo [@item1, p. 12]. > > # References > > --- > references: > - author: > - family: Author > given: > - Al > id: item1 > issued: > year: 2013 > language: 'en-US' > number-of-volumes: 5 > publisher: Publisher > publisher-place: Location > title: Title of the Book > type: book > ... > Yes, this is another one it would be good to have Andrea look into. By the way, I've been wondering, is it intentional that <div > class="references"> ... </div> appears in the markdown output format? > It's intentional to put the bibliography in a pandoc Div element. That allows people to style it differently if they like, plus scripts can see it, slide shows know what is a bibliography, etc. Normally Div elements are rendered using HTML div tags in markdown (though you can turn this off by disabling the 'markdown_in_html_blocks' extension). I'm somewhat tempted to special-case this one and have the markdown writer ignore this particular Div, but I'm not sure. -- 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/d52d9518-9832-45c3-96a0-c3d5b9de3090%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2640 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <d52d9518-9832-45c3-96a0-c3d5b9de3090-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <d52d9518-9832-45c3-96a0-c3d5b9de3090-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-05 7:41 ` Nick Bart [not found] ` <e590b84d-7a2f-40b7-9b4d-26d1644b8a53-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-05 7:41 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1982 bytes --] On the redone bibtex2pandoc: Nice. Glad to see that dates are implemented now. I noticed a few regressions, however: - , collectionTitle = volumeTitle' ++ volumeSubtitle' ++ volumeTitleAddon' collection-title (I'll be using the CSL variable names here) must receive the content of biblatex "series" field (unless the biblatex entry type is "article", "periodical" or "suppperiodical", in which case series is appended to CSL container-title) "volumetitle'" etc. goes to the (not yet official) CSL variable "volume-title" - --, collectionNumber = undefined --:: String --Int and -- , issue = undefined -- :: String The biblatex "number" field is mapped to CSL "number", - unless the entry type is "book", "collection", "proceedings", "reference", "mvbook", "mvcollection", "mvproceedings", "mvreference", "bookinbook", "inbook", "incollection", "inproceedings", "inreference", "suppbook", "suppcollection", in which case it is mapped to CSL "collection-number", - or the entry type is "article", "periodical" or "suppperiodical", in which case the best solution, used in the previous version of bibtex2pandoc, is to map the biblatex fields number *and* issue (in that sequence, separated by a comma) together to CSL "issue". - When Journal and Journalsubtitle are combined, the ": " between them is missing now. container-title: JournalJournalsubtitle -- 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/e590b84d-7a2f-40b7-9b4d-26d1644b8a53%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2436 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <e590b84d-7a2f-40b7-9b4d-26d1644b8a53-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <e590b84d-7a2f-40b7-9b4d-26d1644b8a53-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-05 9:32 ` Nick Bart [not found] ` <967cb63f-a612-4ded-bc2b-6273c0239f68-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-06 0:56 ` John MacFarlane 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-05 9:32 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2551 bytes --] As to the issues with the biblatex "series" field, though I cannot claim to fully understand the new code yet, what I see is that while *sometimes* the output is as expected (test-book-tms.bib below), in other cases it clearly isn't (test-inbook-tbms.bib): $ cat test-book-tms.bib @book{item1, Author = {Author, Al}, Date = {2013}, Hyphenation = {french}, Location = {Location}, Mainsubtitle = {Mainsubtitle}, Maintitle = {Maintitle}, Maintitleaddon = {Maintitleaddon}, Number = {3}, Publisher = {Publisher}, Series = {Series}, Subtitle = {Subtitle}, Title = {Title of the Book}, Titleaddon = {Titleaddon}} $ bibtex2pandoc test-book-tms.bib --- references: - title: ! 'Title of the book: Subtitle. Titleaddon' id: item1 issued: year: 2013 author: given: - Al family: Author container-title: ! 'Maintitle: Mainsubtitle. Maintitleaddon' publisher: Publisher collection-title: Series type: book publisher-place: Location language: fr-FR ... $ cat test-inbook-tbms.bib @inbook{item1, Author = {Author, Al}, Booksubtitle = {Booksubtitle}, Booktitle = {Booktitle}, Booktitleaddon = {Booktitleaddon}, Date = {2011}, Hyphenation = {french}, Location = {Location}, Mainsubtitle = {Mainsubtitle}, Maintitle = {Maintitle}, Maintitleaddon = {Maintitleaddon}, Number = {3}, Publisher = {Publisher}, Series = {Series}, Subtitle = {Subtitle}, Title = {Title of the "@inbook" Entry}, Titleaddon = {Titleaddon}} $ bibtex2pandoc test-inbook-tbms.bib --- references: - title: ! 'Title of the "@inbook" entry: Subtitle. Titleaddon' id: item1 issued: year: 2011 author: given: - Al family: Author container-title: ! 'Maintitle: Mainsubtitle. Maintitleaddon' publisher: Publisher collection-title: ! 'Booktitle: Booksubtitle. Booktitleaddon' type: chapter publisher-place: Location language: fr-FR ... -- 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/967cb63f-a612-4ded-bc2b-6273c0239f68%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3674 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <967cb63f-a612-4ded-bc2b-6273c0239f68-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <967cb63f-a612-4ded-bc2b-6273c0239f68-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-06 0:58 ` John MacFarlane [not found] ` <20131006005856.GA89343-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-06 0:58 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw The difference is due to the line (getTitle lang "maintitle" >> guard hasVolumes >> getTitle lang "booktitle") which matches in test-inbook-tbms.bib. Because we have "maintitle" here, collectionTitle is populated by "booktitle" in this case. I was trying to follow the logic of the old version here -- may have misunderstood something. +++ Nick Bart [Oct 05 13 02:32 ]: > As to the issues with the biblatex "series" field, though I cannot > claim to fully understand the new code yet, what I see is that while > *sometimes* the output is as expected (test-book-tms.bib below), in > other cases it clearly isn't (test-inbook-tbms.bib): > $ cat test-book-tms.bib > @book{item1, > Author = {Author, Al}, > Date = {2013}, > Hyphenation = {french}, > Location = {Location}, > Mainsubtitle = {Mainsubtitle}, > Maintitle = {Maintitle}, > Maintitleaddon = {Maintitleaddon}, > Number = {3}, > Publisher = {Publisher}, > Series = {Series}, > Subtitle = {Subtitle}, > Title = {Title of the Book}, > Titleaddon = {Titleaddon}} > $ bibtex2pandoc test-book-tms.bib > --- > references: > - title: ! 'Title of the book: Subtitle. Titleaddon' > id: item1 > issued: > year: 2013 > author: > given: > - Al > family: Author > container-title: ! 'Maintitle: Mainsubtitle. Maintitleaddon' > publisher: Publisher > collection-title: Series > type: book > publisher-place: Location > language: fr-FR > ... > $ cat test-inbook-tbms.bib > @inbook{item1, > Author = {Author, Al}, > Booksubtitle = {Booksubtitle}, > Booktitle = {Booktitle}, > Booktitleaddon = {Booktitleaddon}, > Date = {2011}, > Hyphenation = {french}, > Location = {Location}, > Mainsubtitle = {Mainsubtitle}, > Maintitle = {Maintitle}, > Maintitleaddon = {Maintitleaddon}, > Number = {3}, > Publisher = {Publisher}, > Series = {Series}, > Subtitle = {Subtitle}, > Title = {Title of the "@inbook" Entry}, > Titleaddon = {Titleaddon}} > $ bibtex2pandoc test-inbook-tbms.bib > --- > references: > - title: ! 'Title of the "@inbook" entry: Subtitle. Titleaddon' > id: item1 > issued: > year: 2011 > author: > given: > - Al > family: Author > container-title: ! 'Maintitle: Mainsubtitle. Maintitleaddon' > publisher: Publisher > collection-title: ! 'Booktitle: Booksubtitle. Booktitleaddon' > type: chapter > publisher-place: Location > language: fr-FR > ... > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/967cb63f-a612-4ded- > bc2b-6273c0239f68%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/967cb63f-a612-4ded-bc2b-6273c0239f68%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131006005856.GA89343-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131006005856.GA89343-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-06 6:29 ` Nick Bart [not found] ` <733d7104-44b1-440a-a386-ec356d2197bd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-06 11:29 ` Nick Bart 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-06 6:29 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 4839 bytes --] Well, "collectionTitle" should never be populated by anything but the biblatex "series" field. biblatex "title", "booktitle", and "maintitle" can only ever map to CSL "title", "container-title", and the new "volume-title", and if you do not want to use the latter yet (I would!), "booktitle" must be discarded until "volume-title" has become part of the CSL specs. On Sunday, October 6, 2013 12:58:56 AM UTC, fiddlosopher wrote: > > The difference is due to the line > > (getTitle lang "maintitle" >> guard hasVolumes >> getTitle lang > "booktitle") > > which matches in test-inbook-tbms.bib. Because we have "maintitle" here, > collectionTitle is populated by "booktitle" in this case. > > I was trying to follow the logic of the old version here -- may have > misunderstood something. > > +++ Nick Bart [Oct 05 13 02:32 ]: > > As to the issues with the biblatex "series" field, though I cannot > > claim to fully understand the new code yet, what I see is that while > > *sometimes* the output is as expected (test-book-tms.bib below), in > > other cases it clearly isn't (test-inbook-tbms.bib): > > $ cat test-book-tms.bib > > @book{item1, > > Author = {Author, Al}, > > Date = {2013}, > > Hyphenation = {french}, > > Location = {Location}, > > Mainsubtitle = {Mainsubtitle}, > > Maintitle = {Maintitle}, > > Maintitleaddon = {Maintitleaddon}, > > Number = {3}, > > Publisher = {Publisher}, > > Series = {Series}, > > Subtitle = {Subtitle}, > > Title = {Title of the Book}, > > Titleaddon = {Titleaddon}} > > $ bibtex2pandoc test-book-tms.bib > > --- > > references: > > - title: ! 'Title of the book: Subtitle. Titleaddon' > > id: item1 > > issued: > > year: 2013 > > author: > > given: > > - Al > > family: Author > > container-title: ! 'Maintitle: Mainsubtitle. Maintitleaddon' > > publisher: Publisher > > collection-title: Series > > type: book > > publisher-place: Location > > language: fr-FR > > ... > > $ cat test-inbook-tbms.bib > > @inbook{item1, > > Author = {Author, Al}, > > Booksubtitle = {Booksubtitle}, > > Booktitle = {Booktitle}, > > Booktitleaddon = {Booktitleaddon}, > > Date = {2011}, > > Hyphenation = {french}, > > Location = {Location}, > > Mainsubtitle = {Mainsubtitle}, > > Maintitle = {Maintitle}, > > Maintitleaddon = {Maintitleaddon}, > > Number = {3}, > > Publisher = {Publisher}, > > Series = {Series}, > > Subtitle = {Subtitle}, > > Title = {Title of the "@inbook" Entry}, > > Titleaddon = {Titleaddon}} > > $ bibtex2pandoc test-inbook-tbms.bib > > --- > > references: > > - title: ! 'Title of the "@inbook" entry: Subtitle. Titleaddon' > > id: item1 > > issued: > > year: 2011 > > author: > > given: > > - Al > > family: Author > > container-title: ! 'Maintitle: Mainsubtitle. Maintitleaddon' > > publisher: Publisher > > collection-title: ! 'Booktitle: Booksubtitle. Booktitleaddon' > > type: chapter > > publisher-place: Location > > language: fr-FR > > ... > > > > -- > > 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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [1] > https://groups.google.com/d/msgid/pandoc-discuss/967cb63f-a612-4ded- > > bc2b-6273c0239f68%40googlegroups.com. > > For more options, visit [2]https://groups.google.com/groups/opt_out. > > > > References > > > > 1. > https://groups.google.com/d/msgid/pandoc-discuss/967cb63f-a612-4ded-bc2b-6273c0239f68%40googlegroups.com > > 2. 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/733d7104-44b1-440a-a386-ec356d2197bd%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 7595 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <733d7104-44b1-440a-a386-ec356d2197bd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <733d7104-44b1-440a-a386-ec356d2197bd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-07 4:43 ` John MacFarlane [not found] ` <20131007044345.GA41791-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-07 4:43 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw OK, I've merged in a number of changes Andrea made to citeproc-hs after I split off pandoc-citeproc. These fix some bugs, including #90, #93, #95, #86. volumeTitle has been added to Reference, so I think I'm now doing the right thing with volumeTitle and containerTitle, but as always your testing will be invaluable! +++ Nick Bart [Oct 05 13 23:29 ]: > Well, "collectionTitle" should never be populated by anything but the > biblatex "series" field. > biblatex "title", "booktitle", and "maintitle" can only ever map to CSL > "title", "container-title", and the new "volume-title", and if you do > not want to use the latter yet (I would!), "booktitle" must be > discarded until "volume-title" has become part of the CSL specs. > On Sunday, October 6, 2013 12:58:56 AM UTC, fiddlosopher wrote: > > The difference is due to the line > (getTitle lang "maintitle" >> guard hasVolumes >> getTitle lang > "booktitle") > which matches in test-inbook-tbms.bib. Because we have "maintitle" > here, > collectionTitle is populated by "booktitle" in this case. > I was trying to follow the logic of the old version here -- may have > misunderstood something. > +++ Nick Bart [Oct 05 13 02:32 ]: > > As to the issues with the biblatex "series" field, though I > cannot > > claim to fully understand the new code yet, what I see is that > while > > *sometimes* the output is as expected (test-book-tms.bib > below), in > > other cases it clearly isn't (test-inbook-tbms.bib): > > $ cat test-book-tms.bib > > @book{item1, > > Author = {Author, Al}, > > Date = {2013}, > > Hyphenation = {french}, > > Location = {Location}, > > Mainsubtitle = {Mainsubtitle}, > > Maintitle = {Maintitle}, > > Maintitleaddon = {Maintitleaddon}, > > Number = {3}, > > Publisher = {Publisher}, > > Series = {Series}, > > Subtitle = {Subtitle}, > > Title = {Title of the Book}, > > Titleaddon = {Titleaddon}} > > $ bibtex2pandoc test-book-tms.bib > > --- > > references: > > - title: ! 'Title of the book: Subtitle. Titleaddon' > > id: item1 > > issued: > > year: 2013 > > author: > > given: > > - Al > > family: Author > > container-title: ! 'Maintitle: Mainsubtitle. Maintitleaddon' > > publisher: Publisher > > collection-title: Series > > type: book > > publisher-place: Location > > language: fr-FR > > ... > > $ cat test-inbook-tbms.bib > > @inbook{item1, > > Author = {Author, Al}, > > Booksubtitle = {Booksubtitle}, > > Booktitle = {Booktitle}, > > Booktitleaddon = {Booktitleaddon}, > > Date = {2011}, > > Hyphenation = {french}, > > Location = {Location}, > > Mainsubtitle = {Mainsubtitle}, > > Maintitle = {Maintitle}, > > Maintitleaddon = {Maintitleaddon}, > > Number = {3}, > > Publisher = {Publisher}, > > Series = {Series}, > > Subtitle = {Subtitle}, > > Title = {Title of the "@inbook" Entry}, > > Titleaddon = {Titleaddon}} > > $ bibtex2pandoc test-inbook-tbms.bib > > --- > > references: > > - title: ! 'Title of the "@inbook" entry: Subtitle. Titleaddon' > > id: item1 > > issued: > > year: 2011 > > author: > > given: > > - Al > > family: Author > > container-title: ! 'Maintitle: Mainsubtitle. Maintitleaddon' > > publisher: Publisher > > collection-title: ! 'Booktitle: Booksubtitle. Booktitleaddon' > > type: chapter > > publisher-place: Location > > language: fr-FR > > ... > > > > -- > > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To post to this group, send email to > [2]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit > > [1][3]https://groups.google.com/d/msgid/pandoc-discuss/ > 967cb63f-a612-4ded- > > bc2b-6273c0239f68%[4]40googlegroups.com. > > For more options, visit [2][5]https://groups.google.com/ > groups/opt_out. > > > > References > > > > 1. [6]https://groups.google.com/d/ > msgid/pandoc-discuss/967cb63f-a612-4ded-bc2b-6273c0239f68% > 40googlegroups.com > > 2. [7]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 > [8]https://groups.google.com/d/msgid/pandoc-discuss/733d7104-44b1-440a- > a386-ec356d2197bd%40googlegroups.com. > For more options, visit [9]https://groups.google.com/groups/opt_out. > > References > > 1. javascript:/ > 2. javascript:/ > 3. https://groups.google.com/d/msgid/pandoc-discuss/967cb63f-a612-4ded- > 4. http://40googlegroups.com/ > 5. https://groups.google.com/groups/opt_out > 6. https://groups.google.com/d/msgid/pandoc-discuss/967cb63f-a612-4ded-bc2b-6273c0239f68%40googlegroups.com > 7. https://groups.google.com/groups/opt_out > 8. https://groups.google.com/d/msgid/pandoc-discuss/733d7104-44b1-440a-a386-ec356d2197bd%40googlegroups.com > 9. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131007044345.GA41791-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131007044345.GA41791-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-07 5:55 ` John MacFarlane 0 siblings, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-10-07 5:55 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I've removed bibtex2pandoc and merged the code into a new library module, Text.CSL.Input.Bibtex. This is now used by pandoc-citeproc instead of bibutils, when you specify a .bib or .bibtex bibliography. You can use biblio2yaml to do what bibtex2pandoc used to do (convert bibtex or biblatex to yaml). John +++ John MacFarlane [Oct 06 13 21:43 ]: > OK, I've merged in a number of changes Andrea made to citeproc-hs > after I split off pandoc-citeproc. These fix some bugs, including > #90, #93, #95, #86. volumeTitle has been added to Reference, so > I think I'm now doing the right thing with volumeTitle and > containerTitle, but as always your testing will be invaluable! > > +++ Nick Bart [Oct 05 13 23:29 ]: > > Well, "collectionTitle" should never be populated by anything but the > > biblatex "series" field. > > biblatex "title", "booktitle", and "maintitle" can only ever map to CSL > > "title", "container-title", and the new "volume-title", and if you do > > not want to use the latter yet (I would!), "booktitle" must be > > discarded until "volume-title" has become part of the CSL specs. > > On Sunday, October 6, 2013 12:58:56 AM UTC, fiddlosopher wrote: > > > > The difference is due to the line > > (getTitle lang "maintitle" >> guard hasVolumes >> getTitle lang > > "booktitle") > > which matches in test-inbook-tbms.bib. Because we have "maintitle" > > here, > > collectionTitle is populated by "booktitle" in this case. > > I was trying to follow the logic of the old version here -- may have > > misunderstood something. > > +++ Nick Bart [Oct 05 13 02:32 ]: > > > As to the issues with the biblatex "series" field, though I > > cannot > > > claim to fully understand the new code yet, what I see is that > > while > > > *sometimes* the output is as expected (test-book-tms.bib > > below), in > > > other cases it clearly isn't (test-inbook-tbms.bib): > > > $ cat test-book-tms.bib > > > @book{item1, > > > Author = {Author, Al}, > > > Date = {2013}, > > > Hyphenation = {french}, > > > Location = {Location}, > > > Mainsubtitle = {Mainsubtitle}, > > > Maintitle = {Maintitle}, > > > Maintitleaddon = {Maintitleaddon}, > > > Number = {3}, > > > Publisher = {Publisher}, > > > Series = {Series}, > > > Subtitle = {Subtitle}, > > > Title = {Title of the Book}, > > > Titleaddon = {Titleaddon}} > > > $ bibtex2pandoc test-book-tms.bib > > > --- > > > references: > > > - title: ! 'Title of the book: Subtitle. Titleaddon' > > > id: item1 > > > issued: > > > year: 2013 > > > author: > > > given: > > > - Al > > > family: Author > > > container-title: ! 'Maintitle: Mainsubtitle. Maintitleaddon' > > > publisher: Publisher > > > collection-title: Series > > > type: book > > > publisher-place: Location > > > language: fr-FR > > > ... > > > $ cat test-inbook-tbms.bib > > > @inbook{item1, > > > Author = {Author, Al}, > > > Booksubtitle = {Booksubtitle}, > > > Booktitle = {Booktitle}, > > > Booktitleaddon = {Booktitleaddon}, > > > Date = {2011}, > > > Hyphenation = {french}, > > > Location = {Location}, > > > Mainsubtitle = {Mainsubtitle}, > > > Maintitle = {Maintitle}, > > > Maintitleaddon = {Maintitleaddon}, > > > Number = {3}, > > > Publisher = {Publisher}, > > > Series = {Series}, > > > Subtitle = {Subtitle}, > > > Title = {Title of the "@inbook" Entry}, > > > Titleaddon = {Titleaddon}} > > > $ bibtex2pandoc test-inbook-tbms.bib > > > --- > > > references: > > > - title: ! 'Title of the "@inbook" entry: Subtitle. Titleaddon' > > > id: item1 > > > issued: > > > year: 2011 > > > author: > > > given: > > > - Al > > > family: Author > > > container-title: ! 'Maintitle: Mainsubtitle. Maintitleaddon' > > > publisher: Publisher > > > collection-title: ! 'Booktitle: Booksubtitle. Booktitleaddon' > > > type: chapter > > > publisher-place: Location > > > language: fr-FR > > > ... > > > > > > -- > > > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to > > [2]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit > > > [1][3]https://groups.google.com/d/msgid/pandoc-discuss/ > > 967cb63f-a612-4ded- > > > bc2b-6273c0239f68%[4]40googlegroups.com. > > > For more options, visit [2][5]https://groups.google.com/ > > groups/opt_out. > > > > > > References > > > > > > 1. [6]https://groups.google.com/d/ > > msgid/pandoc-discuss/967cb63f-a612-4ded-bc2b-6273c0239f68% > > 40googlegroups.com > > > 2. [7]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 > > [8]https://groups.google.com/d/msgid/pandoc-discuss/733d7104-44b1-440a- > > a386-ec356d2197bd%40googlegroups.com. > > For more options, visit [9]https://groups.google.com/groups/opt_out. > > > > References > > > > 1. javascript:/ > > 2. javascript:/ > > 3. https://groups.google.com/d/msgid/pandoc-discuss/967cb63f-a612-4ded- > > 4. http://40googlegroups.com/ > > 5. https://groups.google.com/groups/opt_out > > 6. https://groups.google.com/d/msgid/pandoc-discuss/967cb63f-a612-4ded-bc2b-6273c0239f68%40googlegroups.com > > 7. https://groups.google.com/groups/opt_out > > 8. https://groups.google.com/d/msgid/pandoc-discuss/733d7104-44b1-440a-a386-ec356d2197bd%40googlegroups.com > > 9. 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/20131007044345.GA41791%40Johns-MacBook-Pro.local. > For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131006005856.GA89343-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-10-06 6:29 ` Nick Bart @ 2013-10-06 11:29 ` Nick Bart [not found] ` <cc118a6c-260a-4ed1-9eb9-4f5dab8bb879-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-06 11:29 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 704 bytes --] Another regression: Titles of *non*-English entries are not preserved as is, but converted to lower case in the new version. -- 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/cc118a6c-260a-4ed1-9eb9-4f5dab8bb879%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 967 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <cc118a6c-260a-4ed1-9eb9-4f5dab8bb879-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <cc118a6c-260a-4ed1-9eb9-4f5dab8bb879-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-06 12:26 ` Nick Bart [not found] ` <928cefbc-dcf7-411c-8dee-e555e7cfaf6f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-06 14:46 ` John MacFarlane 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-06 12:26 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1405 bytes --] Something curious: The family name "True" is causing problems: $ cat test.md Foo [@item1, p. 12]. # References --- references: - title: Title id: item1 issued: year: 2012 author: given: - Michael family: True type: article-journal ... $ pandoc --filter pandoc-citeproc -t markdown-citations-markdown_in_html_blocks test.md pandoc-citeproc: Error parsing references: when expecting a String, encountered Boolean instead pandoc: Error running filter pandoc-citeproc In addition, are there other strings values besides "True" and "False" that would be interpreted as Boolean here? I get the same error message when using a larger bibfile.yaml containing 6000+ entries, successfully converted from a biblatex file, even with the "Michael True" entry, and a title beginning with "False" removed. -- 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/928cefbc-dcf7-411c-8dee-e555e7cfaf6f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1818 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <928cefbc-dcf7-411c-8dee-e555e7cfaf6f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <928cefbc-dcf7-411c-8dee-e555e7cfaf6f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-06 14:35 ` John MacFarlane [not found] ` <20131006143549.GC89520-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-06 14:35 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw You can force interpretation as a YAML string: family: 'True' +++ Nick Bart [Oct 06 13 05:26 ]: > Something curious: The family name "True" is causing problems: > $ cat test.md > Foo [@item1, p. 12]. > # References > --- > references: > - title: Title > id: item1 > issued: > year: 2012 > author: > given: > - Michael > family: True > type: article-journal > ... > $ pandoc --filter pandoc-citeproc -t > markdown-citations-markdown_in_html_blocks test.md > pandoc-citeproc: Error parsing references: when expecting a String, > encountered Boolean instead > pandoc: Error running filter pandoc-citeproc > In addition, are there other strings values besides "True" and "False" > that would be interpreted as Boolean here? I get the same error message > when using a larger bibfile.yaml containing 6000+ entries, successfully > converted from a biblatex file, even with the "Michael True" entry, and > a title beginning with "False" removed. > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/928cefbc-dcf7-411c- > 8dee-e555e7cfaf6f%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/928cefbc-dcf7-411c-8dee-e555e7cfaf6f%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131006143549.GC89520-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131006143549.GC89520-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-06 15:11 ` Nick Bart [not found] ` <bfbc1a45-3031-4f2e-bf7f-0c14537011bf-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-06 15:11 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3322 bytes --] Thank you – but isn't there a possibility to fix pandoc2bibtex (e.g., to enclose *all* names in single quotes) or, probably better, pandoc-citeproc (to prevent it from interpreting any fields as Boolean that are quite clearly always to be understood as non-Boolean; which would essentially mean all fields: I don't even think there *are* any Boolean fields currently in use)? Also, are there any *other* strings except True/False that could be (mis-)understood as Boolean, and that could be causing trouble with my large database? Or any other ideas? Capacity issues, perhaps? On Sunday, October 6, 2013 2:35:49 PM UTC, fiddlosopher wrote: > > You can force interpretation as a YAML string: > > family: 'True' > > +++ Nick Bart [Oct 06 13 05:26 ]: > > Something curious: The family name "True" is causing problems: > > $ cat test.md > > Foo [@item1, p. 12]. > > # References > > --- > > references: > > - title: Title > > id: item1 > > issued: > > year: 2012 > > author: > > given: > > - Michael > > family: True > > type: article-journal > > ... > > $ pandoc --filter pandoc-citeproc -t > > markdown-citations-markdown_in_html_blocks test.md > > pandoc-citeproc: Error parsing references: when expecting a String, > > encountered Boolean instead > > pandoc: Error running filter pandoc-citeproc > > In addition, are there other strings values besides "True" and > "False" > > that would be interpreted as Boolean here? I get the same error > message > > when using a larger bibfile.yaml containing 6000+ entries, > successfully > > converted from a biblatex file, even with the "Michael True" entry, > and > > a title beginning with "False" removed. > > > > -- > > 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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [1] > https://groups.google.com/d/msgid/pandoc-discuss/928cefbc-dcf7-411c- > > 8dee-e555e7cfaf6f%40googlegroups.com. > > For more options, visit [2]https://groups.google.com/groups/opt_out. > > > > References > > > > 1. > https://groups.google.com/d/msgid/pandoc-discuss/928cefbc-dcf7-411c-8dee-e555e7cfaf6f%40googlegroups.com > > 2. 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/bfbc1a45-3031-4f2e-bf7f-0c14537011bf%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 4952 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <bfbc1a45-3031-4f2e-bf7f-0c14537011bf-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <bfbc1a45-3031-4f2e-bf7f-0c14537011bf-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-06 15:40 ` John MacFarlane [not found] ` <20131006154016.GE89729-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-06 15:40 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ Nick Bart [Oct 06 13 08:11 ]: > Thank you but isn't there a possibility to fix pandoc2bibtex (e.g., to > enclose *all* names in single quotes) or, probably better, > pandoc-citeproc (to prevent it from interpreting any fields as Boolean > that are quite clearly always to be understood as non-Boolean; which > would essentially mean all fields: I don't even think there *are* any > Boolean fields currently in use)? > Also, are there any *other* strings except True/False that could be > (mis-)understood as Boolean, and that could be causing trouble with my > large database? y|Y|yes|Yes|YES|n|N|no|No|NO |true|True|TRUE|false|False|FALSE |on|On|ON|off|Off|OFF will all be interpreted as Boolean. Since this is standard YAML, there's no way to prevent this (nor would it be desirable to add ad hoc exceptions.) pandoc2bibtex ought to put the strings that can be interpreted as Booleans in quotes. But this work is done by the yaml library, so maybe I need to file a bug report there. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131006154016.GE89729-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131006154016.GE89729-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-06 15:47 ` John MacFarlane [not found] ` <20131006154747.GA89796-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-06 15:47 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Issue report here: https://github.com/snoyberg/yaml/issues/31 +++ John MacFarlane [Oct 06 13 08:40 ]: > +++ Nick Bart [Oct 06 13 08:11 ]: > > Thank you but isn't there a possibility to fix pandoc2bibtex (e.g., to > > enclose *all* names in single quotes) or, probably better, > > pandoc-citeproc (to prevent it from interpreting any fields as Boolean > > that are quite clearly always to be understood as non-Boolean; which > > would essentially mean all fields: I don't even think there *are* any > > Boolean fields currently in use)? > > Also, are there any *other* strings except True/False that could be > > (mis-)understood as Boolean, and that could be causing trouble with my > > large database? > > y|Y|yes|Yes|YES|n|N|no|No|NO > |true|True|TRUE|false|False|FALSE > |on|On|ON|off|Off|OFF > > will all be interpreted as Boolean. Since this is standard YAML, there's > no way to prevent this (nor would it be desirable to add ad hoc exceptions.) > > pandoc2bibtex ought to put the strings that can be interpreted as Booleans > in quotes. But this work is done by the yaml library, so maybe I need to > file a bug report there. > > -- > 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/20131006154016.GE89729%40Johns-MacBook-Pro.local. > For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131006154747.GA89796-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131006154747.GA89796-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-06 17:46 ` Nick Bart 0 siblings, 0 replies; 283+ messages in thread From: Nick Bart @ 2013-10-06 17:46 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2938 bytes --] Thank you. The list of strings matching the pattern for Booleans was helpful: After enclosing all titles starting with "true", "false", and "on" in single quotes, and finally hunting down one - given: - Stephen - N family: Miller and adding a period after the "N", pandoc-citeproc no longer throws the error described above. But of course I'm looking forward to a more permanent fix on the yaml side. On Sunday, October 6, 2013 3:47:47 PM UTC, fiddlosopher wrote: > > Issue report here: > https://github.com/snoyberg/yaml/issues/31 > > +++ John MacFarlane [Oct 06 13 08:40 ]: > > +++ Nick Bart [Oct 06 13 08:11 ]: > > > Thank you but isn't there a possibility to fix pandoc2bibtex (e.g., > to > > > enclose *all* names in single quotes) or, probably better, > > > pandoc-citeproc (to prevent it from interpreting any fields as > Boolean > > > that are quite clearly always to be understood as non-Boolean; > which > > > would essentially mean all fields: I don't even think there *are* > any > > > Boolean fields currently in use)? > > > Also, are there any *other* strings except True/False that could be > > > (mis-)understood as Boolean, and that could be causing trouble with > my > > > large database? > > > > y|Y|yes|Yes|YES|n|N|no|No|NO > > |true|True|TRUE|false|False|FALSE > > |on|On|ON|off|Off|OFF > > > > will all be interpreted as Boolean. Since this is standard YAML, there's > > no way to prevent this (nor would it be desirable to add ad hoc > exceptions.) > > > > pandoc2bibtex ought to put the strings that can be interpreted as > Booleans > > in quotes. But this work is done by the yaml library, so maybe I need > to > > file a bug report there. > > > > -- > > 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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > https://groups.google.com/d/msgid/pandoc-discuss/20131006154016.GE89729%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/7b1f2b56-a682-4026-930a-8d8956b7bb14%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 4040 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <cc118a6c-260a-4ed1-9eb9-4f5dab8bb879-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-06 12:26 ` Nick Bart @ 2013-10-06 14:46 ` John MacFarlane 1 sibling, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-10-06 14:46 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw This is now fixed. +++ Nick Bart [Oct 06 13 04:29 ]: > Another regression: Titles of *non*-English entries are not preserved > as is, but converted to lower case in the new version. > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/cc118a6c-260a-4ed1- > 9eb9-4f5dab8bb879%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/cc118a6c-260a-4ed1-9eb9-4f5dab8bb879%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <e590b84d-7a2f-40b7-9b4d-26d1644b8a53-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-05 9:32 ` Nick Bart @ 2013-10-06 0:56 ` John MacFarlane 1 sibling, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-10-06 0:56 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ Nick Bart [Oct 05 13 00:41 ]: > On the redone bibtex2pandoc: Nice. Glad to see that dates are > implemented now. > I noticed a few regressions, however: > - , collectionTitle = volumeTitle' ++ volumeSubtitle' ++ > volumeTitleAddon' > collection-title (I'll be using the CSL variable names here) must > receive the content of biblatex "series" field (unless the biblatex > entry type is "article", "periodical" or "suppperiodical", in which > case series is appended to CSL container-title) It seems to me that the code should work this way already: volumeTitle' <- (getTitle lang "maintitle" >> guard hasVolumes >> getTitle lang "booktitle") <|> (guard (not isArticle) >> getTitle lang "series") <|> return "" Not that isArticle abbreviates "is article, periodical, or suppperiodical". So the second clause should populate volumeTitle' with "series", unless (a) the type is article, periodical, or suppperiodical, or (b) "maintitle" is set, the type is inbook, incollection, inproceedings, or bookinbook, and "booktitle" is set, in which case this value is taken. > "volumetitle'" etc. goes to the (not yet official) CSL variable > "volume-title" All we have in Reference is collectionTitle, so we have to make do with that until Reference is expanded. > - --, collectionNumber = undefined --:: String --Int > and > -- , issue = undefined -- :: String > The biblatex "number" field is mapped to CSL "number", > - unless the entry type is "book", "collection", "proceedings", > "reference", "mvbook", "mvcollection", "mvproceedings", "mvreference", > "bookinbook", "inbook", "incollection", "inproceedings", "inreference", > "suppbook", "suppcollection", in which case it is mapped to CSL > "collection-number", Should now be fixed. > - or the entry type is "article", "periodical" or "suppperiodical", in > which case the best solution, used in the previous version of > bibtex2pandoc, is to map the biblatex fields number *and* issue (in > that sequence, separated by a comma) together to CSL "issue". Should now be fixed. > - When Journal and Journalsubtitle are combined, the ": " between them > is missing now. > container-title: JournalJournalsubtitle Should now be fixed. ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <15bfac5e-d7df-476c-8a42-193962e6bca3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-01 11:06 ` Nick Bart @ 2013-10-05 5:19 ` fiddlosopher [not found] ` <30423993-afdf-4a47-bb2b-8ae27c6130b6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: fiddlosopher @ 2013-10-05 5:19 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2635 bytes --] I have redone bibtex2pandoc.hs so that it creates a list of Reference objects. This will be easy to integrate into the pandoc-citeproc library, allowing use of bibtex databases without creating a YAML intermediary. One suggestion, though: Readability would improve if (1) empty lines could > be added between entries and (2) id, title, author, editor, and date could > be moved to the top of each entry. > I think this could be done later with some postprocessing of the YAML. The yaml library doesn't have much configurability. > Apart from that, at this stage a few issues remain that I cannot fix alone: > > - date handling (date, urldate, etc. are essential fields in biblatex; > many biblatex users do not even use "year" fields any longer). > This has been implemented, hopefully correctly, in bibtex2pandoc.hs. > - handling of name prefixes and suffixes (I'll see what I can contribute) > Not currently correct, and a bit complex. I'll see what I can do when I can find time. > - handling of multiple publishers, locations, and other "literal list" > field components: Having "getLiteralList", as intended, split such fields > into components would be the cleanest solution, but pandoc-citeproc > currently does not accept arrays (thus I've mostly replaced > "getLiteralList" by "getField" for now), so it would have to be modified. > I'm not sure what the ramifications would be. (Does CSL allow these things to be multiple?) In addition, I came across two issues that are most likely pandoc-citeproc > issues: > > - Extra strings such as "Edited & translated by." in pandoc output. This > has been reported here in detail: > https://code.google.com/p/citeproc-hs/issues/detail?id=92 > No idea yet, haven't really delved into it. Maybe now that Andrea Rossato is back, he can see what is going wrong here. - Very long titles in non-English languages: > > Spanish (French, German, too): Linebreak after title, before '.” > I was able to fix this. -- 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/30423993-afdf-4a47-bb2b-8ae27c6130b6%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 4072 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <30423993-afdf-4a47-bb2b-8ae27c6130b6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <30423993-afdf-4a47-bb2b-8ae27c6130b6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-05 16:52 ` Bruce D'Arcus [not found] ` <615c9846-d27b-4fa0-a549-40748f524a35-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Bruce D'Arcus @ 2013-10-05 16:52 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1431 bytes --] On Saturday, October 5, 2013 1:19:55 AM UTC-4, fiddlosopher wrote: ... > - handling of multiple publishers, locations, and other "literal list" >> field components: Having "getLiteralList", as intended, split such fields >> into components would be the cleanest solution, but pandoc-citeproc >> currently does not accept arrays (thus I've mostly replaced >> "getLiteralList" by "getField" for now), so it would have to be modified. >> > > I'm not sure what the ramifications would be. (Does CSL allow these > things to be multiple?) > The csl-data json schema is here (though with my previous caveat that it's not set in stone, and subject to change): https://github.com/citation-style-language/schema/blob/master/csl-data.json The answer: no. There's a cost to complexity, and so where things can be simple strings, they are. Bruce -- 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/615c9846-d27b-4fa0-a549-40748f524a35%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2246 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <615c9846-d27b-4fa0-a549-40748f524a35-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <615c9846-d27b-4fa0-a549-40748f524a35-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-06 8:35 ` Nick Bart [not found] ` <b717ff1f-ab65-4f1f-85b9-05b7b5bcb9b6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-06 8:35 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2373 bytes --] Thank you, Bruce, for clarifying. Though I hope the CSL schema can be extended at some point - I'd like to remind of the fact that style guides differ in their requirements here, CMoS and APA demanding to print the first publisher and/or place only, ISO 690 and MLA wanting all of them - the sensible thing for bibtex2pandoc, for now, would be to map all "and"s in bibtex/biblatex "literal list" fields, i.e., address, location, origlocation, school, institution, organization, howpublished, publisher, origpublisher - leaving proteced "{and}"s alone, of course - to something that is closer to the average formatting conventions, neutral with regard to language, and does not conflict with commas in place names, either: Hence I would recommend - for now - mapping any "and" in the fields listed above to a semicolon. On Saturday, October 5, 2013 4:52:48 PM UTC, Bruce D'Arcus wrote: > > > > On Saturday, October 5, 2013 1:19:55 AM UTC-4, fiddlosopher wrote: > > ... > > >> - handling of multiple publishers, locations, and other "literal list" >>> field components: Having "getLiteralList", as intended, split such fields >>> into components would be the cleanest solution, but pandoc-citeproc >>> currently does not accept arrays (thus I've mostly replaced >>> "getLiteralList" by "getField" for now), so it would have to be modified. >>> >> >> I'm not sure what the ramifications would be. (Does CSL allow these >> things to be multiple?) >> > > The csl-data json schema is here (though with my previous caveat that it's > not set in stone, and subject to change): > > https://github.com/citation-style-language/schema/blob/master/csl-data.json > > The answer: no. > > There's a cost to complexity, and so where things can be simple strings, > they are. > > Bruce > -- 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/b717ff1f-ab65-4f1f-85b9-05b7b5bcb9b6%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3326 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <b717ff1f-ab65-4f1f-85b9-05b7b5bcb9b6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <b717ff1f-ab65-4f1f-85b9-05b7b5bcb9b6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-07 4:45 ` John MacFarlane [not found] ` <20131007044516.GB41791-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-07 4:45 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ Nick Bart [Oct 06 13 01:35 ]: > Thank you, Bruce, for clarifying. > Though I hope the CSL schema can be extended at some point - I'd like > to remind of the fact that style guides differ in their requirements > here, CMoS and APA demanding to print the first publisher and/or place > only, ISO 690 and MLA wanting all of them - the sensible thing for > bibtex2pandoc, for now, would be to map all "and"s in bibtex/biblatex > "literal list" fields, i.e., address, location, origlocation, school, > institution, organization, howpublished, publisher, origpublisher - > leaving proteced "{and}"s alone, of course - to something that is > closer to the average formatting conventions, neutral with regard to > language, and does not conflict with commas in place names, either: > Hence I would recommend - for now - mapping any "and" in the fields > listed above to a semicolon. Not so sure. Do you really want publisher = {Harcourt, Brace, and Howe} to be mapped to publisher: "Harcourt, Brace; Howe"? ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131007044516.GB41791-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131007044516.GB41791-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-07 6:15 ` Nick Bart [not found] ` <a72be8d7-27fe-4560-ad38-739e4f1287d7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-07 6:24 ` Nick Bart 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-07 6:15 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3060 bytes --] Well, yes, if it's biblatex. It's a literal list field, and according to the biblatex specs, any unprotected "and" *separates* two list elements, it's not part of any of them (see biblatex manual, v2.7a, § 2.3.4, "Literal Lists") If it's actually one publisher with an "and" in their name, the "and" needs to be protected by either wrapping it in braces: publisher = {Harcourt, Brace {and} Howe} or by wrapping the entire name in braces: publisher = {{Harcourt, Brace and Howe}} Both forms should of course be mapped to publisher: "Harcourt, Brace and Howe" If it's indeed two publishers, we'd have: publisher = {Paternoster Press and Eerdmans} publisher = {Univ. of Toronto Press and Routledge {and} Kegan Paul} publisher = {Univ. of Toronto Press and {Routledge and Kegan Paul}} which should come out as publisher: Paternoster Press; Eerdmans publisher: Univ. of Toronto Press; Routledge and Kegan Paul Same for institution, organization, location are literal lists in terms of § 2.2. is also applies to origlocation, origpublisher and to the field aliases address and school. location = {Exeter and Grand Rapids} is mapped to publisher-place = {Exeter; Grand Rapids} On Monday, October 7, 2013 4:45:16 AM UTC, fiddlosopher wrote: > > +++ Nick Bart [Oct 06 13 01:35 ]: > > Thank you, Bruce, for clarifying. > > Though I hope the CSL schema can be extended at some point - I'd like > > to remind of the fact that style guides differ in their requirements > > here, CMoS and APA demanding to print the first publisher and/or > place > > only, ISO 690 and MLA wanting all of them - the sensible thing for > > bibtex2pandoc, for now, would be to map all "and"s in bibtex/biblatex > > "literal list" fields, i.e., address, location, origlocation, school, > > institution, organization, howpublished, publisher, origpublisher - > > leaving proteced "{and}"s alone, of course - to something that is > > closer to the average formatting conventions, neutral with regard to > > language, and does not conflict with commas in place names, either: > > Hence I would recommend - for now - mapping any "and" in the fields > > listed above to a semicolon. > > Not so sure. Do you really want > > publisher = {Harcourt, Brace, and Howe} > > to be mapped to > > publisher: "Harcourt, Brace; Howe"? > -- 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/a72be8d7-27fe-4560-ad38-739e4f1287d7%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3811 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <a72be8d7-27fe-4560-ad38-739e4f1287d7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <a72be8d7-27fe-4560-ad38-739e4f1287d7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-08 3:14 ` John MacFarlane [not found] ` <20131008031419.GA49273-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-08 3:14 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw OK, done. +++ Nick Bart [Oct 06 13 23:15 ]: > Well, yes, if it's biblatex. It's a literal list field, and according > to the biblatex specs, any unprotected "and" *separates* two list > elements, it's not part of any of them (see biblatex manual, v2.7a, § > 2.3.4, "Literal Lists") > If it's actually one publisher with an "and" in their name, the "and" > needs to be protected by either wrapping it in braces: > publisher = {Harcourt, Brace {and} Howe} > or by wrapping the entire name in braces: > publisher = {{Harcourt, Brace and Howe}} > Both forms should of course be mapped to > publisher: "Harcourt, Brace and Howe" > If it's indeed two publishers, we'd have: > publisher = {Paternoster Press and Eerdmans} > publisher = {Univ. of Toronto Press and Routledge {and} Kegan Paul} > publisher = {Univ. of Toronto Press and {Routledge and Kegan Paul}} > which should come out as > publisher: Paternoster Press; Eerdmans > publisher: Univ. of Toronto Press; Routledge and Kegan Paul > Same for institution, organization, location are literal lists in terms > of § 2.2. is also applies to origlocation, origpublisher and to the > field aliases address and school. > location = {Exeter and Grand Rapids} > is mapped to > publisher-place = {Exeter; Grand Rapids} > On Monday, October 7, 2013 4:45:16 AM UTC, fiddlosopher wrote: > > +++ Nick Bart [Oct 06 13 01:35 ]: > > Thank you, Bruce, for clarifying. > > Though I hope the CSL schema can be extended at some point - > I'd like > > to remind of the fact that style guides differ in their > requirements > > here, CMoS and APA demanding to print the first publisher > and/or place > > only, ISO 690 and MLA wanting all of them - the sensible thing > for > > bibtex2pandoc, for now, would be to map all "and"s in > bibtex/biblatex > > "literal list" fields, i.e., address, location, origlocation, > school, > > institution, organization, howpublished, publisher, > origpublisher - > > leaving proteced "{and}"s alone, of course - to something that > is > > closer to the average formatting conventions, neutral with > regard to > > language, and does not conflict with commas in place names, > either: > > Hence I would recommend - for now - mapping any "and" in the > fields > > listed above to a semicolon. > Not so sure. Do you really want > publisher = {Harcourt, Brace, and Howe} > to be mapped to > publisher: "Harcourt, Brace; Howe"? > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/a72be8d7-27fe-4560- > ad38-739e4f1287d7%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/a72be8d7-27fe-4560-ad38-739e4f1287d7%40googlegroups.com > 2. 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/20131008031419.GA49273%40Johns-MacBook-Pro.local. For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131008031419.GA49273-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131008031419.GA49273-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-08 6:25 ` Nick Bart 2013-10-08 6:26 ` Nick Bart 1 sibling, 0 replies; 283+ messages in thread From: Nick Bart @ 2013-10-08 6:25 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 4489 bytes --] Great! On Tuesday, October 8, 2013 3:14:19 AM UTC, fiddlosopher wrote: > > OK, done. > > +++ Nick Bart [Oct 06 13 23:15 ]: > > Well, yes, if it's biblatex. It's a literal list field, and according > > to the biblatex specs, any unprotected "and" *separates* two list > > elements, it's not part of any of them (see biblatex manual, v2.7a, § > > 2.3.4, "Literal Lists") > > If it's actually one publisher with an "and" in their name, the "and" > > needs to be protected by either wrapping it in braces: > > publisher = {Harcourt, Brace {and} Howe} > > or by wrapping the entire name in braces: > > publisher = {{Harcourt, Brace and Howe}} > > Both forms should of course be mapped to > > publisher: "Harcourt, Brace and Howe" > > If it's indeed two publishers, we'd have: > > publisher = {Paternoster Press and Eerdmans} > > publisher = {Univ. of Toronto Press and Routledge {and} Kegan > Paul} > > publisher = {Univ. of Toronto Press and {Routledge and Kegan > Paul}} > > which should come out as > > publisher: Paternoster Press; Eerdmans > > publisher: Univ. of Toronto Press; Routledge and Kegan Paul > > Same for institution, organization, location are literal lists in > terms > > of § 2.2. is also applies to origlocation, origpublisher and to the > > field aliases address and school. > > location = {Exeter and Grand Rapids} > > is mapped to > > publisher-place = {Exeter; Grand Rapids} > > On Monday, October 7, 2013 4:45:16 AM UTC, fiddlosopher wrote: > > > > +++ Nick Bart [Oct 06 13 01:35 ]: > > > Thank you, Bruce, for clarifying. > > > Though I hope the CSL schema can be extended at some point - > > I'd like > > > to remind of the fact that style guides differ in their > > requirements > > > here, CMoS and APA demanding to print the first publisher > > and/or place > > > only, ISO 690 and MLA wanting all of them - the sensible thing > > for > > > bibtex2pandoc, for now, would be to map all "and"s in > > bibtex/biblatex > > > "literal list" fields, i.e., address, location, origlocation, > > school, > > > institution, organization, howpublished, publisher, > > origpublisher - > > > leaving proteced "{and}"s alone, of course - to something that > > is > > > closer to the average formatting conventions, neutral with > > regard to > > > language, and does not conflict with commas in place names, > > either: > > > Hence I would recommend - for now - mapping any "and" in the > > fields > > > listed above to a semicolon. > > Not so sure. Do you really want > > publisher = {Harcourt, Brace, and Howe} > > to be mapped to > > publisher: "Harcourt, Brace; Howe"? > > > > -- > > 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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [1] > https://groups.google.com/d/msgid/pandoc-discuss/a72be8d7-27fe-4560- > > ad38-739e4f1287d7%40googlegroups.com. > > For more options, visit [2]https://groups.google.com/groups/opt_out. > > > > References > > > > 1. > https://groups.google.com/d/msgid/pandoc-discuss/a72be8d7-27fe-4560-ad38-739e4f1287d7%40googlegroups.com > > 2. 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/310ae93b-889b-44af-9da7-97e071c23936%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 6740 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131008031419.GA49273-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-10-08 6:25 ` Nick Bart @ 2013-10-08 6:26 ` Nick Bart [not found] ` <28779dd0-99a6-448c-8967-6d37bdba58ad-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-08 6:26 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1213 bytes --] Now, since yesterday pandoc doesn't build any longer: pandoc $ cabal install --enable-tests --force-reinstalls Resolving dependencies... Warning: The following packages are likely to be broken by the reinstalls: pandoc-citeproc-0.1.1.2 Continuing even though the plan contains dangerous reinstalls. Configuring pandoc-1.12.0.2... Building pandoc-1.12.0.2... setup: internal error: componentsInBuildOrder: no such component: CExeName "make-pandoc-man-pages" Failed to install pandoc-1.12.0.2 cabal: Error: some packages failed to install: pandoc-1.12.0.2 failed during the building phase. The exception was: ExitFailure 1 Any ideas? -- 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/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1521 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <28779dd0-99a6-448c-8967-6d37bdba58ad-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <28779dd0-99a6-448c-8967-6d37bdba58ad-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-08 6:39 ` Nick Bart [not found] ` <3e0e0fc9-ea6c-454e-a12a-5562d48c94cb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-08 13:39 ` John MacFarlane 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-08 6:39 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1560 bytes --] And another two issues, with one example to demonstrate both: - Corporate names are, again, broken - Title: Strings wrapped in braces are not protected from being converted to lowercase $ cat test-corporate-author.bib @report{item1, Author = {{National Aeronautics and Space Administration} and Author, Alfred and {Foo and Bar}}, Date = {2013}, Hyphenation = {USenglish}, Location = {Place1 and Place2}, Title = {The Title, Including a {Proper Name} and an {ACRNM}}} $ ../pandoc-citeproc/dist/build/biblio2yaml/biblio2yaml test-corporate-author.bib --- references: - title: The title, including a proper name and an acrnm id: item1 issued: year: 2013 author: - given: - National family: Aeronautics - given: - Space family: Administration - given: - Alfred family: Author - given: - '' family: Foo - given: - '' family: Bar type: report publisher-place: Place1; Place2 language: en-US ... -- 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/3e0e0fc9-ea6c-454e-a12a-5562d48c94cb%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2234 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <3e0e0fc9-ea6c-454e-a12a-5562d48c94cb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <3e0e0fc9-ea6c-454e-a12a-5562d48c94cb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-08 13:40 ` John MacFarlane 0 siblings, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-10-08 13:40 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2437 bytes --] You need to install the latest pandoc from the github repo for this to work. Then reinstall pandoc-citeproc > On Oct 7, 2013, at 11:39 PM, Nick Bart <nickbart1980-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > And another two issues, with one example to demonstrate both: > - Corporate names are, again, broken > - Title: Strings wrapped in braces are not protected from being converted to lowercase > > $ cat test-corporate-author.bib > > @report{item1, > Author = {{National Aeronautics and Space Administration} and Author, Alfred and {Foo and Bar}}, > Date = {2013}, > Hyphenation = {USenglish}, > Location = {Place1 and Place2}, > Title = {The Title, Including a {Proper Name} and an {ACRNM}}} > $ ../pandoc-citeproc/dist/build/biblio2yaml/biblio2yaml test-corporate-author.bib > --- > references: > - title: The title, including a proper name and an acrnm > id: item1 > issued: > year: 2013 > author: > - given: > - National > family: Aeronautics > - given: > - Space > family: Administration > - given: > - Alfred > family: Author > - given: > - '' > family: Foo > - given: > - '' > family: Bar > type: report > publisher-place: Place1; Place2 > language: en-US > ... > > -- > 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/3e0e0fc9-ea6c-454e-a12a-5562d48c94cb%40googlegroups.com. > 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/432132EE-5C00-4E9A-AB31-63A3E95ED949%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3639 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <28779dd0-99a6-448c-8967-6d37bdba58ad-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-08 6:39 ` Nick Bart @ 2013-10-08 13:39 ` John MacFarlane [not found] ` <9910B96C-195A-4D16-B944-1A1314A94F7F-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-08 13:39 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1977 bytes --] Do cabal clean first, then it should build > On Oct 7, 2013, at 11:26 PM, Nick Bart <nickbart1980-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > Now, since yesterday pandoc doesn't build any longer: > > pandoc $ cabal install --enable-tests --force-reinstalls > Resolving dependencies... > Warning: The following packages are likely to be broken by the reinstalls: > pandoc-citeproc-0.1.1.2 > Continuing even though the plan contains dangerous reinstalls. > Configuring pandoc-1.12.0.2... > Building pandoc-1.12.0.2... > setup: internal error: componentsInBuildOrder: no such component: CExeName "make-pandoc-man-pages" > Failed to install pandoc-1.12.0.2 > cabal: Error: some packages failed to install: > pandoc-1.12.0.2 failed during the building phase. The exception was: > ExitFailure 1 > > Any ideas? > -- > 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/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com. > 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/9910B96C-195A-4D16-B944-1A1314A94F7F%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2855 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <9910B96C-195A-4D16-B944-1A1314A94F7F-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <9910B96C-195A-4D16-B944-1A1314A94F7F-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> @ 2013-10-08 17:45 ` Nick Bart [not found] ` <63edb53b-b03c-468a-a60b-6bba4777cbf4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-08 17:45 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2111 bytes --] Hmm, no. Any other ideas? On Tuesday, October 8, 2013 1:39:05 PM UTC, fiddlosopher wrote: > > Do cabal clean first, then it should build > > > On Oct 7, 2013, at 11:26 PM, Nick Bart <nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> > wrote: > > Now, since yesterday pandoc doesn't build any longer: > > pandoc $ cabal install --enable-tests --force-reinstalls > Resolving dependencies... > Warning: The following packages are likely to be broken by the reinstalls: > pandoc-citeproc-0.1.1.2 > Continuing even though the plan contains dangerous reinstalls. > Configuring pandoc-1.12.0.2... > Building pandoc-1.12.0.2... > setup: internal error: componentsInBuildOrder: no such component: CExeName > "make-pandoc-man-pages" > Failed to install pandoc-1.12.0.2 > cabal: Error: some packages failed to install: > pandoc-1.12.0.2 failed during the building phase. The exception was: > ExitFailure 1 > > Any ideas? > > -- > 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 <javascript:>. > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com > . > 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/63edb53b-b03c-468a-a60b-6bba4777cbf4%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3041 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <63edb53b-b03c-468a-a60b-6bba4777cbf4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <63edb53b-b03c-468a-a60b-6bba4777cbf4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-08 18:10 ` John MacFarlane [not found] ` <20131008181040.GA15025-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-08 18:10 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Try removing the dist subdirectory entirely, if 'cabal clean' doesn't do that. +++ Nick Bart [Oct 08 13 10:45 ]: > Hmm, no. Any other ideas? > On Tuesday, October 8, 2013 1:39:05 PM UTC, fiddlosopher wrote: > > Do cabal clean first, then it should build > On Oct 7, 2013, at 11:26 PM, Nick Bart <[1]nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > Now, since yesterday pandoc doesn't build any longer: > pandoc $ cabal install --enable-tests --force-reinstalls > Resolving dependencies... > Warning: The following packages are likely to be broken by the > reinstalls: > pandoc-citeproc-0.1.1.2 > Continuing even though the plan contains dangerous reinstalls. > Configuring pandoc-1.12.0.2... > Building pandoc-1.12.0.2... > setup: internal error: componentsInBuildOrder: no such component: > CExeName "make-pandoc-man-pages" > Failed to install pandoc-1.12.0.2 > cabal: Error: some packages failed to install: > pandoc-1.12.0.2 failed during the building phase. The exception was: > ExitFailure 1 > Any ideas? > > -- > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To post to this group, send email to [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To view this discussion on the web visit > [4]https://groups.google.com/d/msgid/pandoc-discuss/28779dd0- > 99a6-448c-8967-6d37bdba58ad%40googlegroups.com. > For more options, visit [5]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 > [6]https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a- > a60b-6bba4777cbf4%40googlegroups.com. > For more options, visit [7]https://groups.google.com/groups/opt_out. > > References > > 1. javascript:/ > 2. javascript:/ > 3. javascript:/ > 4. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com > 5. https://groups.google.com/groups/opt_out > 6. https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4%40googlegroups.com > 7. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131008181040.GA15025-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131008181040.GA15025-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2013-10-08 18:33 ` Nick Bart [not found] ` <233c21c4-cff5-452d-8269-80981156bddc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-08 18:33 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3870 bytes --] Sorry but no, not even removing the complete pandoc, pandoc-citeproc, and pandoc-types directories and a fresh git clone git://github.com/jgm/pandoc-types git clone git://github.com/jgm/pandoc-citeproc git clone git://github.com/jgm/pandoc did the trick. Anything else I could try? On Tuesday, October 8, 2013 6:10:41 PM UTC, fiddlosopher wrote: > > Try removing the dist subdirectory entirely, if 'cabal clean' > doesn't do that. > > +++ Nick Bart [Oct 08 13 10:45 ]: > > Hmm, no. Any other ideas? > > On Tuesday, October 8, 2013 1:39:05 PM UTC, fiddlosopher wrote: > > > > Do cabal clean first, then it should build > > On Oct 7, 2013, at 11:26 PM, Nick Bart <[1]nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > wrote: > > > > Now, since yesterday pandoc doesn't build any longer: > > pandoc $ cabal install --enable-tests --force-reinstalls > > Resolving dependencies... > > Warning: The following packages are likely to be broken by the > > reinstalls: > > pandoc-citeproc-0.1.1.2 > > Continuing even though the plan contains dangerous reinstalls. > > Configuring pandoc-1.12.0.2... > > Building pandoc-1.12.0.2... > > setup: internal error: componentsInBuildOrder: no such component: > > CExeName "make-pandoc-man-pages" > > Failed to install pandoc-1.12.0.2 > > cabal: Error: some packages failed to install: > > pandoc-1.12.0.2 failed during the building phase. The exception was: > > ExitFailure 1 > > Any ideas? > > > > -- > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To post to this group, send email to [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit > > [4]https://groups.google.com/d/msgid/pandoc-discuss/28779dd0- > > 99a6-448c-8967-6d37bdba58ad%40googlegroups.com. > > For more options, visit [5]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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [6] > https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a- > > a60b-6bba4777cbf4%40googlegroups.com. > > For more options, visit [7]https://groups.google.com/groups/opt_out. > > > > References > > > > 1. javascript:/ > > 2. javascript:/ > > 3. javascript:/ > > 4. > https://groups.google.com/d/msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com > > 5. https://groups.google.com/groups/opt_out > > 6. > https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4%40googlegroups.com > > 7. 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/233c21c4-cff5-452d-8269-80981156bddc%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 6019 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <233c21c4-cff5-452d-8269-80981156bddc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <233c21c4-cff5-452d-8269-80981156bddc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-08 18:56 ` John MacFarlane [not found] ` <20131008185602.GB21820-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 2013-10-08 19:25 ` Joseph Reagle 1 sibling, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-08 18:56 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Very strange. I just installed with no problems. What OS are you using? What does 'cabal --version' say? +++ Nick Bart [Oct 08 13 11:33 ]: > Sorry but no, not even removing the complete pandoc, pandoc-citeproc, > and pandoc-types directories and a fresh > git clone git://github.com/jgm/pandoc-types > git clone git://github.com/jgm/pandoc-citeproc > git clone git://github.com/jgm/pandoc > did the trick. Anything else I could try? > On Tuesday, October 8, 2013 6:10:41 PM UTC, fiddlosopher wrote: > > Try removing the dist subdirectory entirely, if 'cabal clean' > doesn't do that. > +++ Nick Bart [Oct 08 13 10:45 ]: > > Hmm, no. Any other ideas? > > On Tuesday, October 8, 2013 1:39:05 PM UTC, fiddlosopher wrote: > > > > Do cabal clean first, then it should build > > On Oct 7, 2013, at 11:26 PM, Nick Bart <[1]nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > wrote: > > > > Now, since yesterday pandoc doesn't build any longer: > > pandoc $ cabal install --enable-tests --force-reinstalls > > Resolving dependencies... > > Warning: The following packages are likely to be broken by the > > reinstalls: > > pandoc-citeproc-0.1.1.2 > > Continuing even though the plan contains dangerous reinstalls. > > Configuring pandoc-1.12.0.2... > > Building pandoc-1.12.0.2... > > setup: internal error: componentsInBuildOrder: no such > component: > > CExeName "make-pandoc-man-pages" > > Failed to install pandoc-1.12.0.2 > > cabal: Error: some packages failed to install: > > pandoc-1.12.0.2 failed during the building phase. The exception > was: > > ExitFailure 1 > > Any ideas? > > > > -- > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To post to this group, send email to > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit > > [4][1]https://groups.google.com/d/msgid/pandoc-discuss/ > 28779dd0- > > 99a6-448c-8967-6d37bdba58ad%[2]40googlegroups.com. > > For more options, visit [5][3]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 [4]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To post to this group, send email to > [5]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit > > [6][6]https://groups.google.com/d/msgid/pandoc-discuss/ > 63edb53b-b03c-468a- > > a60b-6bba4777cbf4%[7]40googlegroups.com. > > For more options, visit [7][8]https://groups.google.com/ > groups/opt_out. > > > > References > > > > 1. javascript:/ > > 2. javascript:/ > > 3. javascript:/ > > 4. [9]https://groups.google.com/d/ > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > 40googlegroups.com > > 5. [10]https://groups.google.com/groups/opt_out > > 6. [11]https://groups.google.com/d/ > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > 40googlegroups.com > > 7. [12]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 > [13]https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d > -8269-80981156bddc%40googlegroups.com. > For more options, visit [14]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0- > 2. http://40googlegroups.com/ > 3. https://groups.google.com/groups/opt_out > 4. javascript:/ > 5. javascript:/ > 6. https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a- > 7. http://40googlegroups.com/ > 8. https://groups.google.com/groups/opt_out > 9. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com > 10. https://groups.google.com/groups/opt_out > 11. https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4%40googlegroups.com > 12. https://groups.google.com/groups/opt_out > 13. https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc%40googlegroups.com > 14. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131008185602.GB21820-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131008185602.GB21820-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2013-10-08 19:06 ` Nick Bart [not found] ` <8470226a-c385-42bd-a6ba-71037729c707-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-08 19:06 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 6441 bytes --] Mac OS X 10.7.5 $ cabal --version cabal-install version 1.18.0.2 using version 1.18.1 of the Cabal library On Tuesday, October 8, 2013 6:56:02 PM UTC, fiddlosopher wrote: > > Very strange. I just installed with no problems. What OS > are you using? What does 'cabal --version' say? > > +++ Nick Bart [Oct 08 13 11:33 ]: > > Sorry but no, not even removing the complete pandoc, pandoc-citeproc, > > and pandoc-types directories and a fresh > > git clone git://github.com/jgm/pandoc-types > > git clone git://github.com/jgm/pandoc-citeproc > > git clone git://github.com/jgm/pandoc > > did the trick. Anything else I could try? > > On Tuesday, October 8, 2013 6:10:41 PM UTC, fiddlosopher wrote: > > > > Try removing the dist subdirectory entirely, if 'cabal clean' > > doesn't do that. > > +++ Nick Bart [Oct 08 13 10:45 ]: > > > Hmm, no. Any other ideas? > > > On Tuesday, October 8, 2013 1:39:05 PM UTC, fiddlosopher > wrote: > > > > > > Do cabal clean first, then it should build > > > On Oct 7, 2013, at 11:26 PM, Nick Bart <[1]nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > > > wrote: > > > > > > Now, since yesterday pandoc doesn't build any longer: > > > pandoc $ cabal install --enable-tests --force-reinstalls > > > Resolving dependencies... > > > Warning: The following packages are likely to be broken by the > > > reinstalls: > > > pandoc-citeproc-0.1.1.2 > > > Continuing even though the plan contains dangerous reinstalls. > > > Configuring pandoc-1.12.0.2... > > > Building pandoc-1.12.0.2... > > > setup: internal error: componentsInBuildOrder: no such > > component: > > > CExeName "make-pandoc-man-pages" > > > Failed to install pandoc-1.12.0.2 > > > cabal: Error: some packages failed to install: > > > pandoc-1.12.0.2 failed during the building phase. The > exception > > was: > > > ExitFailure 1 > > > Any ideas? > > > > > > -- > > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to > > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit > > > [4][1]https://groups.google.com/d/msgid/pandoc-discuss/ > > 28779dd0- > > > 99a6-448c-8967-6d37bdba58ad%[2]40googlegroups.com. > > > For more options, visit [5][3]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 [4]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to > > [5]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit > > > [6][6]https://groups.google.com/d/msgid/pandoc-discuss/ > > 63edb53b-b03c-468a- > > > a60b-6bba4777cbf4%[7]40googlegroups.com. > > > For more options, visit [7][8]https://groups.google.com/ > > groups/opt_out. > > > > > > References > > > > > > 1. javascript:/ > > > 2. javascript:/ > > > 3. javascript:/ > > > 4. [9]https://groups.google.com/d/ > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > > 40googlegroups.com > > > 5. [10]https://groups.google.com/groups/opt_out > > > 6. [11]https://groups.google.com/d/ > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > > 40googlegroups.com > > > 7. [12]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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [13] > https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d > > -8269-80981156bddc%40googlegroups.com. > > For more options, visit [14]https://groups.google.com/groups/opt_out. > > > > > References > > > > 1. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0- > > 2. http://40googlegroups.com/ > > 3. https://groups.google.com/groups/opt_out > > 4. javascript:/ > > 5. javascript:/ > > 6. > https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a- > > 7. http://40googlegroups.com/ > > 8. https://groups.google.com/groups/opt_out > > 9. > https://groups.google.com/d/msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com > > 10. https://groups.google.com/groups/opt_out > > 11. > https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4%40googlegroups.com > > 12. https://groups.google.com/groups/opt_out > > 13. > https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc%40googlegroups.com > > 14. 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/8470226a-c385-42bd-a6ba-71037729c707%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 11870 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <8470226a-c385-42bd-a6ba-71037729c707-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <8470226a-c385-42bd-a6ba-71037729c707-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-08 20:49 ` John MacFarlane [not found] ` <20131008204913.GB26656-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-08 20:49 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Even stranger. I use roughly the same setup at home. Why don't you send the output of cabal clean && cabal install -v2 +++ Nick Bart [Oct 08 13 12:06 ]: > Mac OS X 10.7.5 > $ cabal --version > cabal-install version 1.18.0.2 > using version 1.18.1 of the Cabal library > On Tuesday, October 8, 2013 6:56:02 PM UTC, fiddlosopher wrote: > > Very strange. I just installed with no problems. What OS > are you using? What does 'cabal --version' say? > +++ Nick Bart [Oct 08 13 11:33 ]: > > Sorry but no, not even removing the complete pandoc, > pandoc-citeproc, > > and pandoc-types directories and a fresh > > git clone git://[1]github.com/jgm/pandoc-types > > git clone git://[2]github.com/jgm/pandoc-citeproc > > git clone git://[3]github.com/jgm/pandoc > > did the trick. Anything else I could try? > > On Tuesday, October 8, 2013 6:10:41 PM UTC, fiddlosopher wrote: > > > > Try removing the dist subdirectory entirely, if 'cabal clean' > > doesn't do that. > > +++ Nick Bart [Oct 08 13 10:45 ]: > > > Hmm, no. Any other ideas? > > > On Tuesday, October 8, 2013 1:39:05 PM UTC, fiddlosopher > wrote: > > > > > > Do cabal clean first, then it should build > > > On Oct 7, 2013, at 11:26 PM, Nick Bart > <[1]nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > > wrote: > > > > > > Now, since yesterday pandoc doesn't build any longer: > > > pandoc $ cabal install --enable-tests --force-reinstalls > > > Resolving dependencies... > > > Warning: The following packages are likely to be broken > by the > > > reinstalls: > > > pandoc-citeproc-0.1.1.2 > > > Continuing even though the plan contains dangerous > reinstalls. > > > Configuring pandoc-1.12.0.2... > > > Building pandoc-1.12.0.2... > > > setup: internal error: componentsInBuildOrder: no such > > component: > > > CExeName "make-pandoc-man-pages" > > > Failed to install pandoc-1.12.0.2 > > > cabal: Error: some packages failed to install: > > > pandoc-1.12.0.2 failed during the building phase. The > exception > > was: > > > ExitFailure 1 > > > Any ideas? > > > > > > -- > > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to > > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit > > > [4][1][4]https://groups.google. > com/d/msgid/pandoc-discuss/ > > 28779dd0- > > > 99a6-448c-8967-6d37bdba58ad%[2][5]40googlegroups.com. > > > For more options, visit [5][3][6]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 [4]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to > > [5]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit > > > [6][6][7]https://groups.google. > com/d/msgid/pandoc-discuss/ > > 63edb53b-b03c-468a- > > > a60b-6bba4777cbf4%[7][8]40googlegroups.com. > > > For more options, visit [7][8][9]https://groups.google. > com/ > > groups/opt_out. > > > > > > References > > > > > > 1. javascript:/ > > > 2. javascript:/ > > > 3. javascript:/ > > > 4. [9][10]https://groups.google.com/d/ > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > > [11]40googlegroups.com > > > 5. [10][12]https://groups.google.com/groups/opt_out > > > 6. [11][13]https://groups.google.com/d/ > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > > [14]40googlegroups.com > > > 7. [12][15]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 [16]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To post to this group, send email to > [17]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit > > [13][18]https://groups.google.com/d/msgid/pandoc-discuss/ > 233c21c4-cff5-452d > > -8269-80981156bddc%[19]40googlegroups.com. > > For more options, visit [14][20]https://groups.google.com/ > groups/opt_out. > > > > References > > > > 1. [21]https://groups.google.com/d/ > msgid/pandoc-discuss/28779dd0- > > 2. [22]http://40googlegroups.com/ > > 3. [23]https://groups.google.com/groups/opt_out > > 4. javascript:/ > > 5. javascript:/ > > 6. [24]https://groups.google.com/d/ > msgid/pandoc-discuss/63edb53b-b03c-468a- > > 7. [25]http://40googlegroups.com/ > > 8. [26]https://groups.google.com/groups/opt_out > > 9. [27]https://groups.google.com/d/ > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > 40googlegroups.com > > 10. [28]https://groups.google.com/groups/opt_out > > 11. [29]https://groups.google.com/d/ > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > 40googlegroups.com > > 12. [30]https://groups.google.com/groups/opt_out > > 13. [31]https://groups.google.com/d/ > msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc% > 40googlegroups.com > > 14. [32]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 > [33]https://groups.google.com/d/msgid/pandoc-discuss/8470226a-c385-42bd > -a6ba-71037729c707%40googlegroups.com. > For more options, visit [34]https://groups.google.com/groups/opt_out. > > References > > 1. http://github.com/jgm/pandoc-types > 2. http://github.com/jgm/pandoc-citeproc > 3. http://github.com/jgm/pandoc > 4. https://groups.google.com/d/msgid/pandoc-discuss/ > 5. http://40googlegroups.com/ > 6. https://groups.google.com/ > 7. https://groups.google.com/d/msgid/pandoc-discuss/ > 8. http://40googlegroups.com/ > 9. https://groups.google.com/ > 10. https://groups.google.com/d/ > 11. http://40googlegroups.com/ > 12. https://groups.google.com/groups/opt_out > 13. https://groups.google.com/d/ > 14. http://40googlegroups.com/ > 15. https://groups.google.com/groups/opt_out > 16. javascript:/ > 17. javascript:/ > 18. https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d > 19. http://40googlegroups.com/ > 20. https://groups.google.com/groups/opt_out > 21. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0- > 22. http://40googlegroups.com/ > 23. https://groups.google.com/groups/opt_out > 24. https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a- > 25. http://40googlegroups.com/ > 26. https://groups.google.com/groups/opt_out > 27. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com > 28. https://groups.google.com/groups/opt_out > 29. https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4%40googlegroups.com > 30. https://groups.google.com/groups/opt_out > 31. https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc%40googlegroups.com > 32. https://groups.google.com/groups/opt_out > 33. https://groups.google.com/d/msgid/pandoc-discuss/8470226a-c385-42bd-a6ba-71037729c707%40googlegroups.com > 34. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131008204913.GB26656-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131008204913.GB26656-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2013-10-08 21:58 ` Nick Bart [not found] ` <86ec8122-f24b-4251-a8f3-89953c0cf7a5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-08 21:58 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 10916 bytes --] Alright: Output of cabal clean && cabal install -v2 and cabal clean && cabal install -v2 --force-reinstalls is at https://gist.github.com/anonymous/6892387. A few more details: Haskell installed via homebrew: brew install haskell-platform brew install ghc brew install icu4c Also tried, as recommended by Joseph, rm -rf ~/.pandoc ~/.cabal ~/.ghc ~/src/{pandoc,pandoc-types,pandoc-citeproc} before reinstalling. On Tuesday, 8 October 2013 20:49:14 UTC, fiddlosopher wrote: > > Even stranger. I use roughly the same setup at home. > > Why don't you send the output of > > cabal clean && cabal install -v2 > > > +++ Nick Bart [Oct 08 13 12:06 ]: > > Mac OS X 10.7.5 > > $ cabal --version > > cabal-install version 1.18.0.2 > > using version 1.18.1 of the Cabal library > > On Tuesday, October 8, 2013 6:56:02 PM UTC, fiddlosopher wrote: > > > > Very strange. I just installed with no problems. What OS > > are you using? What does 'cabal --version' say? > > +++ Nick Bart [Oct 08 13 11:33 ]: > > > Sorry but no, not even removing the complete pandoc, > > pandoc-citeproc, > > > and pandoc-types directories and a fresh > > > git clone git://[1]github.com/jgm/pandoc-types > > > git clone git://[2]github.com/jgm/pandoc-citeproc > > > git clone git://[3]github.com/jgm/pandoc > > > did the trick. Anything else I could try? > > > On Tuesday, October 8, 2013 6:10:41 PM UTC, fiddlosopher > wrote: > > > > > > Try removing the dist subdirectory entirely, if 'cabal > clean' > > > doesn't do that. > > > +++ Nick Bart [Oct 08 13 10:45 ]: > > > > Hmm, no. Any other ideas? > > > > On Tuesday, October 8, 2013 1:39:05 PM UTC, > fiddlosopher > > wrote: > > > > > > > > Do cabal clean first, then it should build > > > > On Oct 7, 2013, at 11:26 PM, Nick Bart > > <[1]nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > > > wrote: > > > > > > > > Now, since yesterday pandoc doesn't build any longer: > > > > pandoc $ cabal install --enable-tests > --force-reinstalls > > > > Resolving dependencies... > > > > Warning: The following packages are likely to be broken > > by the > > > > reinstalls: > > > > pandoc-citeproc-0.1.1.2 > > > > Continuing even though the plan contains dangerous > > reinstalls. > > > > Configuring pandoc-1.12.0.2... > > > > Building pandoc-1.12.0.2... > > > > setup: internal error: componentsInBuildOrder: no such > > > component: > > > > CExeName "make-pandoc-man-pages" > > > > Failed to install pandoc-1.12.0.2 > > > > cabal: Error: some packages failed to install: > > > > pandoc-1.12.0.2 failed during the building phase. The > > exception > > > was: > > > > ExitFailure 1 > > > > Any ideas? > > > > > > > > -- > > > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To post to this group, send email to > > > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To view this discussion on the web visit > > > > [4][1][4]https://groups.google. > > com/d/msgid/pandoc-discuss/ > > > 28779dd0- > > > > 99a6-448c-8967-6d37bdba58ad%[2][5]40googlegroups.com. > > > > For more options, visit [5][3][6]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 [4]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To post to this group, send email to > > > [5]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To view this discussion on the web visit > > > > [6][6][7]https://groups.google. > > com/d/msgid/pandoc-discuss/ > > > 63edb53b-b03c-468a- > > > > a60b-6bba4777cbf4%[7][8]40googlegroups.com. > > > > For more options, visit [7][8][9]https://groups.google. > > > com/ > > > groups/opt_out. > > > > > > > > References > > > > > > > > 1. javascript:/ > > > > 2. javascript:/ > > > > 3. javascript:/ > > > > 4. [9][10]https://groups.google.com/d/ > > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > > > [11]40googlegroups.com > > > > 5. [10][12]https://groups.google.com/groups/opt_out > > > > 6. [11][13]https://groups.google.com/d/ > > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > > > [14]40googlegroups.com > > > > 7. [12][15]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 [16]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to > > [17]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit > > > [13][18]https://groups.google.com/d/msgid/pandoc-discuss/ > > 233c21c4-cff5-452d > > > -8269-80981156bddc%[19]40googlegroups.com. > > > For more options, visit [14][20]https://groups.google.com/ > > groups/opt_out. > > > > > > References > > > > > > 1. [21]https://groups.google.com/d/ > > msgid/pandoc-discuss/28779dd0- > > > 2. [22]http://40googlegroups.com/ > > > 3. [23]https://groups.google.com/groups/opt_out > > > 4. javascript:/ > > > 5. javascript:/ > > > 6. [24]https://groups.google.com/d/ > > msgid/pandoc-discuss/63edb53b-b03c-468a- > > > 7. [25]http://40googlegroups.com/ > > > 8. [26]https://groups.google.com/groups/opt_out > > > 9. [27]https://groups.google.com/d/ > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > > 40googlegroups.com > > > 10. [28]https://groups.google.com/groups/opt_out > > > 11. [29]https://groups.google.com/d/ > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > > 40googlegroups.com > > > 12. [30]https://groups.google.com/groups/opt_out > > > 13. [31]https://groups.google.com/d/ > > msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc% > > 40googlegroups.com > > > 14. [32]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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [33] > https://groups.google.com/d/msgid/pandoc-discuss/8470226a-c385-42bd > > -a6ba-71037729c707%40googlegroups.com. > > For more options, visit [34]https://groups.google.com/groups/opt_out. > > > > > References > > > > 1. http://github.com/jgm/pandoc-types > > 2. http://github.com/jgm/pandoc-citeproc > > 3. http://github.com/jgm/pandoc > > 4. https://groups.google.com/d/msgid/pandoc-discuss/ > > 5. http://40googlegroups.com/ > > 6. https://groups.google.com/ > > 7. https://groups.google.com/d/msgid/pandoc-discuss/ > > 8. http://40googlegroups.com/ > > 9. https://groups.google.com/ > > 10. https://groups.google.com/d/ > > 11. http://40googlegroups.com/ > > 12. https://groups.google.com/groups/opt_out > > 13. https://groups.google.com/d/ > > 14. http://40googlegroups.com/ > > 15. https://groups.google.com/groups/opt_out > > 16. javascript:/ > > 17. javascript:/ > > 18. > https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d > > 19. http://40googlegroups.com/ > > 20. https://groups.google.com/groups/opt_out > > 21. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0- > > 22. http://40googlegroups.com/ > > 23. https://groups.google.com/groups/opt_out > > 24. > https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a- > > 25. http://40googlegroups.com/ > > 26. https://groups.google.com/groups/opt_out > > 27. > https://groups.google.com/d/msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com > > 28. https://groups.google.com/groups/opt_out > > 29. > https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4%40googlegroups.com > > 30. https://groups.google.com/groups/opt_out > > 31. > https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc%40googlegroups.com > > 32. https://groups.google.com/groups/opt_out > > 33. > https://groups.google.com/d/msgid/pandoc-discuss/8470226a-c385-42bd-a6ba-71037729c707%40googlegroups.com > > 34. 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/86ec8122-f24b-4251-a8f3-89953c0cf7a5%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 22177 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <86ec8122-f24b-4251-a8f3-89953c0cf7a5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <86ec8122-f24b-4251-a8f3-89953c0cf7a5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-09 3:12 ` John MacFarlane [not found] ` <20131009031248.GA51945-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-09 3:12 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Sure enough -- I had cabal-install 1.16 with Cabal 1.16. When I upgraded to 1.18 I got the same error you did. +++ Nick Bart [Oct 08 13 14:58 ]: > Alright: Output of cabal clean && cabal install -v2 and cabal clean && > cabal install -v2 --force-reinstalls is at > https://gist.github.com/anonymous/6892387. > A few more details: Haskell installed via homebrew: > brew install haskell-platform > brew install ghc > brew install icu4c > Also tried, as recommended by Joseph, > rm -rf ~/.pandoc ~/.cabal ~/.ghc > ~/src/{pandoc,pandoc-types,pandoc-citeproc} > before reinstalling. > On Tuesday, 8 October 2013 20:49:14 UTC, fiddlosopher wrote: > > Even stranger. I use roughly the same setup at home. > Why don't you send the output of > cabal clean && cabal install -v2 > +++ Nick Bart [Oct 08 13 12:06 ]: > > Mac OS X 10.7.5 > > $ cabal --version > > cabal-install version 1.18.0.2 > > using version 1.18.1 of the Cabal library > > On Tuesday, October 8, 2013 6:56:02 PM UTC, fiddlosopher wrote: > > > > Very strange. I just installed with no problems. What OS > > are you using? What does 'cabal --version' say? > > +++ Nick Bart [Oct 08 13 11:33 ]: > > > Sorry but no, not even removing the complete pandoc, > > pandoc-citeproc, > > > and pandoc-types directories and a fresh > > > git clone git://[1][1]github.com/jgm/pandoc-types > > > git clone git://[2][2]github.com/jgm/pandoc-citeproc > > > git clone git://[3][3]github.com/jgm/pandoc > > > did the trick. Anything else I could try? > > > On Tuesday, October 8, 2013 6:10:41 PM UTC, fiddlosopher > wrote: > > > > > > Try removing the dist subdirectory entirely, if 'cabal > clean' > > > doesn't do that. > > > +++ Nick Bart [Oct 08 13 10:45 ]: > > > > Hmm, no. Any other ideas? > > > > On Tuesday, October 8, 2013 1:39:05 PM UTC, > fiddlosopher > > wrote: > > > > > > > > Do cabal clean first, then it should build > > > > On Oct 7, 2013, at 11:26 PM, Nick Bart > > <[1]nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > > > wrote: > > > > > > > > Now, since yesterday pandoc doesn't build any > longer: > > > > pandoc $ cabal install --enable-tests > --force-reinstalls > > > > Resolving dependencies... > > > > Warning: The following packages are likely to be > broken > > by the > > > > reinstalls: > > > > pandoc-citeproc-0.1.1.2 > > > > Continuing even though the plan contains > dangerous > > reinstalls. > > > > Configuring pandoc-1.12.0.2... > > > > Building pandoc-1.12.0.2... > > > > setup: internal error: componentsInBuildOrder: no > such > > > component: > > > > CExeName "make-pandoc-man-pages" > > > > Failed to install pandoc-1.12.0.2 > > > > cabal: Error: some packages failed to install: > > > > pandoc-1.12.0.2 failed during the building phase. > The > > exception > > > was: > > > > ExitFailure 1 > > > > Any ideas? > > > > > > > > -- > > > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To post to this group, send email to > > > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To view this discussion on the web visit > > > > [4][1][4][4]https://groups.google. > > com/d/msgid/pandoc-discuss/ > > > 28779dd0- > > > > 99a6-448c-8967-6d37bdba58ad%[ > 2][5][5]40googlegroups.com. > > > > For more options, visit > [5][3][6][6]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 [4]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To post to this group, send email to > > > [5]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To view this discussion on the web visit > > > > [6][6][7][7]https://groups.google. > > com/d/msgid/pandoc-discuss/ > > > 63edb53b-b03c-468a- > > > > a60b-6bba4777cbf4%[7][8][8]40googlegroups.com. > > > > For more options, visit > [7][8][9][9]https://groups.google. > > com/ > > > groups/opt_out. > > > > > > > > References > > > > > > > > 1. javascript:/ > > > > 2. javascript:/ > > > > 3. javascript:/ > > > > 4. [9][10][10]https://groups.google.com/d/ > > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967- > 6d37bdba58ad% > > > [11][11]40googlegroups.com > > > > 5. [10][12][12]https://groups.google. > com/groups/opt_out > > > > 6. [11][13][13]https://groups.google.com/d/ > > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b- > 6bba4777cbf4% > > > [14][14]40googlegroups.com > > > > 7. [12][15][15]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 [16]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to > > [17]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit > > > [13][18][16]https://groups.google.com/d/msgid/pandoc- > discuss/ > > 233c21c4-cff5-452d > > > -8269-80981156bddc%[19][17]40googlegroups.com. > > > For more options, visit > [14][20][18]https://groups.google.com/ > > groups/opt_out. > > > > > > References > > > > > > 1. [21][19]https://groups.google.com/d/ > > msgid/pandoc-discuss/28779dd0- > > > 2. [22][20]http://40googlegroups.com/ > > > 3. [23][21]https://groups.google.com/groups/opt_out > > > 4. javascript:/ > > > 5. javascript:/ > > > 6. [24][22]https://groups.google.com/d/ > > msgid/pandoc-discuss/63edb53b-b03c-468a- > > > 7. [25][23]http://40googlegroups.com/ > > > 8. [26][24]https://groups.google.com/groups/opt_out > > > 9. [27][25]https://groups.google.com/d/ > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > > [26]40googlegroups.com > > > 10. [28][27]https://groups.google.com/groups/opt_out > > > 11. [29][28]https://groups.google.com/d/ > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > > [29]40googlegroups.com > > > 12. [30][30]https://groups.google.com/groups/opt_out > > > 13. [31][31]https://groups.google.com/d/ > > msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc% > > [32]40googlegroups.com > > > 14. [32][33]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 [34]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To post to this group, send email to > [35]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit > > [33][36]https://groups.google.com/d/msgid/pandoc-discuss/ > 8470226a-c385-42bd > > -a6ba-71037729c707%[37]40googlegroups.com. > > For more options, visit [34][38]https://groups.google.com/ > groups/opt_out. > > > > References > > > > 1. [39]http://github.com/jgm/pandoc-types > > 2. [40]http://github.com/jgm/pandoc-citeproc > > 3. [41]http://github.com/jgm/pandoc > > 4. [42]https://groups.google.com/d/msgid/pandoc-discuss/ > > 5. [43]http://40googlegroups.com/ > > 6. [44]https://groups.google.com/ > > 7. [45]https://groups.google.com/d/msgid/pandoc-discuss/ > > 8. [46]http://40googlegroups.com/ > > 9. [47]https://groups.google.com/ > > 10. [48]https://groups.google.com/d/ > > 11. [49]http://40googlegroups.com/ > > 12. [50]https://groups.google.com/groups/opt_out > > 13. [51]https://groups.google.com/d/ > > 14. [52]http://40googlegroups.com/ > > 15. [53]https://groups.google.com/groups/opt_out > > 16. javascript:/ > > 17. javascript:/ > > 18. [54]https://groups.google.com/d/ > msgid/pandoc-discuss/233c21c4-cff5-452d > > 19. [55]http://40googlegroups.com/ > > 20. [56]https://groups.google.com/groups/opt_out > > 21. [57]https://groups.google.com/d/ > msgid/pandoc-discuss/28779dd0- > > 22. [58]http://40googlegroups.com/ > > 23. [59]https://groups.google.com/groups/opt_out > > 24. [60]https://groups.google.com/d/ > msgid/pandoc-discuss/63edb53b-b03c-468a- > > 25. [61]http://40googlegroups.com/ > > 26. [62]https://groups.google.com/groups/opt_out > > 27. [63]https://groups.google.com/d/ > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > 40googlegroups.com > > 28. [64]https://groups.google.com/groups/opt_out > > 29. [65]https://groups.google.com/d/ > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > 40googlegroups.com > > 30. [66]https://groups.google.com/groups/opt_out > > 31. [67]https://groups.google.com/d/ > msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc% > 40googlegroups.com > > 32. [68]https://groups.google.com/groups/opt_out > > 33. [69]https://groups.google.com/d/ > msgid/pandoc-discuss/8470226a-c385-42bd-a6ba-71037729c707% > 40googlegroups.com > > 34. [70]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 > [71]https://groups.google.com/d/msgid/pandoc-discuss/86ec8122-f24b-4251 > -a8f3-89953c0cf7a5%40googlegroups.com. > For more options, visit [72]https://groups.google.com/groups/opt_out. > > References > > 1. http://github.com/jgm/pandoc-types > 2. http://github.com/jgm/pandoc-citeproc > 3. http://github.com/jgm/pandoc > 4. https://groups.google/ > 5. http://40googlegroups.com/ > 6. https://groups.google/ > 7. https://groups.google/ > 8. http://40googlegroups.com/ > 9. https://groups.google/ > 10. https://groups.google.com/d/ > 11. http://40googlegroups.com/ > 12. https://groups.google.com/groups/opt_out > 13. https://groups.google.com/d/ > 14. http://40googlegroups.com/ > 15. https://groups.google.com/groups/opt_out > 16. https://groups.google.com/d/msgid/pandoc-discuss/ > 17. http://40googlegroups.com/ > 18. https://groups.google.com/ > 19. https://groups.google.com/d/ > 20. http://40googlegroups.com/ > 21. https://groups.google.com/groups/opt_out > 22. https://groups.google.com/d/ > 23. http://40googlegroups.com/ > 24. https://groups.google.com/groups/opt_out > 25. https://groups.google.com/d/ > 26. http://40googlegroups.com/ > 27. https://groups.google.com/groups/opt_out > 28. https://groups.google.com/d/ > 29. http://40googlegroups.com/ > 30. https://groups.google.com/groups/opt_out > 31. https://groups.google.com/d/ > 32. http://40googlegroups.com/ > 33. https://groups.google.com/groups/opt_out > 34. javascript:/ > 35. javascript:/ > 36. https://groups.google.com/d/msgid/pandoc-discuss/8470226a-c385-42bd > 37. http://40googlegroups.com/ > 38. https://groups.google.com/groups/opt_out > 39. http://github.com/jgm/pandoc-types > 40. http://github.com/jgm/pandoc-citeproc > 41. http://github.com/jgm/pandoc > 42. https://groups.google.com/d/msgid/pandoc-discuss/ > 43. http://40googlegroups.com/ > 44. https://groups.google.com/ > 45. https://groups.google.com/d/msgid/pandoc-discuss/ > 46. http://40googlegroups.com/ > 47. https://groups.google.com/ > 48. https://groups.google.com/d/ > 49. http://40googlegroups.com/ > 50. https://groups.google.com/groups/opt_out > 51. https://groups.google.com/d/ > 52. http://40googlegroups.com/ > 53. https://groups.google.com/groups/opt_out > 54. https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d > 55. http://40googlegroups.com/ > 56. https://groups.google.com/groups/opt_out > 57. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0- > 58. http://40googlegroups.com/ > 59. https://groups.google.com/groups/opt_out > 60. https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a- > 61. http://40googlegroups.com/ > 62. https://groups.google.com/groups/opt_out > 63. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com > 64. https://groups.google.com/groups/opt_out > 65. https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4%40googlegroups.com > 66. https://groups.google.com/groups/opt_out > 67. https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc%40googlegroups.com > 68. https://groups.google.com/groups/opt_out > 69. https://groups.google.com/d/msgid/pandoc-discuss/8470226a-c385-42bd-a6ba-71037729c707%40googlegroups.com > 70. https://groups.google.com/groups/opt_out > 71. https://groups.google.com/d/msgid/pandoc-discuss/86ec8122-f24b-4251-a8f3-89953c0cf7a5%40googlegroups.com > 72. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131009031248.GA51945-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131009031248.GA51945-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-09 4:04 ` John MacFarlane [not found] ` <20131009040446.GC51945-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-09 4:04 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Try the latest. +++ John MacFarlane [Oct 08 13 20:12 ]: > Sure enough -- I had cabal-install 1.16 with Cabal 1.16. When > I upgraded to 1.18 I got the same error you did. > > +++ Nick Bart [Oct 08 13 14:58 ]: > > Alright: Output of cabal clean && cabal install -v2 and cabal clean && > > cabal install -v2 --force-reinstalls is at > > https://gist.github.com/anonymous/6892387. > > A few more details: Haskell installed via homebrew: > > brew install haskell-platform > > brew install ghc > > brew install icu4c > > Also tried, as recommended by Joseph, > > rm -rf ~/.pandoc ~/.cabal ~/.ghc > > ~/src/{pandoc,pandoc-types,pandoc-citeproc} > > before reinstalling. > > On Tuesday, 8 October 2013 20:49:14 UTC, fiddlosopher wrote: > > > > Even stranger. I use roughly the same setup at home. > > Why don't you send the output of > > cabal clean && cabal install -v2 > > +++ Nick Bart [Oct 08 13 12:06 ]: > > > Mac OS X 10.7.5 > > > $ cabal --version > > > cabal-install version 1.18.0.2 > > > using version 1.18.1 of the Cabal library > > > On Tuesday, October 8, 2013 6:56:02 PM UTC, fiddlosopher wrote: > > > > > > Very strange. I just installed with no problems. What OS > > > are you using? What does 'cabal --version' say? > > > +++ Nick Bart [Oct 08 13 11:33 ]: > > > > Sorry but no, not even removing the complete pandoc, > > > pandoc-citeproc, > > > > and pandoc-types directories and a fresh > > > > git clone git://[1][1]github.com/jgm/pandoc-types > > > > git clone git://[2][2]github.com/jgm/pandoc-citeproc > > > > git clone git://[3][3]github.com/jgm/pandoc > > > > did the trick. Anything else I could try? > > > > On Tuesday, October 8, 2013 6:10:41 PM UTC, fiddlosopher > > wrote: > > > > > > > > Try removing the dist subdirectory entirely, if 'cabal > > clean' > > > > doesn't do that. > > > > +++ Nick Bart [Oct 08 13 10:45 ]: > > > > > Hmm, no. Any other ideas? > > > > > On Tuesday, October 8, 2013 1:39:05 PM UTC, > > fiddlosopher > > > wrote: > > > > > > > > > > Do cabal clean first, then it should build > > > > > On Oct 7, 2013, at 11:26 PM, Nick Bart > > > <[1]nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > > > > wrote: > > > > > > > > > > Now, since yesterday pandoc doesn't build any > > longer: > > > > > pandoc $ cabal install --enable-tests > > --force-reinstalls > > > > > Resolving dependencies... > > > > > Warning: The following packages are likely to be > > broken > > > by the > > > > > reinstalls: > > > > > pandoc-citeproc-0.1.1.2 > > > > > Continuing even though the plan contains > > dangerous > > > reinstalls. > > > > > Configuring pandoc-1.12.0.2... > > > > > Building pandoc-1.12.0.2... > > > > > setup: internal error: componentsInBuildOrder: no > > such > > > > component: > > > > > CExeName "make-pandoc-man-pages" > > > > > Failed to install pandoc-1.12.0.2 > > > > > cabal: Error: some packages failed to install: > > > > > pandoc-1.12.0.2 failed during the building phase. > > The > > > exception > > > > was: > > > > > ExitFailure 1 > > > > > Any ideas? > > > > > > > > > > -- > > > > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > To post to this group, send email to > > > > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > To view this discussion on the web visit > > > > > [4][1][4][4]https://groups.google. > > > com/d/msgid/pandoc-discuss/ > > > > 28779dd0- > > > > > 99a6-448c-8967-6d37bdba58ad%[ > > 2][5][5]40googlegroups.com. > > > > > For more options, visit > > [5][3][6][6]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 [4]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > To post to this group, send email to > > > > [5]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > To view this discussion on the web visit > > > > > [6][6][7][7]https://groups.google. > > > com/d/msgid/pandoc-discuss/ > > > > 63edb53b-b03c-468a- > > > > > a60b-6bba4777cbf4%[7][8][8]40googlegroups.com. > > > > > For more options, visit > > [7][8][9][9]https://groups.google. > > > com/ > > > > groups/opt_out. > > > > > > > > > > References > > > > > > > > > > 1. javascript:/ > > > > > 2. javascript:/ > > > > > 3. javascript:/ > > > > > 4. [9][10][10]https://groups.google.com/d/ > > > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967- > > 6d37bdba58ad% > > > > [11][11]40googlegroups.com > > > > > 5. [10][12][12]https://groups.google. > > com/groups/opt_out > > > > > 6. [11][13][13]https://groups.google.com/d/ > > > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b- > > 6bba4777cbf4% > > > > [14][14]40googlegroups.com > > > > > 7. [12][15][15]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 [16]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To post to this group, send email to > > > [17]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To view this discussion on the web visit > > > > [13][18][16]https://groups.google.com/d/msgid/pandoc- > > discuss/ > > > 233c21c4-cff5-452d > > > > -8269-80981156bddc%[19][17]40googlegroups.com. > > > > For more options, visit > > [14][20][18]https://groups.google.com/ > > > groups/opt_out. > > > > > > > > References > > > > > > > > 1. [21][19]https://groups.google.com/d/ > > > msgid/pandoc-discuss/28779dd0- > > > > 2. [22][20]http://40googlegroups.com/ > > > > 3. [23][21]https://groups.google.com/groups/opt_out > > > > 4. javascript:/ > > > > 5. javascript:/ > > > > 6. [24][22]https://groups.google.com/d/ > > > msgid/pandoc-discuss/63edb53b-b03c-468a- > > > > 7. [25][23]http://40googlegroups.com/ > > > > 8. [26][24]https://groups.google.com/groups/opt_out > > > > 9. [27][25]https://groups.google.com/d/ > > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > > > [26]40googlegroups.com > > > > 10. [28][27]https://groups.google.com/groups/opt_out > > > > 11. [29][28]https://groups.google.com/d/ > > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > > > [29]40googlegroups.com > > > > 12. [30][30]https://groups.google.com/groups/opt_out > > > > 13. [31][31]https://groups.google.com/d/ > > > msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc% > > > [32]40googlegroups.com > > > > 14. [32][33]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 [34]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to > > [35]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit > > > [33][36]https://groups.google.com/d/msgid/pandoc-discuss/ > > 8470226a-c385-42bd > > > -a6ba-71037729c707%[37]40googlegroups.com. > > > For more options, visit [34][38]https://groups.google.com/ > > groups/opt_out. > > > > > > References > > > > > > 1. [39]http://github.com/jgm/pandoc-types > > > 2. [40]http://github.com/jgm/pandoc-citeproc > > > 3. [41]http://github.com/jgm/pandoc > > > 4. [42]https://groups.google.com/d/msgid/pandoc-discuss/ > > > 5. [43]http://40googlegroups.com/ > > > 6. [44]https://groups.google.com/ > > > 7. [45]https://groups.google.com/d/msgid/pandoc-discuss/ > > > 8. [46]http://40googlegroups.com/ > > > 9. [47]https://groups.google.com/ > > > 10. [48]https://groups.google.com/d/ > > > 11. [49]http://40googlegroups.com/ > > > 12. [50]https://groups.google.com/groups/opt_out > > > 13. [51]https://groups.google.com/d/ > > > 14. [52]http://40googlegroups.com/ > > > 15. [53]https://groups.google.com/groups/opt_out > > > 16. javascript:/ > > > 17. javascript:/ > > > 18. [54]https://groups.google.com/d/ > > msgid/pandoc-discuss/233c21c4-cff5-452d > > > 19. [55]http://40googlegroups.com/ > > > 20. [56]https://groups.google.com/groups/opt_out > > > 21. [57]https://groups.google.com/d/ > > msgid/pandoc-discuss/28779dd0- > > > 22. [58]http://40googlegroups.com/ > > > 23. [59]https://groups.google.com/groups/opt_out > > > 24. [60]https://groups.google.com/d/ > > msgid/pandoc-discuss/63edb53b-b03c-468a- > > > 25. [61]http://40googlegroups.com/ > > > 26. [62]https://groups.google.com/groups/opt_out > > > 27. [63]https://groups.google.com/d/ > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > > 40googlegroups.com > > > 28. [64]https://groups.google.com/groups/opt_out > > > 29. [65]https://groups.google.com/d/ > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > > 40googlegroups.com > > > 30. [66]https://groups.google.com/groups/opt_out > > > 31. [67]https://groups.google.com/d/ > > msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc% > > 40googlegroups.com > > > 32. [68]https://groups.google.com/groups/opt_out > > > 33. [69]https://groups.google.com/d/ > > msgid/pandoc-discuss/8470226a-c385-42bd-a6ba-71037729c707% > > 40googlegroups.com > > > 34. [70]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 > > [71]https://groups.google.com/d/msgid/pandoc-discuss/86ec8122-f24b-4251 > > -a8f3-89953c0cf7a5%40googlegroups.com. > > For more options, visit [72]https://groups.google.com/groups/opt_out. > > > > References > > > > 1. http://github.com/jgm/pandoc-types > > 2. http://github.com/jgm/pandoc-citeproc > > 3. http://github.com/jgm/pandoc > > 4. https://groups.google/ > > 5. http://40googlegroups.com/ > > 6. https://groups.google/ > > 7. https://groups.google/ > > 8. http://40googlegroups.com/ > > 9. https://groups.google/ > > 10. https://groups.google.com/d/ > > 11. http://40googlegroups.com/ > > 12. https://groups.google.com/groups/opt_out > > 13. https://groups.google.com/d/ > > 14. http://40googlegroups.com/ > > 15. https://groups.google.com/groups/opt_out > > 16. https://groups.google.com/d/msgid/pandoc-discuss/ > > 17. http://40googlegroups.com/ > > 18. https://groups.google.com/ > > 19. https://groups.google.com/d/ > > 20. http://40googlegroups.com/ > > 21. https://groups.google.com/groups/opt_out > > 22. https://groups.google.com/d/ > > 23. http://40googlegroups.com/ > > 24. https://groups.google.com/groups/opt_out > > 25. https://groups.google.com/d/ > > 26. http://40googlegroups.com/ > > 27. https://groups.google.com/groups/opt_out > > 28. https://groups.google.com/d/ > > 29. http://40googlegroups.com/ > > 30. https://groups.google.com/groups/opt_out > > 31. https://groups.google.com/d/ > > 32. http://40googlegroups.com/ > > 33. https://groups.google.com/groups/opt_out > > 34. javascript:/ > > 35. javascript:/ > > 36. https://groups.google.com/d/msgid/pandoc-discuss/8470226a-c385-42bd > > 37. http://40googlegroups.com/ > > 38. https://groups.google.com/groups/opt_out > > 39. http://github.com/jgm/pandoc-types > > 40. http://github.com/jgm/pandoc-citeproc > > 41. http://github.com/jgm/pandoc > > 42. https://groups.google.com/d/msgid/pandoc-discuss/ > > 43. http://40googlegroups.com/ > > 44. https://groups.google.com/ > > 45. https://groups.google.com/d/msgid/pandoc-discuss/ > > 46. http://40googlegroups.com/ > > 47. https://groups.google.com/ > > 48. https://groups.google.com/d/ > > 49. http://40googlegroups.com/ > > 50. https://groups.google.com/groups/opt_out > > 51. https://groups.google.com/d/ > > 52. http://40googlegroups.com/ > > 53. https://groups.google.com/groups/opt_out > > 54. https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d > > 55. http://40googlegroups.com/ > > 56. https://groups.google.com/groups/opt_out > > 57. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0- > > 58. http://40googlegroups.com/ > > 59. https://groups.google.com/groups/opt_out > > 60. https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a- > > 61. http://40googlegroups.com/ > > 62. https://groups.google.com/groups/opt_out > > 63. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com > > 64. https://groups.google.com/groups/opt_out > > 65. https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4%40googlegroups.com > > 66. https://groups.google.com/groups/opt_out > > 67. https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc%40googlegroups.com > > 68. https://groups.google.com/groups/opt_out > > 69. https://groups.google.com/d/msgid/pandoc-discuss/8470226a-c385-42bd-a6ba-71037729c707%40googlegroups.com > > 70. https://groups.google.com/groups/opt_out > > 71. https://groups.google.com/d/msgid/pandoc-discuss/86ec8122-f24b-4251-a8f3-89953c0cf7a5%40googlegroups.com > > 72. 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/20131009031248.GA51945%40Johns-MacBook-Pro.local. > For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131009040446.GC51945-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131009040446.GC51945-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-09 6:09 ` Nick Bart [not found] ` <3892d517-a405-4c70-a9ab-0b7195d28203-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-09 6:09 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 19028 bytes --] Now that sure fixed it. Thank you! On Wednesday, October 9, 2013 4:04:47 AM UTC, fiddlosopher wrote: > > Try the latest. > > +++ John MacFarlane [Oct 08 13 20:12 ]: > > Sure enough -- I had cabal-install 1.16 with Cabal 1.16. When > > I upgraded to 1.18 I got the same error you did. > > > > +++ Nick Bart [Oct 08 13 14:58 ]: > > > Alright: Output of cabal clean && cabal install -v2 and cabal clean > && > > > cabal install -v2 --force-reinstalls is at > > > https://gist.github.com/anonymous/6892387. > > > A few more details: Haskell installed via homebrew: > > > brew install haskell-platform > > > brew install ghc > > > brew install icu4c > > > Also tried, as recommended by Joseph, > > > rm -rf ~/.pandoc ~/.cabal ~/.ghc > > > ~/src/{pandoc,pandoc-types,pandoc-citeproc} > > > before reinstalling. > > > On Tuesday, 8 October 2013 20:49:14 UTC, fiddlosopher wrote: > > > > > > Even stranger. I use roughly the same setup at home. > > > Why don't you send the output of > > > cabal clean && cabal install -v2 > > > +++ Nick Bart [Oct 08 13 12:06 ]: > > > > Mac OS X 10.7.5 > > > > $ cabal --version > > > > cabal-install version 1.18.0.2 > > > > using version 1.18.1 of the Cabal library > > > > On Tuesday, October 8, 2013 6:56:02 PM UTC, fiddlosopher > wrote: > > > > > > > > Very strange. I just installed with no problems. What OS > > > > are you using? What does 'cabal --version' say? > > > > +++ Nick Bart [Oct 08 13 11:33 ]: > > > > > Sorry but no, not even removing the complete pandoc, > > > > pandoc-citeproc, > > > > > and pandoc-types directories and a fresh > > > > > git clone git://[1][1]github.com/jgm/pandoc-types > > > > > git clone git://[2][2]github.com/jgm/pandoc-citeproc > > > > > git clone git://[3][3]github.com/jgm/pandoc > > > > > did the trick. Anything else I could try? > > > > > On Tuesday, October 8, 2013 6:10:41 PM UTC, > fiddlosopher > > > wrote: > > > > > > > > > > Try removing the dist subdirectory entirely, if > 'cabal > > > clean' > > > > > doesn't do that. > > > > > +++ Nick Bart [Oct 08 13 10:45 ]: > > > > > > Hmm, no. Any other ideas? > > > > > > On Tuesday, October 8, 2013 1:39:05 PM UTC, > > > fiddlosopher > > > > wrote: > > > > > > > > > > > > Do cabal clean first, then it should build > > > > > > On Oct 7, 2013, at 11:26 PM, Nick Bart > > > > <[1]nickba...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > > > > > wrote: > > > > > > > > > > > > Now, since yesterday pandoc doesn't build any > > > longer: > > > > > > pandoc $ cabal install --enable-tests > > > --force-reinstalls > > > > > > Resolving dependencies... > > > > > > Warning: The following packages are likely to > be > > > broken > > > > by the > > > > > > reinstalls: > > > > > > pandoc-citeproc-0.1.1.2 > > > > > > Continuing even though the plan contains > > > dangerous > > > > reinstalls. > > > > > > Configuring pandoc-1.12.0.2... > > > > > > Building pandoc-1.12.0.2... > > > > > > setup: internal error: componentsInBuildOrder: > no > > > such > > > > > component: > > > > > > CExeName "make-pandoc-man-pages" > > > > > > Failed to install pandoc-1.12.0.2 > > > > > > cabal: Error: some packages failed to install: > > > > > > pandoc-1.12.0.2 failed during the building > phase. > > > The > > > > exception > > > > > was: > > > > > > ExitFailure 1 > > > > > > Any ideas? > > > > > > > > > > > > -- > > > > > > 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 [2] > pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > > To post to this group, send email to > > > > > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > > To view this discussion on the web visit > > > > > > [4][1][4][4]https://groups.google. > > > > com/d/msgid/pandoc-discuss/ > > > > > 28779dd0- > > > > > > 99a6-448c-8967-6d37bdba58ad%[ > > > 2][5][5]40googlegroups.com. > > > > > > For more options, visit > > > [5][3][6][6]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 [4] > pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > > To post to this group, send email to > > > > > [5]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > > To view this discussion on the web visit > > > > > > [6][6][7][7]https://groups.google. > > > > com/d/msgid/pandoc-discuss/ > > > > > 63edb53b-b03c-468a- > > > > > > a60b-6bba4777cbf4%[7][8][8]40googlegroups.com. > > > > > > > For more options, visit > > > [7][8][9][9]https://groups.google. > > > > com/ > > > > > groups/opt_out. > > > > > > > > > > > > References > > > > > > > > > > > > 1. javascript:/ > > > > > > 2. javascript:/ > > > > > > 3. javascript:/ > > > > > > 4. [9][10][10]https://groups.google.com/d/ > > > > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967- > > > 6d37bdba58ad% > > > > > [11][11]40googlegroups.com > > > > > > 5. [10][12][12]https://groups.google. > > > com/groups/opt_out > > > > > > 6. [11][13][13]https://groups.google.com/d/ > > > > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b- > > > 6bba4777cbf4% > > > > > [14][14]40googlegroups.com > > > > > > 7. [12][15][15]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 [16]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > To post to this group, send email to > > > > [17]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > To view this discussion on the web visit > > > > > [13][18][16]https://groups.google.com/d/msgid/pandoc- > > > discuss/ > > > > 233c21c4-cff5-452d > > > > > -8269-80981156bddc%[19][17]40googlegroups.com. > > > > > For more options, visit > > > [14][20][18]https://groups.google.com/ > > > > groups/opt_out. > > > > > > > > > > References > > > > > > > > > > 1. [21][19]https://groups.google.com/d/ > > > > msgid/pandoc-discuss/28779dd0- > > > > > 2. [22][20]http://40googlegroups.com/ > > > > > 3. [23][21]https://groups.google.com/groups/opt_out > > > > > 4. javascript:/ > > > > > 5. javascript:/ > > > > > 6. [24][22]https://groups.google.com/d/ > > > > msgid/pandoc-discuss/63edb53b-b03c-468a- > > > > > 7. [25][23]http://40googlegroups.com/ > > > > > 8. [26][24]https://groups.google.com/groups/opt_out > > > > > 9. [27][25]https://groups.google.com/d/ > > > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > > > > [26]40googlegroups.com > > > > > 10. [28][27]https://groups.google.com/groups/opt_out > > > > > 11. [29][28]https://groups.google.com/d/ > > > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > > > > [29]40googlegroups.com > > > > > 12. [30][30]https://groups.google.com/groups/opt_out > > > > > 13. [31][31]https://groups.google.com/d/ > > > > msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc% > > > > [32]40googlegroups.com > > > > > 14. [32][33]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 [34]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To post to this group, send email to > > > [35]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To view this discussion on the web visit > > > > [33][36]https://groups.google.com/d/msgid/pandoc-discuss/ > > > 8470226a-c385-42bd > > > > -a6ba-71037729c707%[37]40googlegroups.com. > > > > For more options, visit [34][38]https://groups.google.com/ > > > groups/opt_out. > > > > > > > > References > > > > > > > > 1. [39]http://github.com/jgm/pandoc-types > > > > 2. [40]http://github.com/jgm/pandoc-citeproc > > > > 3. [41]http://github.com/jgm/pandoc > > > > 4. [42]https://groups.google.com/d/msgid/pandoc-discuss/ > > > > 5. [43]http://40googlegroups.com/ > > > > 6. [44]https://groups.google.com/ > > > > 7. [45]https://groups.google.com/d/msgid/pandoc-discuss/ > > > > 8. [46]http://40googlegroups.com/ > > > > 9. [47]https://groups.google.com/ > > > > 10. [48]https://groups.google.com/d/ > > > > 11. [49]http://40googlegroups.com/ > > > > 12. [50]https://groups.google.com/groups/opt_out > > > > 13. [51]https://groups.google.com/d/ > > > > 14. [52]http://40googlegroups.com/ > > > > 15. [53]https://groups.google.com/groups/opt_out > > > > 16. javascript:/ > > > > 17. javascript:/ > > > > 18. [54]https://groups.google.com/d/ > > > msgid/pandoc-discuss/233c21c4-cff5-452d > > > > 19. [55]http://40googlegroups.com/ > > > > 20. [56]https://groups.google.com/groups/opt_out > > > > 21. [57]https://groups.google.com/d/ > > > msgid/pandoc-discuss/28779dd0- > > > > 22. [58]http://40googlegroups.com/ > > > > 23. [59]https://groups.google.com/groups/opt_out > > > > 24. [60]https://groups.google.com/d/ > > > msgid/pandoc-discuss/63edb53b-b03c-468a- > > > > 25. [61]http://40googlegroups.com/ > > > > 26. [62]https://groups.google.com/groups/opt_out > > > > 27. [63]https://groups.google.com/d/ > > > msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad% > > > 40googlegroups.com > > > > 28. [64]https://groups.google.com/groups/opt_out > > > > 29. [65]https://groups.google.com/d/ > > > msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4% > > > 40googlegroups.com > > > > 30. [66]https://groups.google.com/groups/opt_out > > > > 31. [67]https://groups.google.com/d/ > > > msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc% > > > 40googlegroups.com > > > > 32. [68]https://groups.google.com/groups/opt_out > > > > 33. [69]https://groups.google.com/d/ > > > msgid/pandoc-discuss/8470226a-c385-42bd-a6ba-71037729c707% > > > 40googlegroups.com > > > > 34. [70]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 <javascript:>. > > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > > To view this discussion on the web visit > > > [71] > https://groups.google.com/d/msgid/pandoc-discuss/86ec8122-f24b-4251 > > > -a8f3-89953c0cf7a5%40googlegroups.com. > > > For more options, visit [72] > https://groups.google.com/groups/opt_out. > > > > > > References > > > > > > 1. http://github.com/jgm/pandoc-types > > > 2. http://github.com/jgm/pandoc-citeproc > > > 3. http://github.com/jgm/pandoc > > > 4. https://groups.google/ > > > 5. http://40googlegroups.com/ > > > 6. https://groups.google/ > > > 7. https://groups.google/ > > > 8. http://40googlegroups.com/ > > > 9. https://groups.google/ > > > 10. https://groups.google.com/d/ > > > 11. http://40googlegroups.com/ > > > 12. https://groups.google.com/groups/opt_out > > > 13. https://groups.google.com/d/ > > > 14. http://40googlegroups.com/ > > > 15. https://groups.google.com/groups/opt_out > > > 16. https://groups.google.com/d/msgid/pandoc-discuss/ > > > 17. http://40googlegroups.com/ > > > 18. https://groups.google.com/ > > > 19. https://groups.google.com/d/ > > > 20. http://40googlegroups.com/ > > > 21. https://groups.google.com/groups/opt_out > > > 22. https://groups.google.com/d/ > > > 23. http://40googlegroups.com/ > > > 24. https://groups.google.com/groups/opt_out > > > 25. https://groups.google.com/d/ > > > 26. http://40googlegroups.com/ > > > 27. https://groups.google.com/groups/opt_out > > > 28. https://groups.google.com/d/ > > > 29. http://40googlegroups.com/ > > > 30. https://groups.google.com/groups/opt_out > > > 31. https://groups.google.com/d/ > > > 32. http://40googlegroups.com/ > > > 33. https://groups.google.com/groups/opt_out > > > 34. javascript:/ > > > 35. javascript:/ > > > 36. > https://groups.google.com/d/msgid/pandoc-discuss/8470226a-c385-42bd > > > 37. http://40googlegroups.com/ > > > 38. https://groups.google.com/groups/opt_out > > > 39. http://github.com/jgm/pandoc-types > > > 40. http://github.com/jgm/pandoc-citeproc > > > 41. http://github.com/jgm/pandoc > > > 42. https://groups.google.com/d/msgid/pandoc-discuss/ > > > 43. http://40googlegroups.com/ > > > 44. https://groups.google.com/ > > > 45. https://groups.google.com/d/msgid/pandoc-discuss/ > > > 46. http://40googlegroups.com/ > > > 47. https://groups.google.com/ > > > 48. https://groups.google.com/d/ > > > 49. http://40googlegroups.com/ > > > 50. https://groups.google.com/groups/opt_out > > > 51. https://groups.google.com/d/ > > > 52. http://40googlegroups.com/ > > > 53. https://groups.google.com/groups/opt_out > > > 54. > https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d > > > 55. http://40googlegroups.com/ > > > 56. https://groups.google.com/groups/opt_out > > > 57. https://groups.google.com/d/msgid/pandoc-discuss/28779dd0- > > > 58. http://40googlegroups.com/ > > > 59. https://groups.google.com/groups/opt_out > > > 60. > https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a- > > > 61. http://40googlegroups.com/ > > > 62. https://groups.google.com/groups/opt_out > > > 63. > https://groups.google.com/d/msgid/pandoc-discuss/28779dd0-99a6-448c-8967-6d37bdba58ad%40googlegroups.com > > > 64. https://groups.google.com/groups/opt_out > > > 65. > https://groups.google.com/d/msgid/pandoc-discuss/63edb53b-b03c-468a-a60b-6bba4777cbf4%40googlegroups.com > > > 66. https://groups.google.com/groups/opt_out > > > 67. > https://groups.google.com/d/msgid/pandoc-discuss/233c21c4-cff5-452d-8269-80981156bddc%40googlegroups.com > > > 68. https://groups.google.com/groups/opt_out > > > 69. > https://groups.google.com/d/msgid/pandoc-discuss/8470226a-c385-42bd-a6ba-71037729c707%40googlegroups.com > > > 70. https://groups.google.com/groups/opt_out > > > 71. > https://groups.google.com/d/msgid/pandoc-discuss/86ec8122-f24b-4251-a8f3-89953c0cf7a5%40googlegroups.com > > > 72. 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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > https://groups.google.com/d/msgid/pandoc-discuss/20131009031248.GA51945%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/3892d517-a405-4c70-a9ab-0b7195d28203%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 42226 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <3892d517-a405-4c70-a9ab-0b7195d28203-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <3892d517-a405-4c70-a9ab-0b7195d28203-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-09 7:07 ` Nick Bart [not found] ` <b3d481a7-5937-41b5-a1a7-eb4706a57884-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-09 7:07 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3194 bytes --] Date ranges in same year crash pandoc-citeproc with *some* .csl files ===================================================================== biblio2yaml now converts biblatex dates (YYYY-MM-DD) including date ranges (YYYY-MM-DD/YYYY-MM-DD) very nicely. However, I've noticed an issue concerning date ranges within the same year, where behaviour varies, depending on the .csl file used, from output as expected to pandoc-citeproc crashing. ```` $ cat test-date-range-1.md Foo [@item1, p. 12]. # References --- references: - title: Title id: item1 issued: - day: 02 month: 01 year: 2003 - day: 13 month: 12 year: 2003 author: given: - Al family: Author type: article-journal language: en-US ... $ pandoc -F pandoc-citeproc -t markdown-citations-markdown_in_html_blocks test-date-range-1.md --csl chicago-author-date.csl pandoc-citeproc: Prelude.init: empty list pandoc: Error running filter pandoc-citeproc $ pandoc -F pandoc-citeproc -t markdown-citations-markdown_in_html_blocks test-date-range-1.md --csl chicago-note-bibliography.csl Foo.[^1] References ========== Author, Al. “Title” (2–January 13, 2003). [^1]: Author, “Title,” 12. $ pandoc -F pandoc-citeproc -t markdown-citations-markdown_in_html_blocks test-date-range-1.md --csl chicago-fullnote-bibliography.csl Foo.[^1] References ========== Author, Al. “Title” (January 2–December 13, 2003). [^1]: Al Author, “Title” (January 2–December 13, 2003): 12. $ pandoc -F pandoc-citeproc -t markdown-citations-markdown_in_html_blocks test-date-range-1.md --csl apa.csl pandoc-citeproc: Prelude.init: empty list pandoc: Error running filter pandoc-citeproc $ pandoc -F pandoc-citeproc -t markdown-citations-markdown_in_html_blocks test-date-range-1.md --csl modern-language-association.csl pandoc-citeproc: Prelude.init: empty list pandoc: Error running filter pandoc-citeproc ```` So out of the .csl files tested here, chicago-fullnote-bibliography.csl works as expected, the output from chicago-note-bibliography.csl is there but contains errors, and chicago-author-date.csl, apa.csl, and modern-language-association.csl all crash the processor. Since *some* .csl files work well, it is most probably the other .csl files that need fixing. Still, I'm surprised that a broken .csl file can make pandoc-citeproc crash. I will report this to the CSL style maintainers but thought I'd first bring it up here so the behaviour of pandoc-citeproc can be checked upon. Any thoughts? -- 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/b3d481a7-5937-41b5-a1a7-eb4706a57884%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3718 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <b3d481a7-5937-41b5-a1a7-eb4706a57884-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <b3d481a7-5937-41b5-a1a7-eb4706a57884-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-09 8:26 ` Nick Bart [not found] ` <5689c697-743a-4bb4-a97b-be60c2ded766-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-09 20:07 ` John MacFarlane 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-09 8:26 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3258 bytes --] Sorting of items without an author (or editor) ============================================== - Many styles format entries without an author to start with the title in the list of references. (Some styles use something like "Anon." instead of a missing author's name; what follows is not about these kinds of styles.) If a csl style encloses titles of articles, chapters, etc. in quotation marks, these items come out at the top of the list and not at their intended alphabetic position. (Styles that do not use quotation marks around titles, such as apa.csl, do not show the sorting problem. With apa.csl, however, the in-text references come out totally wrong.) - Also, date disambiguation (2005a, 2005b) shouldn't happen here (except for the unlikely case of no author *and* identical titles). Trying a similar example with Zotero, sorting came out as expected, and no date disambiguation was added. Hence I'd suspect that at least most of these issues are caused by pandoc-citeproc. $ cat test-sorting.md Some claim [@item1; @item2; @item3]. # References --- references: - author: - family: Doe given: - John id: item1 issued: year: 2005 publisher: Publisher publisher-place: Location title: First Book type: book - id: item2 issued: year: 2005 publisher: Publisher publisher-place: Location title: Yellow book without an author, should appear under “Y” type: book - id: item3 issued: year: 2005 container-title: The Journal title: Zany article without an author, should appear under “Z” type: article-journal ... $ pandoc -S --filter pandoc-citeproc -t markdown-citations-markdown_in_html_blocks test-sorting.md --csl chicago-author-date.csl Some claim (Doe 2005; *Yellow Book Without an Author, Should Appear Under “Y”* 2005b; “Zany Article Without an Author, Should Appear Under “Z”” 2005a). References ========== “Zany Article Without an Author, Should Appear Under “Z”.” 2005a. *The Journal*. Doe, John. 2005. *First Book*. Location: Publisher. *Yellow Book Without an Author, Should Appear Under “Y”*. 2005b. Location: Publisher. $ pandoc -S --filter pandoc-citeproc -t markdown-citations-markdown_in_html_blocks test-sorting.md --csl apa.csl Some claim (Doe, 2005; *Yellow book without an author, should appear under “Y”*, 2005a, 2005b). References ========== Doe, J. (2005). *First Book*. Location: Publisher. *Yellow book without an author, should appear under “Y”*. (2005a). Location: Publisher. Zany article without an author, should appear under “Z”. (2005b). *The Journal*. -- 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/5689c697-743a-4bb4-a97b-be60c2ded766%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3805 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <5689c697-743a-4bb4-a97b-be60c2ded766-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <5689c697-743a-4bb4-a97b-be60c2ded766-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-09 19:57 ` John MacFarlane [not found] ` <20131009195731.GA14633-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-09 19:57 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ Nick Bart [Oct 09 13 01:26 ]: > Sorting of items without an author (or editor) > ============================================== > - Many styles format entries without an author to start with the title > in the list of references. (Some styles use something like "Anon." > instead of a missing author's name; what follows is not about these > kinds of styles.) If a csl style encloses titles of articles, chapters, > etc. in quotation marks, these items come out at the top of the list > and not at their intended alphabetic position. > (Styles that do not use quotation marks around titles, such as apa.csl, > do not show the sorting problem. With apa.csl, however, the in-text > references come out totally wrong.) I've fixed this by using only the portion after initial punctuation in sorting. I don't THINK this will have bad side effects, but it would be good if Andrea could review the change. > - Also, date disambiguation (2005a, 2005b) shouldn't happen here > (except for the unlikely case of no author *and* identical titles). > Trying a similar example with Zotero, sorting came out as expected, and > no date disambiguation was added. Andrea will have to help with this -- I don't understand that part of the code yet. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131009195731.GA14633-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131009195731.GA14633-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2013-10-09 20:31 ` andrea rossato [not found] ` <87iox69ofc.fsf-46C4ZU908FJ9y4XLxYaG4V6hYfS7NtTn@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: andrea rossato @ 2013-10-09 20:31 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: >> - Also, date disambiguation (2005a, 2005b) shouldn't happen here >> (except for the unlikely case of no author *and* identical titles). >> Trying a similar example with Zotero, sorting came out as expected, and >> no date disambiguation was added. > > Andrea will have to help with this -- I don't understand that part of > the code yet. yes, cite disambiguation is quite complicated -- well, the standard is quite complicated too. Nick: could you please file a bug report on the citeproc-hs issue tracker with a minimal example(including the CSL style)? That would be very helpful. Thanks. Andrea ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <87iox69ofc.fsf-46C4ZU908FJ9y4XLxYaG4V6hYfS7NtTn@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <87iox69ofc.fsf-46C4ZU908FJ9y4XLxYaG4V6hYfS7NtTn@public.gmane.org> @ 2013-10-09 23:37 ` Nick Bart 0 siblings, 0 replies; 283+ messages in thread From: Nick Bart @ 2013-10-09 23:37 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1448 bytes --] Bug report filed. Thank you for looking into this. On Wednesday, October 9, 2013 8:31:19 PM UTC, arossato wrote: > > John MacFarlane <fiddlo...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> writes: > > >> - Also, date disambiguation (2005a, 2005b) shouldn't happen here > >> (except for the unlikely case of no author *and* identical titles). > >> Trying a similar example with Zotero, sorting came out as expected, > and > >> no date disambiguation was added. > > > > Andrea will have to help with this -- I don't understand that part of > > the code yet. > > yes, cite disambiguation is quite complicated -- well, the standard is > quite complicated too. Nick: could you please file a bug report on the > citeproc-hs issue tracker with a minimal example(including the CSL > style)? That would be very helpful. Thanks. > > Andrea > -- 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/4f95eb7d-cdc4-4f11-a07a-bc8fb2288d15%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2013 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <b3d481a7-5937-41b5-a1a7-eb4706a57884-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-09 8:26 ` Nick Bart @ 2013-10-09 20:07 ` John MacFarlane [not found] ` <20131009200732.GB14633-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-09 20:07 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw It's almost certainly a problem with formatDate in src/Text/CSL/Eval/Date.hs init and last should not be used in situations where there can be an empty list. However, it would be best if Andrea could debug this, as I'm not a CSL expert. +++ Nick Bart [Oct 09 13 00:07 ]: > Date ranges in same year crash pandoc-citeproc with *some* .csl files > ===================================================================== > biblio2yaml now converts biblatex dates (YYYY-MM-DD) including date > ranges (YYYY-MM-DD/YYYY-MM-DD) very nicely. However, I've noticed an > issue concerning date ranges within the same year, where behaviour > varies, depending on the .csl file used, from output as expected to > pandoc-citeproc crashing. > ```` > $ cat test-date-range-1.md > Foo [@item1, p. 12]. > # References > --- > references: > - title: Title > id: item1 > issued: > - day: 02 > month: 01 > year: 2003 > - day: 13 > month: 12 > year: 2003 > author: > given: > - Al > family: Author > type: article-journal > language: en-US > ... > $ pandoc -F pandoc-citeproc -t > markdown-citations-markdown_in_html_blocks test-date-range-1.md --csl > chicago-author-date.csl > pandoc-citeproc: Prelude.init: empty list > pandoc: Error running filter pandoc-citeproc > $ pandoc -F pandoc-citeproc -t > markdown-citations-markdown_in_html_blocks test-date-range-1.md --csl > chicago-note-bibliography.csl > Foo.[^1] > References > ========== > Author, Al. Title (2January 13, 2003). > [^1]: Author, Title, 12. > $ pandoc -F pandoc-citeproc -t > markdown-citations-markdown_in_html_blocks test-date-range-1.md --csl > chicago-fullnote-bibliography.csl > Foo.[^1] > References > ========== > Author, Al. Title (January 2December 13, 2003). > [^1]: Al Author, Title (January 2December 13, 2003): 12. > $ pandoc -F pandoc-citeproc -t > markdown-citations-markdown_in_html_blocks test-date-range-1.md --csl > apa.csl > pandoc-citeproc: Prelude.init: empty list > pandoc: Error running filter pandoc-citeproc > $ pandoc -F pandoc-citeproc -t > markdown-citations-markdown_in_html_blocks test-date-range-1.md --csl > modern-language-association.csl > pandoc-citeproc: Prelude.init: empty list > pandoc: Error running filter pandoc-citeproc > ```` > So out of the .csl files tested here, chicago-fullnote-bibliography.csl > works as expected, the output from chicago-note-bibliography.csl is > there but contains errors, and chicago-author-date.csl, apa.csl, and > modern-language-association.csl all crash the processor. > Since *some* .csl files work well, it is most probably the other .csl > files that need fixing. Still, I'm surprised that a broken .csl file > can make pandoc-citeproc crash. > I will report this to the CSL style maintainers but thought I'd first > bring it up here so the behaviour of pandoc-citeproc can be checked > upon. > Any thoughts? > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/b3d481a7-5937-41b5- > a1a7-eb4706a57884%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/b3d481a7-5937-41b5-a1a7-eb4706a57884%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131009200732.GB14633-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131009200732.GB14633-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2013-10-09 20:41 ` andrea rossato 0 siblings, 0 replies; 283+ messages in thread From: andrea rossato @ 2013-10-09 20:41 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: > It's almost certainly a problem with formatDate in > src/Text/CSL/Eval/Date.hs > > init and last should not be used in situations where there can > be an empty list. > > However, it would be best if Andrea could debug this, as I'm not > a CSL expert. I can indeed reproduce this. The fix should be easy. I'll have a look at that. Best, Andrea ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <233c21c4-cff5-452d-8269-80981156bddc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-08 18:56 ` John MacFarlane @ 2013-10-08 19:25 ` Joseph Reagle 1 sibling, 0 replies; 283+ messages in thread From: Joseph Reagle @ 2013-10-08 19:25 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw On 10/08/2013 02:33 PM, Nick Bart wrote: > did the trick. Anything else I could try? Sounds like a purging isn't your issue, but this is the script I use to clean/install. #!/bin/sh #sudo apt-get install haskell-platform rm ~/.pandoc ~/.cabal ~/.ghc ~/.src/{pandoc,pandoc-types,pandoc-citeproc} cabal update cabal install alex happy cd .src git clone git://github.com/jgm/pandoc-types cd pandoc-types cabal update cabal install --force cd .. git clone git://github.com/jgm/pandoc-citeproc cd pandoc-citeproc cabal install --force cd .. git clone git://github.com/jgm/pandoc cd pandoc git submodule update --init cabal install --enable-tests ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131007044516.GB41791-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-10-07 6:15 ` Nick Bart @ 2013-10-07 6:24 ` Nick Bart [not found] ` <31d1a9fa-e3d5-450a-af7c-89242e0bc0cd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-07 6:24 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2980 bytes --] Well, yes, if it's biblatex. It's a literal list field, and according to the biblatex specs, any unprotected "and" *separates* two list elements, it's not part of any of them (see biblatex manual, v2.7a, § 2.3.4, "Literal Lists") If it's actually one publisher with an "and" in their name, the "and" needs to be protected by either wrapping it in braces: publisher = {Harcourt, Brace {and} Howe} or by wrapping the entire name in braces: publisher = {{Harcourt, Brace and Howe}} Both forms should of course be mapped to publisher: "Harcourt, Brace and Howe" If it's indeed two publishers, we'd have: publisher = {Paternoster Press and Eerdmans} publisher = {Univ. of Toronto Press and Routledge {and} Kegan Paul} publisher = {Univ. of Toronto Press and {Routledge and Kegan Paul}} which should come out as publisher: Paternoster Press; Eerdmans publisher: Univ. of Toronto Press; Routledge and Kegan Paul Same for institution, organization, location, origlocation, origpublisher, address, and school. E.g., location = {Exeter and Grand Rapids} is mapped to publisher-place = {Exeter; Grand Rapids} On Monday, October 7, 2013 4:45:16 AM UTC, fiddlosopher wrote: > > +++ Nick Bart [Oct 06 13 01:35 ]: > > Thank you, Bruce, for clarifying. > > Though I hope the CSL schema can be extended at some point - I'd like > > to remind of the fact that style guides differ in their requirements > > here, CMoS and APA demanding to print the first publisher and/or > place > > only, ISO 690 and MLA wanting all of them - the sensible thing for > > bibtex2pandoc, for now, would be to map all "and"s in bibtex/biblatex > > "literal list" fields, i.e., address, location, origlocation, school, > > institution, organization, howpublished, publisher, origpublisher - > > leaving proteced "{and}"s alone, of course - to something that is > > closer to the average formatting conventions, neutral with regard to > > language, and does not conflict with commas in place names, either: > > Hence I would recommend - for now - mapping any "and" in the fields > > listed above to a semicolon. > > Not so sure. Do you really want > > publisher = {Harcourt, Brace, and Howe} > > to be mapped to > > publisher: "Harcourt, Brace; Howe"? > -- 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/31d1a9fa-e3d5-450a-af7c-89242e0bc0cd%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 3733 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <31d1a9fa-e3d5-450a-af7c-89242e0bc0cd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <31d1a9fa-e3d5-450a-af7c-89242e0bc0cd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-07 6:43 ` Nick Bart [not found] ` <8858a440-482b-43fe-abc7-ca41409511e9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-07 6:43 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 761 bytes --] One more detail: Journal names (fields journal, journaltitle, journalsubtitle; but also title of @periodical) must be left as they appear, and *not* be converted to sentence case. -- 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/8858a440-482b-43fe-abc7-ca41409511e9%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1029 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <8858a440-482b-43fe-abc7-ca41409511e9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <8858a440-482b-43fe-abc7-ca41409511e9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-07 15:40 ` John MacFarlane [not found] ` <20131007154055.GA44833-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-07 15:40 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ Nick Bart [Oct 06 13 23:43 ]: > One more detail: > Journal names (fields journal, journaltitle, journalsubtitle; but also > title of @periodical) must be left as they appear, and *not* be > converted to sentence case. I suspect there might be other exceptions too. Here's a complete list of the fields we currently do untitlecase for. Let me know which of these should be removed. issuetitle issuesubtitle subtitle title titleaddon maintitle booktitle journal journaltitle series mainsubtitle booksubtitle journalsubtitle maintitleaddon booktitleaddon booktitleshort journaltitleshort shortjournal series shorttitle eventtitle origtitle ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131007154055.GA44833-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131007154055.GA44833-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-07 19:32 ` Nick Bart [not found] ` <e8741a5b-2bf7-45f4-8790-6d73011ea95f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-07 19:32 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2129 bytes --] Well, it's actually only names of journals that should not be converted to sentence case. The APA Manual, 6e, e.g. is very clear about this: It says for all titles, “Capitalize only the first word of the title and of the subtitle, if any, and any proper nouns; …”, with the exception of: “Periodical title: Journals, newsletters, magazines. Give the periodical title in full, in uppercase and lowercase letters. Italicize the name of the periodical. [Example:] Social Science Quarterly” Thus untitlecase should not be applied to: - journal - journaltitle - journalsubtitle - shortjournal - title, subtitle, titleaddon, and shorttitle of @periodical On Monday, October 7, 2013 3:40:55 PM UTC, fiddlosopher wrote: > > +++ Nick Bart [Oct 06 13 23:43 ]: > > One more detail: > > Journal names (fields journal, journaltitle, journalsubtitle; but > also > > title of @periodical) must be left as they appear, and *not* be > > converted to sentence case. > > I suspect there might be other exceptions too. Here's a complete list of > the > fields we currently do untitlecase for. Let me know which of these should > be > removed. > > issuetitle > issuesubtitle > subtitle > title > titleaddon > maintitle > booktitle > journal > journaltitle > series > mainsubtitle > booksubtitle > journalsubtitle > maintitleaddon > booktitleaddon > booktitleshort > journaltitleshort > shortjournal > series > shorttitle > eventtitle > origtitle > > > -- 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/e8741a5b-2bf7-45f4-8790-6d73011ea95f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 2606 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <e8741a5b-2bf7-45f4-8790-6d73011ea95f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <e8741a5b-2bf7-45f4-8790-6d73011ea95f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-07 19:46 ` Nick Bart [not found] ` <7b95017f-3db5-40eb-aecf-bf57a71e94e1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-07 19:46 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1464 bytes --] A few more things we'll be needing: - bibtex/biblatex @comment and @preamble entries should be ignored, presently they cause trouble for biblio2yaml. - bibtex/biblatex @string entries should be expanded. Example: @string{AW= "Addison-Wesley"} @book{companion, author = "Goossens, Michel and Mittelbach, Franck and Samarin, Alexander", title = "The {{\LaTeX}} {C}ompanion", publisher = AW, year = 1993, } Note that the shorthand, AW, is *not* wrapped in braces. See http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf - biblatex: @xdata, a similar mechanism for shorthands; see biblatex manual, v2.7a, 3.11.6 “Data Containers” If it will take some time to implement @string and @xdata, a stopgap measure would be to ignore such entries: Presently at least @string, too, causes trouble for biblio2yaml. -- 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/7b95017f-3db5-40eb-aecf-bf57a71e94e1%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1908 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <7b95017f-3db5-40eb-aecf-bf57a71e94e1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <7b95017f-3db5-40eb-aecf-bf57a71e94e1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-07 19:50 ` Nick Bart [not found] ` <828e6e6d-708f-4722-b331-df029341bacc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-08 18:27 ` Tillmann Rendel 2013-10-09 20:35 ` John MacFarlane 2 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-07 19:50 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 898 bytes --] Backslash-escaped dollar signs causing trouble: $ cat test.bib @book{item1, Author = {Author, Al}, Date = {2013}, Hyphenation = {english}, Title = {Title}, Annote = {Price: \$ 34.95} } $ biblio2yaml test.bib --- references: biblio2yaml: "stdin" (line 6, column 27): unexpected "$" expecting letter -- 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/828e6e6d-708f-4722-b331-df029341bacc%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1289 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <828e6e6d-708f-4722-b331-df029341bacc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <828e6e6d-708f-4722-b331-df029341bacc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-08 2:39 ` John MacFarlane 2013-10-09 20:32 ` John MacFarlane 1 sibling, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-10-08 2:39 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I was afraid of that. I'm relying on an external Haskell library, 'bibtex', to parse the bibtex file. Looks like I might have to write my own bibtex parser using pandoc's LaTex reader. +++ Nick Bart [Oct 07 13 12:50 ]: > Backslash-escaped dollar signs causing trouble: > $ cat test.bib > @book{item1, > Author = {Author, Al}, > Date = {2013}, > Hyphenation = {english}, > Title = {Title}, > Annote = {Price: \$ 34.95} > } > $ biblio2yaml test.bib > --- > references: > biblio2yaml: "stdin" (line 6, column 27): > unexpected "$" > expecting letter > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/828e6e6d-708f-4722- > b331-df029341bacc%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/828e6e6d-708f-4722-b331-df029341bacc%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <828e6e6d-708f-4722-b331-df029341bacc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-08 2:39 ` John MacFarlane @ 2013-10-09 20:32 ` John MacFarlane 1 sibling, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-10-09 20:32 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Fixed. +++ Nick Bart [Oct 07 13 12:50 ]: > Backslash-escaped dollar signs causing trouble: > $ cat test.bib > @book{item1, > Author = {Author, Al}, > Date = {2013}, > Hyphenation = {english}, > Title = {Title}, > Annote = {Price: \$ 34.95} > } > $ biblio2yaml test.bib > --- > references: > biblio2yaml: "stdin" (line 6, column 27): > unexpected "$" > expecting letter > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/828e6e6d-708f-4722- > b331-df029341bacc%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/828e6e6d-708f-4722-b331-df029341bacc%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <7b95017f-3db5-40eb-aecf-bf57a71e94e1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-07 19:50 ` Nick Bart @ 2013-10-08 18:27 ` Tillmann Rendel 2013-10-09 20:35 ` John MacFarlane 2 siblings, 0 replies; 283+ messages in thread From: Tillmann Rendel @ 2013-10-08 18:27 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Hi, Nick Bart wrote: > A few more things we'll be needing: > > - bibtex/biblatex @string entries should be expanded. That would be great! I would also like to see support for the # operator for strings. For example: @string{Goossens = "Goossens, Michel"} @string{Mittelbach = "Mittelbach, Franck"} @string{Samarin = "Samarin, Alexander"} @string{AW= "Addison-Wesley"} @book{companion, author = Goossens # "and" # Mittelbach # "and" # Samarin, title = "The {{\LaTeX}} {C}ompanion", publisher = AW, year = 1993, } Tillmann ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <7b95017f-3db5-40eb-aecf-bf57a71e94e1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-07 19:50 ` Nick Bart 2013-10-08 18:27 ` Tillmann Rendel @ 2013-10-09 20:35 ` John MacFarlane [not found] ` <20131009203515.GB17209-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 2 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-09 20:35 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw New custom bibtex parser supports @string, skips @comment and @preamble. Concatenation with # also supported. @xdata still TODO. +++ Nick Bart [Oct 07 13 12:46 ]: > A few more things we'll be needing: > - bibtex/biblatex @comment and @preamble entries should be ignored, > presently they cause trouble for biblio2yaml. > - bibtex/biblatex @string entries should be expanded. Example: > @string{AW= "Addison-Wesley"} > @book{companion, > author = "Goossens, Michel and Mittelbach, Franck and Samarin, > Alexander", > title = "The {{\LaTeX}} {C}ompanion", > publisher = AW, > year = 1993, > } > Note that the shorthand, AW, is *not* wrapped in braces. See > http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > - biblatex: @xdata, a similar mechanism for shorthands; see biblatex > manual, v2.7a, 3.11.6 Data Containers > If it will take some time to implement @string and @xdata, a stopgap > measure would be to ignore such entries: Presently at least @string, > too, causes trouble for biblio2yaml. > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb- > aecf-bf57a71e94e1%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131009203515.GB17209-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131009203515.GB17209-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2013-10-10 0:00 ` Nick Bart [not found] ` <100d2d3a-78ef-4daa-a23a-33acad3e0df3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-10 0:00 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 3652 bytes --] Great! However, it seems to choke on field names it does not know: $ cat test-book-tms.bib @book{item1, Author = {Author, Al}, Date = {2013}, Date-Modified = {2013-10-05 09:26:05 +0000}, Hyphenation = {french}, Location = {Location}, Mainsubtitle = {Mainsubtitle}, Maintitle = {Maintitle}, Maintitleaddon = {Maintitleaddon}, Number = {3}, Publisher = {Publisher}, Series = {Series}, Subtitle = {Subtitle}, Title = {Title of the Book}, Titleaddon = {Titleaddon}} $ biblio2yaml test-book-tms.bib --- references: biblio2yaml: "stdin" (line 4, column 9): unexpected "D" expecting space or "}" Context: "Date-Added", "Date-Modified", and various fields with names starting with "Bdsk" are added by the application BibDesk, and there are probably many other fields added by various other applications and/or users. It would probably be best if biblio2yaml ignored all fields it does not understand. On Wednesday, October 9, 2013 8:35:15 PM UTC, fiddlosopher wrote: > > New custom bibtex parser supports @string, skips @comment and @preamble. > > Concatenation with # also supported. > > @xdata still TODO. > > +++ Nick Bart [Oct 07 13 12:46 ]: > > A few more things we'll be needing: > > - bibtex/biblatex @comment and @preamble entries should be ignored, > > presently they cause trouble for biblio2yaml. > > - bibtex/biblatex @string entries should be expanded. Example: > > @string{AW= "Addison-Wesley"} > > @book{companion, > > author = "Goossens, Michel and Mittelbach, Franck and > Samarin, > > Alexander", > > title = "The {{\LaTeX}} {C}ompanion", > > publisher = AW, > > year = 1993, > > } > > Note that the shorthand, AW, is *not* wrapped in braces. See > > http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > > - biblatex: @xdata, a similar mechanism for shorthands; see biblatex > > manual, v2.7a, 3.11.6 Data Containers > > If it will take some time to implement @string and @xdata, a stopgap > > measure would be to ignore such entries: Presently at least @string, > > too, causes trouble for biblio2yaml. > > > > -- > > 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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [1] > https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb- > > aecf-bf57a71e94e1%40googlegroups.com. > > For more options, visit [2]https://groups.google.com/groups/opt_out. > > > > References > > > > 1. > https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1%40googlegroups.com > > 2. 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/100d2d3a-78ef-4daa-a23a-33acad3e0df3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 5580 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <100d2d3a-78ef-4daa-a23a-33acad3e0df3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <100d2d3a-78ef-4daa-a23a-33acad3e0df3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-10 0:38 ` John MacFarlane [not found] ` <20131010003851.GA24278-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-10 0:38 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Well, I assumed that all field names would consist entirely of letters. That seems to be the case for both bibtex and biblatex fields. I could relax that assumption to allow hyphens, though. +++ Nick Bart [Oct 09 13 17:00 ]: > Great! > However, it seems to choke on field names it does not know: > $ cat test-book-tms.bib > @book{item1, > Author = {Author, Al}, > Date = {2013}, > Date-Modified = {2013-10-05 09:26:05 +0000}, > Hyphenation = {french}, > Location = {Location}, > Mainsubtitle = {Mainsubtitle}, > Maintitle = {Maintitle}, > Maintitleaddon = {Maintitleaddon}, > Number = {3}, > Publisher = {Publisher}, > Series = {Series}, > Subtitle = {Subtitle}, > Title = {Title of the Book}, > Titleaddon = {Titleaddon}} > $ biblio2yaml test-book-tms.bib > --- > references: > biblio2yaml: "stdin" (line 4, column 9): > unexpected "D" > expecting space or "}" > Context: "Date-Added", "Date-Modified", and various fields with names > starting with "Bdsk" are added by the application BibDesk, and there > are probably many other fields added by various other applications > and/or users. It would probably be best if biblio2yaml ignored all > fields it does not understand. > On Wednesday, October 9, 2013 8:35:15 PM UTC, fiddlosopher wrote: > > New custom bibtex parser supports @string, skips @comment and > @preamble. > Concatenation with # also supported. > @xdata still TODO. > +++ Nick Bart [Oct 07 13 12:46 ]: > > A few more things we'll be needing: > > - bibtex/biblatex @comment and @preamble entries should be > ignored, > > presently they cause trouble for biblio2yaml. > > - bibtex/biblatex @string entries should be expanded. Example: > > @string{AW= "Addison-Wesley"} > > @book{companion, > > author = "Goossens, Michel and Mittelbach, Franck and > Samarin, > > Alexander", > > title = "The {{\LaTeX}} {C}ompanion", > > publisher = AW, > > year = 1993, > > } > > Note that the shorthand, AW, is *not* wrapped in braces. See > > [1]http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > > - biblatex: @xdata, a similar mechanism for shorthands; see > biblatex > > manual, v2.7a, 3.11.6 Data Containers > > If it will take some time to implement @string and @xdata, a > stopgap > > measure would be to ignore such entries: Presently at least > @string, > > too, causes trouble for biblio2yaml. > > > > -- > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To post to this group, send email to > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit > > [1][4]https://groups.google.com/d/msgid/pandoc-discuss/ > 7b95017f-3db5-40eb- > > aecf-bf57a71e94e1%[5]40googlegroups.com. > > For more options, visit [2][6]https://groups.google.com/ > groups/opt_out. > > > > References > > > > 1. [7]https://groups.google.com/d/ > msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1% > 40googlegroups.com > > 2. [8]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 > [9]https://groups.google.com/d/msgid/pandoc-discuss/100d2d3a-78ef-4daa- > a23a-33acad3e0df3%40googlegroups.com. > For more options, visit [10]https://groups.google.com/groups/opt_out. > > References > > 1. http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > 2. javascript:/ > 3. javascript:/ > 4. https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb- > 5. http://40googlegroups.com/ > 6. https://groups.google.com/groups/opt_out > 7. https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1%40googlegroups.com > 8. https://groups.google.com/groups/opt_out > 9. https://groups.google.com/d/msgid/pandoc-discuss/100d2d3a-78ef-4daa-a23a-33acad3e0df3%40googlegroups.com > 10. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131010003851.GA24278-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131010003851.GA24278-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2013-10-10 1:11 ` John MacFarlane [not found] ` <20131010011115.GA27831-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-10 1:11 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I've allowed hyphens and fixed a number of bugs. Tried biblio2yaml on a 102K real biblatex file and had no problems. No doubt more testing is needed, but this is getting to the useful stage, I think! Still TODO: proper name resolution, @xdata. +++ John MacFarlane [Oct 09 13 17:38 ]: > Well, I assumed that all field names would consist entirely of > letters. That seems to be the case for both bibtex and biblatex > fields. I could relax that assumption to allow hyphens, though. > > +++ Nick Bart [Oct 09 13 17:00 ]: > > Great! > > However, it seems to choke on field names it does not know: > > $ cat test-book-tms.bib > > @book{item1, > > Author = {Author, Al}, > > Date = {2013}, > > Date-Modified = {2013-10-05 09:26:05 +0000}, > > Hyphenation = {french}, > > Location = {Location}, > > Mainsubtitle = {Mainsubtitle}, > > Maintitle = {Maintitle}, > > Maintitleaddon = {Maintitleaddon}, > > Number = {3}, > > Publisher = {Publisher}, > > Series = {Series}, > > Subtitle = {Subtitle}, > > Title = {Title of the Book}, > > Titleaddon = {Titleaddon}} > > $ biblio2yaml test-book-tms.bib > > --- > > references: > > biblio2yaml: "stdin" (line 4, column 9): > > unexpected "D" > > expecting space or "}" > > Context: "Date-Added", "Date-Modified", and various fields with names > > starting with "Bdsk" are added by the application BibDesk, and there > > are probably many other fields added by various other applications > > and/or users. It would probably be best if biblio2yaml ignored all > > fields it does not understand. > > On Wednesday, October 9, 2013 8:35:15 PM UTC, fiddlosopher wrote: > > > > New custom bibtex parser supports @string, skips @comment and > > @preamble. > > Concatenation with # also supported. > > @xdata still TODO. > > +++ Nick Bart [Oct 07 13 12:46 ]: > > > A few more things we'll be needing: > > > - bibtex/biblatex @comment and @preamble entries should be > > ignored, > > > presently they cause trouble for biblio2yaml. > > > - bibtex/biblatex @string entries should be expanded. Example: > > > @string{AW= "Addison-Wesley"} > > > @book{companion, > > > author = "Goossens, Michel and Mittelbach, Franck and > > Samarin, > > > Alexander", > > > title = "The {{\LaTeX}} {C}ompanion", > > > publisher = AW, > > > year = 1993, > > > } > > > Note that the shorthand, AW, is *not* wrapped in braces. See > > > [1]http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > > > - biblatex: @xdata, a similar mechanism for shorthands; see > > biblatex > > > manual, v2.7a, 3.11.6 Data Containers > > > If it will take some time to implement @string and @xdata, a > > stopgap > > > measure would be to ignore such entries: Presently at least > > @string, > > > too, causes trouble for biblio2yaml. > > > > > > -- > > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to > > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit > > > [1][4]https://groups.google.com/d/msgid/pandoc-discuss/ > > 7b95017f-3db5-40eb- > > > aecf-bf57a71e94e1%[5]40googlegroups.com. > > > For more options, visit [2][6]https://groups.google.com/ > > groups/opt_out. > > > > > > References > > > > > > 1. [7]https://groups.google.com/d/ > > msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1% > > 40googlegroups.com > > > 2. [8]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 > > [9]https://groups.google.com/d/msgid/pandoc-discuss/100d2d3a-78ef-4daa- > > a23a-33acad3e0df3%40googlegroups.com. > > For more options, visit [10]https://groups.google.com/groups/opt_out. > > > > References > > > > 1. http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > > 2. javascript:/ > > 3. javascript:/ > > 4. https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb- > > 5. http://40googlegroups.com/ > > 6. https://groups.google.com/groups/opt_out > > 7. https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1%40googlegroups.com > > 8. https://groups.google.com/groups/opt_out > > 9. https://groups.google.com/d/msgid/pandoc-discuss/100d2d3a-78ef-4daa-a23a-33acad3e0df3%40googlegroups.com > > 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-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/20131010003851.GA24278%40protagoras.phil.berkeley.edu. > For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131010011115.GA27831-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131010011115.GA27831-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2013-10-10 4:40 ` John MacFarlane 2013-10-10 11:14 ` Nick Bart 1 sibling, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-10-10 4:40 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ John MacFarlane [Oct 09 13 18:11 ]: > Still TODO: proper name resolution, @xdata. These are now done. ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131010011115.GA27831-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 2013-10-10 4:40 ` John MacFarlane @ 2013-10-10 11:14 ` Nick Bart [not found] ` <162da1be-e24c-4b90-86ec-d10959146f42-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-10 11:14 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 9746 bytes --] I'd certainly say this is getting useful: Congratulations! I tried it on a 6M real biblatex file myself and was successful, too -- in the sense that I could easily remove or modify the not very many constructs that still caused trouble. The issues I encountered, plus a few others: - citekeys/ids are lowercased by biblio2yaml, so none of the entries with citekeys containing uppercase letters are found by pandoc-citeproc afterwards. - In addition to letters and hyphens, bibtex and biblatex fields commonly in use also contain - numbers (from BibDesk, e.g., Bdsk-Url-1, Bdsk-File-2) - underscores (export from JSTOR, e.g., Jstor_Articletype, Jstor_Formatteddate, Reviewedauthor_1) - if I find others, I'll let you know. - "howpublished" is a "literal field", so it should be fetched with getField, not with getLiteralList. - Names: The biblatex default is to cite Ludwig van Beethoven as “Beethoven” and alphabetize him as “Beethoven, Ludwig van”. So the default is to interpret the prefix, or "von" part, e.g., "von, van, of, da, de, della" etc. as a CSL dropping-particle, not as a non-dropping-particle, as biblio2yaml does now. Only if "useprefix=true" is set in the options field of an entry should prefixes be treated as non-dropping-particles. - "jurisdiction" is not a biblatex field. However, since http://citationstyles.org/downloads/specification.html#appendix-iv-variables defines CSL's "jurisdiction" as "geographic scope of relevance (e.g. "US" for a US patent)", it would fit if a "location" field in a @patent entry were mapped to the CSL variable "jurisdiction", after resolving its biblatex keys such as "countryus". - The biblatex "library" field could be mapped to CSL "call-number". - In the combined CSL "note" variable, I'd suggest separating "note" and "addendum" by ". ". - And then there's the issue of quotation marks that are part of titles: With styles wrapping article and chapter titles in (double) quotation marks, quotation marks that are part of titles should be switched to single quotation marks. (And single, if inside double, back to double.) In biblatex, this can be done nicely using the csquotes package, which supports "active characters", so you can just put smart quotes, “ and ”, inside your titles and let csquotes take care of all necessary changes. Using pandoc and CSL, that's probably difficult, in particular since it's style dependent, but any ideas? On Thursday, October 10, 2013 1:11:15 AM UTC, fiddlosopher wrote: > > I've allowed hyphens and fixed a number of bugs. Tried biblio2yaml > on a 102K real biblatex file and had no problems. No doubt more > testing is needed, but this is getting to the useful stage, I think! > > Still TODO: proper name resolution, @xdata. > > +++ John MacFarlane [Oct 09 13 17:38 ]: > > Well, I assumed that all field names would consist entirely of > > letters. That seems to be the case for both bibtex and biblatex > > fields. I could relax that assumption to allow hyphens, though. > > > > +++ Nick Bart [Oct 09 13 17:00 ]: > > > Great! > > > However, it seems to choke on field names it does not know: > > > $ cat test-book-tms.bib > > > @book{item1, > > > Author = {Author, Al}, > > > Date = {2013}, > > > Date-Modified = {2013-10-05 09:26:05 +0000}, > > > Hyphenation = {french}, > > > Location = {Location}, > > > Mainsubtitle = {Mainsubtitle}, > > > Maintitle = {Maintitle}, > > > Maintitleaddon = {Maintitleaddon}, > > > Number = {3}, > > > Publisher = {Publisher}, > > > Series = {Series}, > > > Subtitle = {Subtitle}, > > > Title = {Title of the Book}, > > > Titleaddon = {Titleaddon}} > > > $ biblio2yaml test-book-tms.bib > > > --- > > > references: > > > biblio2yaml: "stdin" (line 4, column 9): > > > unexpected "D" > > > expecting space or "}" > > > Context: "Date-Added", "Date-Modified", and various fields with > names > > > starting with "Bdsk" are added by the application BibDesk, and > there > > > are probably many other fields added by various other applications > > > and/or users. It would probably be best if biblio2yaml ignored all > > > fields it does not understand. > > > On Wednesday, October 9, 2013 8:35:15 PM UTC, fiddlosopher wrote: > > > > > > New custom bibtex parser supports @string, skips @comment and > > > @preamble. > > > Concatenation with # also supported. > > > @xdata still TODO. > > > +++ Nick Bart [Oct 07 13 12:46 ]: > > > > A few more things we'll be needing: > > > > - bibtex/biblatex @comment and @preamble entries should be > > > ignored, > > > > presently they cause trouble for biblio2yaml. > > > > - bibtex/biblatex @string entries should be expanded. > Example: > > > > @string{AW= "Addison-Wesley"} > > > > @book{companion, > > > > author = "Goossens, Michel and Mittelbach, Franck > and > > > Samarin, > > > > Alexander", > > > > title = "The {{\LaTeX}} {C}ompanion", > > > > publisher = AW, > > > > year = 1993, > > > > } > > > > Note that the shorthand, AW, is *not* wrapped in braces. See > > > > [1]http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > > > > - biblatex: @xdata, a similar mechanism for shorthands; see > > > biblatex > > > > manual, v2.7a, 3.11.6 Data Containers > > > > If it will take some time to implement @string and @xdata, a > > > stopgap > > > > measure would be to ignore such entries: Presently at least > > > @string, > > > > too, causes trouble for biblio2yaml. > > > > > > > > -- > > > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To post to this group, send email to > > > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To view this discussion on the web visit > > > > [1][4]https://groups.google.com/d/msgid/pandoc-discuss/ > > > 7b95017f-3db5-40eb- > > > > aecf-bf57a71e94e1%[5]40googlegroups.com. > > > > For more options, visit [2][6]https://groups.google.com/ > > > groups/opt_out. > > > > > > > > References > > > > > > > > 1. [7]https://groups.google.com/d/ > > > msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1% > > > 40googlegroups.com > > > > 2. [8]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 <javascript:>. > > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > > To view this discussion on the web visit > > > [9] > https://groups.google.com/d/msgid/pandoc-discuss/100d2d3a-78ef-4daa- > > > a23a-33acad3e0df3%40googlegroups.com. > > > For more options, visit [10] > https://groups.google.com/groups/opt_out. > > > > > > References > > > > > > 1. http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > > > 2. javascript:/ > > > 3. javascript:/ > > > 4. > https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb- > > > 5. http://40googlegroups.com/ > > > 6. https://groups.google.com/groups/opt_out > > > 7. > https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1%40googlegroups.com > > > 8. https://groups.google.com/groups/opt_out > > > 9. > https://groups.google.com/d/msgid/pandoc-discuss/100d2d3a-78ef-4daa-a23a-33acad3e0df3%40googlegroups.com > > > 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...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > https://groups.google.com/d/msgid/pandoc-discuss/20131010003851.GA24278%40protagoras.phil.berkeley.edu. > > > 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/162da1be-e24c-4b90-86ec-d10959146f42%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 14779 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <162da1be-e24c-4b90-86ec-d10959146f42-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <162da1be-e24c-4b90-86ec-d10959146f42-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-10 17:00 ` John MacFarlane [not found] ` <20131010170041.GB5487-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-10 17:00 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I've made all the changes you suggested (except for quotations; that's a bigger issue and hard to deal with properly given how things are set up right now). +++ Nick Bart [Oct 10 13 04:14 ]: > I'd certainly say this is getting useful: Congratulations! > I tried it on a 6M real biblatex file myself and was successful, too -- > in the sense that I could easily remove or modify the not very many > constructs that still caused trouble. > The issues I encountered, plus a few others: > - citekeys/ids are lowercased by biblio2yaml, so none of the entries > with citekeys containing uppercase letters are found by pandoc-citeproc > afterwards. > - In addition to letters and hyphens, bibtex and biblatex fields > commonly in use also contain > - numbers (from BibDesk, e.g., Bdsk-Url-1, Bdsk-File-2) > - underscores (export from JSTOR, e.g., Jstor_Articletype, > Jstor_Formatteddate, Reviewedauthor_1) > - if I find others, I'll let you know. > - "howpublished" is a "literal field", so it should be fetched with > getField, not with getLiteralList. > - Names: The biblatex default is to cite Ludwig van Beethoven as > Beethoven and alphabetize him as Beethoven, Ludwig van. So the default > is to interpret the prefix, or "von" part, e.g., "von, van, of, da, de, > della" etc. as a CSL dropping-particle, not as a non-dropping-particle, > as biblio2yaml does now. Only if "useprefix=true" is set in the options > field of an entry should prefixes be treated as non-dropping-particles. > - "jurisdiction" is not a biblatex field. However, since > http://citationstyles.org/downloads/specification.html#appendix-iv-vari > ables defines CSL's "jurisdiction" as "geographic scope of relevance > (e.g. "US" for a US patent)", it would fit if a "location" field in a > @patent entry were mapped to the CSL variable "jurisdiction", after > resolving its biblatex keys such as "countryus". > - The biblatex "library" field could be mapped to CSL "call-number". > - In the combined CSL "note" variable, I'd suggest separating "note" > and "addendum" by ". ". > - And then there's the issue of quotation marks that are part of > titles: With styles wrapping article and chapter titles in (double) > quotation marks, quotation marks that are part of titles should be > switched to single quotation marks. (And single, if inside double, back > to double.) In biblatex, this can be done nicely using the csquotes > package, which supports "active characters", so you can just put smart > quotes, and , inside your titles and let csquotes take care of all > necessary changes. Using pandoc and CSL, that's probably difficult, in > particular since it's style dependent, but any ideas? > On Thursday, October 10, 2013 1:11:15 AM UTC, fiddlosopher wrote: > > I've allowed hyphens and fixed a number of bugs. Tried biblio2yaml > on a 102K real biblatex file and had no problems. No doubt more > testing is needed, but this is getting to the useful stage, I think! > Still TODO: proper name resolution, @xdata. > +++ John MacFarlane [Oct 09 13 17:38 ]: > > Well, I assumed that all field names would consist entirely of > > letters. That seems to be the case for both bibtex and biblatex > > fields. I could relax that assumption to allow hyphens, though. > > > > +++ Nick Bart [Oct 09 13 17:00 ]: > > > Great! > > > However, it seems to choke on field names it does not know: > > > $ cat test-book-tms.bib > > > @book{item1, > > > Author = {Author, Al}, > > > Date = {2013}, > > > Date-Modified = {2013-10-05 09:26:05 +0000}, > > > Hyphenation = {french}, > > > Location = {Location}, > > > Mainsubtitle = {Mainsubtitle}, > > > Maintitle = {Maintitle}, > > > Maintitleaddon = {Maintitleaddon}, > > > Number = {3}, > > > Publisher = {Publisher}, > > > Series = {Series}, > > > Subtitle = {Subtitle}, > > > Title = {Title of the Book}, > > > Titleaddon = {Titleaddon}} > > > $ biblio2yaml test-book-tms.bib > > > --- > > > references: > > > biblio2yaml: "stdin" (line 4, column 9): > > > unexpected "D" > > > expecting space or "}" > > > Context: "Date-Added", "Date-Modified", and various fields > with names > > > starting with "Bdsk" are added by the application BibDesk, > and there > > > are probably many other fields added by various other > applications > > > and/or users. It would probably be best if biblio2yaml > ignored all > > > fields it does not understand. > > > On Wednesday, October 9, 2013 8:35:15 PM UTC, fiddlosopher > wrote: > > > > > > New custom bibtex parser supports @string, skips @comment > and > > > @preamble. > > > Concatenation with # also supported. > > > @xdata still TODO. > > > +++ Nick Bart [Oct 07 13 12:46 ]: > > > > A few more things we'll be needing: > > > > - bibtex/biblatex @comment and @preamble entries > should be > > > ignored, > > > > presently they cause trouble for biblio2yaml. > > > > - bibtex/biblatex @string entries should be expanded. > Example: > > > > @string{AW= "Addison-Wesley"} > > > > @book{companion, > > > > author = "Goossens, Michel and Mittelbach, > Franck and > > > Samarin, > > > > Alexander", > > > > title = "The {{\LaTeX}} {C}ompanion", > > > > publisher = AW, > > > > year = 1993, > > > > } > > > > Note that the shorthand, AW, is *not* wrapped in > braces. See > > > > [1][1]http://tug.ctan.org/info/ > bibtex/tamethebeast/ttb_en.pdf > > > > - biblatex: @xdata, a similar mechanism for > shorthands; see > > > biblatex > > > > manual, v2.7a, 3.11.6 Data Containers > > > > If it will take some time to implement @string and > @xdata, a > > > stopgap > > > > measure would be to ignore such entries: Presently at > least > > > @string, > > > > too, causes trouble for biblio2yaml. > > > > > > > > -- > > > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To post to this group, send email to > > > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To view this discussion on the web visit > > > > [1][4][2]https://groups.google. > com/d/msgid/pandoc-discuss/ > > > 7b95017f-3db5-40eb- > > > > aecf-bf57a71e94e1%[5][3]40googlegroups.com. > > > > For more options, visit > [2][6][4]https://groups.google.com/ > > > groups/opt_out. > > > > > > > > References > > > > > > > > 1. [7][5]https://groups.google.com/d/ > > > msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1% > > > [6]40googlegroups.com > > > > 2. [8][7]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 [8]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to > [9]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit > > > [9][10]https://groups.google.com/d/msgid/pandoc-discuss/ > 100d2d3a-78ef-4daa- > > > a23a-33acad3e0df3%[11]40googlegroups.com. > > > For more options, visit [10][12]https://groups.google.com/ > groups/opt_out. > > > > > > References > > > > > > 1. [13]http://tug.ctan.org/info/ > bibtex/tamethebeast/ttb_en.pdf > > > 2. javascript:/ > > > 3. javascript:/ > > > 4. [14]https://groups.google.com/d/ > msgid/pandoc-discuss/7b95017f-3db5-40eb- > > > 5. [15]http://40googlegroups.com/ > > > 6. [16]https://groups.google.com/groups/opt_out > > > 7. [17]https://groups.google.com/d/ > msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1% > 40googlegroups.com > > > 8. [18]https://groups.google.com/groups/opt_out > > > 9. [19]https://groups.google.com/d/ > msgid/pandoc-discuss/100d2d3a-78ef-4daa-a23a-33acad3e0df3% > 40googlegroups.com > > > 10. [20]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 [21]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To post to this group, send email to [22]pandoc-...@googlegroups. > com. > > To view this discussion on the web visit > [23]https://groups.google.com/d/msgid/pandoc-discuss/ > 20131010003851.GA24278%40protagoras.phil.berkeley.edu. > > For more options, visit [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-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 > [25]https://groups.google.com/d/msgid/pandoc-discuss/162da1be-e24c-4b90 > -86ec-d10959146f42%40googlegroups.com. > For more options, visit [26]https://groups.google.com/groups/opt_out. > > References > > 1. http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > 2. https://groups.google.com/d/msgid/pandoc-discuss/ > 3. http://40googlegroups.com/ > 4. https://groups.google.com/ > 5. https://groups.google.com/d/ > 6. http://40googlegroups.com/ > 7. https://groups.google.com/groups/opt_out > 8. javascript:/ > 9. javascript:/ > 10. https://groups.google.com/d/msgid/pandoc-discuss/100d2d3a-78ef-4daa- > 11. http://40googlegroups.com/ > 12. https://groups.google.com/groups/opt_out > 13. http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > 14. https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb- > 15. http://40googlegroups.com/ > 16. https://groups.google.com/groups/opt_out > 17. https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1%40googlegroups.com > 18. https://groups.google.com/groups/opt_out > 19. https://groups.google.com/d/msgid/pandoc-discuss/100d2d3a-78ef-4daa-a23a-33acad3e0df3%40googlegroups.com > 20. https://groups.google.com/groups/opt_out > 21. javascript:/ > 22. javascript:/ > 23. https://groups.google.com/d/msgid/pandoc-discuss/20131010003851.GA24278%40protagoras.phil.berkeley.edu > 24. https://groups.google.com/groups/opt_out > 25. https://groups.google.com/d/msgid/pandoc-discuss/162da1be-e24c-4b90-86ec-d10959146f42%40googlegroups.com > 26. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131010170041.GB5487-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131010170041.GB5487-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2013-10-11 9:26 ` Nick Bart [not found] ` <9f372a93-08e8-4565-83d0-b04caa1b8a8f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-11 9:26 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 16329 bytes --] This all looks very good so far. Three things I noticed: - For *all* isArticle entries, the "number" field should be mapped to the CSL "issue", not the "number" variable, whether biblatex "issue" is present (and is appended to biblatex "number") or not. (I'm not sure whether the handling of number and issue for isArticle entries could be improved: Concatenating the two is only a compromise solution to avoid that any info gets lost, but not quite what most styles require. In the majority of cases I've seen, issue simple contains one of the seasons, so in principle, "issue" could be parsed and, in case it contains a term for a season, mapped to the season part of CSL's "issued" variable. If it does not match any season, it could still be concatenated with biblatex's "number" as it is done now. Thoughts?) - A regression: for isArticle entries, the biblatex series field is no longer appended to the CSL container-title variable. - On quotation marks inside titles: Surprisingly, this works well if the title contains dumb quotes only: $ cat test-article-quotation-marks.bib @article{item1, Author = {Author, Al}, Date = {2012}, Hyphenation = {english}, Journaltitle = {The Journaltitle}, Title = {The Title with a "Quotation" inside}, Subtitle = {and a "Quotation with "Another Quotation" inside", Too}, } $ echo @item1 | pandoc -S --filter pandoc-citeproc -t markdown-citations-markdown_in_html_blocks --bibliography test-article-quotation-marks.bib Author (2012) Author, Al. 2012. “The Title with a ‘quotation’ Inside: and a ‘quotation with “another quotation” inside’, Too.” *The Journaltitle*. $ echo @item1 | pandoc -S --filter pandoc-citeproc -t markdown-citations-markdown_in_html_blocks --bibliography test-article-quotation-marks.bib --csl apa.csl Author (2012) Author, A. (2012). The title with a “quotation” inside: and a “quotation with ‘another quotation’ inside”, too. *The Journaltitle*. So, quotation marks come out flawless, for both chicago-author-date and apa. Only capitalization fails (for chicago). As soon as smart double quotes are added anywhere, it no longer works, though ... Since using smart quotes is so useful on the LaTeX side of things and I'd like to keep them in my biblatex databases, my question: Could pandoc be made to handle smart quotes in the same fashion, too; at least inside bibliographies? On Thursday, 10 October 2013 17:00:41 UTC, fiddlosopher wrote: > > I've made all the changes you suggested (except for quotations; that's > a bigger issue and hard to deal with properly given how things are set > up right now). > > +++ Nick Bart [Oct 10 13 04:14 ]: > > I'd certainly say this is getting useful: Congratulations! > > I tried it on a 6M real biblatex file myself and was successful, too > -- > > in the sense that I could easily remove or modify the not very many > > constructs that still caused trouble. > > The issues I encountered, plus a few others: > > - citekeys/ids are lowercased by biblio2yaml, so none of the entries > > with citekeys containing uppercase letters are found by > pandoc-citeproc > > afterwards. > > - In addition to letters and hyphens, bibtex and biblatex fields > > commonly in use also contain > > - numbers (from BibDesk, e.g., Bdsk-Url-1, Bdsk-File-2) > > - underscores (export from JSTOR, e.g., Jstor_Articletype, > > Jstor_Formatteddate, Reviewedauthor_1) > > - if I find others, I'll let you know. > > - "howpublished" is a "literal field", so it should be fetched with > > getField, not with getLiteralList. > > - Names: The biblatex default is to cite Ludwig van Beethoven as > > Beethoven and alphabetize him as Beethoven, Ludwig van. So the > default > > is to interpret the prefix, or "von" part, e.g., "von, van, of, da, > de, > > della" etc. as a CSL dropping-particle, not as a > non-dropping-particle, > > as biblio2yaml does now. Only if "useprefix=true" is set in the > options > > field of an entry should prefixes be treated as > non-dropping-particles. > > - "jurisdiction" is not a biblatex field. However, since > > > http://citationstyles.org/downloads/specification.html#appendix-iv-vari > > ables defines CSL's "jurisdiction" as "geographic scope of relevance > > (e.g. "US" for a US patent)", it would fit if a "location" field in a > > @patent entry were mapped to the CSL variable "jurisdiction", after > > resolving its biblatex keys such as "countryus". > > - The biblatex "library" field could be mapped to CSL "call-number". > > - In the combined CSL "note" variable, I'd suggest separating "note" > > and "addendum" by ". ". > > - And then there's the issue of quotation marks that are part of > > titles: With styles wrapping article and chapter titles in (double) > > quotation marks, quotation marks that are part of titles should be > > switched to single quotation marks. (And single, if inside double, > back > > to double.) In biblatex, this can be done nicely using the csquotes > > package, which supports "active characters", so you can just put > smart > > quotes, and , inside your titles and let csquotes take care of all > > necessary changes. Using pandoc and CSL, that's probably difficult, > in > > particular since it's style dependent, but any ideas? > > On Thursday, October 10, 2013 1:11:15 AM UTC, fiddlosopher wrote: > > > > I've allowed hyphens and fixed a number of bugs. Tried biblio2yaml > > on a 102K real biblatex file and had no problems. No doubt more > > testing is needed, but this is getting to the useful stage, I > think! > > Still TODO: proper name resolution, @xdata. > > +++ John MacFarlane [Oct 09 13 17:38 ]: > > > Well, I assumed that all field names would consist entirely of > > > letters. That seems to be the case for both bibtex and biblatex > > > fields. I could relax that assumption to allow hyphens, though. > > > > > > +++ Nick Bart [Oct 09 13 17:00 ]: > > > > Great! > > > > However, it seems to choke on field names it does not know: > > > > $ cat test-book-tms.bib > > > > @book{item1, > > > > Author = {Author, Al}, > > > > Date = {2013}, > > > > Date-Modified = {2013-10-05 09:26:05 +0000}, > > > > Hyphenation = {french}, > > > > Location = {Location}, > > > > Mainsubtitle = {Mainsubtitle}, > > > > Maintitle = {Maintitle}, > > > > Maintitleaddon = {Maintitleaddon}, > > > > Number = {3}, > > > > Publisher = {Publisher}, > > > > Series = {Series}, > > > > Subtitle = {Subtitle}, > > > > Title = {Title of the Book}, > > > > Titleaddon = {Titleaddon}} > > > > $ biblio2yaml test-book-tms.bib > > > > --- > > > > references: > > > > biblio2yaml: "stdin" (line 4, column 9): > > > > unexpected "D" > > > > expecting space or "}" > > > > Context: "Date-Added", "Date-Modified", and various fields > > with names > > > > starting with "Bdsk" are added by the application BibDesk, > > and there > > > > are probably many other fields added by various other > > applications > > > > and/or users. It would probably be best if biblio2yaml > > ignored all > > > > fields it does not understand. > > > > On Wednesday, October 9, 2013 8:35:15 PM UTC, fiddlosopher > > wrote: > > > > > > > > New custom bibtex parser supports @string, skips @comment > > and > > > > @preamble. > > > > Concatenation with # also supported. > > > > @xdata still TODO. > > > > +++ Nick Bart [Oct 07 13 12:46 ]: > > > > > A few more things we'll be needing: > > > > > - bibtex/biblatex @comment and @preamble entries > > should be > > > > ignored, > > > > > presently they cause trouble for biblio2yaml. > > > > > - bibtex/biblatex @string entries should be expanded. > > Example: > > > > > @string{AW= "Addison-Wesley"} > > > > > @book{companion, > > > > > author = "Goossens, Michel and Mittelbach, > > Franck and > > > > Samarin, > > > > > Alexander", > > > > > title = "The {{\LaTeX}} {C}ompanion", > > > > > publisher = AW, > > > > > year = 1993, > > > > > } > > > > > Note that the shorthand, AW, is *not* wrapped in > > braces. See > > > > > [1][1]http://tug.ctan.org/info/ > > bibtex/tamethebeast/ttb_en.pdf > > > > > - biblatex: @xdata, a similar mechanism for > > shorthands; see > > > > biblatex > > > > > manual, v2.7a, 3.11.6 Data Containers > > > > > If it will take some time to implement @string and > > @xdata, a > > > > stopgap > > > > > measure would be to ignore such entries: Presently at > > least > > > > @string, > > > > > too, causes trouble for biblio2yaml. > > > > > > > > > > -- > > > > > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > To post to this group, send email to > > > > [3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > To view this discussion on the web visit > > > > > [1][4][2]https://groups.google. > > com/d/msgid/pandoc-discuss/ > > > > 7b95017f-3db5-40eb- > > > > > aecf-bf57a71e94e1%[5][3]40googlegroups.com. > > > > > For more options, visit > > [2][6][4]https://groups.google.com/ > > > > groups/opt_out. > > > > > > > > > > References > > > > > > > > > > 1. [7][5]https://groups.google.com/d/ > > > > msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1% > > > > [6]40googlegroups.com > > > > > 2. [8][7]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 [8]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To post to this group, send email to > > [9]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > To view this discussion on the web visit > > > > [9][10]https://groups.google.com/d/msgid/pandoc-discuss/ > > 100d2d3a-78ef-4daa- > > > > a23a-33acad3e0df3%[11]40googlegroups.com. > > > > For more options, visit [10][12]https://groups.google.com/ > > groups/opt_out. > > > > > > > > References > > > > > > > > 1. [13]http://tug.ctan.org/info/ > > bibtex/tamethebeast/ttb_en.pdf > > > > 2. javascript:/ > > > > 3. javascript:/ > > > > 4. [14]https://groups.google.com/d/ > > msgid/pandoc-discuss/7b95017f-3db5-40eb- > > > > 5. [15]http://40googlegroups.com/ > > > > 6. [16]https://groups.google.com/groups/opt_out > > > > 7. [17]https://groups.google.com/d/ > > msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1% > > 40googlegroups.com > > > > 8. [18]https://groups.google.com/groups/opt_out > > > > 9. [19]https://groups.google.com/d/ > > msgid/pandoc-discuss/100d2d3a-78ef-4daa-a23a-33acad3e0df3% > > 40googlegroups.com > > > > 10. [20]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 [21]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to [22]pandoc-...@googlegroups. > > com. > > > To view this discussion on the web visit > > [23]https://groups.google.com/d/msgid/pandoc-discuss/ > > 20131010003851.GA24278%40protagoras.phil.berkeley.edu. > > > For more options, visit [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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [25] > https://groups.google.com/d/msgid/pandoc-discuss/162da1be-e24c-4b90 > > -86ec-d10959146f42%40googlegroups.com. > > For more options, visit [26]https://groups.google.com/groups/opt_out. > > > > > References > > > > 1. http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > > 2. https://groups.google.com/d/msgid/pandoc-discuss/ > > 3. http://40googlegroups.com/ > > 4. https://groups.google.com/ > > 5. https://groups.google.com/d/ > > 6. http://40googlegroups.com/ > > 7. https://groups.google.com/groups/opt_out > > 8. javascript:/ > > 9. javascript:/ > > 10. > https://groups.google.com/d/msgid/pandoc-discuss/100d2d3a-78ef-4daa- > > 11. http://40googlegroups.com/ > > 12. https://groups.google.com/groups/opt_out > > 13. http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf > > 14. > https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb- > > 15. http://40googlegroups.com/ > > 16. https://groups.google.com/groups/opt_out > > 17. > https://groups.google.com/d/msgid/pandoc-discuss/7b95017f-3db5-40eb-aecf-bf57a71e94e1%40googlegroups.com > > 18. https://groups.google.com/groups/opt_out > > 19. > https://groups.google.com/d/msgid/pandoc-discuss/100d2d3a-78ef-4daa-a23a-33acad3e0df3%40googlegroups.com > > 20. https://groups.google.com/groups/opt_out > > 21. javascript:/ > > 22. javascript:/ > > 23. > https://groups.google.com/d/msgid/pandoc-discuss/20131010003851.GA24278%40protagoras.phil.berkeley.edu > > 24. https://groups.google.com/groups/opt_out > > 25. > https://groups.google.com/d/msgid/pandoc-discuss/162da1be-e24c-4b90-86ec-d10959146f42%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-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/9f372a93-08e8-4565-83d0-b04caa1b8a8f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 27307 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <9f372a93-08e8-4565-83d0-b04caa1b8a8f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <9f372a93-08e8-4565-83d0-b04caa1b8a8f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-12 4:37 ` John MacFarlane [not found] ` <20131012043715.GA89985-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 2013-10-12 5:23 ` John MacFarlane 1 sibling, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-10-12 4:37 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ Nick Bart [Oct 11 13 02:26 ]: > This all looks very good so far. > > Three things I noticed: > > - For *all* isArticle entries, the "number" field should be mapped to the > CSL "issue", not the "number" variable, whether biblatex "issue" is present > (and is appended to biblatex "number") or not. OK, I think I've got this right now. Please test. > (I'm not sure whether the handling of number and issue for isArticle > entries could be improved: Concatenating the two is only a compromise > solution to avoid that any info gets lost, but not quite what most styles > require. In the majority of cases I've seen, issue simple contains one of > the seasons, so in principle, "issue" could be parsed and, in case it > contains a term for a season, mapped to the season part of CSL's "issued" > variable. If it does not match any season, it could still be concatenated > with biblatex's "number" as it is done now. Thoughts?) I'd prefer to keep it simple for now. > - A regression: for isArticle entries, the biblatex series field is no > longer appended to the CSL container-title variable. Fixed I think. > - On quotation marks inside titles: Surprisingly, this works well if the > title contains dumb quotes only: Looks like this is done in Text.CSL.Output.Pandoc. I'm not sure if the quote parsing and handling is part of the citeproc spec or not -- Andrea could enlighten us here. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131012043715.GA89985-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131012043715.GA89985-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-10-14 6:23 ` Nick Bart [not found] ` <9247c44f-d639-4b7a-903b-96c02c0d4f8e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-14 6:23 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1570 bytes --] It seems that the CSL specs do contain details about “Quote Substitution” and “Flipflopping” (<http://citationstyles.org/downloads/upgrade-notes.html#id46>) – material that, curiously, does not appear in <http://citationstyles.org/downloads/specification.html>. Following <http://citationstyles.org/downloads/upgrade-notes.html#id46>, it seems that both dumb *and* smart quotes (the latter as defined by the open-quote, close-quote, open-inner-quote and close-inner-quote terms in the relevant locale file) should be parsed by a CSL processor. On Saturday, October 12, 2013 4:37:15 AM UTC, fiddlosopher wrote: > > +++ Nick Bart [Oct 11 13 02:26 ]: > > > - On quotation marks inside titles: Surprisingly, this works well if the > > title contains dumb quotes only: > > Looks like this is done in Text.CSL.Output.Pandoc. I'm not sure if the > quote parsing and handling is part of the citeproc spec or not -- Andrea > could enlighten us here. > > -- 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/9247c44f-d639-4b7a-903b-96c02c0d4f8e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1986 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <9247c44f-d639-4b7a-903b-96c02c0d4f8e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <9247c44f-d639-4b7a-903b-96c02c0d4f8e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-14 6:39 ` Nick Bart [not found] ` <fbf636ef-d74c-44a6-8be7-69513f60042f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-11-17 6:17 ` John MacFarlane 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-10-14 6:39 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1435 bytes --] The section “Editor/Translator Name Collapsing” (<http://citationstyles.org/downloads/upgrade-notes.html#id36>) from the "CSL 1.0 Upgrade Notes" document might help understanding the issue of spurious “Edited & translated by .” strings in pandoc output (see example below), described earlier in this thread and at <https://code.google.com/p/citeproc-hs/issues/detail?id=92>. ```` $ cat test-collection-2.bib @collection{item1, Editor = {Editor, Edward}, Hyphenation = {british}, Location = {Location}, Publisher = {Publisher}, Title = {Title}, Date = {2013}} $ echo @item1 | pandoc --filter pandoc-citeproc -t markdown-citations-markdown_in_html_blocks --bibliography test-collection-2.bib Editor (2013) Editor, Edward, ed. 2013. *Title*. Edited & translated by . Location: Publisher. ```` -- 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/fbf636ef-d74c-44a6-8be7-69513f60042f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1828 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <fbf636ef-d74c-44a6-8be7-69513f60042f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <fbf636ef-d74c-44a6-8be7-69513f60042f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-10-15 2:56 ` John MacFarlane 0 siblings, 0 replies; 283+ messages in thread From: John MacFarlane @ 2013-10-15 2:56 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I'm happy to report that Andrea has fixed this bug, and I've merged his changes into pandoc-citeproc. +++ Nick Bart [Oct 13 13 23:39 ]: > The section “Editor/Translator Name Collapsing” > (<http://citationstyles.org/downloads/upgrade-notes.html#id36>) from the > "CSL 1.0 Upgrade Notes" document might help understanding the issue of > spurious “Edited & translated by .” strings in pandoc output (see example > below), described earlier in this thread and at > <https://code.google.com/p/citeproc-hs/issues/detail?id=92>. > > ```` > $ cat test-collection-2.bib > @collection{item1, > Editor = {Editor, Edward}, > Hyphenation = {british}, > Location = {Location}, > Publisher = {Publisher}, > Title = {Title}, > Date = {2013}} > $ echo @item1 | pandoc --filter pandoc-citeproc -t > markdown-citations-markdown_in_html_blocks --bibliography > test-collection-2.bib > Editor (2013) > > Editor, Edward, ed. 2013. *Title*. Edited & translated by . Location: > Publisher. > ```` > > -- > 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/fbf636ef-d74c-44a6-8be7-69513f60042f%40googlegroups.com. > 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/20131015025602.GA10253%40Johns-MacBook-Pro.local. For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <9247c44f-d639-4b7a-903b-96c02c0d4f8e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-10-14 6:39 ` Nick Bart @ 2013-11-17 6:17 ` John MacFarlane [not found] ` <20131117061737.GA80492-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> 1 sibling, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-11-17 6:17 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I think I've got localized quote flipflopping working now. +++ Nick Bart [Oct 13 13 23:23 ]: > It seems that the CSL specs do contain details about “Quote Substitution” > and “Flipflopping” > (<http://citationstyles.org/downloads/upgrade-notes.html#id46>) – material > that, curiously, does not appear in > <http://citationstyles.org/downloads/specification.html>. > > Following <http://citationstyles.org/downloads/upgrade-notes.html#id46>, it > seems that both dumb *and* smart quotes (the latter as defined by the > open-quote, > close-quote, open-inner-quote and close-inner-quote terms in the relevant > locale file) should be parsed by a CSL processor. > > On Saturday, October 12, 2013 4:37:15 AM UTC, fiddlosopher wrote: > > > > +++ Nick Bart [Oct 11 13 02:26 ]: > > > > > - On quotation marks inside titles: Surprisingly, this works well if the > > > title contains dumb quotes only: > > > > Looks like this is done in Text.CSL.Output.Pandoc. I'm not sure if the > > quote parsing and handling is part of the citeproc spec or not -- Andrea > > could enlighten us here. > > > > > > -- > 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/9247c44f-d639-4b7a-903b-96c02c0d4f8e%40googlegroups.com. > 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/20131117061737.GA80492%40Johns-MacBook-Pro.local. For more options, visit https://groups.google.com/groups/opt_out. ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131117061737.GA80492-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131117061737.GA80492-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org> @ 2013-11-18 12:14 ` Nick Bart [not found] ` <941bbcaa-276e-40ec-bae6-baa209d26d30-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-11-18 12:21 ` Nick Bart 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-11-18 12:14 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 912 bytes --] Great. It does work with \enquote{} in biblatex title fields. It does not work, however with either smart (“”) or dumb quotes. I assume there's no good heuristic for parsing nested dumb quotes, but I wonder whether this could be made to work with smart quotes, just like csquotes.sty when “active quotes” are defined. -- 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/941bbcaa-276e-40ec-bae6-baa209d26d30%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 1160 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <941bbcaa-276e-40ec-bae6-baa209d26d30-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <941bbcaa-276e-40ec-bae6-baa209d26d30-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-11-18 15:01 ` John MacFarlane [not found] ` <20131118150100.GC4963-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-11-18 15:01 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw I'm not sure what you mean. Perhaps you could give an example of what doesn't work? +++ Nick Bart [Nov 18 13 04:14 ]: > Great. It does work with \enquote{} in biblatex title fields. It does > not work, however with either smart () or dumb quotes. I assume there's > no good heuristic for parsing nested dumb quotes, but I wonder whether > this could be made to work with smart quotes, just like csquotes.sty > when active quotes are defined. > > -- > 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 > [1]https://groups.google.com/d/msgid/pandoc-discuss/941bbcaa-276e-40ec- > bae6-baa209d26d30%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > 1. https://groups.google.com/d/msgid/pandoc-discuss/941bbcaa-276e-40ec-bae6-baa209d26d30%40googlegroups.com > 2. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131118150100.GC4963-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131118150100.GC4963-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2013-11-18 17:05 ` Nick Bart [not found] ` <4b28864c-fd8b-4215-9c6d-ba75185bf61d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2013-11-20 4:46 ` John MacFarlane 1 sibling, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-11-18 17:05 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 4849 bytes --] Sure. This is what I tried: Note the uppercase “S” in “Doe’S”, too. $ cat quote-enquote-flipflop.bib @article{article, Author = {Author, Ann}, Date = {1888}, Hyphenation = {english}, Title = {A Reinterpretation of Doe’s {\enquote{An Analysis of \enquote{The Book}}}}, Annote = {This entry uses the \verb+\enquote{}+ command from the latex csquotes.sty package.}} @book{book, Author = {Buthor, Bob}, Date = {1888}, Hyphenation = {english}, Title = {A Reinterpretation of Doe’s {\enquote{An Analysis of \enquote{The Book}}}}, Annote = {This entry uses the \verb+\enquote{}+ command from the latex csquotes.sty package.}} $ echo [@article] [@book] | pandoc -S -t markdown-citations --bibliography quote-enquote-flipflop.bib --csl chicago-author-date.csl --- bibliography: 'quote-enquote-flipflop.bib' csl: 'chicago-author-date.csl' ... (Author 1888) (Buthor 1888) <div class="references"> Author, Ann. 1888. “A Reinterpretation of Doe’S ‘An Analysis of “The Book”’.” Buthor, Bob. 1888. *A Reinterpretation of Doe’S “An Analysis of ‘The Book’”*. </div> $ cat quote-smart-flipflop.bib @article{article, Author = {Author, Ann}, Date = {1888}, Hyphenation = {english}, Title = {A Reinterpretation of Doe’s “An Analysis of “The Book””}} @book{book, Author = {Buthor, Bob}, Date = {1888}, Hyphenation = {english}, Title = {A Reinterpretation of Doe’s “An Analysis of “The Book””}} $ echo [@article] [@book] | pandoc -S -t markdown-citations --bibliography quote-smart-flipflop.bib --csl chicago-author-date.csl --- bibliography: 'quote-smart-flipflop.bib' csl: 'chicago-author-date.csl' ... (Author 1888) (Buthor 1888) <div class="references"> Author, Ann. 1888. “A Reinterpretation of Doe’S “an Analysis of “the Book””.” Buthor, Bob. 1888. *A Reinterpretation of Doe’S “an Analysis of “the Book””*. </div> $ cat quote-dumb-flipflop.bib @article{article, Author = {Author, Ann}, Hyphenation = {english}, Date = {1888}, Title = {A Reinterpretation of Doe’s "An Analysis of "The Book""}} @book{book, Author = {Buthor, Bob}, Hyphenation = {english}, Date = {1888}, Title = {A Reinterpretation of Doe’s "An Analysis of "The Book""}} $ echo [@article] [@book] | pandoc -S -t markdown-citations --bibliography quote-dumb-flipflop.bib --csl chicago-author-date.csl --- bibliography: 'quote-dumb-flipflop.bib' csl: 'chicago-author-date.csl' ... (Author 1888) (Buthor 1888) <div class="references"> Author, Ann. 1888. “A Reinterpretation of Doe’S "an Analysis of "the Book"".” Buthor, Bob. 1888. *A Reinterpretation of Doe’S "an Analysis of "the Book""*. </div> On Monday, November 18, 2013 3:01:00 PM UTC, fiddlosopher wrote: > > I'm not sure what you mean. Perhaps you could give an example of > what doesn't work? > > +++ Nick Bart [Nov 18 13 04:14 ]: > > Great. It does work with \enquote{} in biblatex title fields. It does > > not work, however with either smart () or dumb quotes. I assume > there's > > no good heuristic for parsing nested dumb quotes, but I wonder > whether > > this could be made to work with smart quotes, just like csquotes.sty > > when active quotes are defined. > > > > -- > > 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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [1] > https://groups.google.com/d/msgid/pandoc-discuss/941bbcaa-276e-40ec- > > bae6-baa209d26d30%40googlegroups.com. > > For more options, visit [2]https://groups.google.com/groups/opt_out. > > > > References > > > > 1. > https://groups.google.com/d/msgid/pandoc-discuss/941bbcaa-276e-40ec-bae6-baa209d26d30%40googlegroups.com > > 2. 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/4b28864c-fd8b-4215-9c6d-ba75185bf61d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 6655 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <4b28864c-fd8b-4215-9c6d-ba75185bf61d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <4b28864c-fd8b-4215-9c6d-ba75185bf61d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2013-11-18 18:22 ` John MacFarlane [not found] ` <20131118182226.GD21483-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: John MacFarlane @ 2013-11-18 18:22 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw The "Doe'S" is a bug indeed. The others, I'm not so sure what to do. The way the system now works, pandoc-citeproc uses pandoc's latex reader to parse the contents of biblatex fields, and in particular to recognize quoted sections. So, this will be recognized as nested quotes (and flip-flopped appropriately): Title = {A Reinterpretaiton of Doe's ``An Analysis of `The Book'\,''} but if you use " or unicode curly quotes, they will just be passed through verbatim. That's how the latex reader works. (You can verify by doing 'pandoc -f latex -t native'.) I could change the latex reader so it tries to parse quoted sections inside curly quotes. That might be worth doing. I could do the same for dumb double quotes. I wouldn't want to do it for dumb single quotes, though, since a single ' already has a clear meaning in LaTeX. John +++ Nick Bart [Nov 18 13 09:05 ]: > Sure. This is what I tried: > Note the uppercase S in DoeS, too. > $ cat quote-enquote-flipflop.bib > @article{article, > Author = {Author, Ann}, > Date = {1888}, > Hyphenation = {english}, > Title = {A Reinterpretation of Does {\enquote{An Analysis of > \enquote{The Book}}}}, > Annote = {This entry uses the \verb+\enquote{}+ command from the > latex csquotes.sty package.}} > @book{book, > Author = {Buthor, Bob}, > Date = {1888}, > Hyphenation = {english}, > Title = {A Reinterpretation of Does {\enquote{An Analysis of > \enquote{The Book}}}}, > Annote = {This entry uses the \verb+\enquote{}+ command from the > latex csquotes.sty package.}} > $ echo [@article] [@book] | pandoc -S -t markdown-citations > --bibliography quote-enquote-flipflop.bib --csl chicago-author-date.csl > --- > bibliography: 'quote-enquote-flipflop.bib' > csl: 'chicago-author-date.csl' > ... > (Author 1888) (Buthor 1888) > <div class="references"> > Author, Ann. 1888. A Reinterpretation of DoeS An Analysis of The > Book. > Buthor, Bob. 1888. *A Reinterpretation of DoeS An Analysis of The > Book*. > </div> > $ cat quote-smart-flipflop.bib > @article{article, > Author = {Author, Ann}, > Date = {1888}, > Hyphenation = {english}, > Title = {A Reinterpretation of Does An Analysis of The Book}} > @book{book, > Author = {Buthor, Bob}, > Date = {1888}, > Hyphenation = {english}, > Title = {A Reinterpretation of Does An Analysis of The Book}} > $ echo [@article] [@book] | pandoc -S -t markdown-citations > --bibliography quote-smart-flipflop.bib --csl chicago-author-date.csl > --- > bibliography: 'quote-smart-flipflop.bib' > csl: 'chicago-author-date.csl' > ... > (Author 1888) (Buthor 1888) > <div class="references"> > Author, Ann. 1888. A Reinterpretation of DoeS an Analysis of the > Book. > Buthor, Bob. 1888. *A Reinterpretation of DoeS an Analysis of the > Book*. > </div> > $ cat quote-dumb-flipflop.bib > @article{article, > Author = {Author, Ann}, > Hyphenation = {english}, > Date = {1888}, > Title = {A Reinterpretation of Does "An Analysis of "The Book""}} > @book{book, > Author = {Buthor, Bob}, > Hyphenation = {english}, > Date = {1888}, > Title = {A Reinterpretation of Does "An Analysis of "The Book""}} > $ echo [@article] [@book] | pandoc -S -t markdown-citations > --bibliography quote-dumb-flipflop.bib --csl chicago-author-date.csl > --- > bibliography: 'quote-dumb-flipflop.bib' > csl: 'chicago-author-date.csl' > ... > (Author 1888) (Buthor 1888) > <div class="references"> > Author, Ann. 1888. A Reinterpretation of DoeS "an Analysis of "the > Book"". > Buthor, Bob. 1888. *A Reinterpretation of DoeS "an Analysis of "the > Book""*. > </div> > On Monday, November 18, 2013 3:01:00 PM UTC, fiddlosopher wrote: > > I'm not sure what you mean. Perhaps you could give an example of > what doesn't work? > +++ Nick Bart [Nov 18 13 04:14 ]: > > Great. It does work with \enquote{} in biblatex title fields. > It does > > not work, however with either smart () or dumb quotes. I assume > there's > > no good heuristic for parsing nested dumb quotes, but I wonder > whether > > this could be made to work with smart quotes, just like > csquotes.sty > > when active quotes are defined. > > > > -- > > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To post to this group, send email to > [2]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit > > [1][3]https://groups.google.com/d/msgid/pandoc-discuss/ > 941bbcaa-276e-40ec- > > bae6-baa209d26d30%[4]40googlegroups.com. > > For more options, visit [2][5]https://groups.google.com/ > groups/opt_out. > > > > References > > > > 1. [6]https://groups.google.com/d/ > msgid/pandoc-discuss/941bbcaa-276e-40ec-bae6-baa209d26d30% > 40googlegroups.com > > 2. [7]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 > [8]https://groups.google.com/d/msgid/pandoc-discuss/4b28864c-fd8b-4215- > 9c6d-ba75185bf61d%40googlegroups.com. > For more options, visit [9]https://groups.google.com/groups/opt_out. > > References > > 1. javascript:/ > 2. javascript:/ > 3. https://groups.google.com/d/msgid/pandoc-discuss/941bbcaa-276e-40ec- > 4. http://40googlegroups.com/ > 5. https://groups.google.com/groups/opt_out > 6. https://groups.google.com/d/msgid/pandoc-discuss/941bbcaa-276e-40ec-bae6-baa209d26d30%40googlegroups.com > 7. https://groups.google.com/groups/opt_out > 8. https://groups.google.com/d/msgid/pandoc-discuss/4b28864c-fd8b-4215-9c6d-ba75185bf61d%40googlegroups.com > 9. https://groups.google.com/groups/opt_out ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <20131118182226.GD21483-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Decoupling citeproc and highlighting-kate from pandoc [not found] ` <20131118182226.GD21483-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2013-11-18 19:21 ` Nick Bart [not found] ` <60857372-304b-4d5a-9868-f24516a5badb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 283+ messages in thread From: Nick Bart @ 2013-11-18 19:21 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 8752 bytes --] I see. Bit of a misunderstanding, sorry: Since I stopped using anything but UTF8 smart quotes, I totally forgot about `` and '', in my mental map now stored somewhere in the “latex prehistory” department. So, my request would be to make UTF-8 smart quotes, “ and ”, function the same way as `` and '' indeed already do. Thus Title = {A Reinterpretation of {Doe}’s {\enquote{An Analysis of \enquote{The Book}}}} Title = {A Reinterpretation of {Doe}’s {``An Analysis of ``The Book''''}} Title = {A Reinterpretation of {Doe}’s {“An Analysis of “The Book””}} could all be used interchangeably. I'm not actually interested in dumb quotes myself, but if you’d say it's easy to make them function like this as well, why not? On Monday, 18 November 2013 18:22:26 UTC, fiddlosopher wrote: > > The "Doe'S" is a bug indeed. > > The others, I'm not so sure what to do. The way the system now works, > pandoc-citeproc uses pandoc's latex reader to parse the contents of > biblatex fields, and in particular to recognize quoted sections. > > So, this will be recognized as nested quotes (and flip-flopped > appropriately): > > Title = {A Reinterpretaiton of Doe's ``An Analysis of `The Book'\,''} > > but if you use " or unicode curly quotes, they will just be passed > through verbatim. That's how the latex reader works. (You can verify > by doing 'pandoc -f latex -t native'.) > > I could change the latex reader so it tries to parse quoted sections > inside curly quotes. That might be worth doing. I could do the > same for dumb double quotes. I wouldn't want to do it for dumb > single quotes, though, since a single ' already has a clear meaning > in LaTeX. > > John > > +++ Nick Bart [Nov 18 13 09:05 ]: > > Sure. This is what I tried: > > Note the uppercase S in DoeS, too. > > $ cat quote-enquote-flipflop.bib > > @article{article, > > Author = {Author, Ann}, > > Date = {1888}, > > Hyphenation = {english}, > > Title = {A Reinterpretation of Does {\enquote{An Analysis of > > \enquote{The Book}}}}, > > Annote = {This entry uses the \verb+\enquote{}+ command from the > > latex csquotes.sty package.}} > > @book{book, > > Author = {Buthor, Bob}, > > Date = {1888}, > > Hyphenation = {english}, > > Title = {A Reinterpretation of Does {\enquote{An Analysis of > > \enquote{The Book}}}}, > > Annote = {This entry uses the \verb+\enquote{}+ command from the > > latex csquotes.sty package.}} > > $ echo [@article] [@book] | pandoc -S -t markdown-citations > > --bibliography quote-enquote-flipflop.bib --csl > chicago-author-date.csl > > --- > > bibliography: 'quote-enquote-flipflop.bib' > > csl: 'chicago-author-date.csl' > > ... > > (Author 1888) (Buthor 1888) > > <div class="references"> > > Author, Ann. 1888. A Reinterpretation of DoeS An Analysis of The > > Book. > > Buthor, Bob. 1888. *A Reinterpretation of DoeS An Analysis of The > > Book*. > > </div> > > $ cat quote-smart-flipflop.bib > > @article{article, > > Author = {Author, Ann}, > > Date = {1888}, > > Hyphenation = {english}, > > Title = {A Reinterpretation of Does An Analysis of The Book}} > > @book{book, > > Author = {Buthor, Bob}, > > Date = {1888}, > > Hyphenation = {english}, > > Title = {A Reinterpretation of Does An Analysis of The Book}} > > $ echo [@article] [@book] | pandoc -S -t markdown-citations > > --bibliography quote-smart-flipflop.bib --csl chicago-author-date.csl > > --- > > bibliography: 'quote-smart-flipflop.bib' > > csl: 'chicago-author-date.csl' > > ... > > (Author 1888) (Buthor 1888) > > <div class="references"> > > Author, Ann. 1888. A Reinterpretation of DoeS an Analysis of the > > Book. > > Buthor, Bob. 1888. *A Reinterpretation of DoeS an Analysis of the > > Book*. > > </div> > > $ cat quote-dumb-flipflop.bib > > @article{article, > > Author = {Author, Ann}, > > Hyphenation = {english}, > > Date = {1888}, > > Title = {A Reinterpretation of Does "An Analysis of "The Book""}} > > @book{book, > > Author = {Buthor, Bob}, > > Hyphenation = {english}, > > Date = {1888}, > > Title = {A Reinterpretation of Does "An Analysis of "The Book""}} > > $ echo [@article] [@book] | pandoc -S -t markdown-citations > > --bibliography quote-dumb-flipflop.bib --csl chicago-author-date.csl > > --- > > bibliography: 'quote-dumb-flipflop.bib' > > csl: 'chicago-author-date.csl' > > ... > > (Author 1888) (Buthor 1888) > > <div class="references"> > > Author, Ann. 1888. A Reinterpretation of DoeS "an Analysis of "the > > Book"". > > Buthor, Bob. 1888. *A Reinterpretation of DoeS "an Analysis of "the > > Book""*. > > </div> > > On Monday, November 18, 2013 3:01:00 PM UTC, fiddlosopher wrote: > > > > I'm not sure what you mean. Perhaps you could give an example of > > what doesn't work? > > +++ Nick Bart [Nov 18 13 04:14 ]: > > > Great. It does work with \enquote{} in biblatex title fields. > > It does > > > not work, however with either smart () or dumb quotes. I > assume > > there's > > > no good heuristic for parsing nested dumb quotes, but I wonder > > whether > > > this could be made to work with smart quotes, just like > > csquotes.sty > > > when active quotes are defined. > > > > > > -- > > > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To post to this group, send email to > > [2]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit > > > [1][3]https://groups.google.com/d/msgid/pandoc-discuss/ > > 941bbcaa-276e-40ec- > > > bae6-baa209d26d30%[4]40googlegroups.com. > > > For more options, visit [2][5]https://groups.google.com/ > > groups/opt_out. > > > > > > References > > > > > > 1. [6]https://groups.google.com/d/ > > msgid/pandoc-discuss/941bbcaa-276e-40ec-bae6-baa209d26d30% > > 40googlegroups.com > > > 2. [7]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 <javascript:>. > > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>. > > > To view this discussion on the web visit > > [8] > https://groups.google.com/d/msgid/pandoc-discuss/4b28864c-fd8b-4215- > > 9c6d-ba75185bf61d%40googlegroups.com. > > For more options, visit [9]https://groups.google.com/groups/opt_out. > > > > References > > > > 1. javascript:/ > > 2. javascript:/ > > 3. > https://groups.google.com/d/msgid/pandoc-discuss/941bbcaa-276e-40ec- > > 4. http://40googlegroups.com/ > > 5. https://groups.google.com/groups/opt_out > > 6. > https://groups.google.com/d/msgid/pandoc-discuss/941bbcaa-276e-40ec-bae6-baa209d26d30%40googlegroups.com > > 7. https://groups.google.com/groups/opt_out > > 8. > https://groups.google.com/d/msgid/pandoc-discuss/4b28864c-fd8b-4215-9c6d-ba75185bf61d%40googlegroups.com > > 9. 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/60857372-304b-4d5a-9868-f24516a5badb%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. [-- Attachment #2: Type: text/html, Size: 13267 bytes --] ^ permalink raw reply [flat|nested] 283+ messages in thread
[parent not found: <