public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "kurt.pfeifle via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Automating markdown to odt with fields
Date: Tue, 26 Apr 2016 03:46:59 -0700 (PDT)	[thread overview]
Message-ID: <59aae5bf-759e-4ca4-8fd5-e3113694a88e@googlegroups.com> (raw)
In-Reply-To: <9a664450-8fbb-4a6d-abd5-5a4c567b2e69-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2057 bytes --]



On Tuesday, April 26, 2016 at 12:36:08 PM UTC+2, kurt.p...-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org 
wrote:
>
>
>
> On Tuesday, April 26, 2016 at 8:43:34 AM UTC+2, JDani Jiménez wrote:
>>
>> I need to automate the generation of many documents and, hopeful, 
>> maintain change and version control. The main idea is to desing a template 
>> with as many fields as I need. These fields are aimed to be filled in with:
>>
>> formated text
>>
>> item lists
>>
>> different paragraphs
>>
>> images
>>
>> tables...
>>
>  
[....] 

> Do I understand your mentioning of LibreOffice/ODT correctly as *"I do not 
> really need it -- all I want is the final PDF, and a change and version 
> control for my source files"*?
>

Some other questions: Do your item lists each contain a fixed number of 
items? Is the number of paragraphs constant? Your tables with the same 
number of columns and rows? And the layout of the result have to look like 
it is a filled-in paper form? Where does your "automated generation" get 
its inputs from? A data base?

In general, standard Pandoc supports all these formatting elements listed 
above. You'll just need to generate marked-down text for the elements you 
want, run Pandoc to convert to PDF (needs LaTeX installed) and be done (and 
put your texts into source control). 

You'll have to explain a bit more what exactly you need beyond a "standard" 
Pandoc workflow to achieve your desired results.

-- 
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/59aae5bf-759e-4ca4-8fd5-e3113694a88e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 2961 bytes --]

  parent reply	other threads:[~2016-04-26 10:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26  6:43 JDani Jiménez
     [not found] ` <7608243e-3f15-48de-9230-00b78127246e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-26 10:07   ` BP Jonsson
2016-04-26 10:36   ` kurt.pfeifle via pandoc-discuss
     [not found]     ` <9a664450-8fbb-4a6d-abd5-5a4c567b2e69-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-26 10:46       ` kurt.pfeifle via pandoc-discuss [this message]
2016-04-26 20:58   ` JDani Jiménez
     [not found]     ` <1a7138b7-aa6a-4873-b214-9644944c75c6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-26 21:05       ` JDani Jiménez
2016-04-26 21:22       ` John MACFARLANE
     [not found]         ` <20160426212236.GA35686-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2016-04-26 21:42           ` JDani Jiménez
2016-04-27 12:00           ` JDani Jiménez
     [not found]             ` <59292504-c115-4935-b7e2-004c0c875289-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-27 17:21               ` John MacFarlane
     [not found]                 ` <20160427172120.GA40999-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2016-04-29  8:59                   ` JDani Jiménez

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=59aae5bf-759e-4ca4-8fd5-e3113694a88e@googlegroups.com \
    --to=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).