public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Image references in a column break after one character
Date: Sun, 23 Oct 2022 21:12:41 -0700	[thread overview]
Message-ID: <9B3E6EF5-B9D2-47AF-BF28-DC2F06E54D55@gmail.com> (raw)
In-Reply-To: <22b620a8-4869-4cd8-b040-a4c55d0ae521n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Pandoc tries to preserve the relative column widths in the original table.  If you have  table with a very narrow second column, pandoc will reproduce that in a grid table (since the colmun widths in this format matter).

One possible workaround would be to use a Lua filter to adjsut the column widths of Table elements after they are parsed.

Another would be to alter the column widths of the source table.



> On Oct 23, 2022, at 3:25 AM, Jan Stühler <jan.stuehler-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> Hello group.
> 
> I have been using
> ```
> pandoc --reference-links --extract-media=dir -o file.md file.docx
> ```
> on a set of documents, each of those documents has many tables. Especially those tables which have "only" images in the right column,  pandoc will break the image reference after one character. The image references can therefore not be found when converting the document back to docx.
> 
> ```
> +------------------------+---+------------------------------------------+
> 
> | If the Home Screen is  | ! |                                          |
> 
> | locked, the            | [ |                                          |
> 
> | Examination button is  | ] |                                          |
> 
> | dimmed. Please first   | [ |                                          |
> 
> | click on Unlock and    | 4 |                                          |
> 
> | then click on          | 8 |                                          |
> 
> | Examination,           | ] |                                          |
> 
> +========================+===+==========================================+
> 
> ```
> I do not have that problem when passing `--wrap=none` to markdown, but then all the lines in vim are unmanageably long.
> 
> `wrap=preserver|auto|none` with or without `--columns=x`  does not resolve the one-character breaking issue.
> 
> Also, converting to `-t gfm` first and then converting `-f gfm -t markdown` still creates one-character line breaks.
> 
> Is there any way to define a minimum column width?
> 
> -- 
> 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/22b620a8-4869-4cd8-b040-a4c55d0ae521n%40googlegroups.com.

-- 
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/9B3E6EF5-B9D2-47AF-BF28-DC2F06E54D55%40gmail.com.


  parent reply	other threads:[~2022-10-24  4:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23 10:25 Jan Stühler
     [not found] ` <22b620a8-4869-4cd8-b040-a4c55d0ae521n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-24  4:12   ` John MacFarlane [this message]
     [not found]     ` <9B3E6EF5-B9D2-47AF-BF28-DC2F06E54D55-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-29 21:40       ` Jan Stühler
     [not found]         ` <ae1809d9-1873-4a18-abcd-8e76a7f38bf9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-29 22:22           ` Jan Stühler

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=9B3E6EF5-B9D2-47AF-BF28-DC2F06E54D55@gmail.com \
    --to=fiddlosopher-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).