emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Alan Tyree <alantyree@gmail.com>
To: "Bruce D'Arcus" <bdarcus@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: How to debug a CSL problem
Date: Mon, 6 Jun 2022 10:24:41 +1000	[thread overview]
Message-ID: <CAGMsgMxjbHSbWqbGJgSHBEHjFSYvn7PXMz1YeZ9e-L6V1rcebw@mail.gmail.com> (raw)
In-Reply-To: <CAF-FPGOpXaDQ0hWKh4kwueLvYFnhu_kSa6hXXVrBYoR0sQ_qeg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]

Thanks for the prompt reply, Bruce.

I guess the bad news is that the csl file validates. I also should have
mentioned that everything parses properly with pandoc, so I guess it is a
cireproc-el glitch.

From the brief error report, it must just be choking  on a specific bibtex
entry, so it would still be helpful to be able to find it.

Cheers,
Alan

On Mon, 6 Jun 2022 at 09:15, Bruce D'Arcus <bdarcus@gmail.com> wrote:

> On Sun, Jun 5, 2022 at 6:48 PM Alan Tyree <alantyree@gmail.com> wrote:
>
> > I need some help with a debugging problem:
> >
> > I'm using
> >
> > #+cite_export: csl ~/Templates/csl/AGLC-intext.csl
> >
> > where AGLC-intext.csl is a custom csl file.
>
> I'm not sure if citeproc-el checks validity before running, but have
> you confirmed it's a valid style?
>
> This is the easiest way to do that, if you don't have a relax ng
> validator setup, with the schemas and such.
>
> https://validator.citationstyles.org/
>
> If yes, and it is valid, I would report it to the citeproc-el issue
> tracker.
>
> If your bib file(s) work fine with other CSL styles, it seems likely
> it's something with the style or the style and citeproc-el.
>
> Bruce
>


-- 
Alan L Tyree                    http://www2.austlii.edu.au/~alan

[-- Attachment #2: Type: text/html, Size: 2121 bytes --]

next prev parent reply	other threads:[~2022-06-06  0:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 22:47 How to debug a CSL problem Alan Tyree
2022-06-05 23:15 ` Bruce D'Arcus
2022-06-06  0:24   ` Alan Tyree [this message]
2022-06-06  1:03     ` Ihor Radchenko
2022-06-06  1:44       ` Alan Tyree
2022-06-06  5:34         ` András Simonyi
2022-06-06  5:56           ` Alan Tyree

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGMsgMxjbHSbWqbGJgSHBEHjFSYvn7PXMz1YeZ9e-L6V1rcebw@mail.gmail.com \
    --to=alantyree@gmail.com \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).