Provide internationalization advice to other groups developing Web standards, and review their specifications (mostly W3C groups, but we also get involved in Unicode, IDN, IETF and other work).
Develop education and outreach materials to make the internationalization aspects of W3C technology better understood and more widely and consistently used by content authors and implementers.
Gather and make available requirements for the support of local writing systems and languages on the Web.
The project radar lists objectives for current WG work items.
The main point of entry for information and news related to the work of the Internationalization Working Group is the
The chair of the Working Group is Addison Phillips (Amazon).
Much of the technical discussion takes place in various github issues lists. If you want to raise an issue with a document, this is the place to raise it. See a list of open issues.
Technical topics for which no GitHub issue list is appropriate can be discussed on the www-international mailing list, however, we recommend that you start technical threads on w3c/i18n-discuss rather than here, to leverage the significant benefits that GitHub issues bring. Www-international is the main list for the Internationalization Interest Group. The list receives i18n WG minutes, and daily digests of activity on i18n GitHub issues, including review comments sent to other groups. The list is public and anyone can subscribe.
public-i18n-core is used mostly for group-restricted discussions, and for notification of proposed review comments. The archive is public. This list also receives weekly digests of activity on i18n GitHub issues.
There is also a member-only list [archive] which is used for group administravia and any member-confidential topics.
There is also a related, very low traffic list, public-iri, for discussions of IRIs and related topics. The list is public and anyone can subscribe.
The working group holds a weekly Webex teleconference to discuss work items for about one hour.
Meeting agenda are published before each teleconference on the
member-i18n-core mailing list. They include Webex links and telephone numbers, and also include information about how to connect to IRC, which is used during meetings to record minutes and also to share URIs, examples, and so forth. We also use it outside of meetings for quick contacts.
To request an agenda item, send an email to the member list with "agenda+" at the start of the subject.
Minutes and summaries of all teleconferences and face-to-face meetings can be found in the
www-international mail archive.
Next face-to-face meeting
- Vancouver, BC, Canada (TPAC), 26-30 October 2020
The Working Group (WG) is always looking for additional participants, to work on a very varied range of topics and interests. The group needs a variety of people with different skills, from technical authoring to specialised knowledge of particular technologies.
See a list of participation benefits for you and your organization.
See some examples of what WG members do within the group.
Working group members are responsible for the development of the group's deliverables, so some minimum commitment is preferred, but we are flexible about this.
We would like you to participate in weekly teleconferences and in face to face meetings as scheduled or send regrets to list.
We would like you participate in reviews and discussions of documents or specifications where you have an interest or expertise.
The Working Group has fingers in so many pies that it can be a little disorienting or confusing for new people at first. Your participation in the WG will be driven mostly by your interests, so please look for areas where you are interested in contributing and feel free to volunteer or champion an area that is particularly interesting to you.
Participants in the working group are expected to observe the requirements of the W3C Process for Working Groups.
If you are unable to make the required commitment to join the working group, you can still contribute in a number of ways. You can also simply follow the work by accessing the Internationalization Web site, the public mailing lists and archives, and all public documents.
You are also encouraged to join the Internationalization Interest Group.
We use Github to develop our technical reports. You can find links to the github repositories in the project radar.
The folllowing links take you to pages that point to useful information, depending on who you are.
Working Group members contribute in one or more of the following ways.
- Participate in discussions on the various mailing lists and during teleconferences.
- Review articles and documents prior to publication and send comments.
- Review W3C specifications for internationalization issues and forward to the group
- Coordinate notification and discussion of review issues with other Working Groups.
- Provide information about language or script usage in response to our feedback requests.
- Write articles and plan and discuss content for forthcoming articles.
- Develop or review best practices, requirements, guidelines and other Working Group Notes for content authors, implementers, or specification developers.
- Help maintain topic and techniques indexes to the information on the site.
- Develop tests to help implementors and better understand what internationalization features are supported in browsers.
- Help respond to feedback on articles, etc.
What does reviewing a spec involve?
Choose specs you have an interest in or that you think may widen your awareness, and don't worry about revisiting recently reviewed specs and raising new issues if you spot any. See the review radar for suggestions.
There is a page How to review specs and raise issues that describes, step-by-step, how to raise issues as you review a spec.
We are currently developing a checklist to help you with suggestions of things to look for. It's by no means exhaustive, and it's still in development, so don't expect it to be perfect. However, as you drill down in that page you reach a list of "Recommendations" which will give you ideas. If there is a 'more' link at the end of the recommendation, click on it to better understand the topic.