search

w3c / i18n-request

Horizontal review requests are made via issues in this repo, and tracked by our radar.
https://github.com/orgs/w3c/projects/91/views/1
1 stars 7 forks source link

Web Translation API explainer 2024-05-07 > 2024-06-06 #231

Open domenic opened 5 months ago

domenic commented 5 months ago

Name of your specification

Web Translation API explainer

URL of your specification

https://github.com/WICG/translation-api/blob/main/README.md

Does your specification include an Internationalization Considerations section?

When does the review need to be finished?

This is an early-stage explainer and we don't have any deadline at the moment

What has changed since any previous review?

No response

Please point to the results of your own self-review

No response

Where and how should the i18n WG raise issues?

https://github.com/WICG/translation-api/issues

Pointer to any explainer for the spec

https://github.com/WICG/translation-api/blob/main/README.md

Other comments

It seems like this review-request process is a bit heavy-weight and meant for more official spec transitions. However, due to the nature of our API, we'd love to have i18n experts advice from the beginning, even though we only have an explainer at this point.

One specific issue that we'd appreciate i18n expert help on is language tag handling. We've pre-created an issue for discussion here: https://github.com/WICG/translation-api/issues/2.

aphillips commented 4 months ago

@domenic noted:

It seems like this review-request process is a bit heavy-weight and meant for more official spec transitions. However, due to the nature of our API, we'd love to have i18n experts advice from the beginning, even though we only have an explainer at this point.

Review requests (for horizontal review) are part of the Process, so there is at least some formality surrounding it. Historically there have been problems stemming from groups not requesting review in a timely manner.

We sincerely hope that the formality of the mechanism doesn't deter this type of early-review request. We try hard to encourage early engagement like this as the most productive way to ensure high-quality I18N support.

aphillips commented 4 months ago

@domenic

One specific issue that we'd appreciate i18n expert help on is language tag handling. We've pre-created an issue for discussion here: https://github.com/WICG/translation-api/issues/2.

I observe that @xfq, @r12a and @aphillips (me) don't have permissions to manage issues in this repo (and possibly other WICG repos??), as we have with all of the W3C repos. This means that I can't fix the tags on WICG/trasnlation-api#2 so that it is automatically tracked in our activity repo.

Note that you can communicate with our WG about individual issues by adding i18n-tracker as a label to an issue (I18N will upgrade it to i18n-needs-resolution if necessary).

xfq commented 4 months ago

cc @plehegar

aphillips commented 4 months ago

@domenic Please note that the 2024-06-06 date is an artificial self-imposed deadline for initial discussion.

domenic commented 4 months ago

Thanks so much! We're excited to get your feedback.

I've added the i18n-tracker label to WICG/translation-api#2 and given you three triage permissions on the repo. Probably there is something more to do with WICG as a whole; maybe @plehegar can help but also CCing @cwilso and @yoavweiss on that front. (Although probably we should take that discussion elsewhere.)

xfq commented 4 months ago

I've added the i18n-tracker label to https://github.com/WICG/translation-api/issues/2 and given you three triage permissions on the repo.

Would you please change the colours of the labels to match the convention across W3C specifications (that is, making it #F9C9FF)? I don't seem to have permission to do this.

Thanks a lot!