Re: Textile document looks bad in RedMine, Pandoc 3.1.3 for Win

[John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

> On Jun 9, 2023, at 4:50 PM, Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org> wrote:
> 
> 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.

It only implies widths if the overall width of the table exceeds the width set by --columns -- so increasing that is one approach.

> 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.


One solution might be to use a Lua filter that just sets all the column widths to the default.

-- 
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/28BEE147-F780-4EF8-841F-AD669BDBED15%40gmail.com.