public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Felix SOEDJEDE <soefelix-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: [Docx reader] Keep more information between docx and native
Date: Wed, 4 May 2022 11:00:59 -0700 (PDT)	[thread overview]
Message-ID: <8840906c-31d0-4d1b-b5e6-0d5c54ed3d1dn@googlegroups.com> (raw)


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

Hello,

I would like to known what is the best way to keep these type of 
information when converting from docx to native
1. Landscape
Added in docx file by creating a "section break".
Github issue: https://github.com/jgm/pandoc/issues/8054
2. Columns
Added in docx file by creating a "section break"
Github issue: https://github.com/jgm/pandoc/issues/8057
3. Alignement

I think it can be done using *fenced_divs*.

In my knowledge, lua-filters cannot do that because the information is not 
available.
I may be at Haskell level but I'm not sure if it's possible to do it 
without adding code to Pandoc.
I known PHP, Python and recently started writing lua for pandoc filters but 
I don"t know Haskell nor Functional Programming. If it's possible, I could 
try to learn Haskell.

Thanks for your answers

-- 
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/8840906c-31d0-4d1b-b5e6-0d5c54ed3d1dn%40googlegroups.com.

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

             reply	other threads:[~2022-05-04 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AQHYX+II+ZD2UT2UukWK2QsHWF6Ih60P8ZTA>
2022-05-04 18:00 ` Felix SOEDJEDE [this message]
     [not found]   ` <8840906c-31d0-4d1b-b5e6-0d5c54ed3d1dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-05  8:18     ` AW: " denis.maier-NSENcxR/0n0
     [not found]       ` <4c15ea651cd141649c80e84582f20f76-NSENcxR/0n0@public.gmane.org>
2022-05-06 13:26         ` Felix SOEDJEDE

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=8840906c-31d0-4d1b-b5e6-0d5c54ed3d1dn@googlegroups.com \
    --to=soefelix-re5jqeeqqe8avxtiumwx3w@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).