Skip to content

DOM Localization #67

@eemeli

Description

@eemeli

Session description

Users of the web are best served by being able to experience it in their native languages. Currently, localization of web content is achieved with a multitude of custom solutions, most of which are unable to express the full depth and breadth of human expressions in all languages. Introducing an easy-to-use but powerful standard localization solution would improve the experience of all users, in particular the vast majority who do not speak English natively.

This session is a continuation of the 2023 breakout session. Since then, the Unicode MessageFormat standard has been published as a part of Unicode Technical Standard #35 and the DOM Localization explainer has been updated. It has also become clear that a web-compatible file format for localization resources needs to be identified as a part of the work towards DOM localization, or a new file format needs to be specified.

Session goal

Collect comments on the proposal and recruit interests to work on the standard.

Additional session chairs (Optional)

No response

Who can attend

Anyone may attend (Default)

Instructions for meeting planners (Optional)

Please avoid overlap with sessions #57 and #71.

IRC channel (Optional)

#dom-localization

Agenda for the meeting.

Introductory slides

Big Questions

  1. Should we work on introducing localization as a capability of the web platform?
  2. Is the Internationalization WG an appropriate forum for standardizing the message resource file format?
  3. How specific to localization should the HTML capabilities be?

Scheduling conflicts to avoid (For meeting planners only)

Links to calendar

Meeting materials

Metadata

Metadata

Assignees

No one assigned

    Labels

    sessionBreakout session proposal

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions