W3C

– DRAFT –
Clreq Editors' Call

09 May 2019

Attendees

Present
Bobby, Eric, Fuqiao, Huijing, xidorn, Yijun
Regrets
Chair
xfq
Scribe
xfq

Meeting minutes

zh & en versions

xfq: jlreq added the ability to switch language by URL parameter
… and is discussing about making English the default
… because showing both English and Japanese is not a common use case
… should we apply this to clreq too?

Eric: the English version of jlreq is the authoritative version
… and it's written mostly for English readers
… but a lot of readers of clreq are Chinese readers

Bobby: agreed
… Japan has a JIS standard, but we don't have the equivalent
… but displaying multiple languages simultaneously does not look good either

huijing: I think the current status is good enough

Eric: ok
… so we won't change the default language for now

Go through the issue and pull request list

https://‌github.com/‌w3c/‌clreq/‌pull/‌211

Eric: I think we can merge this

All: agreed

https://‌github.com/‌w3c/‌clreq/‌pull/‌208

xfq: Richard commented in the PR
… some editorial issues

Eric: I'll comment on the PR

huijing: I'll also fix the editorial issues

https://‌github.com/‌w3c/‌clreq/‌issues/‌210

Eric: the text is a bit weird
… maybe a translation issue (from jlreq)?
… I propose we change from 需要 to 可以
… and remove "中文书籍无论直、横排大多不分栏"
… should we talk about books and magazines separately?

Yijun: I agree with Eric
… this section is about the differences between horizontal and vertical writing modes

xfq: any objection to Eric's proposal?

[no objection]

xfq: I'll submit a PR

https://‌github.com/‌w3c/‌clreq/‌issues/‌209

Eric: this is a question, and I answered it
… can we close this issue?

[silence]

Eric: I'll close it

https://‌github.com/‌w3c/‌clreq/‌issues/‌207

huijing: should we simplify the text a bit?

Eric: in order to reduce ambiguity, I think it's OK sacrifice some simplicity

https://‌github.com/‌w3c/‌clreq/‌issues/‌125

huijing: I remember Yijun shared some examples about this before

Yijun: this is not common
… one or two example may not be super useful, since people might just lay it out casually

Eric: how is the spacing computed?

xidorn: @@1
… this issue is caused by using the Japanese layout algorithm to lay out Latin characters
… space-around is the default value, and it's designed for Japanese

Bobby: how do we lay it out case in InDesign?

Eric: it's a style issue
… there are several ways to do this
… the default way to do this in Chinese should be set solid and centered
… as in Richard's first illustration

xfq: should we mention this in the document?
… add some text in https://‌w3c.github.io/‌clreq/#interlinear_annotations ?

xidorn: we can add some text in https://‌w3c.github.io/‌clreq/#usage_of_interlinear_annotations

Eric: agreed
… more specifically, we can add some text in § 3.3.1.2 Indicating Meaning or Other Additional Information
… do we really need to mention this in the document?
… comment in the issue and close it might be enough

AOB

Bobby: Anyone going to TPAC?

https://‌www.w3.org/‌2019/‌09/‌TPAC/‌Overview.html

Eric: 16 September is Respect for the Aged Day
… I can't be there for the whole week, but one day might be possible

Bobby: we can look into the possibility of discussing the future of clreq and jlreq (possibly also klreq) for one day

Next telecon time

June 5, 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.

Diagnostics

Succeeded: s/have the eq/have the equivalent/

Succeeded: s/can I comment in the issue and close it?/comment in the issue and close it might be enough/

Maybe present: All, xfq