summary refs log tree commit diff
path: root/pkgs/development/libraries/fontconfig
Commit message (Collapse)AuthorAge
* Merge remote-tracking branch 'upstream/staging' into strictDepsJohn Ericson2018-05-14
|\
| * fontconfig: Clean up crossJohn Ericson2018-05-10
| |
| * Merge commit '70963b382f3f820ba6d3bc3b3aaf50a2957ec1ff' into ↵John Ericson2018-05-10
| |\ | | | | | | | | | lib-platform-simplify
| | * fontconfig: 2.12.1 -> 2.12.6Nikolay Amiantov2018-03-06
| | |
| | * fontconfig: Fix for HFS+ 1s date resolution issueHamish Mackenzie2018-02-12
| | | | | | | | | | | | | | | HFS+ (still common on macOS machines) only has a date resolution of 1 second. This change makes sure that `fcobjshash.h` gets a newer timestamp than `fcobjshash.gperf`.
* | | treewide: Get rid of all uses of crossConfigJohn Ericson2018-05-14
|/ / | | | | | | | | | | | | | | | | | | | | | | The hack of using `crossConfig` to enforce stricter handling of dependencies is replaced with a dedicated `strictDeps` for that purpose. (Experience has shown that my punning was a terrible idea that made more difficult and embarrising to teach teach.) Now that is is clear, a few packages now use `strictDeps`, to fix various bugs: - bintools-wrapper and cc-wrapper
* / treewide: Get rid of `*Platform.arch`John Ericson2018-05-10
|/ | | | Use `parsed.cpu.name` or `platform.gcc.arch` instead.
* make-fonts-cache: remove CACHEDIR.TAG file from Nix storeBjørn Forsman2018-02-11
| | | | | | | | | | A CACHEDIR.TAG file indicates that the contents can be automatically re-generated. This is not really true for Nix store paths. (Well _Nix_ can recreate them, but that's different.) I noticed this issue as I was restoring full system backup that "for some reason" always missed /nix/store/*-fc-cache (found by `nix-store --verify --repair`). Turns out I was excluding caches from my backup...
* misc pkgs: Basic sed to get fix `pkgconfig` and `autoreconfHook` `buildInputs`John Ericson2017-09-21
| | | | Only acts on one-line dependency lists.
* make-fonts-cache.nix: Don't build-depend on unnecessary outputs of fontconfigTuomas Tynkkynen2017-09-11
|
* fontconfig default: Don't use stdenv.crosshsloan2017-06-28
|
* fontconfig 2.10: Don't use stdenv.crosshsloan2017-06-28
|
* fontconfig_210: Remove reference to obsolete patchTuomas Tynkkynen2017-03-30
| | | | | | | | | | | Commit 9b049849bfc385604f240157e129f7a8e3530d7f deleted the patch file (and reference to it from fontconfig default.nix), but left the one in 2.10.nix which break evaluation. As the package seems to build fine without the patch, just remove the reference. cc @ttuegel in case this was not the correct thing to do.
* freetype: disable PCF long family namesThomas Tuegel2017-03-28
| | | | | Backported several patches from upstream. The test suite patch for Fontconfig is no longer necessary.
* freetype: 2.6.5 -> 2.7.1Thomas Tuegel2017-03-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Infinality bytecode interpreter is removed in favor of the new v40 TrueType interpreter. In the past, the Infinality interpreter provided support for ClearType-style hinting instructions while the default interpreter (then v35) provided support only for original TrueType-style instructions. The v40 interpreter corrects this deficiency, so the Infinality interpreter is no longer necessary. To understand why the Infinality interpreter is no longer necessary, we should understand how ClearType differs from TrueType and how the v40 interpreter works. The following is a summary of information available on the FreeType website [1] mixed with my own editorializing. TrueType instructions use horizontal and vertical hints to improve glyph rendering. Before TrueType, fonts were only vertically hinted; horizontal hints improved rendering by snapping stems to pixel boundaries. Horizontal hinting is a risk because it can significantly distort glyph shapes and kerning. Extensive testing at different resolutions is needed to perfect the TrueType hints. Microsoft invested significant effort to do this with its "Core fonts for the Web" project, but few other typefaces have seen this level of attention. With the advent of subpixel rendering, the effective horizontal resolution of most displays increased significantly. ClearType eschews horizontal hinting in favor of horizontal supersampling. Most fonts are designed for the Microsoft bytecode interpreter, which implements a compatibility mode with TrueType-style (horizontal and vertical) instructions. However, applying the full horizontal hints to subpixel-rendered fonts leads to color fringes and inconsistent stem widths. The Infinality interpreter implements several techniques to mitigate these problems, going so far as to embed font- and glyph-specific hacks in the interpreter. On the other hand, the v40 interpreter ignores the horizontal hinting instructions so that glyphs render as they are intended to on the Microsoft interpreter. Without the horizontal hints, the problems of glyph and kerning distortion, color fringes, and inconsistent stem widths--the problems the Infinality interpreter was created to solve--simply don't occur in the first place. There are also security concerns which motivate removing the Infinality patches. Although there is an updated version of the Infinality interpreter for FreeType 2.7, the lack of a consistent upstream maintainer is a security concern. The interpreter is a Turing-complete virtual machine which has had security vulnerabilities in the past. While the default interpreter is used in billions of devices and is maintained by an active developer, the Infinality interpreter is neither scrutinized nor maintained. We will probably never know if there are defects in the Infinality interpreter, and if they were discovered they would likely never be fixed. I do not think that is an acceptable situtation for a core library like FreeType. Dropping the Infinality patches means that font rendering will be less customizable. I think this is an acceptable trade-off. The Infinality interpreter made many compromises to mitigate the problems with horizontal hinting; the main purpose of customization is to tailor these compromises to the user's preferences. The new interpreter does not have to make these compromises because it renders fonts as their designers intended, so this level of customization is not necessary. The Infinality-associated patches are also removed from cairo. These patches only set the default rendering options in case they aren't set though Fontconfig. On NixOS, the rendering options are always set in Fontconfig, so these patches never actually did anything for us! The Fontconfig test suite is patched to account for a quirk in the way PCF fonts are named. The fontconfig option `hintstyle` is no longer configurable in NixOS. This option selects the TrueType interpreter; the v40 interpreter is `hintslight` and the older v35 interpreter is `hintmedium` or `hintfull` (which have actually always been the same thing). The setting may still be changed through the `localConf` option or by creating a user Fontconfig file. Users with HiDPI displays should probably disable hinting and antialiasing: at best they have no visible effect. The fontconfig-ultimate settings are still available in NixOS, but they are no longer the default. They still work, but their main purpose is to set rendering quirks which are no longer necessary and may actually be detrimental (e.g. setting `hintfull` for some fonts). Also, the vast array of font substitutions provided is not an appropriate default; the default setting should be to give the user the font they asked for. [1]. https://www.freetype.org/freetype2/docs/subpixel-hinting.html
* Re-revert "Merge: glibc: 2.24 -> 2.25"Vladimír Čunát2017-02-20
| | | | | This reverts commit 55cc7700e968001c9ac79190fbcf25ed3620680a. I hope most problems have been solved. /cc #22874.
* Revert "Merge: glibc: 2.24 -> 2.25"Vladimír Čunát2017-02-16
| | | | | | | | | This reverts commit 1daf2e26d221712dfbe72f9f6d2f73ef230cc43c, reversing changes made to c0c50dfcb70d48e5b79c4ae9f1aa9d339af860b4. It seems this is what has been causing all the reliability problems on Hydra. I'm currently unable to find why it happens, so I'm forced to revert the update for now. Discussion: #22874.
* fontconfig: fixup fragile build after ab5fe171aVladimír Čunát2017-02-15
| | | | | Sometimes it might fail due to timestamps suggesting some files needed regenerating and failing to find gperf. Now it should be OK, I hope.
* fontconfig: patch to build with glibc-2.25Vladimír Čunát2017-02-12
|
* fontconfig: 2.11.1 -> 2.12.1Alexander Ried2016-10-11
| | | | Fixes #19302.
* Merge remote-tracking branch 'dezgeg/shuffle-outputs' into stagingTuomas Tynkkynen2016-08-30
|\ | | | | | | https://github.com/NixOS/nixpkgs/pull/14766
| * treewide: Shuffle outputsTuomas Tynkkynen2016-08-29
| | | | | | | | Make either 'bin' or 'out' the first output.
* | treewide: stop using fontbhttfVladimír Čunát2016-08-29
|/
* fontconfig module: respect upstream definitionsEric Sagnes2016-08-20
|
* fontconfig: fix etc priorityEric Sagnes2016-08-20
|
* Revert "fontconfig: fix etc priority"obadz2016-07-15
| | | | | | | | This reverts commit 1e53d4a7776acbf61f42c094c103652c8068ad64. Closes #16983 cc @vcunat @ericsagnes @dezgeg
* fontconfig: fix etc priorityEric Sagnes2016-07-09
|
* makeFontsConf: fix with multiple outputsVladimír Čunát2016-02-03
|
* Merge recent 'staging' into closure-sizeVladimír Čunát2016-02-03
|\ | | | | | | Let's get rid of those merge conflicts.
| * fontconfig: reorder cache dirsNikolay Amiantov2016-01-29
| |
| * makeFontsCache: initNikolay Amiantov2016-01-29
| |
* | fontconfig_210: Split into multiple outputsTuomas Tynkkynen2015-10-28
| |
* | libxml2,libxslt: split into multiple outputsVladimír Čunát2015-10-05
| | | | | | | | | | Fixed all references, hopefully. libxml2Python is slightly hacky now, but it seems to work.
* | fontconfig: split into multiple outputsVladimír Čunát2015-10-05
|/ | | | Fixed all 'fontconfig}' references as well, hopefully, ugh!
* freetype: fix pcf fonts by upstream patchesVladimír Čunát2014-12-17
| | | | | | | The problem was uncovered by the last security patches. Firefox seems to build and work fine. Includes reverting 374a9cc16271, as this is a proper fix.
* Disable fontconfig tests: they break after Freetype security update, and ↵Michael Raskin2014-12-17
| | | | apparently we get something working regardless of the test problems
* fontconfig: include user config through NixOS moduleThomas Tuegel2014-12-08
|
* Merge branch 'master' into stagingDomen Kožar2014-12-07
|\ | | | | | | | | Conflicts: pkgs/development/libraries/fontconfig/default.nix
| * fontconfig: current behavior makes substitutes failDomen Kožar2014-12-01
| |
* | fontconfig: drop infinality (for now), close #5140Vladimír Čunát2014-11-26
|/ | | | Also the simplify the expression when we rebuild anyway.
* fontconfig: avoid questionmark in patch name on darwinShaun Sharples2014-11-26
| | | | | Close #5135. @vcunat made this conditional to avoid rebuild for now.
* fontconfig: patch and documentVladimír Čunát2014-11-05
|
* fontconfig: add an upstream bugfix, remove other config inclusionVladimír Čunát2014-10-23
|
* fontconfig: update 2.10.2 -> 2.11.1. Close #4410, #2050Luca Bruno2014-10-23
|
* fontconfig: stop using xml:space; vital for nixos+2.11Vladimír Čunát2014-09-28
| | | | | This is a proper fix for problems described in ec985c8ffa6d29 . The code is from @lethalman.
* makeFontsConf: give up fontDirectories checks for nowVladimír Čunát2014-08-11
| | | | | This reverts e26188938c3142 and 77487fe6615f CC #3515.
* makeFontsConf: fixup to accept older font packagesVladimír Čunát2014-08-11
| | | | They contain fonts on the silly path lib/X11/fonts/
* makeFontsConf: check for share/fonts/ in fontDirectoriesVladimír Čunát2014-08-10
| | | | Fixes #3515.
* fontconfig: revert to sysconfdir=/etc. Closes #3453Luca Bruno2014-08-04
|
* fontconfig: attempt to fix installation on darwinVladimír Čunát2014-06-22
|
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-08-06 14:38:19 +0000