public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Textile document looks bad in RedMine, Pandoc 3.1.3 for Win
Date: Fri, 9 Jun 2023 19:50:43 -0400	[thread overview]
Message-ID: <93fdc0f4-9198-b143-e88c-a4cf552faa43@usa.net> (raw)
In-Reply-To: <947553D1-2D58-4BDA-AE1F-27DDE27029C5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 6/9/23 5:33 PM, John MacFarlane wrote:
> It depends what you mean by "just fine."  Embedded HTML is perfectly fine in Textile, and in this case it is needed in order to preserve the semantic information about column widths.  (Btw, can't see these links - it says the file is in owner's trash.)

As someone else who occasinally gets bit by this: I think the main issue 
really is that the Markdown reader often seems to assume column widths 
that I didn't actually mean.  Especially if I do something like 
hand-write a table, use Pandoc to format it, and then edit it, if I then 
format it to Textile I'll be surprised that there's widths assigned. 
Pipe tables are particularly prone to it, as the 'nice' way to write 
them is to have the header seperator line match the widths of the 
headers (or the width of the longest element in the column) - but that 
implies widths, when really all I'm normally looking for is the column 
boundries to match up in my text.

And if it's then going into Redmine (which is my common usecase for this 
conversion as well), then converting to embedded HTML makes it look ugly 
and be hard to edit further in the wiki.

Not sure what the correct response is, really.  Since the real issue is 
that I'm effectively trying to use a subset of the full syntax.

Daniel T. Staal

-- 
---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------


  parent reply	other threads:[~2023-06-09 23:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 14:18 Tatiana Kallaur
     [not found] ` <661f2ce6-df0b-40a7-bb06-c43aefd3cf45n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-07 15:24   ` BP Jonsson
     [not found]     ` <CAFC_yuTBmkkFiv9VmYb2ip7EU6G8Dm9e0qL1gLYp7XW1nRgvZA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-06-08  6:17       ` Tatiana Kallaur
     [not found]         ` <CAPhsaWEGm4jCU8zO_i4aDK4M=WDTG1aDxuneo5AuL9C9VH05VQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-06-08  7:56           ` BPJ
     [not found]             ` <CADAJKhBN23eEjQegQe7gvHK7ZAtGS-tb6LD0vHN30Kc6n=xppA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-06-08  8:34               ` Tatiana Kallaur
     [not found]                 ` <CAPhsaWE6taXziqyunkfc46V8NOzboa9TGrbMaeHrG9cDnK0aYQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-06-08 15:44                   ` John MacFarlane
     [not found]                     ` <0FE7A079-0C7C-42AF-AED9-DAD6841474B4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-09  6:38                       ` Tatiana Kallaur
     [not found]                         ` <CAPhsaWGmD7tJAEh3km-1C=nCrmcZAW5kELhcS5CB+2yJfrWGKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-06-09 21:33                           ` John MacFarlane
     [not found]                             ` <947553D1-2D58-4BDA-AE1F-27DDE27029C5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-09 23:50                               ` Daniel Staal [this message]
     [not found]                                 ` <93fdc0f4-9198-b143-e88c-a4cf552faa43-Jdbf3xiKgS8@public.gmane.org>
2023-06-10  3:49                                   ` John MacFarlane

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=93fdc0f4-9198-b143-e88c-a4cf552faa43@usa.net \
    --to=dstaal-jdbf3xikgs8@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).