Clreq Editors' Call

14 June 2022


Bobby, Eric, huijing, xfq, Zhengyu

Meeting minutes


xfq: I'm trying to use Netlify to preview the changes to clreq


xfq: PR Preview doesn't support copying images into the preview



xfq: you can see the preview by clicking Deploy Preview
… Do you think it is useful?
… Netlify is a platform for automating site deployments.
… one downside is that it doesn't support diff
… but we can use both PR Preview and Netlify
… It's just a little confusing for people who don't know

huijing: I think we can use both, because not a lot of people look at the preview

huijing: If people get confused, we can mention the situation in the readme.

xfq: OK

Go through the pull request list



xfq: I updated links and translations

Eric: looks good to me

xfq: I'll merge it then


xfq: I added explicit width and height on images to reduce layout shifts

All: looks good

xfq: I'll merge it then

[Bobby joins]

PR #464 and #466

[Zhengyu introduces the two PRs]


xfq: @acli commented that em and 字寛 are not equivalent

Zhengyu: I know the translation of the word em/字寛 is controversial, but in contexts that don't cause ambiguity, I think the word em can be used.

Zhengyu: I also added 'class="checkme"' to those places

Zhengyu: Unicode also uses the word 'em'

Eric: Ken Roger Lunde translated the word 'em' to 全角 in Japanese, because in Japanese it is two-dimensional, not one-dimensional.

Eric: The meaning of the word 'em' is disputed even in traditional Western typography

Eric: We are not defining the word 字寛 as em, we are just using the word em

Eric: Because the word em and 字寛 are more natural

Zhengyu: I can't find a better word in English for 字寛

Zhengyu: and 字寛 can mean height in vertical writing mode

Zhengyu: If the Chinese character is not a square character, there may be problems

Eric: This value of one em is clear in Western typography

Zhengyu: em is a "virtual" value

Zhengyu: You can't find an actual visible thing and say this is one em

xfq: about space between the numerical value and unit symbol, can we mention it in our editorial guidelines as well?

Eric: yes


Zhengyu: it can be a separate PR

xfq: we can merge these two PRs, then?

Eric: yes


xfq: There are some terms we define with the <dfn> element, but there is no link to that definition anywhere, so ReSpec emits a warning. To clear the warning emitted by ReSpec, I propose several possible solutions.

Eric: let's add `lint-ignore` for Song (宋体), Kai (楷体), Hei (黑体), and Fangsong (仿宋体)

Eric: link to the glossary for character frames (文字外框), character face (字面), solid setting (密排), loose setting (疏排), Line height (行高), and interlinear annotation (行间注)

[Discuss what to do with the term character advance (字幅)]

[Discuss what to do with the term character size (文字尺寸/字号)]

Eric: We can add a note to mention the issue with the term 'character advance' (字幅). I'll file a separate issue.
… let's put the issue of 'character size' (文字尺寸/字号) aside for now.
… the PR https://github.com/w3c/clreq/pull/466 is not affected

xfq: I'll submit a PR to fix other terms

Eric: please read https://github.com/w3c/clreq/issues/463 before the next teleconference

xfq: OK

Next teleconference time

July 12 (Tuesday), 19:00-20:00 (UTC+8)

Minutes manually created (not a transcript), formatted by scribe.perl version 188 (Sat Jan 8 18:27:23 2022 UTC).