Internationalization (I18N) WG Teleconference
- Past
- Confirmed
- Past
- Confirmed
Meeting
NOTE WELL This meeting is scheduled in the Europe/London
time zone. That time zone observes Daylight Savings/Summer Time. Your local time for this call may vary due to differences in your local time zone's observation of DST/ST from that of the UK.
WHAT IS THIS? This is the regular weekly teleconference of the W3C Internationalization Working Group.
AGENDA+ If you would like the chair to consider adding an item to the agenda, please send email to the public-i18n-core@ mailing list with a subject line starting agenda+
. Here is an example.
Agenda
BE PREPARED
Things to do before the meeting:
- Read this section of the proposed changes to String-Meta: https://deploy-preview-86--string-meta.netlify.app/#bp-producers
- Review this PR with proposed changes related to IDNs: https://github.com/w3c/bp-i18n-specdev/pull/128
AGENDA
Topic: Agenda Review
Topic: Action Items
Review of open action items from previous meetings
Topic: Info Share
Share information of interest to the working group or pertaining to internationalization in general.
Topic: RADAR Review
Time to review new and on-going requests for specification review. Incoming requests are assigned to shepherds in this part of the call.
In addition, we review the status of specifications that have received comments. Please review your issues and owned items in advance of the call
Topic: Pending Issue Review
Review of new and pending issues raised by working group members or via the various bots.
Topic: FPWD of Khmer Layout Requirements
Richard is seeking approval of a first public working draft of a new LREQ document for Khmer.
Topic: RFC9457 and string-meta
_Verifiable Credentials filed a PR [2] that references RFC9457 in response to our comment [1]. _
- RFC9457 defines a JSON (and alternate XML) structure for returning error information. Seems like they could follow our guidance in string-meta and include lang/dir metadata in the document. They do provide for localization externally by doing language negotiation off of Accept-Language, but it seems criminal not to tell the recipient what language was negotiated??
- We should update specdev to include guidance about this.
- I made a comment on VC's specific text that this group should review.
- https://lists.w3.org/Archives/Public/public-i18n-core/2024JanMar/0110.html
- [1] https://github.com/w3c/vc-bitstring-status-list/issues/140
- [2] https://github.com/w3c/vc-bitstring-status-list/pull/152
Topic: String-meta best practices for producers
The section "Guidance for Producers" was added to the PR. Let's review.
- https://github.com/w3c/string-meta/pull/86
- https://deploy-preview-86--string-meta.netlify.app/#bp-producers
Topic: Specdev changes to support IDNs
Per last week's call, review Fuqiao's work for inclusion this week
- https://github.com/w3c/bp-i18n-specdev/pull/128
- https://deploy-preview-128--bp-i18n-specdev.netlify.app/#idn
Topic: AOB?
REMINDER
Getting too many of these notifications? Read this email from Richard on how to manage notifications.
SCRIBE
If you are set to scribe and cannot make it, please send regrets to the chair. Volunteers to act as scribe cheerfully accepted.
Atsushi
[2024-03-14] Fuqiao
[2024-03-21] Bert
Chair's Link Farm
https://github.com/w3c/i18n-actions/issues
https://github.com/w3c/i18n-request/projects/1
https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending
Export options
Personal Links
Please log in to export this event with all the information you have access to.
Public Links
The following links do not contain any sensitive information and can be shared publicly.