[MUSIC]
>> All right. Welcome everyone to this online workshop.
Today, we'll be talking about how to translate
content for learn.wordpress.org.
We have three people on the call here.
How many people have used learn.wordpress.org before?
You can give me a thumbs up or maybe type in the Zoom chat.
Have you ever used learn.wordpress.org before?
Did I see? Yes?
No.
No? Martin? No?
No.
I mean, that's totally fine.
And Louisa, you only saw the website.
All right.
So I'm going to start by just giving a brief introduction of learn.wordpress.org.
And then we'll dive into translation after that.
that.
So learn.wordpress.org.
I'll drop the link in the Zoom chat as well.
This is the WordPress Project's official site
for learning about WordPress.
So the WordPress also has a lot of documentation,
which is where you can read about features
and read about different things.
But on Learn WordPress, we provide different learning
resources that go beyond documentation.
So we have four types of content on learn.wordpress.log.
And I'm just going to call it learn.wordpress.
So we have four types of content on learn.wordpress.
The first one are tutorials.
Tutorials are short videos, about five minutes to 10 minutes,
that talk about specific topics.
So I will briefly show--
so we have tutorials here.
You can filter tutorial videos by series, topic, language,
et cetera.
But you'll see here this tutorial is six minutes.
It's about using page templates.
Or if you scroll down, you'll see more.
For example, a 12-minute tutorial,
how to switch from a classic theme to a block theme.
This one is more for developers.
Five minutes, managing a WordPress multi-site network
is a nine-minute workshop.
building a page with only patterns.
So that just gives you an idea of what tutorials are.
Short videos that help people learn a specific concept.
And if you open tutorials, you'll see there's
a video at the top.
And then we also have some more information
listed underneath it.
So here's an overview of what you'll learn in this video.
Some learning outcomes, comprehension questions.
This is like just to make sure you've understood
the details of the video.
And then the transcript.
So there's a transcript here of everything
that is mentioned inside the video.
And then we have a bit of information
about the presenter there.
All right, so that is the tutorial.
And you'll see here, we have the full content types.
So the first one is tutorials.
Next one is online workshops.
and online workshops is what you are attending right now.
So these are live interactive sessions.
They're usually an hour, sometimes they're shorter,
sometimes they're longer.
And if you click on online workshops,
you'll see we have a calendar here
of all the sessions we're hosting.
So today, let's see,
how to translate content for learn.wordpress.org.
There was actually a session earlier today
about custom CSS in the site editing era.
And then we have more sessions next week.
You'll see there's a Japanese online workshop here as well.
And our goal is to have just online workshops hosted
all the time so that people can log in and learn something
new about WordPress whenever they want.
So again, I think these times are shown in your local time
zone.
So that says how to translate content for learn.workpress.org
starts at 5 PM.
That's for me in Japan.
If you open this page in your own browser,
you'll see these times in your own local time zone.
All right, so tutorials, online workshops.
Next, we have courses.
So courses are just online courses.
So you might know other education websites that have courses.
And we have four types of courses.
So we have courses for developers, courses
about introduction to WordPress.
So that's using WordPress.
We have courses using the site at the time,
and then courses about contributing solutions.
So if you want to contribute to WordPress,
then these courses are for you as well.
You'll sit down here.
Let's see, well, I think we have like 20 courses
or something at the moment.
So for example, if you pick on small point source basis,
there's a bit of an overview.
And then you can click into the different lessons
of those courses here.
So yeah, courses are mostly text-based,
but they also use images, videos.
Some courses have quizzes, so you can test yourself
and your understanding.
And you'll see here this says seven of seven lessons
completed, 100%.
The Learn WordPress website records your course progress.
So if you start a course, then you have to step away
for a while, it will record your progress
and you can come back at the late today
and start again from where you left off.
So we've done tutorials on more courses
and finally lesson plans.
Now lesson plans, these are aimed at teachers of WordPress.
So the first three types of content
aimed at learners of WordPress
and lesson plans are aimed at teachers.
So lesson plans, resources a teacher can pick up
and then go and teach a lesson about WordPress.
So for example, for example,
submitting block patterns to the directory.
So if you click on that,
again, lesson plans are aimed at teachers, not learners.
So when a teacher takes this, they can see,
okay, this is a 45 minute lesson plan
for beginning intermediate users,
instruction type is demonstration, show and tell.
So this will be showing people how to submit
block patterns to the directory.
There's a description that gives an overview
of the lesson, objectives,
what we want people to learn from this lesson,
prerequisite skills, skills people need
before they start attending the lesson,
readiness questions, materials needed.
This is all helping the teacher know
how to prepare for the lesson.
And if you come here, we finally get to notes
for the presenter, lesson outline,
and then exercise and assessment.
So we have here different exercise questions,
different assessment questions the teacher can use.
And finally, if you come down to example lesson,
we'll actually have the text here a teacher can read
and different slides or images
they can share with their class when they're teaching about this particular concept.
So just to refresh again, those are the four types of content on loan.
We have tutorials, online workshops, courses, and lesson plans.
Now today's topic is how to translate content for the Learn WordPress website.
And to do that, the most important information
is the training team handbook.
So I'm going to drop this link in the Zoom chat.
So at the moment on my screen,
you'll see I have the training team handbook open.
So bookmark this link,
I've just dropped in the Zoom chat,
or you can access it directly from make.wordpress.org/training/handbook.
Now, if you open it on the computer, you'll see we have a table of contents on the side.
So you have about, getting started, how-to guides, etc., etc.
And what we're really interested in today is how to translate.
We open the How To guides.
Under How To, you'll have content localization.
So we've come to the training team handbook.
We've clicked on How To guides.
And under that, we have content localization.
So this is the main page to help you get started.
We're translating content for Learn WordPress.
And we're going to detail a little bit more.
So, content localization.
I like to look at these subpages.
We have content localization and then we have translating content, creating new content
in languages other than English, reviewing translations, translating subtitles, etc.
So we have a few more detailed pages here.
content, how do you translate content? And this URL is very long. So I will paste the
link again in the Zoom chat here. But hopefully you can find how to get there. You go to the
training team website, you go to Handbook, you go to how to guides, you go to localization.
And here we list how to translate the four different types of content. So we mentioned
before we have lesson plans, we have tutorials, we have online workshops, and we have courses.
And this handbook page here gives you details about how to translate each of these pieces of context.
So just quickly, for example, if you look at lesson plans, you'll see it's a six-step process.
The first of all is choose an existing lesson plan.
Next is create a new GitHub issue, etc., etc.
I'm going to walk through one of these processes,
but there's another document I wanted to share before we start.
If you look at the left here under the index,
under content localization,
just this last week,
we've published a new page and it's
called High Priority Content to Translate.
If you go to the Loan WordPress website,
you can translate any tutorial or any lesson plan.
If there's a particular tutorial that your community really needs,
you're free to just choose that and translate that.
Or if there's a particular course you want to translate,
you can just pick that up and translate it.
This handbook page will walk you through how to translate.
There's a particular lesson plan you want to translate,
you can click that directly here.
But if you want to translate and there's nothing really that you,
like you don't really know what to translate from,
then we have a high priority content to translate document here,
which lists just a handful of high priority content.
We were wanting to get translated first.
So if you're stuck and not sure what to translate,
then this high priority document is the best place to start.
Today, I'm going to take, for example,
and we'll go for this one here for Beginners Tutorials.
Then we have down here,
getting to know the WordPress dashboard.
I'm going to click on that,
and this will open up the Getting to Know the WordPress Dashboard tutorial.
I'm going to spend the next half an hour or so,
walking through how to translate this tutorial.
So I've chosen the piece of content,
and we'll come back to this talk and we'll walk
through the steps on the translating content,
and I'll show you the steps of how you can translate a tutorial.
But I wanted to pause there.
Some people joined in a bit later.
I wanted to see if anybody has any questions in that before we
actually get into the translation part.
If you have a question, feel free to unmute,
or you can drop your question in the Zoom chat.
No questions? Oh good.
Let's fine with me.
All right, so let's start translating this tutorial.
So getting to know the WordPress dashboard,
just so you can follow along, I'll drop the link in the Zoom
chat.
So this is the tutorial we're going to translate.
And we're going to follow the steps on this page,
the translating content.
Now, there's a bit of information at the top here,
which I highly recommend you read before you get started.
It says here, "If you are new to translating resources
for WordPress, then we recommend you first read
through the general expectations for translators."
So just to clarify, this is if you're
new to translation in any of WordPress.
So if you have experience translating in the Polyglot
team, then you can skip this, because it's
the same information that's shared with the polyglots.
But just mentioning here, we do have a document general
expectations for translators.
For example, don't include random links.
Don't translate literally.
Translate organically so that people
can read your translation and understand better.
Try to keep the same level of formality.
Don't use slang.
Learn from other localizations in your language, et cetera.
So there are some guidelines there
we'd like training team translators
to read before they get started.
All right.
Once you have familiarized yourself with those expectations,
then you can follow the steps below to translate
each content type.
And then we have two tips here.
The first one.
The translation consistency tool is a great tool
for translators to book by.
If you come across a word or phrase,
you're not sure how to translate,
then you can search for it in that tool
to see how other people have translated it in the path.
So I'm gonna open this translation consistency tool.
And again, this is the tool polygots use.
So if you have a translation experience
in the polygots team, and this isn't new,
but this is a really good tool.
So what you can do is you enter the original sentence here.
For example, let's say block editor.
So just pretend I don't know how to translate block editor.
I can then choose the language.
So for example, I translate into Japanese,
so I can look up Japanese.
And I'll just leave that all projects.
And if I click analyze, then what this tool does
is it looks at all the other themes and plugins
and translations in the WordPress project
and tells me how other people have translated
block editor into Japanese.
And then you'll see all originals have the same translations.
So they all translated Biroku Eritah.
Sometimes there might be two or three translations
of a word.
And if that's the case, this will say here,
there are two translations for this word,
or there are three translations for these words.
And then you can pick one of the translations
that have been used before.
You don't have to use this for every single word,
but if you ever get stuck with a word or a phrase,
then this translation consistency tool
is a great tool to use to help you get over that block.
And then finally, we have an LTE.
If you're looking for something to translate,
but are not sure what to start on,
and check out high priority content to translate for ideas.
So that's where we got this tutorial.
And then we'll jump down to tutorials.
So first I've learned something here,
but we'll come down to tutorials.
Now tutorials, for tutorials,
you can either rerecord the tutorial in your own language
or just translate the subtitles and other texts
shown on the tutorial page.
So a tutorial is a short video, five to 10 minute video.
If you want, you can rerecord the audio on the tutorial.
You can even like recreate the slides
and do the whole presentation in your own language.
And if you're interested in doing that,
we have steps here that walk you through it.
But creating a five to 10 minute video
takes a lot of effort.
So what I recommend is to just translate the subtitles
of the tutorial first.
And then if you find your community
has a really big need for the tutorial video,
then you can remake the video then.
And but as you get started, translating the subtitles
is the best way to go.
So tutorial and subtitles to the English video,
this is what we're going to work on.
Step one, choose an existing tutorial
that you'd like to translate.
And we've already chosen that, so we can move on to step two.
Step two, open a new GitHub issue
using the content translation template.
Creating a GitHub issue at the beginning of the process
allows the team to track localized content
currently being created and offer any support
you need throughout the process.
So the training team, we use GitHub to manage translation.
So what I would do is I would click on new GitHub issue
and then it says using the content translation template.
So if you look here, the training team,
we have lots of different templates we use for different tasks.
But the important thing here
is to use content translation template.
So if you look down the side,
you'll see we have content translation template.
So then we click get started.
All right.
Now, let's come back over here.
So open a new Git issue.
Okay. And so then we have to fill out this issue.
So if you're new to GitHub,
this might look a bit overwhelming.
So I'll try and make it as simple as possible.
What we have to look at is the title of the GitHub issue
here and the content or the details of the issue,
which is here.
These are the only two places we need to edit.
So first of all, the title, it says,
Language Translation for Content Type, Content Title.
So for my case, I'm going to translate into Japanese.
So I'll change this into Japanese.
So Japanese translation for content type.
So content type, in this case, I'm translating a tutorial.
I would type tutorial and then content title.
So the content title is getting to know the WordPress dashboard.
So I'll copy that and I will paste that over here.
So now the title is Japanese translation for tutorial,
getting to know the WordPress dashboard.
OK?
And then it says here, the steps to translate content
on Learn WordPress can be found in the handbook.
So that takes us back to this page here.
Remember to update the title of the issue, which I've just
done.
So example, it gives an example there,
but we've just done that.
So we've updated the title.
So now we come to the details.
So it says here, link to original content.
So the link is this link over here.
So we get that link.
We copy that.
We paste that into GitHub issue.
I might just make my screen a little larger
so it's easy for people to see.
So details linked to original content.
We did that.
Link to original content GitHub issue.
Now this one, we can skip if we need.
But what we do,
what it is is we want to track the original content.
We want to track all the issues in GitHub
and we want to make sure they're connected.
We might need to make this optional
because this is a bit difficult.
You need to understand GitHub a bit.
What we can do is in GitHub, I've just opened the new tab here.
And we can search for issues with a particular title.
Whoops.
So getting to know the WordPress dashboard.
Let me just copy this again.
If I search for issues with the title
Getting to know the WordPress dashboard.
Here we go.
Getting to know the WordPress dashboard.
So this was the original issue that was used
when they created the workshop.
And you'll see if you come down here,
here is the link to the video for feedback.
please review by this date.
So what we want to do is we want to copy this link,
come back to the issue and paste the link
to the original content here.
All right, next.
And if that process looks a bit difficult,
then you can leave a blank
and the translation coordinator will come through
and update that link for you.
So if you're able to add the link, that's very good.
If that's a bit difficult, then feel free to skip that.
Next, language you'll be translating to.
So in my case, I'll be translating to Japanese.
Have you arranged for someone to review this translation?
So for every piece of content on Learn,
we like to have it reviewed before it goes published.
This is the same for English content
and for translated content.
And that's just to make sure that we
keep ourselves accountable to high quality content online.
So if you already have someone you've set,
you've arranged as a reviewer, you can say yes.
But if you don't have anybody arranged yet
to review your content, you can say no.
And the translation coordinator will help
find the translation reviewer for you.
So for example, if you already have found someone,
then the next question is the reviewer's GitHub username.
So you could add their username here.
For example, destiny is another training team representative.
So if I had her range, I can add her name like this.
But if I didn't have anybody arranged,
I would leave that blank
and I would just write no.
Okay?
And then finally, other information.
So if there's any other notes you wanted to add,
you can add that here.
But again, this can be blank.
Okay.
Next step.
Once translated, please link or upload
your translated files in a comment on this issue
and request a translation review.
So just to refresh, what I did right now
was I updated the GitHub title
And then I filled out information here on the details.
And then I would click submit new issue.
All right, so I've just created a new GitHub issue.
The title is Japanese translation for tutorial,
getting to know the WordPress dashboard.
You'll see the different details listed here.
And the next step is once translated,
please link or upload your translated files
in a comment on this issue and request a translation review.
So I've completed step two on this guide
and I can now move on to step three.
Before I do, with any questions so far
or something people want me to explain a bit better.
No.
All right. If you have any questions along the way,
feel free to drop them in the Zoom chat.
Let's move on to step three.
All right. Here we go.
Pierre-Marie. Hello, Ben.
So far, it seems pretty similar to
the process we followed for other content types.
Great. It's supposed to be similar.
So that's good.
All the content so far is the same.
You choose a piece of content,
you create a GitHub issue.
Now, this is where it becomes specific for each content type.
So for tutorial subtitles, it says,
"In the application of your choice,
translate the text shown on a tutorial page under the video,
such as learning outcomes, comprehensive questions,
and transcript."
So if you open a-- oops, we can close this one now.
If you open the content under tutorials, under the video,
you'll see there's some information here.
So we have an overview, learning outcomes, comprehension
questions.
Sometimes there are resources, and then a transcript.
So what you want to do is you want
to translate this in the application of your choice.
I like to use Google Docs because the next step,
we're going to be receiving reviews about this content.
And a Google Doc has a comment feature,
so people can leave comments on specific parts
of your translation.
But it doesn't have to be Google Docs.
It can just be any other application,
and that's where you would translate this content.
So what we'll do is I'll copy all this content.
Copy.
And then I'm going to create a new Google Doc.
There we go.
And I'm going to paste.
Then we do that.
All right.
That's probably this.
Okay, so that's pasted there.
And I'm going to start trans IE this.
So let's see, Japanese translation
for tutorial dashboard overview.
And then I'm not gonna translate all of this right now,
but for example, this English here would be,
let's see.
(indistinct)
(將在裝置上上向前 send)
And you'll notice I've left the English here in the Google Doc.
This helps the reviewer when they come along after me,
when they check my translation against the review.
If you have the English there, it helps them sort of compare and make sure it's all right.
You can get rid of the English and they can compare with the original over here.
But me personally, I think leaving the original English there helps reviewers.
OK, so let's pretend I've completed the translation.
So number three was in the application of your choice,
translate the text shown.
We've done that.
So number four, update the GitHub issue with links
to your translated resources and request a translation review.
So what we would do is we would copy the link to this Google
Doc and add it to this GitHub issue over here.
So with Google Docs, I would click Share,
and I would copy the link.
But when you do this, make sure people have access.
Sometimes Google Docs can be private,
and people can't see the contents.
So anyone with the link can comment.
Anyone with the link can comment.
Make sure your access is all good.
Copy the link.
Once you've copied that, you would come over to the GitHub
issue, and you would say, this translation is ready for a review.
And then paste the link to your translation and comment.
OK?
Now, if you're using Google Docs,
you can share the link like this.
If you've translated this into, say, a text file,
then you can upload the text file to your GitHub comment here.
So I think you just need to drag and drop the file
into this box.
Oh, yeah.
So you can say like translation is ready for a review.
And then drag and drop the file from your computer like this.
And then you'll take a moment to upload.
I'm just dragging and dropping a random file here.
But it looks something like that.
But you can then comment, and then your file
will be uploaded to other people's look at.
So either works.
So you can share a link or you can share the actual file.
Now, once you get to this stage, we
want you to notify a translation coordinator
that your translation is ready for review.
So if you've arranged for a translation from someone,
then you can just ping them and let them know,
and they can translate or they can review for you.
But if you have an arrangement for someone,
then ping a translation coordinator in Slack,
and then they can arrange for someone
to review this for you.
So what you would do is,
I'm going to bring my Slack screen onto the screen here,
just a moment.
All right.
So in the WordPress Slack,
I'm looking at the training team channel at the moment.
And what you could do is type something like,
we have translation coordinators.
So we have a special call word
for translation coordinators, translation.
So you'll see I started with an @ mark
and then type translation.
And at the top here, we have training, faculty,
translation coordinators.
If you use this, then you can ping
all the translation coordinators at once,
and then whoever's logged in will get that ping
and be able to respond to you.
Faculty translation coordinators,
and then you'll type something like,
"Hi everyone.
This translation is ready for a review.
And then you can copy and paste the link to the GitHub issue.
And then the translation coordinator
can look at that and assign a translation reviewer for you.
So let me just type.
[BLANK_AUDIO]
This is the test, all right.
So translation coordinates, hi everyone, this translation is ready for review.
[BLANK_AUDIO]
And I do that, and then we can keep this preview open or
we can close it, but then all the faculty translation coordinates will get
will get notified and someone will respond to your ping for you.
So let's see, we came to step four, update the GitHub issue with links to your translated
resource and request the translation review.
So we've updated the GitHub issue with this.
We've made a request for a translation review in Slack.
And then so the translation reviewer will come along and review your translation and they
leave comments in the Google Doc or they might leave comments in the GitHub issue.
But wait for them to review your content and if they make any suggestions then see if it's valid,
apply those suggestions to your content and prepare it to publish.
OK, next five.
Once reviewed, request a translation coordinator
to create a new post on Learn WordPress for the content.
Then copy and paste the translated content
into that new post.
So at the moment, the translation
just lives in a Google Doc, but we
want to put this on Learn WordPress.
And so a translation coordinator has
to prepare a new post for you.
So the translation coordinator will prepare a new post
and they will comment in the GitHub issue here and say,
oh, let me create a new post.
So this is what I'm about to show now
is what the translation coordinator will do.
So a normal translator doesn't see this part.
for the translation coordinator,
they would go into Learn Word Press
and they would create a new post for you.
Like first of all, finding the English post,
they will copy that.
And so they would do this,
they would change the language to Japanese.
Save draft.
All right, so.
They'll say something like, please copy paste your translation
into this post.
OK.
So a translation coordinator will prepare a post for you
for you to copy and paste your translation into.
So what you would do is you would click on this link.
The translation coordinator gives you.
You click on that.
And initially, it will all be English,
because we're starting from English.
So what you would do is you would take the translation you
made in this Google Doc, you would copy that,
and you would come over here and replace the English--
oops, oops-- you would replace the English
with the translation.
So right now, I've only translated this first paragraph,
But you would go through and replace all this content
with your translation from the Google Doc.
And once you've done that, don't publish yet,
click Save Draft.
All right, so we'll click Save Draft.
So that was step five.
Once reviewed, request the translated coordinator
to create a new post on WordPress for the content
and copy and paste the translated content
into that new post, all right?
If you're doing like a lesson plan, then that's it.
But for tutorials, we still have to get the subtitles
onto the video itself.
So step six, follow translating subtitles
to download an English subtitle file,
transfer the translated transcript into this file
and upload it back to WordPress TV.
So before we dive into that,
let me translate the first section of the transcripts
so we have something to work with.
So the first section here says,
(speaking in foreign language)
All right, so what I've just done
I've just translated the first two sentences here into Japanese.
All right.
So then we'll follow the steps here.
Step six, follow translating subtitles,
download an English subtitle file,
transfer the translated transcript into the file,
and upload it back to WordPress TV.
So let's open this up.
So there's a bit of information here
about translating subtitles.
I'll skip over that for now and show you these steps.
So first, find the video you want to translate subtitles
for on WordPress TV.
You can use the search bar on WordPress TV
to search for the video title.
So what we need to do is we need to go to WordPress TV
and once again, what we're searching for is this video.
So going to know the WordPress dashboard.
So here, I like to use the parentheses symbol here.
Getting to know the WordPress dashboard, okay?
And then you'll find the top one is probably
what we're looking for, getting to know the WordPress dashboard.
So all our tutorial videos also live on WordPress.tv.
All right, so we found the video,
which is step one, so now we come down here.
Once you've opened the video, search for subtitles
in the menu bar on the right underneath the video.
If it has been subtitled already,
you should see TTML English.
So we come over here, you scroll down in the sidebar,
you'll see we have subtitles,
and here it has all the languages
it has subtitles for at the moment.
So we have English, we have, oh,
I think that's Gujarati, maybe.
And then we also have French.
But anyway, so we want to click on English.
And when you click on English,
you'll see a pop-up just opened up.
This downloads the subtitle file to your computer.
So we've just downloaded the English subtitles
to our computer.
All right, step three.
Click on the word English to download the English subtitle file.
Okay, we've done that.
So next, format the subtitle file.
So once downloaded,
open the subtitle file in your text editor.
Oftentimes, the file will look like this.
All right. So I am going to open
the subtitle file in my text editor.
If you're not sure what a text editor is, at the very top of the page, we have here,
in order to translate subtitle files, you'll need a text editor.
And we have some different options of text editors you can use.
So any text editor will work fine.
So what we'll do, oops, I've just opened my text editor, and I will open the file we
just downloaded.
OK, this is the subtitle file, and that looks difficult to read.
So it's recommended that you format the file first
so that it is easier to translate the subtitles.
Search online for free XML code format.
So for example, we'll use this.
And what this software does is you
You can copy all of this text into the left.
And then you'll see--
beautify.
If you click on beautify, it has put indents and things
in the right.
So when you copy this and take it back--
oops-- if you copy this and take it back to this document,
It's a bit easier to read. You can see each line now starts with P and it's all indented
a bit, making it a bit easier to read.
So step two, use the tools to format the subtitle file. You can download the formatted file as
as a new file or copy and paste the formatted text back
into your editor.
So formatted files should now look like this.
So we've done that.
Next, translate the subtitles.
You'll notice the majority of subtitle files look like this.
So they start with a P and end with a P.
The text that appears between the two P brackets
is the text you'll want to translate.
you'll want to leave the rest of the file as is.
So for example, here's a sample subtitle file,
and then it gives an, you'll see we have a P,
P bracket here, and it finishes with a P bracket there,
and then the English subtitles are in the middle here
between the brackets, and we want to translate that
into Japanese.
So let's open this file over here.
So skip the first few lines,
You'll see down here, we have a P bracket.
And it says, welcome to Learn WordPress.
Join us as we get more acquainted with the--
and then dashboard comes over here.
So what we want to do is we want to replace this English
with the translation that's already been improved over here.
So the transcript was the translation of the video.
And so all the text you see here,
welcome to the Learn WordPress.
join us as we get more acquainted with the dashboard.
That text appears here in the subtitle file.
So I copy the Japanese translation,
come over here, and I replace the English with the Japanese.
And you'll notice the word dashboard came over here
into the new P-bracket.
If it's just one word or two,
you can move that like,
At the moment, the Japanese word for dashboard appears here.
It's not at the end of the sentence like English is.
So I've just included dashboard in the top P bracket here.
And you can make minor adjustments like that.
But sometimes if it's a long sentence,
then you'll want to split the sentence in two
so that the length of the translation between P brackets
is pretty much the same as the original.
I hope that makes sense.
All right. So then you'll just go through the whole file here and do the same. So you'll
see there's other information here inside the P-racket. You can just leave that as is.
All we want to change is the text between the two P-rackets. All right. Then let's see,
Let's come back over here.
Once you have translated the file,
save the file as a new .ttml file.
So we'll file save as,
and we'll call this Japanese test.ttml.
Okay.
So save the .ttml file.
Then we can finally upload the translated file to WordPress.tv.
So open the page you originally downloaded subtitles from.
From the subtitles section in the right menu bar, click on Subtitle this video.
So we'll go back to WordPress.tv, WordPress TV,
getting to another WordPress dashboard.
On the right, under subtitles, you'll see there was a link subtitled this video.
So we're going to upload a new subtitle file.
So click on this.
And then, well, you saw it automatically filled in my email address.
But there's a bit of information here.
So what's your WordPress.org username, email address, language.
We want to change this to Japanese.
And then subtitle files.
So choose your file.
So you can open that.
Japanese test Ttml, and then click on submit.
Oops, I had to enter into my email address.
Oh well, I will delete that for the recording.
But anyway, open, submit.
Okay, so I've just submitted a new translation of the subtitle file to WordPress TV.
Now, before that shows up on the video, it has to be approved.
So on the following page, fill out your WordPress.log username and email address. We did all that.
Number three, uploaded subtitle files must be approved by site admin on WordPress.tv
before they show up on the video. Feel free to ping a faculty admin in the training site channel,
asking them to approve your translation file.
I will update this later because now we have translation coordinators.
You can ping them again in Slack like we did before, or the translation coordinator should be
following your GitHub issue now, so you can even leave a comment on GitHub and say, "Hi, I've uploaded
the subtitle file. Please approve this. Thanks.
And then the translation coordinator will see that so they can log into WordPress.tv
and approve your subtitle files for you.
And that was the end of that step.
So number six was translating subtitles.
Number seven was once done, notify a translation coordinator
to approve the subtitles.
So a translation coordinator, they
will approve the subtitles for you.
And then they will also check this post.
So remember before we were copying and pasting
our translation into the post on Learn WordPress,
the translation coordinator will check this for you,
make sure it all looks good.
A translation coordinator will also
look at the settings on the right here,
make sure they're all correct.
And then a translation coordinator
will click Publish for you.
And then it will say, they'll let you know
in the GitHub issue, they'll say,
I've approved your subtitles,
I've published the content for you,
and the content has been published on Learn.
And that takes us to the very end
of translating subtitles on a tutorial.
What I realized while I was saying all that
is that this process takes a bit of time.
Once you get used to it,
like anything, once you get used to it,
it's not as overwhelming.
So I guess something I want to leave everyone with
is translation coordinators are happy to answer your questions
in Slack at any time.
If nobody is online right now, they'll see your PIM
and give back to you later.
But if you ever get stuck, I'm translating content.
Or if you ever need help with GitHub,
or maybe you just need help to get something published,
feel free to PIM back with the translation coordinators in Slack.
and they will be happy to answer your questions for you.
So I'll just leave this app, this unswack
notification in the Zoom chat here.
So you'll see I just copy pasted @faculty-translationcoordinators
ping these people anytime in the training channel
and they will be happy to answer
your transition questions for you.
All right, so I'm coming to the end of the content
I have prepared for this online workshop.
Are there any questions people have
or anything you want me to show again?
Pierre-Mauriel, no real questions,
we just need a bit of practice.
I think that's it.
And what I plan on doing is,
this recording is going to be posted on WordPress.tv,
but I plan on cutting it into small sections
and somehow putting those small sections into the handbook.
So like just a 30 second clip about creating a GitHub issue
or a 30 second clip about translating subtitles.
So if you, when you come back later,
you can just click that video and get a quick overview
of how to do those specific processes.
Hopefully that will help people
unless they get used to the training teams process.
So we say, yes, I indeed need to test the process.
Here, Mario, I was personally considering
that for shorter videos, it would be probably
fast down creating a new video in our language.
The other advantage would be showing the localized interface
to those following the tutorial.
I agree.
For tutorials, if you can rerecord the tutorial
in the language, that would be really good.
And something we did before, so with this GitHub issue,
I went into GitHub and looked for the original content.
And what you can do is--
what you can do-- let's see.
So if you scroll down here, you'll
Let's see, this person created the original video.
If this person is still active in Slack,
you could reach out in Slack and ask them to share their slides
with you.
So if they used English Slides, sometimes just
getting the English Slides helps you.
And you can then translate the slides on your computer
and re-record the video with those exact same slides.
And sometimes you can just retake the screenshots on that.
So that's one good benefit of finding the original GitHub
issue.
You can figure out who the original presenter was.
But actually, if you scroll down to the bottom here--
so I'm looking at the Learn Word Press tutorial--
you scroll down to the bottom, the presenting information
is right here.
So you could reach out to this person in Slack
and say, hey, I want to translate your slides
to create a localized version.
Can you share your slides with me?
And that might work.
It depends what software they use.
Some people don't use slides.
They use demonstrations and things.
So it depends on the video,
but that could also be something you can do.
All right, and Margarita,
maybe starting translations from lesson plan
to test the process is more easier
than translating a tutorial, I think.
That is true.
Translating a lesson plan is probably a bit easier
because you don't have the subtitle process.
That is true.
So the reason why we did a tutorial today is because
at the moment the training team's high priority content.
We have a list of high priority content to translate tutorials and courses.
So that's why I did a demonstration about tutorial.
But what you say is true.
Lesson plans aren't easier to translate.
So even just getting used to GitHub and getting reviews and everything,
lesson plans could be a good place to start.
All right. Any final questions people want to ask? Martin, it will require a lot of review
of this video before it will all become clear. Yes. And so once again, if you have questions,
like once this video is published, I will post the recording link in the meetup.com event.
So you'll get notified about the recording.
And while you're watching it, if you have questions,
you can even ping me in Slack too.
You can even use this faculty translation coordinates
and say, I'm watching the video and at like 35 minutes in,
that you do this specific thing and I
need you to help me understand this better.
And then we can look at the video, 35 minutes.
OK, that's what we were doing and then help you with that.
So please ask questions.
The training team for like 10 years
has only mainly created English content.
So translation is a whole new thing for us.
So that's why it's a bit still rough around the edges.
The process is a bit rough because it's a new process.
But we are open to feedback.
So let us know where you get stuck, what's difficult,
what's easy, and we hope to improve the process from here
on.
PMI, I know several of the high-product content are video tutorials.
All right.
So we went over for about 15 minutes, but thank you, everyone, who stayed and watched
to the very end.
Once again, we'll open the feedback.
Please let us know how the process is as you experience it.
And I will let you all know once the recording has been processed and uploaded to WordPress.tv.
Thank you everyone for joining today and I look forward to seeing you all again in the
online workshop soon.
Okay then.
Thank you everyone.
Great being.
Thank you, Samir.
All right.
Bye.