public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pandoc transform between markdown and rst support Chinese character not well?
Date: Fri, 20 Oct 2017 09:28:33 -0700	[thread overview]
Message-ID: <20171020162833.GB33085@protagoras> (raw)
In-Reply-To: <CA+R_Ot=vGzOaC_kx-RpC-k2Jrz+U2g+LEKSxOsZxczX1LzcMPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

If you insert a regular space character, that will allow
pandoc to break the line.  The other alternative, as noted,
is to use a very wide --columns setting, but that's going
to give you a very wide table.


+++ Baozheng Liu [Oct 20 17 10:52 ]:
>   So will pandoc be able to solve this problem in another way?


  parent reply	other threads:[~2017-10-20 16:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 15:44 iromise
     [not found] ` <b5d59708-1d56-4c95-aa79-9360c1a14580-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-16 16:13   ` John MACFARLANE
2017-10-17  2:39   ` iromise
     [not found]     ` <feb05f9a-a367-495e-94f2-50dfc9bb3f74-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-17  3:53       ` John MacFarlane
     [not found]         ` <20171017035353.GC57897-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-10-17 23:33           ` Václav Haisman
     [not found]             ` <61410aee-bec7-4697-a46f-68129f92bf8f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-18  1:36               ` John MacFarlane
     [not found]                 ` <20171018013611.GC72258-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-10-18  9:45                   ` Baozheng Liu
2017-10-19 11:56   ` BP Jonsson
     [not found]     ` <4f48a015-3dc7-f663-81d5-a1d74333304b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-19 16:10       ` John MACFARLANE
2017-10-20  2:52         ` Baozheng Liu
     [not found]           ` <CA+R_Ot=vGzOaC_kx-RpC-k2Jrz+U2g+LEKSxOsZxczX1LzcMPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-20 16:28             ` John MACFARLANE [this message]
2017-10-21  7:56               ` Baozheng Liu
     [not found]                 ` <CA+R_OtkDLgyG67Ziy6LM_zFxdWfFCiHS4MavZGzar1knQgQ7-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-21 16:02                   ` John MacFarlane
     [not found]                     ` <20171021160255.GC88234-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-10-23  1:28                       ` Baozheng Liu
     [not found]                         ` <CA+R_OtmZsToSgJoriRaDktVCDYaaH5+QcA1KYSMBvj24UivevA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-27  8:42                           ` Kolen Cheung

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=20171020162833.GB33085@protagoras \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).