►
From YouTube: Translator Call 2019.11.27
Description
Call agenda and details are on the GitHub issue:
https://github.com/bisq-network/growth/issues/166
Join the discussion to help out on our Keybase group in the #transifex channel:
https://keybase.io/team/bisq
A
Everybody
today
is
our
November
translator
call
and
I'm
a
Luna
and
I
am
back
from
a
long
hiatus
and
I'm
taking
over
the
role
of
transifex
admin
from
you
can
see.
So
we
have
a
lot
on.
The
agenda
will
have
several
participants,
some
of
them
new
and
so
first
item
on
the
agenda.
I.
Think
we'll
just
move
to.
The
first
item
is
just
needing
a
review
of
the
current
project.
A
A
That's
translating
the
software
then
so
that
project
has
over
like
around
10
or
maybe
a
little
more
core
languages,
and
then
we
have
bisque
website
where
we
started
translating
certain
pages,
the
landing
page
and
in
other
important
pages
into
several
languages,
and
there
is
an
overlap.
So,
basically,
since
the
software
is
available
in
certain
languages,
we
want
to
make
sure
that
other
information
is
available
in
those
languages.
So
the
website
and
and
then
there's
another
project
subtitle
where
some
YouTube
videos
were
translated
into
several
languages.
So
regarding
their
the
desktop.
A
So
we
before
I
left
we
have
like
it
was
kind
of
not
very
formal,
but
the
reason
we
have
certain
languages
and
that
are
basically
given
priority-
is
that
there
are
many
reasons.
But
one.
The
reason
is
if
the
if
there
is
based,
if
there's
a
multi-phase
in
those
countries
for
those
languages
or
if
there
is
a
significant
number
of
people
who
speak
those
languages,
so
the
core
languages
as
far
as
I
know-
and
please
correct
me-
for
those
who
have
been
with
disk
for
during
my
absence.
A
B
A
So
for
the
in
the
four
new
newcomers
is
good
to
join
transifex
disrespect
project,
and
so
you
can
see
there
on
the
kind
of
among
the
line
which
is
there
so
many
languages
on
transifex,
but
basically
11
languages,
I
give
entire
area
and
Portuguese
includes
Brazilian
and
Portugal,
and
so
two
quite
active
translators
who
and
contributors
in
general
have
been
working
on
Chinese
traditional
Chinese,
and
they
raised
a
couple
of
questions.
First
of
all,
because
it
seems
like
traditional
Chinese
is
kind
of
more
encompassing
in.
A
Southeast
Asia
and
they
have
done
some
work
and
they
would
like
to
know
if
this
is
the
language
that
should
be
poor
and
yeah.
Basically,
does
anyone
have
any
ideas
or
basically,
what
we
need
to
figure
out
and
I
have
spoken
to
Christophe
just
a
few
minutes
ago,
how
we
need
to
connect
our
translation
activity
to
the
actual
use
of
the
software
in
those
countries,
so
I
don't
know
kind
of
whether
we
should
gather
some
I
think
that
there
was
Google,
Analytics
statistics
but
connect.
A
We
need
to
figure
out
how
important
it
is
to
include
a
new
language,
because
it's
important
to
have
to
focus
on
the
completeness
of
each
language
and
on
the
quality
and
consistency
so
in
the
translator.
Documentation
in
the
Virginia
and
I
pointed
out
that
it's
good
to
have
in
each
team
a
translator
at
the
reviewer.
So
we
need
to
make
sure.
Yes,
you
have
that
so
does
anyone
have
any
suggestions
or
idea
for
that.
B
Well,
I
think,
there's
two
considerations,
I
think
number
one
we
have
to
like.
You
said:
make
sure
that
there
is
a
solid
utility
for
the
language
I
mean
because
we
can
have
and
we've
had
people
who
speak
a
number
of
languages,
approach
us
and
offer
translating
because
they
can,
but
that
doesn't
mean
that
it's
worthwhile
to
include
the
language
in
the
software
mm-hmm,
so
I
think
I,
guess
website.
Metrics
could
be
one
way
of
determining
which
ones
are
useful
or
not.
A
A
So
that's
a
really
good
point,
because
I
think,
then
we
have
these
11
lines,
the
languages
we
can
maintain
them
and
because
I
saw
that
there
was
also
check
and
I'm,
not
sure
how
much
I
think
there's
only
one
person
to
check
and
I'm
not
sure
how
much
demand
there
is
and
how
it's
great,
that
people
are
very,
very
interested.
It's
really
great
that
to
have
it,
but
it
becomes
a
little
kind
of
unmanageable
to
have
all
these
languages.
A
We
need
to
make
sure
I
think
we
need
to
make
sure
that
there's
consistent
and
up-to-date
translations
across
for
the
desktop
and
relevant
information
for
the
best.
So
maybe
we
should
just
just
maintain
these
11
languages.
We
don't
have
any
we
can
just
I
will
discuss
more
was
the
contributors
who
are
interested
in
having
traditional
Chinese
and
see
how
it
goes
yeah
so
for
the
websites.
Then
there
are
fewer
languages
than
the
core
languages:
I,
don't
think
it's
available
and
Thai
well
in
Persian.
There
is
still
a
problem
right
because
we
cannot
there's
a
right.
B
A
B
A
B
A
So
so
that's
next
week
so
see,
then
it's
a
good
idea,
then
I
think
we
focus
first
and
foremost
on
translations.
Right
Christophe
mentioned
that
there
are
translations
that
I
have
not
been
reviewed,
are
still
available
at
the
with
each
new
release.
So
for
anyone
who
is
doing
any
translations,
please
try
to.
If
you
have
time
to
get
as
much
of
it,
translated
as
possible
focus
more
on
the
translations
and
then
the
reviews
yeah,
ideally,
of
course,
are
performed
by
a
separate
person
but
yeah.
A
A
B
B
A
A
Top
priority
and
yes,
the
priority-
we
have
this
already
bliss
but
we'll
just
maybe
against
make
sure,
add
I,
think
I've
added
Japanese.
So,
yes,
maybe
even
like
it
will
be
like
German
Russian,
Spanish,
Portuguese,
French,
Chinese,
Japanese
and
then
Persian
Thai
Vietnamese
are
a
little
bit
on
the
lower
priority,
because
I
don't
think
we
have.
We
still
have
big
issues
and
we
don't
have
any
I.
A
B
A
B
A
Because
so
for
you
can
see
it's
really
great,
he
really
has
done
a
fantastic
job.
It
looks
really
wonderful
and
but
there's
a
button
where
it's
like
stars
come
inside
and
then
depression
when
there's
it
leads
to
information
in
English.
So
we
need
to
figure
out
what
relevant
information
we
should
provide
to
people
to
translators
and,
ideally
to
be
up-to-date.
It
will
be
simple
to
understand
because
there's
so
many
new
concepts
and
we
need
to
make
sure
that
the
translators
themselves
understand
this
concept,
so
they
are
able
to
translate
them
well.
Yeah
and.
A
B
B
B
Yeah,
so
that
that
has
been
tricky
to
to
do
translations
for
I'm
in
the
process
of
talking
to
Chris
Chris
beams
is
one
of
the
original.
Well,
he
is
the
original
maintainer
of
the
documentation,
repository
and
we're
talking
about
ways
to.
We
just
started
talking
about
ways
to
make
documentation
a
little
bit
more
collaborative
right.
Now,
it's
it's
maintained
through
the
typical
pull
request,
workflow
that
we
have
for
everything
else
in
bisque
and.
B
It's
also
just
technically
hard
to
integrate
new
new
languages
because
of
the
the
way
the
tooling
is
for
the
the
framework
that
we
use
to
build
the
documentation
website,
but
but
basically,
what
I
propose
and
what
I'm
thinking
we'll
talk
more
about
in
the
coming
days
is
to
split
documentation
into
two
parts.
The
first
part
would
be
the
typically
conceptual
stuff
like
how
does
bisque.
How
is
this
structured?
What
are
the
principles
that
works
that
it
uses
to
work?
Well,
you
know
about
the
DAO:
how
does
the
dowel
work?
What
are
the
different
roles?
B
All
of
that
documentation
that
doesn't
really
relate
to
using
bisque,
but
it's
important
to
have
to
explain
what
bisque
is
and
how
it
works.
Have
that
in
the
documentation
repository
that
we
have
right
now
and
then
complement
that
with
the
second
part,
what
I'll
call
the
knowledge
base,
which
will
have
more
practical
how-to
guides
that
people
can
use
to
actually
understand
how
to
use
the
software
and
for
this
part
of
the
documentation,
what
I'm
thinking
is
this
could
be
more
collaborative,
perhaps
in
a
wiki
style.
You
know
anybody
can
contribute
to
it.
B
They
won't
be
directly
translating
something
they'll
be
making
a
guide
as
they
want
to
make
it
for
their
region
or
for
their
users.
So,
essentially,
what
I'm
saying
is:
there's
a
possibility
that
Doc's
as
we
have
it
right
now,
will
be
split
into
two
parts,
one
of
which
will
be
much
much
easier
to
translate.
B
Let's,
let's
hold
off
so
I,
just
so
Chris
and
I
just
started
talking
last
night,
and
then
this
is
part
of
the
support
initiative
that
we
just
kicked
off
last
week.
The
knowledge
base
is
a
support
thing
and
what
I'm
hoping
to
do
is
combine
the
documentation,
effort
and
the
support
effort
to
make
these
two
new
documentation
tools.
A
B
C
A
Regarding
how
to
I
think
how
to
I
think
is
more
urgent,
because
small
tactical,
it's
more
because
there
are
a
lot
of
changes,
that
we
need
to
make
sure
that
people
understand
people
on
a
consistent
mediator
and
arbitrator.
So
this
this
information
may
be.
What
we
can
do
is
that
we
can
link
like
we
can
have
kind
of
very
simple
how
to
do
think
that
the
the
chart
that
the
flow
chart
idea
would
be
a
good
idea
in
this
case
for
the
house
tour.
Oh
yeah,.
B
A
B
A
A
C
Question
maybe
also
after
the
call
we
can
in
part
of
the
summary,
have
a
list
of
the
channels
that
we
should
be
members
of,
so
that
we
don't
miss
anything
relating
to
the
translation
project.
So
it
seems
like
there
is
a
translation
channel,
but
these
other
channels
for
the
ticketing
and
and
the
test
yeah.
B
A
Maybe
that's
something
that
we
can
have
a
continuous
discussion
and
on
see
days
start
talking
about
that
I
think
maybe
some
translators
who
don't
feel
like
to
ask
to
have
some
input
into
how
to
specially
just
move
on
to
the
next
item
on
the
agenda.
It's
the
right.
We
have
in
the
translator,
documentation
I'll
go
to
talk
about
this
array.
A
Right
now
is
0.07
cents
per
words
for
translation
and
point
show
35
for
review,
but
I
think
that
for
more
complex
languages
like
Chinese
and
Japanese,
maybe
it
should
be
a
little
higher
and
that's
something
that
I
can
discuss
with
the
translators
themselves
for
those
languages,
but
for
the
other
languages
we
have
that
built
right.
Let's
you
know,
if
you
have
any
questions
still
concerned
and
then
put
the
this
website
and
the
transfer
of
information
procedure,
I
think
he
was
involved
so
I'm,
not
sure
Steve.
B
A
A
B
B
A
B
A
B
A
This
is
a
really
good
question.
I
think
it's
just
first
come
first
serve
now
is
just
more
very
like
informal
people
to
do
it,
but
I
think
that,
ideally,
it
would
be
great
if,
for
instance,
like
one
person
does
some
part
of
translation
and
another
person
reviews
that
person's
work.
So
that's
like
four
qualities
just
to
make
sure
that
and
of
course
it
would
be
wonderful
if
people
could
work
together.
A
It's
just
because
people
are
all
over
the
world,
maybe
a
little
hard
to
coordinate,
but
I
think
it
would
be
wonderful
to
have
a
more
like
a
coherent
team
of
translators.
And
then
maybe
you
can
share
ideas
on
what
other,
because
you
will
know
your
audience
better.
So
you
can
share
more
ideas
on
what
would
be
useful.
What
information
would
be
useful?
A
So
that's
a
particular
language,
so
yeah,
but
for
now
you
can
just
start
translating
Union
you
just
join
you're
just
doing
it
make
a
request
to
join
translation
and
your
first
translate
and
then
probably
what
will
happen
in
Siberia
or
some
other
more
experienced
translator
can
check
how
it
goes
and
I'm
sure
it
will
be
like
great.
But
then
we
don't.
First
we
give
translator
access
and
then
review
us
a
little
later.
If
you're
interested
and
yes,
you
have
kind
of
shown
yourself
to
be
reliable
and
really.
B
A
That's
a
great
idea.
Ideally
it
would
be
the
translators
most
experienced
translators
if
they're
interested
in
that,
of
course,
that
would
be
great
I
would
have
to
talk
to
like
all
of
them.
Some
teams
have
only
one
translator,
so
I
think
what
I
can
do
is
we
need
to
learn
to
figure
out
which
translators
are
kind
of
fasting
and
then
maybe
ask
them
reach
out
to
them.
It
depends
some
translators
are
active
at
some
point
and
then
the
other
point
I
think
I
should
know
this.
A
A
B
A
A
Okay,
so
number
one
will
discuss
the
core
languages
we'll
make
a
list.
So
the
next
truly
is:
please
try
to
do
as
much
translation
at
the
end
for
the
next
release
next
week
and
we
will
provide
more
information
for
what
information
to
translate
to
the
website
and
many
other
things
we'll
keep
you
posted.
Now
we
are
on
T
based
primarily,
but
that
will
pose
major
announcements
still.