Clreq Editors' Call

06 August 2019


Bobby, Eric, xfq, Xidorn, Yijun

Meeting minutes

Organization of clreq


xfq: In a GitHub issue ^
… r12a said that he preferred to break out the general information about punctuation and move it under section 2
… then reassign the other subsections under headings related to both line breaking and text-alignment
… what do you think?


Bobby: our document structure is complex
… not easy to grasp

Eric: link break is complicated
… does not seem to fit in one section
… I wrote an article about line break ^

Eric: I don't think the general information about punctuation fits in § 2

Xidorn: perhaps a new section?

Eric: I'll think about it

Go through the issue and pull request list



Eric: I think we can merge this

All: Agreed.


xfq: #225 looks good to me
… it fixes https://‌github.com/‌w3c/‌clreq/‌issues/‌172

Eric: looks good to me

xfq: @lizheming is a contributor from 360


xfq: r12a and huijing reviewed this PR
… Zheming asked a question
… he thinks "末侧" is unnecessary in the Chinese description "可以缩减该符号末侧二分之一个汉字大小的空白"

Eric: I think "末侧" is necessary
… 末侧 does not apply to 间隔号 (middle dot), since it's vertically and horizontally centered within its square frame
… and we're rewriting this section

Eric: I don't see 末侧 appear in the English translation?

xfq: no, it doesn't appear
… nor in General Rules for Punctuation § 5.1.10
… GB standard only mentions "应占半角字符的宽度"

Eric: GB standard describes in terms of the width the character occupies
… but we describes in terms of the space can be reduced/compressed
… therefore, we need to mention *which* part of space is reduced
… in jlreq, the character advance of the puncutations are half-width by default
… they only become full-width when they're placed side-by-side with ideographic/kana
… clreq does not use this approach
… in clreq, puncutations are full-width by default

Xidorn: I think 末侧 is needed

Eric: rereading the paragraph, now I think we can remove 末侧

Xidorn: what about other instances of 始侧 and 末侧 in this section?


Eric: we can probably remove all instances of 始侧 and 末侧
… does publications in Taiwan and Hong Kong compress the punctuation marks?

Yijun: some books do

Eric: which side?

Yijun: 始末 (both sides)

Eric: but the punctuation marks are at the center of the square space

Yijun: not for brackets

Eric: any real example?

Yijun: I'll find examples

Eric: we probably can't resolve on whether 末侧 is necessary today
… let's discuss this after rewriting § 3.1.6 Compression Rules for Punctuation Marks

xfq: I propose that we merge #226 first
… since it's only about the English translation, not the Chinese version

Eric: OK


xfq: I marked this as future work

Eric: there are multiple different conventions for this
… if we want to mention this in clreq, we can only say "one way to do this is..."


Eric: please have a look at my text in #221

[Eric goes through the text]

Eric: the 8 points in § Compression of adjacent punctuation marks is too complicated
… so I rewrote them
… any comment?

xfq: it looks better than the current text

Eric: I asked a question about the third point in the comment

Xidorn: what are the differences between 3b and 3d

[Eric explains the differences between 3a, 3b, 3c, and 3d]

Eric: the space should be compressed to the state in 3b at least
… whether there's need to compress further (as in 3c and 3d), depends on the style
… please look into my text and comment in the issue
… after hearing feedback, I can submit a pull request
… I haven't found the time for #220 yet
… I'll look into it

Next telecon time

xfq: ATypI (5-7), Mid-Autumn Festival (13), and TPAC (16-20) in September
… I'll be in Japan from September 15 to 21

September 11, Wed, 19:00-20:00 (UTC+8)

Minutes manually created (not a transcript), formatted by Bert Bos's scribe.perl version Mon Apr 15 13:11:59 2019 UTC, a reimplementation of David Booth's scribe.perl. See history.


Maybe present: All