Re: [PATCH 1/1] docs/zh_CN: Add sched-capacity translation

On Wed, 8 Dec 2021 at 12:55, yanteng si [off-list ref] wrote:

Tang Yizhou [off-list ref] 于2021年12月8日周三 12:35写道：

quoted

On 2021/12/8 11:16, Alex Shi wrote:

quoted

On Tue, Dec 7, 2021 at 10:57 PM Jonathan Corbet [off-list ref] wrote:

quoted

Alex Shi [off-list ref] writes:

quoted

What the result of scripts/checkpatch.pl or make htmldocs say?
Let's tame these tools and follow the regluar styles of kernel.

checkpatch knows nothing about different languages, and "make htmldocs"
doesn't do that sort of stylistic checking.

Thanks for the info!

quoted

I don't know enough (i.e. anything :) to have an opinion on the best
length for lines of Chinese text.  Surely there must be some conventions
out there?

The only reason I know is to remove extra spaces char in 'rendered
documentation'
which is generated by line break. For this purpose, 40 or 60 line chars limit
can't fulfill it obviously.

Yizhou's suggestion has no line break unless a punctuation hitted, so the
space will happen with the punctuation.   This makes the rendered document look
good, but will lead to toooo long and never alignment lines in the
source document.
It looks like we have no good way to resolve this issue by style
change. Also the '60'
number seems an arbitrary number? If we have to relief this problem from coding
style change, why not follow the new rule after checkpatch's change:
from 80 to 100,
let's say about 50 Chinese chars plus breaking after a meaningful Chinese word?

Agreed.

Now I prefer 50 Chinese chars plus breaking after a meaningful Chinese word.

All guys:

ref <https://stackoverflow.com/questions/8550112/prevent-browser-converting-n-between-lines-into-space-for-chinese-characters>

Hi, Alex, Yanteng, Tang,

According to the CSS3 Text draft, we could use the "white-space"
property. Shall we wait until most browsers support this feature
and change the rendering configuration of Chinese documents?

ref <https://www.w3.org/TR/css-text-3/#line-break-transform>

Thanks,
Feiyang

I have tested that firefox has no space problem. Looks like some
browser issues, But I still think it's because rst didn't consider
Chinese support when it was originally designed.

I'm sure there are many ways to solve the space problem elegantly, but
changing the document source code is definitely not one of them.

Thanks,
Yanteng

quoted

Thanks,
Tang

quoted

Thanks
Alex

quoted

Thanks,

jon

.