#217 Tutorial/Classroom session - L10N using Weblate
Closed: Fixed 3 years ago by shehroz. Opened 3 years ago by shehroz.

L10N using Weblate - An overview of Localization & Translation Project

Dear All i have started work on proposed Tutorial/Classroom session about L10N, i have created a slideshow; to accompany my tutorial video.

I am presenting my draft for record and input from the community.

These are the links to my slide.

(https://switch.shehroz.pk/L10N-Slide.pdf)
(https://switch.shehroz.pk/L10N-Slide.odp)

So, What is Localization?

Localization (L10N, l10n and sometimes LoCo) is the process of adapting a software’s translation to a specific language, country or region. It is a constituent part of a larger process called ‘tailor made solution for a niche segment’.

What are the activities of L10Nteam of Fedora?

Well, we at the Fedora L10N team; or more commonly Fedora Translation Project; primarily translate the visible text & descriptions in one & other of local languages; most of the time.
The text you read on your screens, on your title bars, and in modules is most of the time translated as per conventions of local language.

What tools do we use?

We use multiple tools for several purpose, Our biggest tool is Weblate; a web base translation tool, which allow developers to gather translation suggestions from almost anywhere from the earth.

We organize/communicate using mailing lists (email), and internet relay chat (IRC).
Our contributions into Weblate are pushed/pulled towards a git instance (like pagure, github and other) from where developers use them to integrate into end software packages.

We also use ‘pagure’ to track issues and/or to request assistance from other parts of Fedora Project.

We use FAS (Fedora Accounts System) to authenticate across the platform and tools.
… and some other tools; you would get acquainted when you dive deep enough :-)

How translation project works?

When developer(s) of a certain package wants the software to be translated into different language, other than primary, They create .PO files in the Git repository of that package. These .PO files contain basically Three types of things (strings) 1, placeholder reference; 2, the source string; and 3, the newly translated string or a BLANK string.

These .PO files are fetched by Weblate; and presents the data in such a manner, that the contributing translator can suggest/translate these strings without getting their hands messed up with these complex .PO files; using a easy to use web interface; which is accessible through your favorite web browser.

These translated strings are forwarded to repository (Git instance) and used accordingly.

How can you contribute your time & put your effort in translation?

This is pretty straight forward and easy… if you want to dive-in and try to give your one cent; then follow this…. First and foremost thing; you need to be passionate enough to do something ;-)

Jokes apart; first you need to create a Fedora accounts system account (if you don’t already have) using this link https://admin.fedoraproject.org/accounts please follow on-screen instructions (and those in the email that you receive) and sign the FPCA (Fedora Project Contribution Agreement).

Then after setting up open this link https://translate.fedoraproject.org/ please login using Fedora account (OpenID) and lurk around to explore.

Please take some time to post an introduction to trans mailing list by sending an email to trans@lists.fedoraproject.org and fedora-join@lists.fedoraproject.org after subscribing to list.

How to get started using Fedora Weblate to translate?

More details about in the (currently under production) video tutorial.

Thank you!

Presented by Shehroz Kaleem (FAS: @shehroz)


Done!

Uploaded the tutorial to YouTube!

See the link https://youtu.be/PFOesx6Zh-k

Metadata Update from @shehroz:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata