public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "ivo....-xwz7R8GQi1g@public.gmane.org" <ivo.welch-xwz7R8GQi1g@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Feature Idea: docx -> HTML table styling
Date: Fri, 17 Jun 2022 17:19:23 -0700 (PDT)	[thread overview]
Message-ID: <3dff9bb1-eed9-4252-9b72-1aa090c5865fn@googlegroups.com> (raw)
In-Reply-To: <m235g35h13.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>


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


my use case is to use pandoc md as a quasi-universal way to write text that 
I can output to pdf, html, and pptx.  unfortunately, I am limited by the 
lack of multi-column cells :-(.



On Friday, June 17, 2022 at 10:36:15 AM UTC-7 John MacFarlane wrote:

> Daniel Staal <DSt...-Jdbf3xiKgS8@public.gmane.org> writes:
>
> > On 6/16/22 1:21 PM, John MacFarlane wrote:
> >> I don't know what the best solution is. Pandoc is really
> >> designed to preserve the features of documents that are encoded
> >> in its types. Anything else -- including the use of
> >> "stringly typed" attributes -- is a bit of a hack, and tends to
> >> lead to unmaintainable messes down the road.
> >> 
> >> We could try to establish some generic conventions for
> >> representing things like vertical-alignment in the attributes,
> >> e.g. with a "vertical-align" attribute that gets interpreted
> >> by different writers, but as I said, once we depart from the
> >> structured types things get to be a bit of a mess.
> >
> > A thought: One option would be to suggest some generic conventions for 
> > readers, but maintain that *writers* will ignore anything not in the 
> > official AST. This would allow people like the original poster to 
> > handle many issues with custom LUA filters/writers, and if any 
> > particular attribute becomes widespread in readers you can decide if you 
> > want to adopt it into the official AST and add it to writers.
>
> That's more or less what I was thinking.
>

-- 
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/3dff9bb1-eed9-4252-9b72-1aa090c5865fn%40googlegroups.com.

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

  parent reply	other threads:[~2022-06-18  0:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 19:13 Noah Malmed
     [not found] ` <cf7005a8-0447-4667-acb2-c1eccbaacaden-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-15 22:36   ` John MacFarlane
     [not found]     ` <m2tu8l7dwk.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-06-16 15:16       ` Noah Malmed
     [not found]         ` <ec31e976-089b-4916-949a-fad874b2a8adn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-16 17:21           ` John MacFarlane
     [not found]             ` <m2v8t05xsf.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-06-17 13:56               ` Daniel Staal
     [not found]                 ` <98db6638-9fe8-90bc-8fc0-051d0307983c-Jdbf3xiKgS8@public.gmane.org>
2022-06-17 17:36                   ` John MacFarlane
     [not found]                     ` <m235g35h13.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-06-18  0:19                       ` ivo....-xwz7R8GQi1g@public.gmane.org [this message]
     [not found]                         ` <3dff9bb1-eed9-4252-9b72-1aa090c5865fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-21 17:42                           ` William Lupton
2022-06-16  6:49   ` Albert Krewinkel
     [not found]     ` <87y1xxvzt3.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-16 15:19       ` Noah Malmed

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=3dff9bb1-eed9-4252-9b72-1aa090c5865fn@googlegroups.com \
    --to=ivo.welch-xwz7r8gqi1g@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).