we're going to talk about various stakeholders and
contributors to any localization uh Enterprise and we're going to talk about what they all want
and balancing that or harmonizing what people want so everybody gets what they they want to be
successful all right so briefly um I'm going to mention before I do instructions that there is a
uh chat and a Q&A uh section within uh the zoom interface please type your questions into the
Q&A interface we will take them at the end uh if you're like m
e it really works to write the
questions down right away as opposed to thinking of them later just because um if if if you're
like me like I said you'll think about that question and that's where your head will be at or
you'll forget the question later on that's me all right so some brief introductions we have as our
special guest uh Nat goodye uh and he is with RWS tratos he is one of those uh technical G whiz guys
who gets trotto Enterprise to work for all the customers so he is uh um bus
iness process analyst
is the the uh official title but I think of him as hey Nate can you make this work and he does it
so that's that's my title for you Nate um and uh uh me uh uh I'm not the star here but uh I'm the
CEO founder of lingo port and then Olivier runs our product development uh if you've attended our
webinars you've seen plenty of Olivier in the past uh but he's going to show some coordinated stuff
between our localizer software and Nat's uh uh work with trotto Enterprise But
ultimately we're
going to be talking about our stakeholders uh we'll go over developers management localization
team and translation partners because they're all uh part of having a successful release or series
of releases for Global products so first of all let's think of the developers um they are for
localization team members often difficult to please um it's very frequent to see friction
between the developer teams and localization teams and it really doesn't have to be that way
um the
uh uh fact is is if a developer understands that localization gets a broader audience for
the work that he or she does they usually get kind of excited about it actually it's just the
the drudgery around localization that is a a distraction or the disconnectedness of it that
I find when I talk to developers is something to overcome so most developers only have a basic
familiarity with localization they often speak one or maybe two languages and it's not like their
thing um they uh just bec
ause somebody uh for instance you sometimes have developers who are
born outside of whatever home country is and they speak multiple languages but they don't really
think about it like a linguist does um but uh the other thing is that in increasingly we see
developers following a design uh that they may not have made so when it turns into the UI uh and
they're coding it up they're looking at something uh done in figma and the like so increasingly
localization and awareness needs to push eve
n further Upstream into development I don't know
that we'll have a chance to go into it but uh you definitely want to link localization to say
your figma development um and the like um but for a developer some aspect of localization should
be integrated with the work that they do and that takes the form of various Sprints if they're using
anything even agile like which most people are and those deliverables for localization they should
be visible to the developer um it's important to rememb
er that developers are used to showing their
work in a pull request or even in a commit uh when they complete a Sprint they often have to make
a video of their work not in every organization but in a lot of them they make a video of their
work showing like here's the function here's how it works I'm proving that it works uh not so for
localization if it's happening in a separate kind of thing um they want automation they're really
used to automating uh remember if they if you're still you k
now using using uh uh spreadsheets
and having developers manually send files it's not great um there's really no reason for that
in this day and age with all of the tools and automation that are available and finally and
I can't underestimate this uh development teams don't want you to break the code if let's
say you're automating and you're automating a mistake you are speeding up a problem um and
uh scaling that problem across so so you've got to have checks and balances in that that are
part of your automation otherwise you could be creating a problem um don't break the code
is just a really important thing because that brings everybody to a stop until they can fix it
now management um you know there's an emphasis on Roi and and I I just want to say that um a lot
of thought will go into say using this blue font or something like that and it should right uh
but you rarely see people have to justify that in terms of dollars so it's a it's a bone to
pick that I have that loc
alization still has to justify itself it uh with all kinds of uh
dollars and cents be that as it may you need to be able to uh understand what your costs are
um and uh then run it against your success in various markets U repeatable success so you need
a system that works across your teams whether you have one product with a bunch of developers or
thousands of products uh we had we definitely have clients in in both of those departments and
uh your it department will be all over security um
are you exposing your intellectual Pro uh
properties to potential problems so essentially your source code uh to potential problems and that
uh often comes into play uh in pretty much every uh technologically oriented uh organization um
you must uh uh for the localization team you're straddling in between all these people um I want
to mention that I've never seen a localization team that wasn't underst staffed um it's often
uh uh you're outnumbered by like 100 to one in terms of other othe
r people uh uh um speaking
about uh in this presentation it's it's a push to get localization awareness and response
within your organization um and it's hard to predict localization Cadence from software
teams in particular that I'm speaking with you you know frequent I'll hear that localization
teams uh I'll put in a plug before our technology um you're often just sort of told hey we're done
this is ready for localization instead of having a window into what's coming and the ITN quality o
f
what's coming as well so um it's not just what's in the TMS that you have to be aware of it's
what's actually in the software repositories where the development teams are doing their work
and again many manual processes often uh you see that particularly uh uh different teams will use
different file formats and those all need to be massaged and all that and all of that can be uh
automated but it takes a little upfront work to to get that done and lastly I don't want to forget
the transla
tors um uh LSPs and then translators down the line uh always pressed on cost timing
being efficient um there's of course a lot of uh uh push on AI these days but uh as localization
experts we know that AI is been around for us for a long time uh nmt certainly is a form of AI
it's even being finally acknowledged um so uh uh but now more than ever people are saying hey
we don't want to pay for this uh which as the guardian of localization quality the localization
team really has to be uh uh u
h take care of that but anyway LSPs translators uh small changes
shouldn't need engineering time uh I see that complaint among uh LSPs all the time if they uh
get a small continuous localization project let's say it's a hundred words if they have to spend
QA time on it um that's bad because that impacts their speed and obviously impacts the cost of
of that um uh little episode and translators finally they want to use a workbench they know
and like um they don't necessarily want it to fit in
to whatever they're being shoved into so
with that um it's time to do a little showand tell uh in terms of Technology I'm going to have
Olivier go first he'll he'll show what what's in there how you can see into repositories and then
I'll let him take it from there uh and then Nat is going to show the second part of that which
is let's focus on the actual translation uh uh event and managing that so with that Olivier
um I'll unshare and let you share your screen all right thank you Adam I s
hould see my screen
in a short while here let me know if you do see it yes I see it looks good right so on the left
hand side we're seeing what developers uh where they push their work and their work typically is
Java files or C or whatever programming languages and also files that need to be translated
they are called resource F in this simple example they are under accounts directory they
are already translated partially and so what we're going to do is with command center we're
going to
unboard this and get the process going to do that we need to know what is the URL it's
up there it's highlighted up there what are the local codes in repository so dnfr for English
German and French and then what is the type of file that's pretty much it once to know
that you're going to create a project in the command center and that project is going to be
uh using localizer Implement Center to do that you see that currently we have a few projects
some of them have developer erors some of
them are clean some of them are late for translation
each one corresponds to a repository you see the translation uh status right now is 35% for this
one it's 99% for this one 100% for that one you can run different processes we're just going to
add a new project here for this one that I was just talking about this mention Olivia can you
just mention what Command Center is because it's not a a lingal port product it's it's something
else Command Center is the user interface that uh Aggrega
tes two different products at inle Port
one is globalizer to detect issues in the code and one is localizer to enable automation of
translation from the repository or other data sources maybe databases for example or some other
things over to a TMS like RWS TR centerprise so those are the steps here that we're going to
go through one two three and then those it's going to go really quickly so first is what
are your credentials to go there then what is the repository you've seen that one ove
r
there the branch is translation you see that there translation at that point where cloning
the repository and we're giving it a default name the default name I'm going to change that to
something else like a webinar for example for for today and I want to keep translation I may add a
tag like uh like demo for example and maybe RWS and I'm going to add a localizer configuration
to this I'm going to use trus Enterprise as the translation management system so so you notice
that it was en no
tus I'm going to change that for the repository local I'm going to add two locals
to start with I'm going to add French and French for FRS there are a number of locals those codes
here come from tros Enterprise so we we're using the TR Enterprise code on this end and we're
using the repository code on that the left side I'm going to add German and German here was the
German from Germany and it's uh just de so what you are seeing here is what we're doing with this
here German English French
that's it for the local for now we could add sud loal we're going to do
that later on at that point it's a Json file that we saw that and uh the way to do that is just to
say it's a directory name followed by the files here that's it after that you can just click next
if you want there are more uh things that you may want to check but here before finalizing things
you may want to say okay look house translation is going to be translated into look house D
translation dojon or those locals an
d that's what I want so now that it's verified I'm going to
add methal here to um the people who have access to this repository maybe a couple of people create
project and that's it it was that simple so right now the project is created it was called webinar
and the analysis has already been run what you notice is that there's a red dot here the Red
Dot means that there is there are Developer errors in the repository I'm going to close this
guy here I'm just going to expand this to be um to
be better for viewers and uh I'm 75% complete
the analysis has around 28 seconds ago but I want to see this what is going on here to do that I
see that Source localities there are two target locals 34 words 15 Source Keys meaning strings
one source file it's going to tr us Enterprise and there is one developer error it's in red it
really calls for your attention here and so I'm going to click here and it's going to tell me
where do I have an error I have an error that's a duplicate key it'
s in translation. jsonline
13 I can have more information by clicking here but what I just want to do is click that go to
line in source code and it's going to tell me well uh on this line right here drive you have
a duplicate key so let's highlight this I see that I have two drive I have starting to drive and
Driver obviously in the application when you use the reference drive to show in the your UI you
don't want to be wondering if it's going to be this one or that one right so there is a
n error
from the developer there needs to be unique keys in each one of the resource files so with this
purpose here we're going to edit this file and change uh drive to uh driveing for example so
remove the duplicate key and that would be done by a developer IM me the change there is and
now we we're going to Simply um do that again so let's see if that disappears and I'm going to
go back to localizer here there are zero errors it's gone so it's that easy to detect errors
and if errors uh
have been fixed you see that it's uh correctly identified here in terms of uh
your total completion report meaning what is the status of your translation you can see for each
local how many words have been translated how many words need to be translated now you may want a bit
more visibility in terms of what are those unsent words because you're about to send something and
maybe you want to see what is about to be sent so to do that you click on strings which is really
showing to be sent b
y default but you can show more things so what needs to be sent are those
starting to drive which was the duplicate key by the way before that driver aggressive Drive
harsh breaking harsh corner and inh maybe uh starting to drive is not the right grammar that
you want maybe you want something else so may want somebody to review that maybe driver yeah
you're okay with that aggressive Drive L is not that great either what happens is that you're
marking things for either future reviews or to s
ay yeah I reviewed those and I'm okay with that
I already click here it will tell me that CC admin which is who I am logged in here has reviewed that
on 328 at 1019 Which is my sign in Colorado here and uh it's saying y I'm all good here it's it's
been reviewed so you can tell who has reviewed this particular string here if somebody comes in
later on you can say I just want to see uh things that need to be reviewed I'm going to click
here and maybe you have 100,000 strings it's just going t
o show those two strings those need
to be reviewed whomever again you can go to the chice code if you a developer you can have more
information here but if you want to review it at that point just click here and that one maybe
uh is fine or maybe you want the developer and you can give that URL to the developer or ask
the developer to go here and modify that hello to welcome or something at that point if I want
to see the scours that are reviewed this one is reviewed there they are so very
briefly here
what we've done is in a very short time we've oned a new project that was partially translit
from prior um configurations prior tooling with identify what needs to be sent for translation
we can see what is about to be sent or what has been fully translated previously or what is
outstanding in Translation so you can really decide what you want to see here uh and depending
on your selection you will see different part of the strings that have been uh that have been
selected I f
ully translated those have been fully translated if I go back and I want to say let's
me add more locals right now I just have German and French but maybe I want more loal I'm just
going to click edit I'm going to click localizer settings loal settings and at that point I can
either choose from another project that has AAL that I want maybe this one here for example at
that point I just added Alan and polish from uh this one or I can add by an by hand new one like
Norwegian for example so I
want to add Norwegian here I'm just going to go here um book mode we go
and I want MV for book mode I'm going to save that and so at that point I have a new configuration
I can just run this it's going to do that in one second it's done already by the way and uh when
I look at localizer again it's going to tell me that my percent Compu is different and I'm not
at all translit in those new accounts that I just created if I want to send them to be translated
to RWS the trus Enterprise config
uration I'm I'm just going to click this if I want to check if
anything was translated I can check that here typically it's going to be all automated pulling
back from TR centeres but if I want to check I can check here or a few more things but that's the
basic overview for what you can do really briefly uh in terms of onboarding detecting errors can
also add if you want pseudo loal so for example here if I wanted to add a pseudo loal I would
just say Pudo loal save and when I run this not
only is it going to analyze the project but then
run sud Lookout and by the way it's already done and if I go back here I now have a Pudo loal that
has been created for EO and you're going to see the strings here that are in there there are PUD
localized that's it for me I'm going to pass the hand over to nathanial for AR of gas I'm just
going to interject that that pseudo local what that does is it lets the developer see the impact
of localization right away um they they don't have to wait
for the translation project to come back
um you could do that with machine translation as well uh pseudo localization lets you make sure the
character set is supported and you have expansion that that uh might be needed in uh various
Target languages Natt you your screen thank you Adam thank you again for that introduction
and and the Pud really the key I think to software or smooth software localization
is really falling in step with their Sprint Cycles you're breaking up uh uh whoops we
lost you oh you're back I'm back sorry about that
no worries you try a sharing screen again yeah there we go you're good yeah you screen
so sorry about that so yeah so as I was saying like you know the position is really following
in step with their with their Sprint Cycles uh and it might be happening again my zoom is
quitting you're back you're there you're just okayyy all right so let's take a look at a
quick demo job I want to show you you can sort of extend the visibility uh and um the
various
processes that we can effectively offer through a not I'm going to suggest you turn off your video that you know maybe a little
less bandwidth might might help uh we lost him totally Olivier is it
just me or you you lost him also seeing Nathaniel or actually I'm seeing it Frozen
and the screen is still showing for me okay you um do you want to
go over questions if there are questions before uh in terms of what we should I'm sorry folks every time I try and share
I seem to be um ye
ah disconnecting or Zoom seems to be dying on me I may have to
talk this through uh instead n sorry uh Adam just uh offered that you just
turn off your camera maybe it will be better and try to share your screen
still because this is important part okay looking good you're able to see it I'm not
getting an exception so that's great so yeah so for the third time falling in in step
with uh your Sprint Cycles so it's really it's really important to have translation be
a part of of the develop
ment process so that you catch problems early and you're not sort of
surprised at the tail end of your development uh um causing delays to your product releases
uh so on and so forth so taking advantage of the translation process and things like
pseudo localization early on in your Sprint Cycles so that you sort of see if you need to
make adjustments within your application uh to accommodate a translation uh is really really
important so so by the end uh you can deliver on time so once the
projects are delivered to
tratos Enterprise uh we can track and handle any variety of of file types we can even create
custom file types for for you specifically and the reason to configure these file types is really
so that we can handle things like maybe inline variables or things like this you know things
that might break the code if they were altered by a linguist and we can protect them through
our system additionally we can add any kind of um again pseudo localization just like lingo
Port uh we can uh offer a variety of different Services whether it be a pure human translation
or or Mt assisted translation uh we can configure that within the system itself but taking a look
at one of these files uh let's take look excuse me at one of these files we can open it up uh in
our online editor that can be used by linguists uh and also reviewers so that if you have internal
smmes that maybe speak the local dialect uh they may want to do a final review and be a part
of the trans
lation process we can certainly include them uh the online editor is really
bent uh for ease of use uh while providing a full functional uh uh transl interface um
for the users the users can make use of V of various uh linguistic assets throughout
the entire of the process so we can set up things like terminology translation memories
uh meaning uh previously approved translations uh and and even machine translation to enhance
the the offering and uh speed up the translation process uh in te
rms of review like I said
we can include external reviewers as part of that process who can leave comments uh uh
on the translations uh in case anything needs to be corrected maybe shortened or lengthened
depending on the the actual use case um apart from that tros Enterprise also comes with a no
data connector that allows you to actually track at a very granular level and build dashboards
live dashboards through business intelligence tools so you can track the progress of your
translation
s uh and you know things like total spend so things that cost will be visible through
this uh through these OD data feeds uh and you can check on the on-time delivery uh total spend
how much leverage you're achieving across all the languages that you're asking for but a full
featured set of of data reporting that allows you to really understand uh your spend within
the translation space we can also accommodate uh other LSPs we can onboard other vendors
uh to be a part of that process uh we
can also uh if um uh our language Weaver neural Mt
or uh neural machine translation uh is it your preferred technology although we we strongly
suggest that you try it out uh we we also can accommodate other uh engines as well so Microsoft
engines Google engines uh Chachi PT and the rest uh We've also introduced a new feature
uh within tratos recently that allows you to actually have a direct communication line with
the production team so that the production teams if they have any like conte
xtual questions uh
or clarification questions can do so directly through the portal itself and sort of ease the
communication between the requesters uh and and the actual production teams themselves obviously
we have full versioning uh and we have a full task history so that uh it's easy to audit if there
are any quality concerns with the translation of your products we can identify where that
came into the process very easily uh and as I as I mentioned just just prior uh we have full
file
versioning throughout the entire of the process so it's really quick to identify where
those errant translations made their way into the process so really a full featured translation
management system here that can really be expanded depending on your on your requirements we can
have we can tailor the workflows to your specific needs if you have multiple rounds of review we
can do that but aligning with Sprint Cycles is something that we do very well with a system like
chadow Enterprise uh
and really can be tell your specifications with that I'll hand
it back to Adam unless there are any outright questions okay uh
thank you I'm gonna hold a second share okay thank you okay um so uh let me
get to the right screen sorry and by the way if people have questions this is a good time to think
of them and and write them down uh we also by the way have this uh uh this streaming on LinkedIn
live uh as well all right so it in in summary we really have quite a bit of balance available f
or
various teams we have uh the de developers getting everything they want uh they don't have to manage
files and uh if there's something that's broken about the localization that's being checked
uh and uh you know I'm missing curly bracket we saw a string ID uh that was duplicated which
probably wouldn't break the code but it would not necessarily make the right word show up uh
in in the right uh uh place um and um that's easily found and then uh directed as far as the
corrections so it i
sn't like uh unknown what the error is or or where to find the error or anything
like that is very precise uh the localization team can really scale um over to many teams remember
to set up set up this continuous localization they don't really need much from anybody um they
just need the Source path and declare what local locals they want and a couple of other settings
that they can all handle uh without um having to wait from some for somebody in it or wait for
somebody from the developmen
t department uh to say hey look here all of that detection happens
automatically uh once you know the the path for the repositories and um the files are grabbed and
everything everything so that's pretty cool um and you saw Olivier just quickly set up a project and
of course pseudo localization can be added so the developers can see the impact um you could do that
with machine translation also returning right away which then would get checked um uh and uh uh then
we have the management team
being able to report it accurately what what speed is uh what what
costs are and and the like and the translator team having having a familiar uh uh project a work
environment that they can work with um pretty much every translator knows what uh tros is uh uh
and that that's just very cool and uh you've got the backing of RWS behind it so so the two
environments really just almost become one uh uh uh within all the teams all right and with that
we're uh ready to take questions um uh I have
a couple of questions that have come in through uh
LinkedIn uh one is that um okay this is a good one I have many projects do I have to review all
strings manually um you saw Olivier did a little bit of a string review um that's that's something
that's elective um and it's funny before we develop that technology we we talked to a number
of customers and some were like oh this is awesome you know I I really want to be able to review
strings before they go out and you know the the need for t
hat is fairly obvious like why would you
want to spend time translating something that that uh isn't precise or isn't correct uh in the first
place in its source um now many times in some organizations the developers are not necessarily
adding strings on their own that that's very well established in design and other times it's
not so I would say that's a feature it's not necessarily for everybody and so it's elective
you don't have to use it um we had you know kind of one team that we talk
ed to and they were like
well I manage 70 products and it's changing all the time I couldn't possibly review all great
you don't have to but other teams were really pretty excited about that all right uh other
questions through the Zoom team that are coming up okay anything in chat okay uh I have one more question that
came out um can you provide context to the translators um I'm going to guess that what you
mean by that is a a visual context um and the answer to that is yes uh we didn't de
monstrate
that here um but uh we have a system by which uh context is automatically collected uh up
front and can be passed as a comment into the TMS um the uh that that's that's kind of
collected automat automatically the developer doesn't really have to do much when they run
their unit tests that that it's it's gathered automatically um the second aspect of that is
there's some configuration involved in that but once it's set up it it it works pretty
nicely all right uh other questions I
'm kind of okay Kate you have anything else coming in
um nope I don't okay with that I'm going to let it go if anybody has a question let me know
uh recordings will be sent out automatically there's nothing you have to do uh that'll
come in the next few days or possibly early next week um and uh thank you for attending
and sticking around through all of it Olivier Nat thank you for your support and providing
some pretty cool demos all right take care and we'll see you next month we're proba
bly
probably going to talk about accessibility I have to get that all together again uh
but uh the next webinar thank you bye-bye
Comments