Windows fonts on fedora

Frields has been a Linux user and enthusiast since , and joined the Fedora Project in , shortly after launch.

He was a founding member of the Fedora Project Board, and has worked on docsc, websites, advocacy, toolchain, and package maintenance. He currently lives with his wife and two children in Virginia where he also runs a recording studio 5thdom. However, it would be nice to have some command-free option to refresh the font cache, or to be able to install the new font with a transparent font cache refresh.

Anyway, nice article! Glad to see that this is not one of those things necessarily requiring the command line!

These were very helpful tips. However, everything has been working as expected. So I wonder what exactly the fc-cache command does. This font is currently available at:. It is a classical, historically accurate Garamond font, and it is very well done.

It is excellent for texts or anywhere an elegant serif font is appropriate. I prefer to install them in. They will survive also a system move, then you copy your home from a machine to another. I only wish Fira Code was available. If you prefer working in a C. Many fonts are available from the RPM Fusion repository. To enable the repository on your system, follow these instructions. In many cases, you may want to use a specific font that is not available in Fedora or is not made available under Free Culture licenses.

Unpackaged fonts are not managed by a package manager. You will not automatically receive updates or optimizations. If a font is provided by a distribution package, you should always use a packaged version of a font.

System fonts are installed for all users. Anyone with an account on the machine will be able to use these fonts. Therefore packaging a font family in multiple OpenType formats should only be done as a limited exception. Want to help? Learn how to contribute to Fedora Docs. Edit this Page. Foreword The bulk of Fedora software relies on OpenType compliance and was tested against compliant fonts. Trademark uses MUST be authorized by their owners, trademarks may occur in font naming or font content logos….

Packaging unit: an ideal font family Because fonts upstreams are, on average, extremely messy, a large part of packaging fonts involves sorting files and fixing font file metadata to produce the consistent and reliable font catalog expected by applications and users. Font family. Packagers MUST apply the definition provided in this section to determine font family boundaries, it takes precedence over application support concerns, over upstream and packager habits and practices.

Font file formats OpenType: one standard, five formats. Font packages. A font family MUST NOT be packaged in multiple or mixed OpenType formats, except for variable font data, except when mixing is required, to achieve full symbol glyph coverage, except as an application workaround; see Packaging a font family in multiple OpenType formats; application support. Fontconfig Font packages SHOULD include the fontconfig files, that define the selection and substitution rules applying to their font files, written by the packager if upstream does not provide them.

See also the Tooling section for fontconfig syntax guidance. Source SRPM package break-up Separate source archives MUST be packaged in separate spec files, except when those contain parts of the same font family and upstream coordinates their release.

Other upstream files. Building Packagers SHOULD build font files from sources, whenever their prefered modification format is not the packaged OpenType format and if the required toolchain is available as free software under Linux. Dependencies in font packages Font packages MAY require or supplement other font packages, when they contain the same font family, as defined in Assembling same-family font packages.

Dependencies to font packages in other packages Non-font packages MAY suggest or recommend font packages, the weakest Suggests form is preferred over Recommends , except in presence of strong pre-existing user habits. Assembling different-family font packages: partial designs Font reuse and font extension.

The font package containing the new font family SHOULD recommend the package containing the original font family, only the core package of the original font family in case of Assembling same-family font packages. Assembling different-family font packages: font metapackages Packagers MAY provide convenience font metapackages, for example, when an upstream releases a collection of font families, intended to be used together, a common case is matched serif , sans-serif and monospaced font families.

Exceptions Bitmap console fonts Bitmap console fonts MAY be packaged in a legacy font format, understood by kbd. Console fonts. Involved packagers MUST choose a core font package. This core package MAY contain fontconfig rules, for all the font files composinng the font family, fontconfig ignores rules that do not match installed files. Splitting a font family interacts badly with font auto-provides. Packaging a font family in multiple OpenType formats; application support Packagers MUST make a reasonable effort, to get applications that do not support all OpenType formats, fixed upstream.

Packagers MUST ensure that the resulting additional font data, is separated in distinct font packages, that the average Fedora user can install those font families in a single format, that he is not left wondering, which package to install.

Tooling Creating font packages by hand can be extremely repetitive, error-prone and labor-intensive. Fontconfig The fonts-rpm-templates package contains fontconfig templates, corresponding to common fonts packaging needs. Using fontconfig, you can help users and software make sense of broken font files. On brokenness and interoperability. Style naming The OpenType specification , the CSS specification and the fontconfig manual document the canonical mappings of style keywords.

Spec template documentation The fonts-rpm-templates package contains spec templates, corresponding to common fonts packaging needs. Packaging a single font family This is the simplest packaging pattern, when upstream releases:. Macros and variables Declaration ordering. SRPM generic declarations This pattern starts with a block of traditional spec declarations:.

Version: Release: URL:. Shared font declarations Then it declares elements, that will be shared by all the packaged font families. Family-specific font declarations This is followed by a family-specific declaration block. It must be less than 80 columns in length. The focus is on clear, easy-to-perceive letterforms that will not be readily confused with one another. Source declarations Then package sources are declared the usual way. Font package names. Remainer of the spec file All those declarations are used and processed in the rest of the spec file by the following macros:.

Annotated spec template Putting it all together:. Packaging template: basic single-family fonts packaging. SPDX-License-Identifier: MIT This template documents the minimal set of spec declarations, necessary to package a single font family, from a single dedicated source archive.

Declaration order is chosen to limit divergence between those templates, and simplify cut and pasting. Adjust as necessary. The OFL is our recommended font license.

Keeping the filename in sync with the package name is a good idea. See the fontconfig templates in fonts-rpm-templates for information on how to write good fontconfig files and choose the correct priority [number]. Packaging a single font family advanced Sometimes, packaging a font family requires a little more work, with the associated automation.

Macros and variables Shared font declarations One more shell glob list:. It is dedicated to the year anniversary of the Russian civil type invented by Peter the Great from to , and was realized with financial support from the Russian Federal Agency for Press and Mass Communications. Remainer of the spec file Bulky documentation can be split in a separate subpackage. It takes the following optional arguments: -e [encoding] source OS encoding automatically detected otherwise -n do not recode files, only adjust folding and end of lines.

Packaging template: less common patterns for single-family fonts packaging. Split those files in a dedicated optional doc package. I display these all at font size 16 as I like to use a larger font, plus it shows up minor issues. This has a hairline fracture on the right hand side arrows, but is otherwise perfect. I actually prefer it to the Inconsolata-dz as the LN icon is more readable. On top of these regulars, I tried almost all the available fonts and my other favourite was Source Code Pro.

Source Code Pro is a very detailed and complete font that has been considered to work in a large range of scenarios. This kind of completeness matters for edge cases. Used as a patched font it almost perfectly displays the vim-airline bar. The benefit of so many alternatives is the use of the light font which has an even better display of the vim-airline bar.

Skeptic coder View all posts by ianchanning. You are commenting using your WordPress. You are commenting using your Google account.

You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. This site uses Akismet to reduce spam.

Learn how your comment data is processed.