< L10N FAQ
L10N is an abbreviation of the term "Localization" by means of a so-called numeronym, a way of replacing the middle letters of a word (in case 'ocalizatio') by naming the number of letters between the first and last letter of that word (in case 10): Localization.
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 in tact when it covers legal matters.
- Issues or Feature requests specific to Fedora Infrastructure should be reported to 
e.g. XYZ package is not available for Translation Submission or Statistics.
- Issues or Feature requests specific to Transifex should be reported to .
e.g. Statistics should show last committer information as well on the status page, Sorting of statistics should be available.
The fastest way of getting things done is to approach FLP-admin group via IRC #fedora-l10n .
The website of the Fedora Localization Project is http://translate.fedoraproject.org/.
Before opening a new bug report, please take a look at the above query 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 bug report describing what's wrong with the service in clarity. Include the nature of the problem, the module/branch combination, 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.
If the issue is about Transifex as a software like feature requests and general problems not specific to the Fedora instance, please use the upstream ticketing system of Transifex .
See L10N Maintainer on how to become a maintainer of a new language.
To add your team, create a bug report on l10n-requests. Include language, your name and FAS account, e-mail address, and URL to team's website and mailing list, if they exist.
如何为我的语言创建 Bugzilla 组成？ (#bugzilla-team)
We have a separate Bugzilla component for every language, in order for bug reports to reach the correct people (ie. the ones that can fix them). We maintain these entries in an owners.list file on our VCS. You can find it in the L10n CVS, at /cvs/l10n/owners/. Each organized language group should have an entry there.
For more information, refer to L10N Maintainer .
我已经 100% 翻译了，但我仍见到英文字符串！ (#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.
- The PO file you translated was not msgmerged. In this case Transifex will show a statistic less than 100% (since it auto-merges the files). You need to acquire the file from Tx or msgmerge it with the POT file yourself.
我的 PO 文件已经 100% 翻译了，但网站没有这样报告！ (#100-percent)
There are a number of reasons this would happen, but here are the most common ones.
- The statistics are not updated on-the-fly but on a scheduled base -- you might need to wait until the next run of the update script. See #live .
- Most likely the PO file you submitted needed an msgmerge first, because it didn't contain the latest strings from the POT file. Let's say you checked out the PO file from the Version Control System (VCS), translated it 100% and committed it back. Before calculating the statistics, Transifex does an
msgmergeon the PO file with the POT.
如何添加一个模块到 Transifex? (#add-transifex)
To enable translators send contributions to your project through Transifex, you need to have a special VCS account for Transifex. The Fedora Infrastructure-side details are described at Translations_Infrastructure_SOP.
我是一名开发者，如何使我的 .desktop 文件可翻译？
Take a look at this email on fedora-trans-list.
Most of the cases, this is a problem with SSH keys. When a user creates a new account, we associate an SSH key with it. When a new account is created, the user is requested to upload the public part of her SSH key (located in
~/.ssh/ of your PC), and this key is used to identify the user. This way is more secure than using a simple password. If you can't authenticate to cvs.fedoraproject.org, then the SSH key of the user on the system you are using doesn't have the same SSH key as the one we have on our servers, associated with your username.
If you have changed your SSH key recently, please visit Edit your Fedora account and upload your new SSH key.
If you haven't changed your SSH key recently, make sure the system and user account you are using has your SSH keys (eg. copy them from your other PC).
No. This is purposely set up as non-translatable. Please refer to Non-translatable export regulations?.
Straight after String Freeze, the developers will merge latest strings of software for the translators. It is same for documentation, the authors will merge latest strings of each document after their String Freeze. Software, Beta Release Notes, GA Release Notes and other guides have different String Freezes, and those are scheduled in "Translation Task List" for each release, which can be found under "Detailed Schedules" section in Schedule page.
Email the  mailing list!
There can be two possibilities: 1. You have overwritten wrong file in your own locale: you should locate the previous version of the overwritten .po file from http://git.fedorahosted.org/git/ and replace the wrongly updated file with this file.
2. You have overwritten file which belongs to some other language: in this case, you have to send an e-mail to the mailing list about this immediately, locate the correct file of that language from the 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.