w3c
Seeking Korean help
On behalf of the i18n WG, i would like to ask @jihyerish, @anawhj, Dongwoo Joshua Im, and any other Korean folks in the CSS WG whether they can help comment on Korean script requirements, or recommend anyone else who could help. For example, we recently had 4 short contributions to the following issues and we'd like to get confirmation of what's proposed.
- https://github.com/w3c/klreq/issues/8
- https://github.com/w3c/klreq/issues/62
- https://github.com/w3c/klreq/issues/11
- https://github.com/w3c/klreq/issues/4
We'd like to sign up a bunch of people who are aware of Korean typography requirements to monitor and contribute to our https://lists.w3.org/Archives/Public/public-i18n-korean/ mailing list. There are very few posts, so we expect the commitment to be very small — but it will be a big help to ensure that Korean is supported correctly by CSS and other W3C technologies.
Thanks for your help.
(You can learn more about our work on Korean language enablement at https://w3c.github.io/klreq/home.)
@r12a I recall that the KLReq document was actively authored by Prof. Soonbum and others a decade ago, though it hasn't been maintained recently. I will share your request for help with several groups, such as the W3C Korea Chapter and Korean language researchers.
I have a couple of questions regarding the draft:
- How are the JLReq and CLReq documents maintained these days? Is there an active authoring group, a dedicated process, or regular meetings? Knowing their status would help me see if we can form a similar group or mobilize researchers in Korea to follow suit.
- Regarding KLReq, are there major requirements for enhancing the draft, or would a small update be sufficient?
Thanks @anawhj . Much appreciated.
JLReq and CLReq documents have active groups that meet regularly to work on the documents (in Japanese and Chinese, respectively). See the discussions in the JLReq and CLReq repositories. Our framework allows us to set up a similar group for Korean, and there are no barriers to participation. There are guidelines for conducting the work, but it's up to the people in the group to choose a chair and set up meetings and work items. The following pages may help:
- Language enablement [Overview of the framework]
- Get involved with Language Enablement
- Setting up a Gap Analysis Project
I can help answer questions and help get the group rolling.
Wrt KLReq: It very much depends on what the group is able to commit to as to the amount of work involved in improving the draft. We recently reorganised the CLReq doc to follow the structure used throughout the Language Enablement work (see for example the structure in the Gap Analysis doc template), and it may be useful, though not essential, to reorder the content of KLReq in a similar fashion. Otherwise, small but timely additions would also be fine. We encourage the group to identify gaps in Korean support and report them using the Gap Analysis document, and one way of working would be to document requirements in the KLReq doc as gaps are identified. But if the group wants to work on the KLReq doc as its primary focus, that's ok too.
Another thing a KLReq group could do is answer the outstanding questions we have about how Korean text works. Answers would initially be appropriate in the respective issue, but could also be added to the KLReq doc.
Thanks Richard, for sharing the helpful links and for your kind comments. (In addition, I have always appreciated your long-standing dedication to i18n!)
First, I have added my comments regarding the four short contributions you asked for review. If I have further questions or any update from Korean side, I will let you know it. Thanks!