From Fedora Project Wiki
m (wiki links)
(we now use matrix)
 
(31 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{autolang|base=yes}}
{{autolang|base=yes}}
[[Image:L10n-images-translator.png|right]]


= Fedora Localization Guide =
== Introduction ==


= 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.


Welcome to Guide Location Fedora on this page you will find instructions on how to join our translation team and starting 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 [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.}}


{{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.}}
== 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/'''


= Getting Help =
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 Matrix, at {{matrix|#l10n:fedoraproject.org}}, where you will find people from different teams in the same space.


For help we suggest you to register in our main {{fplist|trans}} maillist and is also recommended to subscribe to the maillist of the team you want to join or ask for help in your native language, please refer to our list of the maillists: '''https://lists.fedoraproject.org/mailman/listinfo'''
== Becoming a Fedora Translator ==
 
The teams following this name schema: trans-TEAM, for example, trans-fr@ for the French language, or trans-it@ to Italian.
You can also ask for help via Internet Relay Chat (IRC), at irc.freenode.org on channel #fedora-g11n, 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:
To be a Fedora Translator you need to follow the following steps:


#[[#Create_a_Fedora_account|Create a Fedora account]]
#[[#Create_a_Fedora_account|Create a Fedora Account]]
#[[#Login_to_Zanata_with_your_FAS_account|Login into Zanata with your FAS credentials]]
#[[#Subscribe_to_the_main_Mailing_List|Subscribe to the Main Mailing List]]
#[[#Subscribe_to_the_main_Mailing_List|Subscribe to the main Mailing List]]
#[[#Subscribe_to_team_Mailing_List|Subscribe to your Team's Mailing List]]
#[[#Subscribe_to_team_Mailing_List|Subscribe to team Mailing List]]
#[[#Introduce_Yourself|Introduce Yourself]]
#[[#Introduce_Yourself|Introduce Yourself]]
#[[#Login_to_Weblate_with_your_FAS_account|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 [[#How-to_create_a_Bugzilla_account|create a Bugzilla account]] to work on bugs reported by users.
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.


 
=== Creating a Fedora Account ===
== Create a Fedora account ==


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


=== 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.
# To sign up for a Fedora account, first visit https://accounts.fedoraproject.org/ and select ''Register''.
# Fill in Username, Full Name and Email, and click Sign up!. Your password will be emailed to you.
# Fill in ''Username'', ''First Name'', ''Last Name'' and ''Email'', and click ''Register''. Your password will be e-mailed 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.
# Go back to https://accounts.fedoraproject.org/ and login with your password. The welcome page will be displayed.
# To submit public SSH key and GPG key ID, click My Account or go to https://admin.fedoraproject.org/accounts/user/edit.
# To submit your public SSH key and GPG key ID, click ''Edit Profile'' and click ''SSH & GPG keys''.
# 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 [[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 the ''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''.


=== Join to the group cvsl10n ===
==== Joining the l10n Group ====


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


# In the Fedora account select Group List
# In the Fedora account select Group List
# Search for group cvsl10n
# Search and apply for ''l10n'' group
# Apply for group cvsl10n


Wait for the sponsor approval, this step is part of process [[#Becoming_a_Fedora_Translator|Becoming a Fedora Translator]].
Wait for the sponsor approval, this step is part of process [[#Becoming_a_Fedora_Translator|Becoming a Fedora Translator]].


 
=== Subscribe to the main L10N mailing list and local L10N mailing list ===
=== Joining your Fedora translation team ===
* Main L10N mailing list
 
# Visit the Fedora Teams page at https://fedora.zanata.org/language/list.
# 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.
 
== Login to Zanata with your FAS account ==
 
* Open https://fedora.zanata.org/ and click the blue 'Log In' button on the top-right of the page.
[[File:zanata_login.png |600px]]
* Then it will guides you to FedOAuth page in which you can Login with your FAS account and password you have registered in last section.
[[File:Fedoauth.png|600px]]
* Then you will be directed to a authentication page, click 'Approve'.
[[File:fas_approve.png|600px]]
* A 'new user' page will be opened.
You should enter your full name, username(FAS username) and your email address. Note: Please use your true email address but not your Fedora project alias(username@fedoraproject.org). When you finish them, click the Save button. A activation email will be sent immediately to your email address. Please find the mail in your inbox and open the  activation link that is provided in the mail. Then login with your FAS username and password. You won't need to follow this step again when you login next time. It's only necessary for new user login.
 
{{Admon/note|Note| Some time ago we were using Transifex for localization, but now we've replaced it completely with Zanata. However, part of the documentation may be outdated and still use Transifex. If you encounter such a page, feel free to report it so that we can update it appropiately. }}
 
 
== Subscribe to the main Mailing List ==
 
# Visit {{fplist|trans}} and subscribe to the main translation 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.
# 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
 
== Subscribe to team Mailing List ==
 
# Check [[L10N/Teams]] to join mailing list for your language.
# Check [[L10N/Teams]] to join mailing list for your language.
# Subscribe to the 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.
# Wait for the confirmation email which contains a link to confirm your subscription. Click the link to confirm your subscription.


=== Introduce yourself ===


== Add yourself to your language translation team in Zanata ==
# 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.
# 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.


# First log into [https://fedora.zanata.org/ Zanata] with your Fedora account
=== Login to Weblate with your FAS account ===
# Visit the [https://fedora.zanata.org/language/list team page] and find your language
Fedora L10N platform had been migrated from Zanata to Weblate since the end of 2019.
# Click on Request To Join Team and Send Message
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]].


== Online/Offline Translation Using Weblate ==


== Introduce Yourself ==
Visit [[L10N/Translate_on_Weblate]] for more info.


# Create a personal page at [[User:Username]]. This is very useful for Fedora contributors to get to know and contact each other. You'll need to [[#Create_a_Fedora_Account|create a Fedora account]] for that.
== FAQ (Frequently Asked Questions) ==
# 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 user name and your language. With this information, your language leader can identify you and approve you as a translator on his team.
 
 
= Online / Offline translation using Zanata =
 
Visit [[L10N/Translate on Zanata]] for more info.
 
 
= FAQ (Frequently Asked Questions) =


Here are some FAQs about the Localization Project.
Here are some FAQs about the Localization Project.


=== Should I translate legal notices? ===
{{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.  
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? ===
{{Anchor|reporting-issues}}
==== How do I report issues? (#reporting-issues) ====


Before reporting (either opening a new ticket or the list), please search to see if there's an existing report opened. It sometimes help to ask in #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.
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 {{matrix|#l10n:fedoraproject.org}} 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? ===
==== Where do I report issues? ====


* Issues '''specific to Transifex''' should be reported using the "Feedback" button on the right-side of the website.
* Issues '''specific to Fedora L10N''' should be first reported on {{matrix|#l10n:fedoraproject.org}} Matrix 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: Questions related to Transifex, possible bugs, feature requests, problems you are having with the site, such as a slow webpage, login issues.
** These '''do not include''' missing Fedora projects, Fedora team creation requests, Fedora coordinators etc.
 
* Issues '''specific to Fedora L10n''' should be first reported on IRC channel {{fpchat|#fedora-l10n}} and then on the trans-XX mailing list.(Replace trans-XX with your L10N team's maillist name.Seek your team's name at: [[L10N_Teams|L10N Teams]] page.)
** These include team questions, releases, projects, Fedora maintainers, developers etc.
** These include team questions, releases, projects, Fedora maintainers, developers etc.
** These do NOT include questions Transifex bugs, feature requests, problems you are having with the site, such as a slow webpage, login issues, or wrong statistics because a project is missing from the release.
=== Where do I report feature requests? ===
Please see above section, 'issues specific to Transifex'.


{{Anchor|new-team}}
{{Anchor|new-team}}
=== How do I create a new team? (#new-team) ===
==== How do I create a new team? (#new-team) ====


See [[L10N_Maintainer| L10N Maintainer]] on how to become a maintainer of a new language.
See [[L10N Coordinator]] on how to become a coordinator of a new language.


{{Anchor|missing-strings}}
{{Anchor|missing-strings}}
=== My file is 100% but when I test the application I still see English strings! (#missing-strings) ===
==== 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. Nevermind. 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 of Transifex 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.
 
{{Anchor|update-frequency}}
=== Are the statistics live? How often are they updated? (#update-frequency) ===
 
The statistics on Transifex are always live on the project pages. The Release pages are updated once per day.
 
{{Anchor|add-transifex}}
=== How do I add a module to Transifex? (#add-transifex) ===
 
# Navigate to https://www.transifex.com/projects/add/
# Follow the instructions from http://help.transifex.com/intro/projects.html
 
If you want the Fedora Localization Project to handle your translations (i.e. you are NOT an upstream project):
 
# Click 'Access Control' on your Project Details Page
# Outsource team control to "The Fedora Project"
# Send an email to fedora-trans-list and let the contributors know about the change. One of the Fedora L10n Editors will add your project to one of the Fedora releases.
 
http://fedora.transifex.com/
 
Here are two more pages you might want to read:
 
* http://lists.fedoraproject.org/pipermail/trans/2011-January/008573.html
* http://lists.fedoraproject.org/pipermail/docs/2011-February/013109.html
 
=== I'm a developer, how can I make .desktop files translatable? ===
 
Transifex will natively support .desktop files soon.


=== I can't find "About this Computer" string. Where is it? ===
This wasn't a question, by the way. Never mind. The following might have gone wrong:


It can be found at [[WillWoods/AboutThisComputer|AboutThisComputer]].
* 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 fedoraproject.org/get-fedora page translatable? ===
{{Anchor|export-regulations}}
==== 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 [http://lists.fedoraproject.org/pipermail/legal/2010-March/001183.html Non-translatable export regulations?].
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?].


=== If some strings change past string freeze, how do I request a string freeze breakage? ===
{{Anchor|breaking-freeze}}
==== If some string changes miss string freeze, how do I request a string freeze breakage? (#breaking-freeze) ====


Email the [mailto:trans@lists.fedoraproject.org trans] mailing list!
Email the [mailto:trans@lists.fedoraproject.org trans] mailing list!


=== What if I overwrite a wrong file? ===
{{Anchor|creating-bugzilla}}
 
==== How to create a Bugzilla account? (#creating-bugzilla) ====
If you have overwritten a wrong file in your own locale, try to find the old file on the developer's git repo (http://git.fedorahosted.org/git/) and replace the wrongly updated file with this file.
 
Even though these are measures to correct mistake, we strongly advice you to take extra care while submitting the translations via Transifex and make sure that you are uploading file in proper location under proper locale because some projects don't keep translation files under their CVS tree (do I say "Anaconda" ? oO)
 
=== I'm from the Docs Project. How do I make my Guide / Release Notes / other document available for translation? ===
 
If you keep you document in a git repository, see [[Setting_up_a_document_with_Transifex|Setting up a document with Transifex]] to find out how to make it available to translators on Transifex.
 
=== How-to create a Bugzilla account ===


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


= Guide information =
The following people have contributed to this guide:
* Diego Búrigo Zacarão
* Dimitris Glezos
* [[User:fredlima| Frederico Henrique Gonçalves Lima]]
* Manuel Ospina
* [[User:firemanxbr| Marcelo Barbosa]]
* Misha Shnurapet
* Noriko Mizumoto
* Paul W. Frields
* Petr Kovar
* Piotr Drąg


[[Category:Localization]]
[[Category:Localization]]

Latest revision as of 21:01, 30 July 2024

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.

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 Matrix, at #l10n:fedoraproject.org(other clients|?), 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 Register.
  2. Fill in Username, First Name, Last Name and Email, and click Register. 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 the 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 #l10n:fedoraproject.org(other clients|?) 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 #l10n:fedoraproject.org(other clients|?) Matrix 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.