UDSKRIFT 🔗
WEBVTT
00:00:02.619 --> 00:00:05.519
Hi everybody. Welcome to the Language Worker.
00:00:05.700 --> 00:00:08.580
Let's talk about terminology. Surprise, surprise,
00:00:08.720 --> 00:00:11.859
right? So this series is obviously dedicated
00:00:11.859 --> 00:00:14.300
to terminology because I thought it was time
00:00:14.300 --> 00:00:18.460
for me to talk about the real love of my life.
00:00:18.600 --> 00:00:21.280
You can say that if you can say that. Definitely
00:00:21.280 --> 00:00:24.579
the first love of my life. The whole reason why
00:00:24.579 --> 00:00:28.059
I entered into the language adventure had to
00:00:28.059 --> 00:00:30.539
do with terminology, believe it or not, right?
00:00:30.760 --> 00:00:33.079
So this is the real deal. This is what I love
00:00:33.079 --> 00:00:35.119
the most. This is something that's always been
00:00:35.119 --> 00:00:37.799
present in my life, and it's something that I
00:00:37.799 --> 00:00:40.859
love talking about. So it's only fair to myself
00:00:40.859 --> 00:00:43.320
that I should, and everybody else, that I should
00:00:43.320 --> 00:00:46.780
do a bit of a series about terminology. So today
00:00:46.780 --> 00:00:49.259
we're going to talk about a thing that people
00:00:49.259 --> 00:00:52.719
ask me a lot about. So it's governance, right?
00:00:53.079 --> 00:00:58.189
Terminology. I just find this word so far -fetched,
00:00:58.250 --> 00:01:02.070
right? Because it can be applied to one glossary
00:01:02.070 --> 00:01:06.590
or to a whole corporation of the size of Apple.
00:01:06.810 --> 00:01:10.290
right? Or Microsoft, right? So I did work for
00:01:10.290 --> 00:01:12.629
Microsoft as what they called at the time a language
00:01:12.629 --> 00:01:15.890
moderator, but it really meant translation or
00:01:15.890 --> 00:01:18.769
terminology manager because that's what I did.
00:01:18.829 --> 00:01:21.989
I was like the person in the middle trying to
00:01:21.989 --> 00:01:27.290
get everybody's consensus and ideas and suggestions
00:01:27.290 --> 00:01:32.329
and validating and working my way out of all
00:01:32.329 --> 00:01:35.530
the trouble that one can get into when having
00:01:35.530 --> 00:01:38.230
terminology. discussions, right? So that's what
00:01:38.230 --> 00:01:42.329
I did. So that's governance, I suppose, when
00:01:42.329 --> 00:01:44.769
it's a huge cooperation and all of that. But
00:01:44.769 --> 00:01:48.049
it's also governance when you're trying to manage
00:01:48.049 --> 00:01:51.090
your glossary that you did for your own thing,
00:01:51.290 --> 00:01:53.489
if you're a freelancer, for example, right? So
00:01:53.489 --> 00:01:56.549
but the word is huge. And to be honest, I'd rather
00:01:56.549 --> 00:02:00.939
use the word ownership, right? I'm really a fan
00:02:00.939 --> 00:02:03.579
of this word compared to governance just because
00:02:03.579 --> 00:02:05.859
I think it makes it more real, right? I think
00:02:05.859 --> 00:02:09.379
governance is such an abstract concept or it's
00:02:09.379 --> 00:02:14.419
more complicated to grasp. So on saying that,
00:02:15.500 --> 00:02:21.560
most of all workflows or plans or terminology
00:02:22.769 --> 00:02:26.650
projects start with a glossary, right? So this
00:02:26.650 --> 00:02:29.349
is also a concept that can tell you all sorts
00:02:29.349 --> 00:02:31.750
of things or nothing at all. Some people consider
00:02:31.750 --> 00:02:36.830
that just a list of possible keywords that's
00:02:36.830 --> 00:02:39.129
present in a text is a glossary. And the truth
00:02:39.129 --> 00:02:43.729
is that it is a glossary, right? Or if you find
00:02:43.729 --> 00:02:48.300
a list of, a bilingual list of terms, one in
00:02:48.300 --> 00:02:50.139
one language, the other one in the target language,
00:02:50.240 --> 00:02:52.560
that's a glossary. Yes, that's true. That's a
00:02:52.560 --> 00:02:55.300
glossary too, right? So basically the glossary
00:02:55.300 --> 00:03:00.000
itself could be just a list of words that have
00:03:00.000 --> 00:03:04.159
some logic behind it. Usually it's part of a
00:03:04.159 --> 00:03:09.530
text or a whole... work of art or, you know,
00:03:10.150 --> 00:03:13.490
a document, a manual, it can be anything, or
00:03:13.490 --> 00:03:17.210
it can be really something with a lot of information
00:03:17.210 --> 00:03:21.270
that can serve multiple, multiple purposes. I'm
00:03:21.270 --> 00:03:25.310
obviously a fan of that. I love glossaries that
00:03:25.310 --> 00:03:28.150
have a lot of information, are very rich, because
00:03:28.150 --> 00:03:31.189
then you can do with them whatever you need to
00:03:31.189 --> 00:03:34.330
do with them, and you don't ever need to start
00:03:34.430 --> 00:03:38.870
from scratch. So if all that you have is a glossary,
00:03:39.050 --> 00:03:43.490
great, you've started, right? So this is a great
00:03:43.490 --> 00:03:45.909
starting point. It's the starting point, even
00:03:45.909 --> 00:03:48.710
if then you take it further in whatever direction,
00:03:48.849 --> 00:03:51.349
right? Unless you already have, your corporation
00:03:51.349 --> 00:03:56.229
already has one of those big TMSs, what we call
00:03:56.229 --> 00:03:59.930
terminology management systems, then you usually
00:03:59.930 --> 00:04:03.699
have a glossary, right? But if you have multiple
00:04:03.699 --> 00:04:05.860
departments, if you have multiple projects, if
00:04:05.860 --> 00:04:09.460
you have multiple clients, then it's pretty complicated
00:04:09.460 --> 00:04:12.939
to work with one glossary only. So what's the
00:04:12.939 --> 00:04:15.759
story with this glossary? What's in there, right?
00:04:15.840 --> 00:04:18.100
What kind of content do you have there? Is it
00:04:18.100 --> 00:04:20.980
just that? One of the things that I get a lot
00:04:20.980 --> 00:04:23.500
is when people ask me to look at their glossaries,
00:04:23.800 --> 00:04:28.759
they will have a list of the supposed approved
Load full transcript
00:04:28.759 --> 00:04:30.980
terms that they already decided are going to
00:04:30.980 --> 00:04:34.699
be, you know, the ones that are going to go everywhere,
00:04:34.819 --> 00:04:37.519
travel with your product or service, your texts
00:04:37.519 --> 00:04:41.139
in general, your communication. And then there's
00:04:41.139 --> 00:04:45.240
usually a list of maybes. Is this maybe the right
00:04:45.240 --> 00:04:47.860
term? Is this appropriate? Is this what we used
00:04:47.860 --> 00:04:51.439
last time? And then there's a list of whatever
00:04:51.439 --> 00:04:55.259
else right so is this the right translation did
00:04:55.259 --> 00:04:58.279
we use this before is this possible is this even
00:04:58.279 --> 00:05:01.939
correct so it's it's very interesting right so
00:05:01.939 --> 00:05:04.680
I'd say if that's the case and usually is if
00:05:04.680 --> 00:05:07.740
there's nobody who is responsible like the owner
00:05:08.089 --> 00:05:11.329
of the glossary, let's call it that, then it's
00:05:11.329 --> 00:05:16.209
going to be impossible to actually keep a clean
00:05:16.209 --> 00:05:19.209
and very functional glossary for a long time,
00:05:19.310 --> 00:05:22.269
right? So this is why I say that ownership is
00:05:22.269 --> 00:05:24.730
one of those concepts that needs to be present
00:05:24.730 --> 00:05:28.149
if you're going to have terminology management
00:05:28.149 --> 00:05:32.329
or terminology workflow, or both ideally, right?
00:05:33.370 --> 00:05:36.449
So what should happen? What should happen is
00:05:36.449 --> 00:05:39.769
that if you have that one or multiple documents
00:05:39.769 --> 00:05:43.709
or Excel sheets or whatever you use, that works
00:05:43.709 --> 00:05:47.050
okay, I suppose, as a starting point, then what
00:05:47.050 --> 00:05:50.769
you have to do is actually to consolidate, to
00:05:50.769 --> 00:05:56.769
clean and to create some sort of way of harmonizing
00:05:56.769 --> 00:05:59.569
all the content that you already have. there.
00:05:59.970 --> 00:06:02.790
So someone needs to be responsible for this cleanup,
00:06:02.930 --> 00:06:04.529
right? If you're a freelancer, if you work by
00:06:04.529 --> 00:06:08.209
yourself, you will know the history on how this
00:06:08.209 --> 00:06:10.230
glossary is created, if you created yourself,
00:06:10.230 --> 00:06:12.930
or if you've had a relationship for a long time
00:06:12.930 --> 00:06:16.449
with a certain client, or you've had contact
00:06:16.449 --> 00:06:19.129
with their content. content for a long time,
00:06:19.290 --> 00:06:22.290
you will know this like a bit of history. But
00:06:22.290 --> 00:06:24.629
if this is the first time that you're looking
00:06:24.629 --> 00:06:27.529
at this thing, you probably need assistance,
00:06:27.730 --> 00:06:30.790
you need help. This is why I also say that one
00:06:30.790 --> 00:06:34.310
of the things that we should do is to document
00:06:34.310 --> 00:06:38.189
our rationale, the way we come up with the idea
00:06:38.189 --> 00:06:42.569
of including each one of the entries in a glossary.
00:06:42.689 --> 00:06:45.850
And I'll say entries right now, because some
00:06:45.850 --> 00:06:50.370
of the entries in glossary are not necessarily
00:06:50.370 --> 00:06:55.269
terminology, right? They are other linguistic
00:06:55.269 --> 00:06:58.709
or not. Sometimes even images can be in a glossary,
00:06:58.889 --> 00:07:01.930
right? There are other elements that convey meaning,
00:07:02.170 --> 00:07:05.350
but they're not necessarily terms in the classic
00:07:05.470 --> 00:07:08.810
uh sense which means that they would be the jargon
00:07:08.810 --> 00:07:14.029
the specific specialized words used for a certain
00:07:14.029 --> 00:07:21.470
science or um object you know something that
00:07:21.470 --> 00:07:27.370
is strictly related to that And it's not other
00:07:27.370 --> 00:07:30.209
things that we also need to find in a glossary
00:07:30.209 --> 00:07:33.649
in the case of people who work in the language
00:07:33.649 --> 00:07:38.029
services area, right? We usually need other elements.
00:07:38.310 --> 00:07:43.129
There are not only the technical terms used in
00:07:43.129 --> 00:07:46.730
that science or domain or vertical, right? So
00:07:46.730 --> 00:07:48.550
that's the first thing we need to do. We need
00:07:48.550 --> 00:07:52.389
to consolidate whatever information we have and
00:07:52.389 --> 00:07:54.949
actually clean out because then That's one of
00:07:54.949 --> 00:07:58.509
the other things that I see. I see super extensive
00:07:58.509 --> 00:08:02.670
glossaries where some of the words actually are
00:08:02.670 --> 00:08:05.889
pretty common sense, right? So they have pretty
00:08:05.889 --> 00:08:09.170
well -established equivalence, if we're talking
00:08:09.170 --> 00:08:11.810
about a more technical thing, or a translation,
00:08:12.009 --> 00:08:14.870
right? So these are well -established and maybe
00:08:14.870 --> 00:08:18.370
these glossaries came from a time where this
00:08:18.370 --> 00:08:22.050
area was not as mainstream and these were still
00:08:22.050 --> 00:08:25.310
a bit opaque. let's say. So this is the first
00:08:25.310 --> 00:08:27.709
thing that this owner needs to do because there
00:08:27.709 --> 00:08:30.490
has to be some documentation, some history to
00:08:30.490 --> 00:08:33.429
actually understand what is going on there and
00:08:33.429 --> 00:08:37.990
how these entries came about, how they came to
00:08:37.990 --> 00:08:40.889
be part of this glossary. So this is the very
00:08:40.889 --> 00:08:43.549
first step to find out who the person is who
00:08:43.549 --> 00:08:47.210
can be responsible to actually harmonize whatever
00:08:47.210 --> 00:08:50.860
information is there. Then unless you work solo
00:08:50.860 --> 00:08:52.960
and you created the glossaries because you wanted
00:08:52.960 --> 00:08:55.519
to, to make your work easier. If you're part
00:08:55.519
--> 00:08:57.580
of a team and if this glossary is going to be
00:08:57.580 --> 00:09:00.259
used by other people, we cannot forget that this
00:09:00.259 --> 00:09:03.059
ownership needs to be shared. And that's for
00:09:03.059 --> 00:09:05.220
multiple, multiple reasons. One of the reasons
00:09:05.220 --> 00:09:09.120
is that that person can just go away and then
00:09:09.120 --> 00:09:11.860
you're as lost as you were before, right? So
00:09:11.860 --> 00:09:15.470
ideally this person is responsible but there
00:09:15.470 --> 00:09:18.669
are other let's call them stakeholders right
00:09:18.669 --> 00:09:21.210
other people who have to be responsible for this
00:09:21.210 --> 00:09:24.230
glossary because if you have more than that more
00:09:24.230 --> 00:09:26.889
than a freelance practice you cannot sustain
00:09:26.889 --> 00:09:30.450
a glossary by yourself you can manage a group
00:09:30.450 --> 00:09:33.789
of people you can be the go -to person to make
00:09:33.789 --> 00:09:36.529
sure that this has one structure and goes into
00:09:36.529 --> 00:09:39.529
one direction but you cannot expect one person
00:09:39.529 --> 00:09:43.240
to be responsible for the terminology for the
00:09:43.240 --> 00:09:49.019
workflow, for the management of all words, expressions.
00:09:49.789 --> 00:09:53.330
brands, all sorts of things that need to be in
00:09:53.330 --> 00:09:56.070
this glossary. So we have to remember that if
00:09:56.070 --> 00:09:58.669
it's one person or if it's one team, they have
00:09:58.669 --> 00:10:01.049
to collaborate with everybody else. They have
00:10:01.049 --> 00:10:04.350
to have the ability, the visibility and the knowledge
00:10:04.350 --> 00:10:07.009
to go to the right people for the right task.
00:10:07.629 --> 00:10:12.230
So a glossary, ideally, is not a one man or woman
00:10:12.230 --> 00:10:14.950
job. So it's something that needs to be done
00:10:14.950 --> 00:10:19.539
by a group of people who are not only using the
00:10:19.539 --> 00:10:22.259
knowledge that they have that it's super valuable,
00:10:22.519 --> 00:10:26.639
but also getting this ownership idea. You cannot
00:10:26.639 --> 00:10:29.919
implement terminology or whatever it is in your
00:10:29.919 --> 00:10:32.740
company without making it part of a culture.
00:10:32.960 --> 00:10:36.500
People have to somehow understand why this glossary
00:10:36.500 --> 00:10:40.159
exists, the benefits, and their role in it. So
00:10:40.159 --> 00:10:44.029
they have to own it too. This is why I call it
00:10:44.029 --> 00:10:46.870
ownership a lot more than governance because
00:10:46.870 --> 00:10:50.230
governance is in another stage, right? I think
00:10:50.230 --> 00:10:53.669
that if we get to the ownership part, then it's
00:10:53.669 --> 00:10:55.970
much easier to get to the governance part, right?
00:10:56.210 --> 00:10:58.990
Let's go with the ownership and with the conscience
00:10:58.990 --> 00:11:02.750
that it's a team effort. A lot of people have
00:11:02.750 --> 00:11:06.570
to be involved or else it will not work. It could
00:11:06.570 --> 00:11:10.679
actually... harm the whole workflow if things
00:11:10.679 --> 00:11:14.100
are decided one way, one day, another way, another
00:11:14.100 --> 00:11:17.159
day, right? So the idea is to make this into
00:11:17.159 --> 00:11:20.320
a team effort that will benefit the whole team,
00:11:20.740 --> 00:11:25.259
the whole company, the brand and brand visibility.
00:11:25.700 --> 00:11:28.399
So I'll see you next week with a little bit more
00:11:28.399 --> 00:11:31.759
about my favorite topic and that's. terminology.
00:11:31.919 --> 00:11:34.860
Let me know if you're enjoying the series. Leave
00:11:34.860 --> 00:11:38.779
me your comments, your questions. I'll be happy
00:11:38.779 --> 00:11:42.399
to talk about this always, right? Thank you so
00:11:42.399 --> 00:11:43.200
much. See you next week.