Clreq Editors' Call

08 July 2020


Eric, Huijing, xfq, Xidorn

Meeting minutes

Go through the pull request list



xfq: I fixed the description of line height
… can we merge this?

Eric: looks good to me

xfq: I'll merge it then


xfq: I mentioned that ellipses should be horizontally and vertically centered
… think we can merge this
… 破折号 can be discussed in https://‌github.com/‌w3c/‌clreq/‌issues/‌310


xfq: translation fix
… I think we can merge this

Eric: looks good to me

Rewrite of Compression Rules for Punctuation Marks


Eric: @RuixiZhang42 did not object, but just made some explanations
… let's look at @xfq's comment: https://‌github.com/‌w3c/‌clreq/‌issues/‌221#issuecomment-642448401
… 基本挤压 and 原则调整 are the same thing
… I propose that we use 原则调整 instead of creating a new term ("基本挤压")
… I'll comment on the issue

xfq: I submitted a PR: https://‌github.com/‌w3c/‌clreq/‌pull/‌307
… the section name was renamed
… we still need an English image

Eric: I'll make an English image

xfq: I haven't translated the "Adjustment of adjacent punctuation marks" section yet

Huijing: noticed a typo
… "because these punctuation points are always take half"
… should be "because these punctuation points always take half"
… saw no issues in other parts of the PR

xfq: I'll update this sentence and translate the "Adjustment of adjacent punctuation marks" section

Line Adjustment


Eric: this is an important issue
… please review https://‌github.com/‌w3c/‌clreq/‌issues/‌255#issuecomment-586071816
… text based on jlreq, with some modifications
… we need a new section in § 3 Line composition
… similar to jlreq

[Eric goes through the structure in jlreq]

Eric: we also need a section for 雙行夾注
… see https://‌github.com/‌w3c/‌clreq/‌issues/‌109
… I'll translate § 3.4 Inline Cutting Note (Warichu) of jlreq and comment it in clreq#109
… back to #255
… please have a look at the terminology, like "compression" vs "adjustment", Fuqiao

xfq: OK, will have a look at your comment in #255

Eric: we can read it again in the next meeting

Huijing: I'll help review & translate it

Go through the issue list



xfq: The English of name of 省略号 is sometimes "ellipsis/ellipses", sometimes "horizontal ellipsis/ellipses"
… I think the first one is better
… because the second one might make the reader feel that it can only be used in horizontal writing mode

Eric: what is the difference between ellipsis and ellipses?

xfq: ellipsis is singular, and ellipses is plural

Eric/Huijing: +1 to xfq's comment in #312

xfq: I'll send a PR


xfq: em dashes should be horizontally and vertically centered, like ellipses

Eric: yes, in both horizontal and vertical writing mode

[Discuss font issues of em dashes]

xfq: I'll submit a PR


xfq: I'll submit a PR


xfq: translation issue

Eric: I think 完成尺寸 is better

xfq: 印刷版面 is more common in the document, tho
… the term is used in 2.3.1, 2.3.4, and 2.3.5

Huijing: I agree that 完成尺寸 is better

[Go through all the places where the term "trim size" is used]

xfq: should we add "trim size" to the Glossary?

Eric: I don’t think so. The meaning is obvious.

xfq: not so obvious to me though, especially the Chinese term 完成尺寸

Eric: I don’t oppose or support adding it to the Glossary.

[Discuss the term "bleed" in the Glossary]

xfq: I'll send a PR


xfq: should we use "line spacing" or "line gap"?

Eric: "line spacing" is ambiguous
… line height = character size + line gap
… back to the days of metal type, "line gap" was called "leading"

[Discuss the terminology in Adobe InDesign]

xfq: see https://‌w3c.github.io/‌clreq/#id53
… we should define what the line gap is
… see also https://‌w3c.github.io/‌clreq/#h-note-10
… I'll craft a pull request


xfq: looks like a translation issue

Eric: both the Chinese and English text are difficult to understand and need to be revised

[Discuss new Chinese text]

xfq: related jlreq section: https://‌w3c.github.io/‌jlreq/#kihonhanmen_and_examples_of_real_page_format

Eric: please assign #296 to me

Next telecon time

August 12 (Wednesday), 19:00-20:00 (UTC+8)

Minutes manually created (not a transcript), formatted by scribe.perl version 121 (Mon Jun 8 14:50:45 2020 UTC).