From: BP Jonsson <bpjonsson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: iromise <uromise-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pandoc transform between markdown and rst support Chinese character not well?
Date: Thu, 19 Oct 2017 13:56:42 +0200 [thread overview]
Message-ID: <4f48a015-3dc7-f663-81d5-a1d74333304b@gmail.com> (raw)
In-Reply-To: <b5d59708-1d56-4c95-aa79-9360c1a14580-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]
Den 2017-10-16 kl. 17:44, skrev iromise:
> When I use pandoc to transform markdown format table in which there is some
> Chinese character to rst format table,the generated table seems some wrong.
[snip]
>
> is there any way I can solved it? thanks.
>
>
Does it help to replace those spaces you actually have in the
source with non-breaking spaces? "You can insert a non-breaking
space in Pandoc Markdown by typing a backslash followed by an
ordinary space character.
Otherwise setting a high --columns value is the way to go.
If the table in your example is typical --columns=250 would be
about enough, and shouldn't be a problem on modern screens.
I often need tables with many narrow columns, and then I need to
set --columns=200 in order to not get unwanted line breaks in the
middle of (Western script) words.
Moreover this particular table looks like it could profitably be
reformatted as a definition list, since it has only two columns
(see the attached file!)
/bpj
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/4f48a015-3dc7-f663-81d5-a1d74333304b%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: markdown_and_rst_support_Chinese.md --]
[-- Type: text/x-markdown; name="markdown_and_rst_support_Chinese.md", Size: 1809 bytes --]
st_name
: 符号在字符串表中对应的索引。如果该值非 0,则它表示了给出符号名的字符串表索引,否则符号表项没有名称。 注:外部 C > 符号在 C 语言和目标文件的符号表中具有相同的名称。
st_value
: 给出与符号相关联的数值,具体取值依赖于上下文,可能是一个正常的数值、一个地址等等。
st_size
: 给出对应符号所占用的大小。如果符号没有大小或者大小未知,则此成员为0。
st_info
: 给出符号的类型和绑定属性。之后会给出若干取值和含义的绑定关系。
st_other
: 目前为0,其含义没有被定义。
st_shndx
: 每个符号表项都会和某个节区有所关系。此成员给出相关的节区头部表索引。某些索引具有特殊含义。
pandoc -r markdown+east_asian_line_breaks -w rst %
st\_name
符号在字符串表中对应的索引。如果该值非
0,则它表示了给出符号名的字符串表索引,否则符号表项没有名称。
注:外部 C > 符号在 C 语言和目标文件的符号表中具有相同的名称。
st\_value
给出与符号相关联的数值,具体取值依赖于上下文,可能是一个正常的数值、一个地址等等。
st\_size
给出对应符号所占用的大小。如果符号没有大小或者大小未知,则此成员为0。
st\_info
给出符号的类型和绑定属性。之后会给出若干取值和含义的绑定关系。
st\_other
目前为0,其含义没有被定义。
st\_shndx
每个符号表项都会和某个节区有所关系。此成员给出相关的节区头部表索引。某些索引具有特殊含义。
next prev parent reply other threads:[~2017-10-19 11:56 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 [this message]
[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
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=4f48a015-3dc7-f663-81d5-a1d74333304b@gmail.com \
--to=bpjonsson-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=uromise-Re5JQEeQqe8AvxtiuMwx3w@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).