Re: [csswg-drafts] Seeking Korean help (#13210)

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](https://w3c.github.io/jlreq/home) and [CLReq](https://w3c.github.io/clreq/home) 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](https://www.w3.org/International/i18n-drafts/nav/languagedev) [Overview of the framework]
- [Get involved with Language Enablement](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation)
- [Setting up a Gap Analysis Project](https://github.com/w3c/typography/wiki/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](https://w3c.github.io/i18n-activity/templates/gap-analysis/gap-analysis_template.html), 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](https://www.w3.org/TR/kore-gap/), 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.

-- 
GitHub Notification of comment by r12a
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13210#issuecomment-3646914388 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 12 December 2025 15:10:17 UTC