public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Layout Hooks in a JSON => PDF Pipeline
Date: Tue, 21 Mar 2023 13:31:07 +0000	[thread overview]
Message-ID: <ZBmxm/na+wA129AO@localhost> (raw)
In-Reply-To: <9b05df21-d6cc-4312-963b-d706b24e4f38n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Your custom reader can store the required information in divs, spans or attributes (for the elements that support it). Then, when writing to LaTeX, you can use a custom filter to convert this information to LaTeX code.

A word of caution: in your figure, the LaTeX engine comes after Pandoc (Pandoc outputs a TeX file taking account of the custom template; then this TeX file is processed by the LaTeX engine). 

Le Tuesday 21 March 2023 à 05:31:48AM, Matan Bendix Shenhav a écrit :
> I'm looking to implement a web app which allows users to write articles which
> automatically get typeset into newspapers. I will be consuming JSON data and
> want to output PDFs, and want to understand how to provide limited control of
> element positioning (especially of images) through some sort of layout hooks.
> 
> Articles will be written in a simple linear rich-text format, but some limited
> settings would allow users to control elements of positioning, in particular
> whether images would appear inline inside a column or blown up to full page
> width.
> 
> Editing is highly contained to keep things simple. Users select a collection of
> articles and pick their preferred order, and the application can decide the
> details of how to position them. The output is a section of the newspaper, N
> pages long, as a PDF.
> 
> The web editor will output the content in some sort of JSON format (probably
> extending [1]this API), but if necessary I can easily convert this into HTML
> (and indeed, I will have to anyway for the use to view the content in the
> editor).
> 
> If I understand correctly, the Pandoc pipeline should be something like this:
> 
> Screenshot from 2023-03-21 13-25-28.png
> 
> My main question is about provide element-level hooks to allow to input JSON to
> influence output layout. As a simple example, let's say the user adds some
> images into the markup. Some images should be inline, while others should be
> full page width or even full page.
> 
> How do I implement such hooks in this sort of Pandoc pipeline?
> 
> Thank you for your time!
>             
> 
> --
> 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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [3]https://groups.google.com/d/msgid/
> pandoc-discuss/9b05df21-d6cc-4312-963b-d706b24e4f38n%40googlegroups.com.
> 
> References:
> 
> [1] https://editorjs.io/base-concepts/#what-is-clean-data
> [2] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [3] https://groups.google.com/d/msgid/pandoc-discuss/9b05df21-d6cc-4312-963b-d706b24e4f38n%40googlegroups.com?utm_medium=email&utm_source=footer


-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ZBmxm/na%2BwA129AO%40localhost.


  parent reply	other threads:[~2023-03-21 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 12:31 Matan Bendix Shenhav
     [not found] ` <9b05df21-d6cc-4312-963b-d706b24e4f38n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-21 13:31   ` Bastien DUMONT [this message]
2023-03-21 16:12     ` Matan Bendix Shenhav
     [not found]       ` <f2109e96-b0b2-42da-b19a-0312a41f5952n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-21 16:26         ` Bastien DUMONT

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=ZBmxm/na+wA129AO@localhost \
    --to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).