From Fedora Project Wiki
(Headings and <pre>)
(Update Fedora Project Contributor Agreement and FAS)
 
(89 intermediate revisions by 22 users not shown)
Line 1: Line 1:
= Fedora Localization Guide (UNDER CONSTRUCTION)=
+
{{autolang|base=yes}}
 +
[[Image:L10n-images-translator.png|right]]
  
= Introduction =
+
== Introduction ==
  
This guide is a fast, simple, step-by-step set of instructions for translating Fedora Project software and documents. You may find some FAQ at the end of the page.
+
Welcome to Fedora Localization Guide. On this page, you will find instructions on how to join our translation team and start the translations for our projects, documentation, wiki and websites to make a more friendly Fedora for all regions.
  
{{Admon/note | We Need Feedback! | If you find a typographical error in this manual, or if you have thought of a way to make this manual better, please feel free to either edit the page directly or simply send an email to the Fedora Localization Project mailing list. If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.}}
+
{{Admon/note | We Need Feedback! | If you find a typographical error in this manual, or if you have thought of a way to make this manual better, please feel free to either edit the page directly or simply send an email to the Fedora Localization Project [https://lists.fedoraproject.org/admin/lists/trans@lists.fedoraproject.org/ mailing list]. If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.}}
  
 +
== Getting Help ==
  
= Getting Help =
+
For help, we suggest you registering to our main {{fplist|trans}} mailing list and also recommend subscribing to mailing list of the team you want to join or ask for help in your native language. Please refer to our list of mailing lists: '''https://lists.fedoraproject.org/archives/'''
  
If you have questions, post them on the trans mailing list, or ask for help via Internet Relay Chat (IRC), at irc.freenode.org on channel #fedora-l10n.
+
The teams follow this naming schema: trans-TEAM. For example, ''trans-fr'' for French, or ''trans-it'' for Italian.
 +
You can also ask for help via Internet Relay Chat (IRC), at {{fpchat|#fedora-l10n}} channel on [https://libera.chat/ Libera.Chat], where you will find people from different teams in the same space.
  
= Becoming a Fedora Translator =
+
== Becoming a Fedora Translator ==
  
== Subscribing to the Mailing List ==
+
To be a Fedora Translator you need to follow the following steps:
  
# Visit https://admin.fedoraproject.org/mailman/listinfo/trans and subscribe to the main translation mailing list.
+
#[[#Create_a_Fedora_account|Create a Fedora Account]]
# Wait for the confirmation email which contains a link to confirm your subscription. Click the link to confirm your subscription.
+
#[[#Subscribe_to_the_main_Mailing_List|Subscribe to the Main Mailing List]]
 
+
#[[#Subscribe_to_team_Mailing_List|Subscribe to your Team's Mailing List]]
Check https://fedoraproject.org/wiki/L10N/Teams to see if there is a special mailing list for your language. If so, subscribe to that list too.
+
#[[#Introduce_Yourself|Introduce Yourself]]
 
+
#[[#Login_to_Weblate_with_your_FAS_account|Login into Weblate with Your FAS Credentials]]
== Create a Fedora Account ==
 
 
 
The steps below guide you through the creation of a Fedora Account. This is required for all Fedora Contributors.
 
 
 
=== Making an SSH Key ===
 
 
 
If you do not have a SSH key yet, follow these steps:
 
  
# Create key.
+
Your self-introduction is important. It raises your chances to be approved for write access. You may also want to [[#How-to_create_a_Bugzilla_account|create a Bugzilla account]] to work on bugs reported by users.
ssh-keygen -t rsa
 
# Accept the default location (~/.ssh/id_rsa) and enter a passphrase.
 
# Write it down, you can not recover it if lost.
 
 
# Change permissions to your key and .ssh directory:
 
chmod 700 ~/.ssh
 
chmod 600 ~/.ssh/id_rsa
 
chmod 644 ~/.ssh/id_rsa.pub
 
  
This public key (~/.ssh/id_rsa.pub) will be used for your Fedora account creation described in the section “Applying for an Account”.
+
=== Creating a Fedora Account ===
  
=== Making a GPG Key ===
+
The steps below guide you through the creation of a Fedora Account.
  
Generate a key by typing in a command line:
+
==== Applying for an Account ====
  
gpg --gen-key
+
# To sign up for a Fedora account, first visit https://accounts.fedoraproject.org/ and select ''Sign up''.
 
+
# Fill in ''Username'', ''First Name'', ''Last Name'' and ''Email'', and click ''Sign up!''. Your password will be e-mailed to you.
A series of prompts guides you through the process. The default values suffice in almost all cases. Remember to choose a good password. A good password consists of uppercase and lowercase letters, numbers, punctuation, and other characters
+
# Go back to https://accounts.fedoraproject.org/ and login with your password. The welcome page will be displayed.
does not include any words or names, with or without substitutions
+
# To submit your public SSH key and GPG key ID, click ''Edit Profile'' and click ''SSH & GPG keys''.
is not the same as any other password used for other systems
 
 
 
In the resulting text, find your key ID in the statement that resembles pub 1024D/1B2AFA1C. Your key ID is the 8 character word after the slash (/). In the previous example, the GPG Key ID is 1B2AFA1C. Write down your key ID.
 
Export your public key to a public server so that others can find it with the following command, substituting your key ID:
 
 
 
gpg --keyserver subkeys.pgp.net --send-keys GPGKEYID
 
 
 
This GPG key ID will be used for your Fedora account creation described in the section “Applying for an Account”.
 
 
 
=== Applying for an Account ===
 
 
 
# To sign up for a Fedora account, first visit https://admin.fedoraproject.org/accounts and select New Account.
 
# Fill in Username, Full Name and Email, and click Sign up!. Your password will be emailed to you.
 
# Go back to https://admin.fedoraproject.org/accounts and log in with your password. The welcome page will be displayed, and it reminds you that CLA is not completed and that an SSH key is not submitted.
 
# To submit public SSH key and GPG key ID, click My Account or go to https://admin.fedoraproject.org/accounts/user/edit.
 
# In the Edit Account (user_name) page, enter your GPG key ID in GPG Key ID: field. For the public SSH key, click Browse... button located next to Public SSH Key: field and specify your public SSH key.
 
# Telephone Number and Postal Address fields are also required to fill in for signing the CLA. These information is NOT accessible by others except admin groups. Please refer to Fedora Privacy Policy at https://fedoraproject.org/wiki/Legal:PrivacyPolicy.
 
 
# Other fields will be displayed by any other member by visiting the user's view page.
 
# Other fields will be displayed by any other member by visiting the user's view page.
# Now click Save! located at the bottom of this page to save your information.
+
# Now click ''Save!'' button located at the bottom of this page to save your information.
  
=== Signing the CLA ===
+
==== Signing the CLA ====
  
 
You must complete the Contributors License Agreement, or CLA.
 
You must complete the Contributors License Agreement, or CLA.
  
# Visit https://admin.fedoraproject.org/accounts and login your account using your user name and password obtained from the previous process.
+
# Visit https://accounts.fedoraproject.org/accounts and login to your account using your username and password obtained from the previous process.
# In the Welcome page, click complete the CLA or go to https://admin.fedoraproject.org/accounts/user/edit.
+
# In the welcome page, click ''Edit Profile'' and click ''Agreements''.
# If the information of telephone number and postal address have not been provided yet, the Edit Account (user_name) page will be appeared. Otherwise Fedora Contributor License Agreement page will be displayed. Read through the agreement carefully and click I agree if you are happy to do so.
+
# Fedora Contributor License Agreement page will be displayed. Read through the agreement carefully and click ''I agree'' if you are happy to do so.
# The user-view page is appeared and shows the CLA: field as CLA Done.
+
# The user-view page is appeared and shows the ''Fedora Project Contributor Agreement'' field as ''Signed''.
  
== Introduce Yourself ==
+
==== Joining the l10n Group ====
  
# Create a personal page at https://fedoraproject.org/wiki/User:Username. This is very useful for Fedora contributors to get to know and contact each other.
+
This step will introduce other Fedora contributors that you're part of the translation team.
# Post a short self introduction to the trans mailing list and to the list of your local team with instructions from https://fedoraproject.org/wiki/L10N_Self_introduction. Please remember to include your FAS user name and your language. With this information, your language leader can identify you and approve you as a translator on his team.
 
  
== Start using Transifex ==
+
# In the Fedora account select Group List
 +
# Search and apply for ''l10n'' group
  
Fedora uses Transifex to manage its localization workflow. These steps will guide you through the creation of a Transifex account and joining your team.
+
Wait for the sponsor approval, this step is part of process [[#Becoming_a_Fedora_Translator|Becoming a Fedora Translator]].
  
http://fedora.transifex.net/
+
=== Subscribe to the main L10N mailing list and local L10N mailing list ===
 +
* Main L10N mailing list
 +
# Visit {{fplist|trans}} and subscribe to the main translation mailing list.
 +
# Wait for the confirmation email which contains a link to confirm your subscription. Click the link to confirm your subscription.
 +
* Your local language L10N mailing list
 +
# Check [[L10N/Teams]] to join mailing list for your language.
 +
# Subscribe to the mailing list for your language.
 +
# Wait for the confirmation email which contains a link to confirm your subscription. Click the link to confirm your subscription.
  
=== Create a Transifex Account ===
+
=== Introduce yourself ===
  
# Visit https://fedora.transifex.net/ and click on the top-right corner "Register"
+
# Create a personal page at [[User:Username]]. This is very useful for Fedora contributors to get to know and contact each other. Because of spam problem, you'll need to [[#Joining_the_cvsl10n_Group|be added L10N FAS group]] to do this step.
# Fill-in the form and click Register! You can use your Fedora email or the same email you used to create your Fedora account. Choose a good password (as described above). This password can be resetted if you forget it, though.
+
# Post a short self introduction to the {{fplist|trans}} mailing list and to the list of your local team with instructions from [[L10N Self introduction]]. Please remember to include your FAS username and your language. With this information, your language coordinator can identify you and approve you as a translator on his team.
# Check your email. An email should arrive soon to verify your email address. There will be a link in it -- click it!
 
# You should be able to login on Transifex with your credentials now.
 
  
=== Joining your Fedora translation team ===
+
=== Login to Weblate with your FAS account ===
 +
Fedora L10N platform had been migrated from Zanata to Weblate since the end of 2019.
 +
Please visit this link to access Weblate https://translate.fedoraproject.org/.
 +
For details of translating on Weblate, please read the wiki page [[L10N/Translate_on_Weblate | Translate on Weblate]].
  
# Visit the Fedora Teams page at https://www.transifex.net/projects/p/fedora/teams/.
+
== Online/Offline Translation Using Weblate ==
# If your language is there, click on it.
 
# You should see a list of the members, the leader (coordinator). Click "Join this team" to ask to join the team.
 
# The team leader will receive a notification about your request. He will check your information, and check whether you introduced yourself.
 
# If all goes well, the maintainer will accept your application, and you'll receive a notification.
 
  
This may take between a few hours or days. If takes more, click on the maintainer's username on Transifex and send him a message asking him for more information.
+
Visit [[L10N/Translate_on_Weblate]] for more info.
  
== Creating a Bugzilla Account ==
+
== FAQ (Frequently Asked Questions) ==
  
If you are asked to use Bugzilla, create an account by visiting https://bugzilla.redhat.com/bugzilla/createaccount.cgi.
+
Here are some FAQs about the Localization Project.
  
 +
{{Anchor|legal-notices}}
 +
==== Should I translate legal notices? (#legal-notices) ====
  
 +
No. You must never do that. The exact wording of the legal notices is very important and a translation not approved by lawyers is very risky. Red Hat is the legal representative and primary sponsor of the Fedora Project and does not have the resources to cross check every single translation. Just leave the original English notice intact when it covers legal matters.
  
= Translating =
+
{{Anchor|reporting-issues}}
 +
==== How do I report issues? (#reporting-issues) ====
  
The translatable part of a software package is available in one or more PO files. Some projects might use other file formats as well, such as QT TS ones. These files may be maintained in any of a number of version control systems (VCSs) depending on the project, such as Subversion, Mercurial, and git. They may be hosted on either fedorahosted.org or other systems.
+
Before reporting (either opening a new ticket or on the list), please search to see if there's an existing report opened. It sometimes helps to ask on {{fpchat|#fedora-l10n}} if there's a known issue at that exact moment. If not, please open a ticket describing what's wrong with the service in clarity. Include the nature of the problem, the project/resource, the time (in UTC) it happened and your Fedora username. If you suspect it might be a problem with the particular file you are uploading or the target file, include that information as well.
  
This chapter explains how to translate the projects which use Transifex to manage their L10n workflow. Translators can work on the web interface or the command-line to obtain and submit files. Before you start, you must first prepare the directories which hold your po files.
+
==== Where do I report issues? ====
  
{{Admon/note | Fedora and Upstream projects | Using Transifex, you can contribute to both Fedora and Upstream projects. Fedora ones are those which Fedora is upstream for, ie. maintaining and handling. These are usually only used by Fedora.}}
+
* Issues '''specific to Fedora L10N''' should be first reported on {{fpchat|#fedora-l10n}} IRC channel and then on the trans-XX mailing list. (Replace trans-XX with your L10N team's mailing list name. Seek your team's name at [[L10N Teams]] page.)
 +
** These include team questions, releases, projects, Fedora maintainers, developers etc.
  
== Listing Translatable Fedora Projects ==
+
{{Anchor|new-team}}
 +
==== How do I create a new team? (#new-team) ====
  
# Visit https://www.transifex.net/projects/p/fedora/.
+
See [[L10N Coordinator]] on how to become a coordinator of a new language.
# Choose the type of Fedora Projects you want to translate by choosing the appropriate '''Release'''. You should see Fedora itself, Fedora Documentation and other upstream projects. Click on the release you choose to contribute to.
 
# The new page shows the full statistics for this release per language. Choose your language.
 
# This page shows all translatable resources (ie. files) for this release. Click on one of the table rows to get information on the resource you're interested in.
 
  
 +
{{Anchor|missing-strings}}
 +
==== My file is 100% but when I test the application I still see English strings! (#missing-strings) ====
  
== Translate Online ==
+
This wasn't a question, by the way. Never mind. The following might have gone wrong:
  
The easiest way to translate is by using the Transifex Web Editor. It's an intuitive interface which does not require you to download files on your system and re-upload them back.
+
* The strings in question have not been marked for translation by the developer, hence they haven't been included in the POT file, and thus not in the PO file. He needs to use ''gettext'' on them.
 +
* The source files of these strings have not been marked for inclusion, in the ''intltool'' case.
 +
* The POT file on Weblate is not up to date. The component page includes the date when the POT file has been produced. If this is more than a few hours in the past, please notify the admins, otherwise it should be OK.
  
# Follow the instructions above to locate the resource which interests you.
+
{{Anchor|export-regulations}}
# On the popup, you should see a "Translate Now" button. If you are logged-in on Transifex and a member of the language team, it should be clickable. Click it!
+
==== Is the section of export regulations shown at the bottom of the https://getfedora.org/workstation/download/ page translatable? (#export-regulations) ====
# You should now be in the Transifex Web editor (codenamed Lotte). Go on and translate as much as you want, and at the end, click "Save and Exit".
 
  
Note: When you translate online, the file is automatically "Locked" and other people are notified about your work. Never translate something that another translator has already locked -- you might be overwriting his own work!
+
No. This is purposely set up as non-translatable. Please refer to [http://lists.fedoraproject.org/pipermail/legal/2010-March/001183.html Non-translatable export regulations?].
  
 +
{{Anchor|breaking-freeze}}
 +
==== If some string changes miss string freeze, how do I request a string freeze breakage? (#breaking-freeze) ====
  
== Translating Offline ==
+
Email the [mailto:trans@lists.fedoraproject.org trans] mailing list!
  
(needs content)
+
{{Anchor|creating-bugzilla}}
 +
==== How to create a Bugzilla account? (#creating-bugzilla) ====
  
Before you download any files, we suggest you prepare a directory to hold your files. The described structure below is an example only, and your structure can be formed differently.
+
If you are asked to use Bugzilla, create an account by visiting https://bugzilla.redhat.com/bugzilla/createaccount.cgi.
 
 
mkdir -p ~/fedora-translations/
 
 
 
=== Obtaining and Translating Projects ===
 
 
 
Now that you have prepared a directory structure, you can download a file to translate. You may need to communicate with other translators in your language team to avoid conflict. If you are not sure, please contact your language coordinator. Also locking a file will avoid conflict.
 
  
  
(TO BE CONTINUED)
+
[[Category:Localization]]

Latest revision as of 13:43, 9 October 2021

L10n-images-translator.png

Introduction

Welcome to Fedora Localization Guide. On this page, you will find instructions on how to join our translation team and start the translations for our projects, documentation, wiki and websites to make a more friendly Fedora for all regions.

Note.png
We Need Feedback!
If you find a typographical error in this manual, or if you have thought of a way to make this manual better, please feel free to either edit the page directly or simply send an email to the Fedora Localization Project mailing list. If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.

Getting Help

For help, we suggest you registering to our main trans mailing list and also recommend subscribing to mailing list of the team you want to join or ask for help in your native language. Please refer to our list of mailing lists: https://lists.fedoraproject.org/archives/

The teams follow this naming schema: trans-TEAM. For example, trans-fr for French, or trans-it for Italian. You can also ask for help via Internet Relay Chat (IRC), at #fedora-l10n[?] channel on Libera.Chat, where you will find people from different teams in the same space.

Becoming a Fedora Translator

To be a Fedora Translator you need to follow the following steps:

  1. Create a Fedora Account
  2. Subscribe to the Main Mailing List
  3. Subscribe to your Team's Mailing List
  4. Introduce Yourself
  5. Login into Weblate with Your FAS Credentials

Your self-introduction is important. It raises your chances to be approved for write access. You may also want to create a Bugzilla account to work on bugs reported by users.

Creating a Fedora Account

The steps below guide you through the creation of a Fedora Account.

Applying for an Account

  1. To sign up for a Fedora account, first visit https://accounts.fedoraproject.org/ and select Sign up.
  2. Fill in Username, First Name, Last Name and Email, and click Sign up!. Your password will be e-mailed to you.
  3. Go back to https://accounts.fedoraproject.org/ and login with your password. The welcome page will be displayed.
  4. To submit your public SSH key and GPG key ID, click Edit Profile and click SSH & GPG keys.
  5. Other fields will be displayed by any other member by visiting the user's view page.
  6. Now click Save! button located at the bottom of this page to save your information.

Signing the CLA

You must complete the Contributors License Agreement, or CLA.

  1. Visit https://accounts.fedoraproject.org/accounts and login to your account using your username and password obtained from the previous process.
  2. In the welcome page, click Edit Profile and click Agreements.
  3. Fedora Contributor License Agreement page will be displayed. Read through the agreement carefully and click I agree if you are happy to do so.
  4. The user-view page is appeared and shows the Fedora Project Contributor Agreement field as Signed.

Joining the l10n Group

This step will introduce other Fedora contributors that you're part of the translation team.

  1. In the Fedora account select Group List
  2. Search and apply for l10n group

Wait for the sponsor approval, this step is part of process Becoming a Fedora Translator.

Subscribe to the main L10N mailing list and local L10N mailing list

  • Main L10N mailing list
  1. Visit trans and subscribe to the main translation mailing list.
  2. Wait for the confirmation email which contains a link to confirm your subscription. Click the link to confirm your subscription.
  • Your local language L10N mailing list
  1. Check L10N/Teams to join mailing list for your language.
  2. Subscribe to the mailing list for your language.
  3. Wait for the confirmation email which contains a link to confirm your subscription. Click the link to confirm your subscription.

Introduce yourself

  1. Create a personal page at User:Username. This is very useful for Fedora contributors to get to know and contact each other. Because of spam problem, you'll need to be added L10N FAS group to do this step.
  2. Post a short self introduction to the trans mailing list and to the list of your local team with instructions from L10N Self introduction. Please remember to include your FAS username and your language. With this information, your language coordinator can identify you and approve you as a translator on his team.

Login to Weblate with your FAS account

Fedora L10N platform had been migrated from Zanata to Weblate since the end of 2019. Please visit this link to access Weblate https://translate.fedoraproject.org/. For details of translating on Weblate, please read the wiki page Translate on Weblate.

Online/Offline Translation Using Weblate

Visit L10N/Translate_on_Weblate for more info.

FAQ (Frequently Asked Questions)

Here are some FAQs about the Localization Project.

Should I translate legal notices? (#legal-notices)

No. You must never do that. The exact wording of the legal notices is very important and a translation not approved by lawyers is very risky. Red Hat is the legal representative and primary sponsor of the Fedora Project and does not have the resources to cross check every single translation. Just leave the original English notice intact when it covers legal matters.

How do I report issues? (#reporting-issues)

Before reporting (either opening a new ticket or on the list), please search to see if there's an existing report opened. It sometimes helps to ask on #fedora-l10n[?] if there's a known issue at that exact moment. If not, please open a ticket describing what's wrong with the service in clarity. Include the nature of the problem, the project/resource, the time (in UTC) it happened and your Fedora username. If you suspect it might be a problem with the particular file you are uploading or the target file, include that information as well.

Where do I report issues?

  • Issues specific to Fedora L10N should be first reported on #fedora-l10n[?] IRC channel and then on the trans-XX mailing list. (Replace trans-XX with your L10N team's mailing list name. Seek your team's name at L10N Teams page.)
    • These include team questions, releases, projects, Fedora maintainers, developers etc.

How do I create a new team? (#new-team)

See L10N Coordinator on how to become a coordinator of a new language.

My file is 100% but when I test the application I still see English strings! (#missing-strings)

This wasn't a question, by the way. Never mind. The following might have gone wrong:

  • The strings in question have not been marked for translation by the developer, hence they haven't been included in the POT file, and thus not in the PO file. He needs to use gettext on them.
  • The source files of these strings have not been marked for inclusion, in the intltool case.
  • The POT file on Weblate is not up to date. The component page includes the date when the POT file has been produced. If this is more than a few hours in the past, please notify the admins, otherwise it should be OK.

Is the section of export regulations shown at the bottom of the https://getfedora.org/workstation/download/ page translatable? (#export-regulations)

No. This is purposely set up as non-translatable. Please refer to Non-translatable export regulations?.

If some string changes miss string freeze, how do I request a string freeze breakage? (#breaking-freeze)

Email the trans mailing list!

How to create a Bugzilla account? (#creating-bugzilla)

If you are asked to use Bugzilla, create an account by visiting https://bugzilla.redhat.com/bugzilla/createaccount.cgi.