All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu XiangCheng <wu.xiangcheng@linux.dev>
To: YanTeng Si <siyanteng@loongson.cn>
Cc: alexs@kernel.org, bobwxc@email.cn, seakeel@gmail.com,
	corbet@lwn.net, chenhuacai@kernel.org, jiaxun.yang@flygoat.com,
	linux-doc@vger.kernel.org, siyanteng01@gmail.com
Subject: Re: [PATCH v1 1/5] docs/zh_CN: add PCI acpi-info translation
Date: Tue, 6 Sep 2022 00:41:35 +0800	[thread overview]
Message-ID: <YxYmvxbCIuFV8S0O@bobwxc.mipc> (raw)
In-Reply-To: <65774b2e-0a58-590d-0be3-84e8fb9a22da@loongson.cn>

2022-09-05 (一) 20:27:42 +0800 YanTeng Si 曰:
> BTW:
> 
> 
> I have received some feedback from readers that
> 
> 
> They are used to writing with spaces between Chinese and English, and I
> found that some of the documents we translated have spaces and some do not.
> 
> 
> As the number of documents rises, do we need to follow some conventions to
> make the documents look better?

"spaces between Chinese and English" are not actual document
informations. Such style/display issue should be implemented by
rendering software rather than add space manually. If someone want a
perfect view experience, they might try Word, Latex or something else
and generate a pdf, those tools will auto add proper spaces. Or they may
improve the sphinx to get a better html.

And one more important, these spaces are easy to add automatically by
the tools, but difficult to remove later.

Existing documents, let it go. New documents, should not go back to this
outdated rule.
 
> 
> Readers gave me this link <https://github.com/sparanoid/chinese-copywriting-guidelines/blob/master/README.zh-Hans.md>
> .

以及我本来不想说的一点,把“「有研究显示,打字的时候不喜欢在中文和英文之间加空
格的人,感情路都走得很辛苦,有七成的比例会在 34 岁的时候跟自己不爱的人结婚,
而其余三成的人最后只能把遗产留给自己的猫。毕竟爱情跟书写都需要适时地留白。
与大家共勉之。」——vinta/paranoid-auto-spacing”这种东西放在教程开头,实在不
是什么好主意,我建议给出参考文献。否则我就得说“有研究显示,打字的时候喜欢乱加
空格的人,一般大脑都比较空白,有七成的比例会在34岁的时候被公司优化,而其余的
三成最后只能去当产品经理。毕竟思考这种东西是不能在空白基础上展开的。与大家
共勉”,权当博各位一笑。

Thanks,

-- 
Wu XiangCheng	0x32684A40BCA7AEA7


  reply	other threads:[~2022-09-05 16:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 11:15 [PATCH v1 0/5] docs/zh_CN: Add some dt and PCI Chinese translation Yanteng Si
2022-09-01 11:15 ` [PATCH v1 1/5] docs/zh_CN: add PCI acpi-info translation Yanteng Si
2022-09-02 12:56   ` Wu XiangCheng
2022-09-05 12:27     ` YanTeng Si
2022-09-05 16:41       ` Wu XiangCheng [this message]
2022-09-06  2:19         ` Alex Shi
2022-09-01 11:15 ` [PATCH v1 2/5] docs/zh_CN: add dt changesets translation Yanteng Si
2022-09-02  6:56   ` Alex Shi
2022-09-05 11:58     ` YanTeng Si
2022-09-01 11:15 ` [PATCH v1 3/5] docs/zh_CN: add dt dynamic-resolution-notes translation Yanteng Si
2022-09-02  8:13   ` Alex Shi
2022-09-01 11:15 ` [PATCH v1 4/5] docs/zh_CN: add dt overlay-notes translation Yanteng Si
2022-09-02  8:23   ` Alex Shi
2022-09-05 12:05     ` YanTeng Si
2022-09-01 11:15 ` [PATCH v1 5/5] docs/zh_CN: add dt kernel-api translation Yanteng Si
2022-09-02  8:29   ` Alex Shi

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=YxYmvxbCIuFV8S0O@bobwxc.mipc \
    --to=wu.xiangcheng@linux.dev \
    --cc=alexs@kernel.org \
    --cc=bobwxc@email.cn \
    --cc=chenhuacai@kernel.org \
    --cc=corbet@lwn.net \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=seakeel@gmail.com \
    --cc=siyanteng01@gmail.com \
    --cc=siyanteng@loongson.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.