►
Description
In The Hitchhikers’s Guide to the Galaxy, the Babel Fish is a universal translator. By allowing all beings to communicate regardless of language, it ‘neatly crosses the language divide between any species’. Aditya Mukerjee, an Engineer at Stripe notes in this talk that most programming languages are designed for English speakers, and most open source projects require some familiarity with English. How do we create a multilingual programming language and a multilingual open source community, allowing developers who only speak English to collaborate on open-source projects with developers who don't speak English at all?
About GitHub Universe:
GitHub Universe is a two-day conference dedicated to the creativity and curiosity of the largest software community in the world. Sessions cover topics from team culture to open source software across industries and technologies.
For more information on GitHub Universe, check the website:
https://githubuniverse.com
A
A
Well,
ninety-five
percent
of
the
world
doesn't
speak
English
as
their
first
language
and
eighty-nine
percent
of
the
world
doesn't
speak
English
at
all.
So
let's
just
raise
your
hand
here.
If
you,
if
you
speak
more
than
one
language,
that's
a
good
number
of
people.
How
many
of
you
do
not
speak
English
as
your
first
language?
A
Okay,
that's
a
good
show
if
this
conference
were
perfectly
representative
of
the
world
in
every
way,
this
entire
conference,
only
165
people,
who've
attended,
would
even
be
able
to
understand
this
talk
at
all
and
of
those
all,
but
75
would
be
listening
to
me
speak
in
what's
to
them
a
foreign
language.
So
if
the
people
who
are
best
equipped
to
solve
the
world's
problems
are
the
ones
who've
experienced
them
firsthand,
this
is
itself
a
problem.
A
So
the
findings
I'm
presenting
on
today
are
combination
of
what
I've
encountered
in
my
own
work,
both
as
a
risk
engineered
stripe
and
elsewhere,
and
some
weeks
ago,
I
also
sent
around
a
survey
for
developers
whose
native
language
is
not
English
or
developers
who
have
experience
working
across
language
barriers
and
some
common
key
pain
points
emerged,
namely,
if
you
don't
speak
English
or
if
you
don't
even
know
how
to
read
an
alphabet
Latin
alphabet.
Even
reading
code
requires
proficiency.
A
That's
a
that's
a
hurdle,
but
things
like
error
message
is
documentation
participating
in
the
community
through
vents
and
mailing
lists.
All
of
these
represent
hurdles
that
you
need
to
understand.
English
would
be
able
to
part
to
be
able
to
participate
in
fully
so
we're
going
to
talk
about
some
simple
low-tech
ways
that
we
can
make
open
source
communities
accessible
to
speakers
of
all
languages
and
we're
also
going
to
see
some
slick,
higher
tech
techniques
that
we
can
apply
to
our
code
as
well.
A
So,
let's
look
at
this
visual
aid
that
shape
right
there.
It
looks
like
an
oval,
but
that's
just
doing
the
map
projection
on
a
globe
that
would
be
a
perfect
circle.
More
people
live
inside
that
circle,
then,
outside
of
it
that's
more
than
half
of
the
world's
population
right
there,
one-fifth
of
the
world
lives
in
China
and
another
half.
Oh
sorry,
another
fifth
live
in
India,
but
that's
not
what
the
open
source
world
looks
like.
As
of
today,
only
ten
percent
of
the
world's
programmers
live
in
China.
A
Only
one
point:
four
percent
a
stack
overflow
visits
came
from
China
now
since
then,
they've
actually
launched
the
beta
version
of
stack
overflow
in
Chinese,
so
these
numbers
are
no
longer
current,
but
the
underlying
theme
is
still
relevant
and
it
raises
the
question
that,
where
would
all
of
those
other
eighty-six
percent
of
programmers
in
China
go
if
they're
not
going
to
stack
overflow
for
for
their
information
in
the
answer
is
that
they
go
to
chinese
language
versions.
Instead,
some
of
these
are
direct
clones
of
stack
overflow
there's
one.
A
That's
literally
titled
Chinese
stack
overflow,
but
there
are
other
community
resources
of
all
forms.
Just
like
we
have
in
English,
and
it's
not
a
phenomenon.
That's
you
need
to
Chinese.
Either
there
are
language,
specific
resources
targeted
at
speakers
of
Arabic
Russian,
German,
French
Spanish.
Yet.
B
A
Name
it
and
they're
not
just
limited
to
help
forums
either
so
for
right.
Here
you
can
see
that
the
Chinese
go
community
has
actually
taken
the
work
of
translating
the
official
go
documentation
into
Chinese
complete
with
the
iconic
go
go
for
mascot
and
there
are
other
projects
you
can
find
on
github,
in
which
all
of
the
project
collaboration
the
issue
tracking
the
readme,
the
comments
everything
happens
all
in
Chinese.
So
it's
great
that
Chinese,
programmers
and
people
who
programmed
as
you
speak.
A
Other
languages
have
developed
thriving
communities
for
themselves,
but
fragmenting
resources
is
bad
for
open-source
development
fragmentation
means
duplicated
work.
It
means
incompatible
interfaces.
So
how
do
we
bridge
these
two
communities
of
these
many
communities
and
it's
a
problem
that
affects
a
non-native
English
speakers
too?
A
There
was
a
blog
post,
a
while
back
that
was
titled,
more
bad
english,
please
and
implored
people
to
participate
in
developer
mailing
list
and
not
let
fear
or
embarrassment
hold
them
back
from
from
participating,
even
if
they
feel
that
their
English
isn't
very
good
and
from
the
responses
to
the
post
by
non-native,
English
speakers,
it
was
clear
that
this
was
and
still
is,
a
very
big
problem,
a
major
point
of
hesitation
for
developers
who
don't
speak
English
as
their
first
language.
The
language
barrier
can
cause
them
to
feel
disconnected
from
the
community.
A
They
can
feel
like
the
community,
isn't
isn't
for
them
that
they're
not
welcome
and
as
fragments
the
open
source
world.
Even
more
so
we
can
agree
that
fragmentation
is
bad
in
both
code
and
in
community.
It
leads
to
wasted
time,
duplicated
effort,
solving
the
same
problems
over
and
over
again
with
only
minor
variations.
A
A
As
native
speakers,
we
don't
really
think
about
this.
We're
oftentimes
used
to
switching
our
registers
based
on
the
context
and
we're
used
to
understanding
multiple
dialects
and
not
thinking
about
that.
But
if
our
solution
would
be
to
use
a
single
language,
we'd
have
to
standard
our
usage
of
these
as
well
and
linguistically
that's
impossible.
A
This
is
actually
one
of
the
reasons
at
the
very
first
lingua
franca
franca
clang,
which
the
Mediterranean
language
sabir
died
out
as
its
usage
grew
as
a
pidgin
language,
it
got
fragmented
and
it
ended
up
influencing
the
local
languages
across
the
Mediterranean
instead,
so
the
languages
that
became
modern,
Spanish,
French
Portuguese
Italian,
all
of
those.
So
it's
much
better
for
us
to
embrace
multilingual
workflows.
Instead
of
fighting
an
uphill
battle
against
what
languages
are
literally
meant
to
do,
which
is
evolved
and
diverge.
A
It's
no
accident
that
this
is
what
we
already
do
for
programming
languages,
you'll
notice,
we
don't
tell
everyone,
everyone
has
to
use,
see,
no
matter
what
no
matter
what
project
they're
doing,
no
matter
who
they
are
no
matter.
What
they're
writing
note.
We
recognize
that
different
projects
will
use
different
languages
or
even
within
a
saint,
the
same
project.
A
We
might
have
different
languages
depending
on
the
needs
and
as
our
languages
grow
as
they
get
more
developers
as
they
as
they
grow
in
popularity
or
as
their
needs
evolve,
as
they
are
ported
to
different
platforms,
different
architectures,
different
runtimes.
They
evolve
as
well.
They
form
different
dialects
day,
for
you
can
see
this
very
easily.
In
JavaScript,
for
example,
we
have
languages
like
typescript
and
coffee
script,
which
is
event
which
have
emerged,
emerged
to
solve
different
needs,
or
you
can
see.
A
Look
at
react
native,
it's
very
similar
to
react
for
the
web,
but
it's
it's
not
exactly
the
same,
and
we
certainly
wouldn't
say
that
react
is
literally
the
same
as
JavaScript.
It's
a
variation.
It
involves
JavaScript,
but
it's
also
something
new
as
well
same
with.
You
know:
C
C++
originally
started
as
a
dialect
of
C,
and
now
I
mean
the
C++
templating
language
is
itself.
You
know
many
different
languages
all
together.
So
we
accept
this
kind
of
divergence
and
accept
multilingualism
in
our
programming
languages
without
a
problem.
A
So
how
do
we
do
this?
How
do
we
make
our
code
multilingual
and
what
does
that
actually
even
mean
to
make
our
code
multilingual?
We
can
go
back
in
history.
Grace
Hopper
was
one
of
the
first
computer
scientists
and
she
wrote
the
very
first
compiler
for
a
programming
language
ever
the
language
that
she
invented.
As
many
of
you
will
know,
it
was
called
cobalt
and
the
original
goal
was
to
have
English
like
natural
language
syntax,
so
that
business
executives
could
write
code
and
she
received
incredible
pushback
about
this
engineers
were
furious.
They
thought
well.
A
If
business
executives
are
going
to
write
code,
that's
going
to
put
us
out
of
a
job
and
don't
worry
this
was
60
years
ago,
so
it
seven
years
ago,
so
it
hasn't
actually
happened
yet,
but
hoppers
vision
actually
went
even
further.
Why
should
we
restrict
this
to
english
speaking
to
english-like
syntax?
What
if
developers,
who
spoke
other
languages,
also
wanted
to
write
programs?
She
wanted
cobalt
to
be,
and
I
quote
a
language
you
can
use
to
talk
to
programmers
around
the
world
and
the
response
to
that
part
was
even
more
vitriolic.
A
The
basic
viel
said:
well,
how
can
we
teach
American
computers
to
run
German,
German
programs,
German
code
and
to
be
clear,
this
was
not
a
technical
question
of
how
do
we
do
it
on
a
practical
level,
it
was
very
much
a
political
one.
Even
though
this
was
a
decade
and
a
half
after
World
War
Two,
it
ended
the
fear
of
a
threat
from
Germany
or
from
Russia,
still
looms
strong
in
people's
minds.
A
It's
the
idea
of
opening
up
American
hardware
and
having
that
having
that
accessible
to
German
programmers
and
German
code
or
Russian
Russian
code
was
anathema
to
people,
but
even
if
hoppers
idea
was
put
on
the
back
burner
due
to
xenophobia
and
politics
in
the
1950s,
we
can
still
look
at
what
that
means.
Today.
This
is
hopper
speaking
many
years
later
about
what
COBOL
meant
to
her.
She
said.
A
I
would
have
thought
that
it
would
be
useful
to
NATO
because
they
had
the
common
verbs
for
things
that
they
were
going
to
do
and
the
nouns
they
just
have
to
have
a
dictionary
for
the
things
they
were
referring
to
for
inventory.
Control
they'd
have
common
nouns
throughout
NATO
and
they
can
make
a
dictionary
of
common
verbs
and
translate
the
program.
You
could
write
one
in
English
and
you
could
translate
it
and
it
could
go
to
the
other
language.
No
problem
you'd
have
communication.
It
would
be
a
limited
vocabulary
as
just
a
tangent.
A
That's
why
most
languages,
the
directives,
the
key
words
we
all
use
the
imperative,
the
imperative
form
of
verbs
now
COBOL,
unfortunately,
was
invented
before
structured
programming
had
really
caught
on
with
alcohol,
and
today
we
might
take
it
for
granted
that
good
programs
have
things
like
subroutines
functions,
loops
but
believe
it
or
not
that
wasn't
actually
known
in
hoppers
time.
So
what
would
hoppers
vision?
Look
like
in
a
modern
and
structured
programming
language,
that
is
to
say
how
would
we
translate
this
hello
world
program
which
is
written
and
go
to
a
different
language.
A
We'd
probably
get
something
like
this,
assuming,
though,
of
course
we
could
feed
it
to
the
compiler
and
have
it
run
now.
We've
left
the
identifier
names
intact,
like
main
format
main
true,
but
the
keywords
are
all
now
in
Bengali,
so
that
right
there
is
the
first
challenge
the
go.
Compiler
won't
just
understand
what
you're
doing,
if
you
try
to
throw
it
unrecognized
keywords
at
it,
but
if
you
speak
Bengali,
this
is
great.
You
can
understand
this
readily.
A
A
A
Goro
uses
Bengali
translations
of
all
of
the
NGO
keywords,
but
it
otherwise
functions
exactly
the
same
way.
So
here's
a
hello
world
in
practice-
hopefully
you
can
see
it
so
there's
just
a
program
we
had
before
hello
world
and
there
you
go.
You
run
it
but
remember.
Our
goal
is
to
defragment
the
open
source
community,
not
too
fragmented,
even
more,
and
so
we
need
to
make
sure
our
code
is
interoperable
with
code
written
by
english-speaking
go
developers.
So
let's
translate
this
goro
code
back
into
English.
Go.
A
A
So
how
does
this
work
go?
Source
code
is
already
utf-8,
so
it
has
no
trouble
dealing
with
non-ascii
or
non
extended
asking
keywords.
There
are
a
few
internal
checks
that
ensure
that
non-latin
and
non-alphanumeric
characters
are
excluded
from
keywords,
but
it
turns
out
that
you
can
actually
just
disable
those
without
any
issue.
So
all
we
have
to
do
is
extend
the
lexer
to
handle
the
bengali
translations
of
each
keyword
and,
of
course,
figure
out
what
those
should
be.
A
So
some
of
these
translations
are
pretty
easy,
like
you
know,
for
if
some
of
them
are
really
fun
to
think
about
like
fall
through
for
a
for
a
switch
statement.
How
do
you?
How
do
you
actually
translate
that
into
another
language?
It's
a
metaphor.
It
doesn't
even
make
sense
literally,
but
for
those
of
you
keeping
track
at
home,
this
is
all
done
purely
by
the
lexer.
The
parser
actually
has
no
idea
that
anything
has
even
changed
and
that's
not
something
that
you
can
do
easily.
A
In
most
other
languages,
which
use
flex
space
lectures
because
flex
and
licks
don't
support
multi
byte
code
points
which
which
goes
lexer
does
you
can
accomplish
the
same
goal
in
pretty
much
any
language?
But
you
have
to
dig
a
little
bit
deeper
into
the
parser
to
get
it
to
work.
It
requires
some
more
effort.
A
As
for
the
translation
step,
go
already,
has
a
handy
utility
for
formatting,
so
source
code
called
go
format
or
go
funk
depending
on
who
you
ask,
and
mostly
we
just
use
it-
to
prevent
bike
shedding
over
things
like
the
tabs
versus
spaces
argument.
So,
instead
of
arguing
over
the
proper
way
to
format
source
code,
everyone
just
can
set
up
their
editor.
The
way
they
want.
So
if
I
want
to
use
force
bases
for
indentation,
and
you
want
to
use
two
spaces-
that's
fine
go
format
means
that
we
can
still
work
together
harmoniously.
A
We
set
up
our
editors
to
use
the
width
at
to
render
tabs
with
the
wit
that
we
want,
and
then
after
we
save
our
code,
we
run
go
format
and
will
automatically
translate
our
code
to
this
standard
style.
No
work
needed,
and
in
fact
we
don't
even
need
to
be
aware
that
we
have
different
indentation
preferences,
because
the
code
that
actually
gets
committed
is
in
the
standard
form
in
our
editors,
simply
display
it
in
our
preferred
forms,
but
go
for
McCann
handle
a
lot
more
to
like
removing
unnecessary
parentheses
or
even
simplifying
expressions.
A
Having
bi-directional
translation
layers
means
that
you
don't
even
need
to
know
that
I'm
writing
my
code
in
English
and
I.
Don't
even
need
to
know
that
you're
actually
writing
your
code.
In
Bengali
we
can
localize
our
source
code
as
a
commit
hug.
So
as
a
developer,
gordo
means
that
we
only
ever
need
to
be
able
to
look
at
source
code
in
our
own
native
languages.
A
So
we
translated
the
key
words
but
you'll
notice
that
we
didn't
touch
everything
like
the
package
and
the
variable
names
we
we
left,
those
in
talent
and
lots
of
ink
has
been
spilled
on
the
topic
of
choosing
good
variable
names.
The
one
thing
that
everyone
seems
to
agree
on
is
that
variable
names
should
be
both
descriptive
and
concise,
and
then,
of
course,
no
one
agrees
on
what
descriptive
a
concise
mean,
but
that's
that's
another
topic.
A
A
Well,
in
reality,
many
variable
and
function
names
are
already
quite
highly
structured
or,
to
put
it
in
the
terms
that
hopper
mentioned
earlier,
we
already
have
the
verbs
that
we
use
quite
frequently
when
we're
writing
code,
so
getters
and
setters
are
pretty,
are
pretty
standard
billed
as
a
common
pattern,
if
you're
right
Java,
if
you're
right
Ruby
to
foo,
is
a
way
of
expressing
that
you
are
going
to
be
converting
converting
a
type.
So
we
can
take
advantage
of
this
knowledge.
A
This
structure
that
we're
already
using
and
translate
those
in
the
translation
step
as
well
by
being
a
little
bit
more
conscious
of
the
conventions
that
were
already
using,
we
can
make
our
code
much
more
accessible
to
non-english
speakers.
So
if
we
know
that
get
foo
means
that
it's
an
access
or
method
for
foo,
we
can
say
that
access
or
methods
for
fields
are
translated
in
this
way,
setter
methods,
mutator
methods
for
four
fields,
are
translating
this
way
and
so
on.
A
Now,
while
it's
fun
to
talk
about
fully
automatic
isomorphic
translations
of
source
code
between
arbitrary
sets
of
languages,
it's
not
all
that
it
takes
to
make
open
source
development
accessible
to
non-english
speakers.
So
we've
all
struggled
at
some
point
with
software,
that's
undocumented
or
poorly
documented,
and
if
we
want
to
fully
bridge
the
divide,
we
need
to
make
sure
that
non-english
speakers
have
access
to
this
information
as
well.
A
A
It's
an
automatic
translation
works
quite
well
for
specialized
and
technical
text
for
any
domain,
not
just
software
as
well
as
text
with
very
narrow
context.
The
reasons
for
that
we
won't
get
into,
but
fortunately,
for
us
that
describes
open
source
documentation.
Quite
well.
We're
not
looking
to
bridge
all
communication
in
every
context
between
every
pair
of
languages,
we're
just
looking
to
bridge
communication
within
our
context
within
open
source
software
development
between
the
languages
that
we
need.
A
You
know
you
don't
have
to
read
at
all:
it's
pretty
standard
technical
documentation,
but
let's
see
what
happens
when
Google
tries
to
translate
that
into
Bengali
there
you
go
so
how
many
of
you
can
actually
read
this
by
the
way:
anyone,
okay,
that's
what
I
thought.
So,
if
you
don't
read
Bengali,
this
doesn't
actually
look
very
impressive
and
I
could
tell
you
that
you
know
this
is
a
pretty
good
translation
asked
me
to
take
my
word
for
it,
but
that's
a
little
bit
anti-climactic
and
a
talk
like
this.
A
By
the
way,
can
you
read
this,
I'm
not
entirely
sure.
Ok,
I'm
seeing
seeing
some
nods,
at
least
from
the
back.
So
that's
good.
So
the
first
paragraph
which
describes
what
regular
expressions
are.
It
falls
a
little
short.
You
can
tell
that
it
has
something
to
do
with
matching
strings,
but
it's
a
little
bit
clumsy.
A
The
second
paragraph,
though,
is
absolutely
spot-on.
It's
a
if
a
and
B
are
both
regular
expressions.
Then
a
B
is
a
regular
expression
in
general.
If
you
are
a
match
for
string
p
and
another
string,
q
matches
be,
the
string
will
match
abp
q.
This
holds
unless
a
or
b
contain
low
precedence
operations.
So
the
emphasis
the
bold
is
mine,
but
everything
else
is
exactly
what
Google
Translate
provided
the
punctuation
the
capitalization.
A
All
of
that
big
ol
e
doesn't
even
have
capital
letters,
but
it
was
able
to
translate
that
back
correctly
from
the
from
the
context
and
for
the
third
paragraph
the
original
said
you
know
format.
A
brief
explanation
follows
a
gentler
presentation.
We
still
even
get
the
idioms
follows
gentler,
so
maybe
your
school
still
skeptical.
A
That's
all
so
you
might
be
thinking
well
if
automatic
translation
works
so
well
like
I,
don't
even
need
to
bother
right.
No
can't
other
people
just
use
a
browser
extension
to
localize
content
automatically,
and
the
answer
is
that
that's
what
people
are
already
doing
and
we
saw
the
numbers-
it's
not
working
the
reason
it's
failing,
isn't
just
because
automatic
translation
isn't
good
enough.
It's
because
relying
on
machine
translation
for
to
participate
in
the
community
it
makes
for
a
really
alien
ating
experience.
It
doesn't
make
people
feel
welcome
or
encouraged
to
participate
when
I
surveyed
people.
A
This
was
11
common
point.
One
of
my
co-workers
even
said
that
when
he
was
first
learning
to
program
he's
French
websites
and
even
though
he
did
speak
some
English
and
it
took
him
years
before,
he
felt
comfortable
participating
in
english-speaking
forums
and
if
they
saw
earlier
even
people
who
do
speak,
English
it's
reasonably
well,
but
as
a
native
language
or
as
a
non-native
language,
they're
already
hesitant
to
participate
in
communities
that
they
perceive
as
English
dominant
that
they
don't
think
are
meant
for
them.
A
So
the
goal
with
automatic
translation
is
to
signal
interest
or
just
planting
the
seed
you're,
letting
people
know.
Yes,
we
are
interested
in
you
where
interest
in
your
contributions,
we're
interested
in
reaching
out
to
your
community
to
your
language
group.
It
takes
time
for
this
to
happen,
but
it's
not
going
to
happen
automatically.
We
need
to
make
the
active
effort
we
need
to
reach
out.
A
Within
your
existing
set
of
contributors
and
users,
you
might
not
speak
Spanish
or
Russian
or
Hindi,
but
there's
a
good
chance
that
someone
who
already
uses
your
project
or
works
on
your
open
source
project
does
and
go
to
almost
any
conference
organized
around
a
specific
piece
of
open-source
software
and
you're
almost
guaranteed
to
hear
an
entire
talk
dedicated
to
how
do
we
encourage
more
people
to
contribute
to
this
project
even
today?
This
is
we
heard
people
talking
about
this,
and
this
is
a
project.
This
is
a
conference
just
about
open
source
programming
in
in
general.
A
The
key
here,
though,
is
that
you
have
to
ask
for
it,
and
it
might
sound
very
obvious
that
I'm
saying
it
here
now,
but
it's
not
actually
something
that
your
users
are
going
to
think
to
do
think
to
offer.
Unless
you
actually
make
a
clear
point
of
soliciting
it
they're
not
going
to
think
that's
something
that
you're
interested
in
or
that
that's
a
need
that
you
have
and
it
doesn't
have
to
be
overly
elaborate,
create
project
milestones.
A
A
We've
all
struggled
with
cryptic
error
messages,
and
this
one
is
one
of
my
favorites
from
Java-
cannot
past
parameter
type
from
type
system,
dot
straying
to
argument
type
system,
dot
strength
is
any
actually
know
what
this
means.
Okay,
there's
a
punchline
I'll
tell
you
afterwards
if
you're
interested,
but
you
can
really
tear
your
hair
out,
trying
to
let
trying
to
figure
out
what's
going
on
here,
but
the
only
thing
worse
than
a
cryptic
error
message
is
a
cryptic
error
message.
A
Documentation
is
the
next
easiest,
providing
alternative
forms
of
documentation
even
condensed.
Also
like
error
messages
has
an
incredibly
high
impact
on
developers.
You
don't
speak
English
and
fortunately
we
have
an
existing
model
for
how
to
present
the
same
information
in
multiple
different
languages.
Wikipedia
does
a
great
job
of
this.
Every
page
has
a
list
of
languages
in
which
that
same
information
can
already
be
found.
Now
and
and
of
course,
if
a
language
is
missing,
anyone
can
add
it
themselves
now.
A
The
github
wiki
doesn't
support
this
directly,
but
you
can
accomplish
the
same
goal
by
creating
that
index.
For
yourself
manually
from
the
infant
languages
you
already
support,
and
if
it's
something
you'd
be
interested
in,
if
github
would
support,
I
hear
there
might
be
some
github
employees
at
this
conference
that
you
could
talk
to
so
so
now,
it's
possible
for
information
to
diverge
between
different
language
versions
of
the
same
page,
on
a
wiki,
and
this
is
something
that
even
wikipedia
has
happened.
So
it's
bound
to
happen
on
a
smaller
open
source
product
as
well.
A
The
key
here
is
to
find
interpreters
who
have
experience
with
translating
technical
topics,
because
not
all
interpreters
will
be
trained
in
that
vocabulary.
The
same
way
that
not
all
English
speakers
understand
technical
jargon
in
a
separate
approach
is
to
get
live.
Stenography
some
of
the
best
conferences
I've
been
that
I've
been
to
have
done
this
to
provide
live,
captions
and
turns
out
github
universe
is
doing
this
as
well.
A
Now
captions
are
going
to
be
in
English,
but
they
can
help
people
who
speak
english
as
a
non-native
language,
because
reading
captions
is
often
much
easier
than
trying
to
catch
words
as
they're
spoken
in
real
time,
especially
if
people
are
speaking
quickly
like
I
tend
to.
If
you
miss,
hear
something
or
miss
a
word,
you
can
go
back,
you
can.
You
can
read.
What's
going
on
now,
of
course,
live.
Captions
are
also
useful
for
a
whole
host
of
other
groups
that
people
are
deaf.
A
People
are
hard
of
hearing
people
of
ADHD
or
auditory
processing
disorders
and
so
on,
and
it
can
be
a
great
way
to
include
them
as
well
now
for
a
live,
stenography
I'd
recommend
these
two
groups
I
personally
been
to
events
around
the
country
where
both
Steiner,
I,
cart
and
white
coat
have
been
providing
captions,
so
I
can
testify
their
effectiveness.
Firsthand.
I'm
told
that
manifold
is
the
group.
A
Now
a
lot
of
key
project
collaboration
happens
over
mailing
list,
and
so
it's
hard
for
developers
to
be
first-class
citizens
of
open
source
development
if
they
can't
participate
in
conversations
around
project
direction
or
technical
discussions.
As
we
saw
earlier
with
the
more
bad
english,
please
post
even
non-native
speakers
don't
always
feel
welcome,
participating
in
developer
mailing
lists.
Now
more
about
english.
Please
encourages
people
to
participate,
even
if
they
aren't
confident
in
their
own
english
skills.
But
what?
A
We
could
do
the
same
on
our
mailing
list
archives.
This
is
what
that
might
look
like.
This
is
a
german
language,
debian
mailing
list,
and
you
know
we
could
have,
for
example,
right
there
like
spanish
english
chinese.
We
could
provide
links
to
community
translations
or
links
for
people
to
provide
those,
even
if
not
every
message
gets
translated
into
every
language.
It
provides
the
space
for
that
to
happen
when
it's
needed
and
it's
again
it's
much
better
to
centralize
us
information
within
the
project.
A
I'd
highly
encourage
you
to
do
that,
but
let's
also
not
underestimate
how
effective
some
of
the
more
straightforward
approaches
can
be
and
that
we
can
all
take
part
in,
as
I
said
the
beginning
at
the
end
of
the
day,
we're
all
here,
because
we
wanna
have
an
impact.
We
want
to
change
the
world
and
we
think
that
software,
particularly
open-source
software,
is
a
really
powerful
tool
for
doing
that,
and
while
technology
is
key
to
making
that
happen,
social
change
isn't
just
about
building
the
fanciest
technologies
that
we
can.
It's
also
about
improving
and
mobilizing
technologies.
A
We
already
have
if
you
want
another
example:
look
at
efforts
to
eradicate
polio
around
the
world
or
or
combating
so
HIV
prevention
efforts.
Those
wouldn't
be
possible
without
the
polio
vaccine
without
antiretrovirals,
but
at
the
same
time,
the
major
breakthroughs
that
we've
had
in
recent
years,
the
cutting
edge
it
it
isn't
around
developed
just
around
developing
new
medicines.
We've
had
those
for
decades,
it's
around
providing
the
infrastructure
to
get
those
medicines
to
people
where
the
people
who
need
them
when
they
need
them.
It's
about
providing
the
money
about
providing
the
resources.
A
So
if
we
think
of
technology,
if
that
open
source
software
can
change
the
world,
let's
prove
it,
and
to
do
that,
we
need
to
make
sure
that
developing
open-source
software
is
an
option
not
just
for
us
but
for
the
other.
Ninety
five
percent
of
the
world
too.
So
let's
commit
ourselves
to
doing
that.
Thank.
A
Almost
trivial,
in
fact,
you
can
honestly
do
it
with
google
translate.
If
your,
if
you
want
your
dedicated
to
core,
is
something
that
you
can
look
at.
It's
on
github
go
back
here,
you
good!
You
can
look
at
how
I
did
it.
It's
really
just
a
matter
of
stubbing
out
the
keywords
and
what
tokens
that
they're
going
to
map
to
you
have
to
do
a
little
bit
more
around
the
formatting,
the
translation
side.
But
it's
it's
pretty
roads.
A
/
me,
it's
pretty
straightforward
doing
in
other
languages
a
little
bit
more
technically
complex,
but
it's
still
pretty
abstract.
If
you,
if
you
figured
out
the
way
to
localize
languages
or
localize,
a
particular
compiler
plugging
in
whatever
language
you
want
to
translate
it
to
is
very
straightforward.
So
please
go
home.
Do
that
localize!
All
of
your
all
of
your
favorite
languages
think
that's
time
but
I'm
happy
to
talk
to
people
afterwards.
Thank
you.