I'm Ben, aka obensource

Howdy howdy howdy

People of g11n & i18n

Internationalization and Globalization Support for Node.js

Part One

Some History

Unicode

ICU
CLDR

Unicode

The Standard & Consortium

ICU

International Components for Unicode

CLDR

Common Locale Data Repository

ECMA-402

The Intl Specification

ICU in Node.js

Intl history & Current Status

From v0.12 up through the latest (v14.4.0)

Node.js i18n WG

History & Current Status

First Wave

io.js l10n teams and the Intl WG

Second Wave

Node.js i18n WG

g11n, i18n, l10n

New Evolutions

ICU4X

Message Format

OpenJS as a

Unicode Consortium

liaison member

Looking Forward

ECMA-402

is moving across the language landscape

(ICU4X)

OpenJS & Unicode

can standardize g11n, i18n, and l10n across

the JavaScript ecosystem, and beyond!

Part Two

nodejs/i18n Discussion

g11n

How do we onboard new g11n contributors and keep the node/i18n-api healthy?

What are the greatest needs of this team right now?

i18n

What's the scope for node?

(eg. Websites/documentation, etc)

What potential g11n / i18n vectors would be useful to target?

(eg. V8 error messages, what else?)

i18n (continued)

How can node/i18n maintain parity with

node's projects that require i18n?
(eg. node/website-redesign)?

What are some infrastructure best-practices we can leverage to surmount node/i18n's current challenges?

l10n

How do we set up l10n groups for greater autonomy, reciprocity, and success?

OpenJS & Unicode

How do we build a meaningful relationship between the Unicode Consortium and OpenJS projects like Node.js?

Part Three

A call to participate

How to get involved

Current Needs

Thank you!