public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: Frederik Eichler
	<frederik.eichler-3KB0vxIR/cnR7s880joybQ@public.gmane.org>
Subject: Re: Pandoc Citeproc doesn't work on HTML format
Date: Tue, 08 Nov 2022 09:07:30 +0100	[thread overview]
Message-ID: <87r0ydoo0n.fsf@zeitkraut.de> (raw)
In-Reply-To: <b67f836a-8d65-4124-bb6c-900d9933d2d2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Mladen Babic <mladen.babic-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> What I actually want to do is when the user uploads the DOCX file,
> Pandoc converts the file to HTML and shows it to the HTML editor for
> additional editing by the user and converts it back to DOCX.
> After converting to Html, the system (my app) will replace current
> cites in HTML cite i.e. [1] with the key from the .bib file (like in
> my case [@test1] so the citeproc will know how to process it.

That's an interesting use case. I don't have any immediate ideas; going
via Markdown might be the best option.

But please make sure to also checkout [OS-APS], an open-source
project that uses pandoc for some of the document conversions. Going
from your description it sounds like it could be exactly what you need.
I've added Frederik from that org to CC, he may be able give more info.

[OS-APS]: https://os-aps.de

-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


  parent reply	other threads:[~2022-11-08  8:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 13:26 Mladen Babic
     [not found] ` <8e24d40c-5977-4912-9e1b-6cfa0f66d5e5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-07 14:21   ` Albert Krewinkel
     [not found]     ` <87v8nqon26.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-07 15:12       ` Mladen Babic
     [not found]         ` <b67f836a-8d65-4124-bb6c-900d9933d2d2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-08  8:07           ` Albert Krewinkel [this message]
     [not found]             ` <87r0ydoo0n.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-08  9:21               ` 'William Lupton' via pandoc-discuss
     [not found]                 ` <CAEe_xxizCtYTk_m5ROjitBB9WPxivF3rKdmk2vOFqEdZBtLX0Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-10 14:09                   ` Mladen Babic

Reply instructions:

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

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

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

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

  git send-email \
    --in-reply-to=87r0ydoo0n.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@public.gmane.org \
    --cc=frederik.eichler-3KB0vxIR/cnR7s880joybQ@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

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

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).