The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation status

431 Strings
0%
Browse Translate
6,008 Words
0%
42,707 Characters
0%

Strings status

Strings Words Characters
431 6,008 42,707
All strings Browse Translate Zen
431 6,008 42,707
Unfinished strings Browse Translate Zen
431 6,008 42,707
Untranslated strings Browse Translate Zen
2 2 16
Strings with suggestions Browse Translate Zen
429 6,006 42,691
Unfinished strings without suggestions Browse Translate Zen

Summary

Project website pagure.io
Instructions for translators

Mailing list for translators: <trans@lists.fedoraproject.org
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository ssh://pagure.io/fedora-docs-l10n/packaging-guidelines.git
Repository branch master
Last remote commit automatic update of pot/po files 1f908188a
♪ I'm a bot, bot, bot ♪ authored 02/07/2026
Last commit in Weblate Translated using Weblate (Spanish) 8a52ab906
User avatar serrador authored 03/05/2026
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/FontsPolicy.po
Translation file Download po/zh_Hans/master/pages/FontsPolicy.po
Last change Sept. 4, 2025, 10:22 p.m.
Last change made by None
Language Chinese (Simplified Han script)
Language code zh_Hans
Text direction Left to right
Case sensitivity Case-insensitive
Number of speakers 1,286,444,445
Number of plurals 1
Plural type None
Plurals
Plural formula 0
02/11/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 431 6,008 42,707
Translated 0% 0 0% 0 0% 0
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 1% 2 1% 2 1% 16
Untranslated strings 100% 431 100% 6,008 100% 42,707
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 53 changes 0 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes
MarAprMayJunJulAugSepOctNovDecJanFeb

Quick numbers

6,008
Hosted words
431
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
—
—
Contributors
—
User avatar None

Resource updated
The “po/zh_Hans/master/pages/FontsPolicy.po” file was changed. 09/04/2025
User avatar None

String added in the repository
Fonts are comparatively bulky. Shipping fonts in multiple formats makes the situation worse on user systems, mirrors and live images. Every font family that ships in multiple formats, consumes space that could be used by another font package, enhancing the user experience.
 
09/04/2025
User avatar None

String added in the repository
Building from source ensures it will be possible to modify the font when problems are reported and upstream is not responsive. Sometimes that means working with upstream to sanitize its build processes.
 
09/04/2025
User avatar None

String added in the repository
As noted in the xref:index.adoc#bundling[Packaging Guidelines], Fedora packages should make every effort to avoid having multiple, separate, upstream projects bundled together in a single package. This applies equally to font packages.
 
09/04/2025
User avatar None

String added in the repository
Remember that a lot of upstream naming decisions are taken to accomodate systems, that are missing an automatic font substition / font merging layer. The format and coverage information in `family` names is intended to help manual selection of font files. Our guidelines ask packagers to convert those to information fontconfig understands. Free Desktop systems can do a lot more, as long as the information provided to fontconfig is correct.
 
09/04/2025
User avatar None

String added in the repository
The other decisions are just choosing good defaults for the font family. While fontconfig can take a guess at those, its guess will never be as accurate as packager decisions. Packagers can ask upstream for clarifications. Fontconfig can not.
 
09/04/2025
User avatar None

String added in the repository
Removing coverage attributes from `family` enables merging all matching files in a single synthetic family. That is more user friendly, and prevents breakage when upstream decides to split the font family over different lines. Because creating a wide-coverage font family is a hard, long-term endeavour — Unicode is not finalized yet — such changes are common.
 
09/04/2025
User avatar None

String added in the repository
Removing format attributes from `family` prevents breakage, when the technical format shipped by the distribution changes after an update. Because font technology continues to improve, format changes are bound to happen sooner or later. Applications can still request font format information via the fontconfig API if they need to.
 
09/04/2025
User avatar None

String added in the repository
Free Desktop systems rely on multiple upstreams to provide their fonts. They are heavily dependent on fontconfig to present a consistent user-friendly font pool in applications. High quality fontconfig rules are indispensable to permit easy substitution of font families, and to mask upstream messiness.
 
09/04/2025
User avatar None

String added in the repository
The users of this legacy backend won't thank you for destabilizing it with new fonts. They value stability. Otherwise they'd have moved to fontconfig like everyone else a long time ago.
 
09/04/2025
Browse all translation changes