fontconfig issueshttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues2018-08-21T03:13:12Zhttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/96Missing closing bracket in src/fcstr.c (git master)2018-08-21T03:13:12ZBugzilla Migration UserMissing closing bracket in src/fcstr.c (git master)## Submitted by sor..@..teo.jp
Assigned to **fon..@..op.org**
**[Link to original bug (#107444)](https://bugs.freedesktop.org/show_bug.cgi?id=107444)**
## Description
There is a missing closing bracket in src/fcstr.c at line 875: ...## Submitted by sor..@..teo.jp
Assigned to **fon..@..op.org**
**[Link to original bug (#107444)](https://bugs.freedesktop.org/show_bug.cgi?id=107444)**
## Description
There is a missing closing bracket in src/fcstr.c at line 875: https://cgit.freedesktop.org/fontconfig/tree/src/fcstr.c#n875
Patch:
diff --git a/src/fcstr.c b/src/fcstr.c
index bfddd68..4247c85 100644
--- a/src/fcstr.c
+++ b/src/fcstr.c
@@ -872,7 +872,7 @@ FcStrIsAbsoluteFilename (const FcChar8 *s)
{
#ifdef _WIN32
if (*s == '\\' ||
- (isalpha (*s) && s[1] == ':' && (s[2] == '/' || s[2] == '\\'))
+ (isalpha (*s) && s[1] == ':' && (s[2] == '/' || s[2] == '\\')))
return FcTrue;
#endif
return *s == '/';
--
2.18.0https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/109build issue with --enable-static2018-09-03T07:33:56ZAkira TAGOHbuild issue with --enable-staticwhen enabling the static linkage, the following errors happens:
```
CCLD test-bz106632
/usr/bin/ld: ../src/.libs/libfontconfig.a(fccfg.o): in function `IA__FcConfigHome':
/home/tagoh/work/repo/fontconfig/src/fccfg.c:2080: multiple...when enabling the static linkage, the following errors happens:
```
CCLD test-bz106632
/usr/bin/ld: ../src/.libs/libfontconfig.a(fccfg.o): in function `IA__FcConfigHome':
/home/tagoh/work/repo/fontconfig/src/fccfg.c:2080: multiple definition of `IA__FcConfigHome'; test_bz106632-test-bz106632.o:/home/tagoh/work/repo/fontconfig/test/test-bz106632.c:167: first defined here
/usr/bin/ld: ../src/.libs/libfontconfig.a(fclang.o): in function `IA__FcLangNormalize':
/home/tagoh/work/repo/fontconfig/src/fclang.c:183: multiple definition of `IA__FcLangNormalize'; test_bz106632-test-bz106632.o:/home/tagoh/work/repo/fontconfig/test/test-bz106632.c:161: first defined here
```Akira TAGOHAkira TAGOHhttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/110~/.fonts.conf not respected2018-09-05T12:21:21ZEvangelos Foutras~/.fonts.conf not respectedI believe d1f48f11d5dffa1d954a1b0abe44ce9e4bfc3709 breaks reading ~/.fonts.conf. Looking at the code, the `*url == '~'` case does not seem to be handled properly (`file` gets overwritten by code that was previously under a different case...I believe d1f48f11d5dffa1d954a1b0abe44ce9e4bfc3709 breaks reading ~/.fonts.conf. Looking at the code, the `*url == '~'` case does not seem to be handled properly (`file` gets overwritten by code that was previously under a different case in the switch statement).Akira TAGOHAkira TAGOHhttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/112Font update lets Opera and Vivaldi crash2018-09-19T10:28:48ZWalter BishopFont update lets Opera and Vivaldi crashA few days ago I updated my font cache because a game needed windows fonts. I followed the Arch Wiki to copy the W10 fonts and regenerated the fontconfig cache.
https://wiki.archlinux.org/index.php/Microsoft_fonts#Using_fonts_from_a_Win...A few days ago I updated my font cache because a game needed windows fonts. I followed the Arch Wiki to copy the W10 fonts and regenerated the fontconfig cache.
https://wiki.archlinux.org/index.php/Microsoft_fonts#Using_fonts_from_a_Windows_partition
When Opera or Vivaldi are started via the terminal I get the same output from both.
Vivali output https://8n1.org/13727/bb20
Opera output https://8n1.org/13728/3a56
The only difference is that Opera repeats the process four times, while Vivaldi stops after one try.
Chromium, the mother, is not affected. Just as Firefox or any other program I use regularly.
Arch Linux 4.18.7
Cinnamon 3.8.8
mesa 18.2https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/58fontconfig cache creation takes a long time during GIMP startup2018-10-02T06:09:00ZBugzilla Migration Userfontconfig cache creation takes a long time during GIMP startup## Submitted by Michael Schumacher
Assigned to **fon..@..op.org**
**[Link to original bug (#101820)](https://bugs.freedesktop.org/show_bug.cgi?id=101820)**
## Description
On Microsoft Windows platforms, the first start of an appli...## Submitted by Michael Schumacher
Assigned to **fon..@..op.org**
**[Link to original bug (#101820)](https://bugs.freedesktop.org/show_bug.cgi?id=101820)**
## Description
On Microsoft Windows platforms, the first start of an application using fontconfig can be the first time the fontconfig cache is actually created.
For GIMP, we get the occasionally bug report that this takes a very long time on startup, on every DST change (due to how MS Windows reports file modification dates), and sometimes "every time".
We take that last one with several grains of salt, because "every time" may just be "I noticed it the last time I started GIMP, and oops it doesn't happen just now...".
Anyway, in bug https://bugzilla.gnome.org/show_bug.cgi?id=782676 there is a description of what is happening to some users upgrading to GIMP 2.8.22 right now - including a copy of the fontconfig cache folder which allows to reproduce the issue.
Maybe someone working on fontconfig can shed some light on the issue, and tells us whether this is an issue in fontconfig, or in the way it is packaged in the GIMP installers, or the way it is used by GIMP?
### See also
* [Bug 782676](https://bugzilla.gnome.org/show_bug.cgi?id=782676)
* https://bugs.freedesktop.org/show_bug.cgi?id=99360https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/45X11 fc-cache and XQuartz fc-cache disagree, causing 100% CPU at every start o...2018-10-02T06:36:46ZBugzilla Migration UserX11 fc-cache and XQuartz fc-cache disagree, causing 100% CPU at every start of XQuartz## Submitted by Jörg Höhle
Assigned to **fon..@..op.org**
**[Link to original bug (#100278)](https://bugs.freedesktop.org/show_bug.cgi?id=100278)**
## Description
Hi,
I recently installed XQuartz 2.7.11 (incl. fontconfig 2.12) on...## Submitted by Jörg Höhle
Assigned to **fon..@..op.org**
**[Link to original bug (#100278)](https://bugs.freedesktop.org/show_bug.cgi?id=100278)**
## Description
Hi,
I recently installed XQuartz 2.7.11 (incl. fontconfig 2.12) on my OSX 10.6.8 64 bit Mac Mini machine, upgrading from Apple's X11 (2.3.6). When XQuartz starts, the CPU gets 100% busy for one minute, while two instances of fc-cache produce error messages. One instance is reported as org.macosforge.xquartz.privileged_startx, the other is org.macosforge.xquartz.startx in Konsole.app.
What seems to distinguish my bug report from other ones about fc-cache is that X11 fc-cache and XQuartz disagree. X11 fc-cache finds everything is fine, while XQuartz fc-cache wants to recache *every* directory and fails at that, each time XQuartz starts.
Otherwise, it seems very similar to the old https://github.com/XQuartz/xquartz-old-tickets/blob/master/ticket/820.md about 2.7.5.
So the issue is:
A) Either disagreement is normal, e.g. because the file format changed; (But then, how can X11 still run after installing XQuartz?)
In that case, the present issue is about a bug in the XQuartz installer process, which should have generated proper caches initially.
B) Or XQuartz fc-cache is wrong, for whatever reason; the caches are fine and fc-cache should be quiet and exit fast.
I don't believe that the installation process failed. "ls -alt" shows that some root-owned files named fonts.* were created when I installed XQuartz last week:
$ LANG=C ls -alt /opt/X11/share/fonts/misc
-rw-r--r-- 1 root wheel 32637 Mar 12 20:50 fonts.dir
drwxr-xr-x 416 root wheel 14144 Mar 12 20:49 .
-rw-r--r-- 1 root wheel 4268 Mar 12 20:49 encodings.dir
-rw-r--r-- 1 root wheel 2 Mar 12 20:49 fonts.scale
-rw-r--r-- 1 root wheel 19562 Mar 12 20:49 fonts.list
-rw-r--r-- 1 root wheel 6270 Oct 7 19:23 fonts.alias
-rw-r--r-- 1 root wheel 1371 Oct 7 19:23 olcursor.pcf.gz
[...]
Note that in /usr/X11R6/lib/X11/fonts/ no files were updated, except in encodings/
$ ls -alt /usr/X11R6/lib/X11/fonts/misc
-rw-r--r-- 1 root wheel 32637 Feb 2 2013 fonts.dir
drwxr-xr-x 416 root wheel 14144 Feb 2 2013 .
-rw-r--r-- 1 root wheel 4456 Feb 2 2013 encodings.dir
-rw-r--r-- 1 root wheel 2 Feb 2 2013 fonts.scale
[...]
$ ls -alt /usr/X11R6/lib/X11/fonts/encodings
drwxr-xr-x 38 root wheel 1292 Mar 19 09:07 .
-rw-r--r-- 1 root wheel 4456 Mar 19 09:07 encodings.dir
drwxr-xr-x 12 root wheel 408 May 19 2009 ..
-rw-r--r-- 1 root wheel 616 May 19 2009 microsoft-cp1250.enc.gz
[...]
Is that how the files should be?
What I don't understand is why xquartz.privileged_startx equally fails to write caches, as it seems to run as root, whereas xquartz.startx runs under the normal login UID, according to the Activity Monitor.app.
Here is X11's fc-cache -v output (edited for brevity):
/usr/X11/lib/X11/fonts: skipping, existing cache is valid: 0 fonts, 10 dirs
/usr/X11/..fonts/100dpi: skipping, existing cache is valid: 398 fonts, 0 dirs
[...]
/usr/X11/..fonts/encodings: skipping, existing cache is valid: 0 fonts, 1 dirs
/usr/X11/..fonts/encodings/large: skipping, existing cache is valid: 0 fonts, 0 dirs
/usr/X11/..fonts/misc: skipping, existing cache is valid: 59 fonts, 0 dirs
/usr/X11/..fonts/util: skipping, existing cache is valid: 0 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts: skipping, existing cache is valid: 0 fonts, 10 dirs
/usr/X11R6/..fonts/100dpi: skipping, existing cache is valid: 398 fonts, 0 dirs
[...]
/usr/X11R6/..fonts/encodings: skipping, existing cache is valid: 0 fonts, 1 dirs
/usr/X11R6/..fonts/encodings/large: skipping, existing cache is valid: 0 fonts, 0 dirs
/usr/X11R6/..fonts/misc: skipping, existing cache is valid: 59 fonts, 0 dirs
/usr/X11R6/..fonts/util: skipping, existing cache is valid: 0 fonts, 0 dirs
/Users/foobar/.fonts: skipping, no such directory
/System/Library/Fonts: skipping, existing cache is valid: 69 fonts, 0 dirs
/Library/Fonts: skipping, existing cache is valid: 211 fonts, 0 dirs
/Users/foobar/Library/Fonts: skipping, existing cache is valid: 0 fonts, 0 dirs
/usr/X11/var/cache/fontconfig: not cleaning unwritable cache directory
/Users/foobar/.fontconfig: cleaning cache directory
fc-cache: succeeded
For comparison, XQuartz output:
$ time fc-cache -v
/opt/X11/share/fonts: caching, new cache contents: 0 fonts, 10 dirs
/opt/X11/share/fonts: failed to write cache
/opt/X11/share/fonts/100dpi: caching, new cache contents: 398 fonts, 0 dirs
/opt/X11/share/fonts/100dpi: failed to write cache
[...]
/opt/X11/share/fonts/encodings: caching, new cache contents: 0 fonts, 1 dirs
/opt/X11/share/fonts/encodings: failed to write cache
/opt/X11/share/fonts/encodings/large: caching, new cache contents: 0 fonts, 0 dirs
/opt/X11/share/fonts/encodings/large: failed to write cache
/opt/X11/share/fonts/misc: caching, new cache contents: 59 fonts, 0 dirs
/opt/X11/share/fonts/misc: failed to write cache
/opt/X11/share/fonts/util: caching, new cache contents: 0 fonts, 0 dirs
/opt/X11/share/fonts/util: failed to write cache
/usr/X11R6/lib/X11/fonts: caching, new cache contents: 0 fonts, 10 dirs
/usr/X11R6/lib/X11/fonts: failed to write cache
/usr/X11R6/lib/X11/fonts/100dpi: caching, new cache contents: 398 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts/100dpi: failed to write cache
[...]
/usr/X11R6/lib/X11/fonts/encodings: caching, new cache contents: 0 fonts, 1 dirs
/usr/X11R6/lib/X11/fonts/encodings: failed to write cache
/usr/X11R6/lib/X11/fonts/encodings/large: caching, new cache contents: 0 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts/encodings/large: failed to write cache
/usr/X11R6/lib/X11/fonts/misc: caching, new cache contents: 59 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts/misc: failed to write cache
/usr/X11R6/lib/X11/fonts/util: caching, new cache contents: 0 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts/util: failed to write cache
/Users/foobar/.local/share/fonts: skipping, no such directory
/Users/foobar/.fonts: skipping, no such directory
/System/Library/Fonts: caching, new cache contents: 61 fonts, 0 dirs
/System/Library/Fonts: failed to write cache
/Library/Fonts: caching, new cache contents: 218 fonts, 0 dirs
/Library/Fonts: failed to write cache
/Users/foobar/Library/Fonts: caching, new cache contents: 0 fonts, 0 dirs
/Users/foobar/Library/Fonts: failed to write cache
/opt/X11/var/cache/fontconfig: not cleaning unwritable cache directory
/Users/foobar/.cache/fontconfig: cleaning cache directory
/Users/foobar/.fontconfig: cleaning cache directory
fc-cache: failed
real 0m54.362s
user 0m49.486s
sys 0m1.398s
So do X11 and XQuartz 2.7.11 share a common (or at least downward compatible) cache format?
What's causing XQuartz to believe the caches need rebuilding?
Is it expected that two occurrances of fc-cache run concurrently (privileged and regular startx)?
Note that above, both versions of fc-cache disagree about the number of fonts in /System/Library/Fonts and /Library/Fonts. How comes? There's no such difference about /usr/X11R6/lib/X11/fonts.
The good news is that e.g. xterm opens way before fc-cache completes.
BTW, Konsole also shows, alas without line number, 3 occurrences of
org.macosforge.xquartz.startx expr: syntax error
The Mac mini machine is almost bare bones, with very few apps installed (parts of XCode, perhaps remnants of an XQuartz from Leopard before the migration to Snow Leopard)
Thank you for your work on X11/XQuartz,
Jörg Höhle
Version: 2.12https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/84fontconfig test fails2018-10-02T06:43:34ZBugzilla Migration Userfontconfig test fails## Submitted by Petr Gajdos
Assigned to **fon..@..op.org**
**[Link to original bug (#47704)](https://bugs.freedesktop.org/show_bug.cgi?id=47704)**
## Description
Test fails imho because of wrong out.expected.
fontconfig-2.9.0/tes...## Submitted by Petr Gajdos
Assigned to **fon..@..op.org**
**[Link to original bug (#47704)](https://bugs.freedesktop.org/show_bug.cgi?id=47704)**
## Description
Test fails imho because of wrong out.expected.
fontconfig-2.9.0/test[1]> for i in 4x6.pcf 8x16.pcf ; do fc-query $i; done | grep "family\|size"
Pattern has 18 elts (size 32)
family: "Misc Fixed"(s)
pixelsize: 6(f)(s)
Pattern has 18 elts (size 32)
family: "Sony Fixed"(s)
pixelsize: 16(f)(s)
fontconfig-2.9.0/test[0]> cat out.expected
Fixed:pixelsize=16
Fixed:pixelsize=6
=
Fixed:pixelsize=16
Fixed:pixelsize=6
=
Fixed:pixelsize=16
Fixed:pixelsize=6
fontconfig-2.9.0/test> cat out
Misc Fixed:pixelsize=6
Sony Fixed:pixelsize=16
=
Misc Fixed:pixelsize=6
Sony Fixed:pixelsize=16
=
Misc Fixed:pixelsize=6
Sony Fixed:pixelsize=16
Version: 2_1https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/81Add caching of PostScript names2018-10-02T06:56:38ZBugzilla Migration UserAdd caching of PostScript names## Submitted by Isaiah Beerbower
Assigned to **fon..@..op.org**
**[Link to original bug (#18095)](https://bugs.freedesktop.org/show_bug.cgi?id=18095)**
## Description
Created attachment 19703
A patch which adds the desired feature...## Submitted by Isaiah Beerbower
Assigned to **fon..@..op.org**
**[Link to original bug (#18095)](https://bugs.freedesktop.org/show_bug.cgi?id=18095)**
## Description
Created attachment 19703
A patch which adds the desired feature.
I am working on GNUstep's (http://www.gnustep.org/) font support. One
of GNUstep's goals is to implement the OpenStep specification
(http://www.gnustep.org/resources/OpenStepSpec.pdf.gz). Fontconfig is
already being used by GNUstep, however, in order to properly implement
the OpenStep standard the PostScript name should be used to uniquely
reference a font. Right now GNUstep is using the full font name,
however, it would be better if the PostScript name was cached so that
it could be used instead.
I've attached a patch (postscript_name.diff) which implements this functionality.
Related are these threads:
http://lists.freedesktop.org/archives/fontconfig/2008-October/003028.html
http://lists.freedesktop.org/archives/fontconfig/2008-June/002957.html
**Patch 19703**, "A patch which adds the desired feature.":
[postscript_name.diff](/uploads/68287e1245efb05d6fc80d61cf74573b/postscript_name.diff)
Version: 2_1https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/89Consider moving fontconfig-monitor into fontconfig tree2018-10-02T07:28:29ZBugzilla Migration UserConsider moving fontconfig-monitor into fontconfig tree## Submitted by Behdad Esfahbod
Assigned to **fon..@..op.org**
**[Link to original bug (#101997)](https://bugs.freedesktop.org/show_bug.cgi?id=101997)**
## Description
The code at:
https://github.com/behdad/fontconfig-monitor## Submitted by Behdad Esfahbod
Assigned to **fon..@..op.org**
**[Link to original bug (#101997)](https://bugs.freedesktop.org/show_bug.cgi?id=101997)**
## Description
The code at:
https://github.com/behdad/fontconfig-monitorhttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/107fc-cache on empty directory prints an error2018-10-05T02:42:54ZEvangelos Foutrasfc-cache on empty directory prints an errorStarted with f5dd8512bdf9fd8e01c30ae36f593758b29385cf and [affects](https://bugs.archlinux.org/task/59889) Arch Linux users upgrading to fontconfig 2.13.1.
It appears to be a cosmetic issues only, since it only happens with directories ...Started with f5dd8512bdf9fd8e01c30ae36f593758b29385cf and [affects](https://bugs.archlinux.org/task/59889) Arch Linux users upgrading to fontconfig 2.13.1.
It appears to be a cosmetic issues only, since it only happens with directories that contain no fonts.
```
$ mkdir empty-test-dir
$ fc-cache empty-test-dir
/../../empty-test-dir: failed to write cache
```Akira TAGOHAkira TAGOHhttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/122I think, `FcDirCacheDeleteUUID()` should not be called from `FcDirCacheRead()`2018-10-08T12:53:24ZRinat IbragimovI think, `FcDirCacheDeleteUUID()` should not be called from `FcDirCacheRead()``FcDirCacheDeleteUUID()` is called from `FcDirCacheRead()`.
But why so often? Say, there are `.uuid` files in empty directories. They shouldn't cause any issues. If package manager wants to clear those files, it can call `fc-cache -r`. ...`FcDirCacheDeleteUUID()` is called from `FcDirCacheRead()`.
But why so often? Say, there are `.uuid` files in empty directories. They shouldn't cause any issues. If package manager wants to clear those files, it can call `fc-cache -r`. Package managers already call `fc-cache` in post-inst scripts, so there should be any difficulties with running it in pre-rm scripts too.
There are no ways to unlink file and change directory in an atomic way. There always will be a gap. More often there are directory modifications due to UUID removal, more opportunities to cause some application to eat CPU. On the other hand, if `FcDirCacheRead()` will no longer call `FcDirCacheDeleteUUID()`, there will be no need to change mtime back: font installations are usually rare.
[1] https://gitlab.freedesktop.org/fontconfig/fontconfig/commit/f5dd8512bdf9fd8e01c30ae36f593758b29385cf#1ef5b33055f6cfe48c7e8807ab69a8dadd818bc5_424_429
[2] https://gitlab.freedesktop.org/fontconfig/fontconfig/merge_requests/7https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/128Remove broken bengali mono font name entry from 65-nonlatin.conf2018-10-29T12:44:37ZMahfuzur RahmanRemove broken bengali mono font name entry from 65-nonlatin.conf( On Linux Mint 18)
```
$ fc-list :mono:lang=bn
/usr/share/fonts/truetype/fonts-beng-extra/mitra.ttf: Mitra Mono,\\u09ae\\u09bf\\u09a4\\u09cd\\u09b0:style=Regular
```
There seems to be only one mono font for Bengali language available w...( On Linux Mint 18)
```
$ fc-list :mono:lang=bn
/usr/share/fonts/truetype/fonts-beng-extra/mitra.ttf: Mitra Mono,\\u09ae\\u09bf\\u09a4\\u09cd\\u09b0:style=Regular
```
There seems to be only one mono font for Bengali language available which is Mitra Mono. But sadly this mono font cannot render Bangla(bn) correctly. Bangla is complex script font, for which there's currently no mono font available AFAIK.
The font itself is broken if I'm correct. It's listed as mono,serif,sans-serif. But ironically it can't show bangla correctly.
```
$ fc-list :sans | grep -i mitra && fc-list :serif | grep -i mitra && fc-list :mono | grep -i mitra
/usr/share/fonts/truetype/fonts-beng-extra/mitra.ttf: Mitra Mono,\\u09ae\\u09bf\\u09a4\\u09cd\\u09b0:style=Regular
/usr/share/fonts/truetype/fonts-beng-extra/mitra.ttf: Mitra Mono,\\u09ae\\u09bf\\u09a4\\u09cd\\u09b0:style=Regular
/usr/share/fonts/truetype/fonts-beng-extra/mitra.ttf: Mitra Mono,\\u09ae\\u09bf\\u09a4\\u09cd\\u09b0:style=Regular
```
Test file: [nde.txt](/uploads/f8953aa6cdaab675215960ce5815326f/nde.txt)
This font has highest priority for bangla mono selection. For a system that has this installed, opening files in text editor looks like this:
![screenshot-2018-10-26_15-35-57](/uploads/3cdd6f203606a5ce9e2d164dde8a8c94/screenshot-2018-10-26_15-35-57.png)
This(above) is unreadable.
![screenshot-2018-10-25_16-00-41](/uploads/2e96375940e2bdc304ad7a645dcfeb56/screenshot-2018-10-25_16-00-41.png)
Above is "Noto Sans Bengali" which correctly shows Bangla.
So I'm requesting to remove https://gitlab.freedesktop.org/fontconfig/fontconfig/blob/master/conf.d/65-nonlatin.conf#L178 entry.
Without Mitra mono font Bangla shows with `Lohit Bengali` which has correct rendering.
![screenshot-2018-10-26_15-55-21](/uploads/d5da6339ece5385e0f8354ec0d38e695/screenshot-2018-10-26_15-55-21.png)
There are at least three other fonts that can't show bangla correctly
1) Ani 2)FreeSans 3)FreeSerif
These 3 have problems with bangla ligatures.Akira TAGOHAkira TAGOHhttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/131FTBFS on hurd-i3862018-11-06T08:33:23ZLaurent BigonvilleFTBFS on hurd-i386Hello,
Apparently since 2.13, fontconfig FTBFS on hurd-i386.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912699 with the included patch
ThanksHello,
Apparently since 2.13, fontconfig FTBFS on hurd-i386.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912699 with the included patch
ThanksAkira TAGOHAkira TAGOHhttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/132Problems relating xfsettingsd and fontconfig on Fedora 292018-11-07T09:22:46ZpolemonProblems relating xfsettingsd and fontconfig on Fedora 29After upgrading from Fedora 28 to Fedora 29, I noticed a problem with xfsettingsd.
It will lock up the system every five seconds or so, for about one second. This happens right after logging in. A quick remedy is to kill xfsettingsd.
Ru...After upgrading from Fedora 28 to Fedora 29, I noticed a problem with xfsettingsd.
It will lock up the system every five seconds or so, for about one second. This happens right after logging in. A quick remedy is to kill xfsettingsd.
Running xfsettingsd again, it seems things are alright, until I open a terminal emulator, then the problem starts anew, and necessitates killing xfsettingsd.
Originally, I thought this was related to terminal emulators or vte3, but it turns out this is a fontconfig issue, most likely.
Other people have apparently been hit with the problem, using a different distro, so it's not purely Fedora related:
https://forums.kali.org/showthread.php?42495-xfsettingsd(xfce4-settings)-cause-the-pc-freeze-every-two-or-three-seconds
There is a reference to this commit: https://gitlab.freedesktop.org/fontconfig/fontconfig/commit/5f12f564f8748deaa603adb7a4b8f616b6390ad4
Is that the solution to that issue, and I should simply wait for an update, or is there something I can or must do, to alleviate the problem?
Unfortunately, I can't find any error messages to narrow the problem down, if there is a way for me to provide further information, please tell me so.
Thanks,
--pbhttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/133<description> configuration XML element not documented2018-11-15T12:19:49ZDamien Flament<description> configuration XML element not documentedThe `<description>` XML element can be used in the *.conf configuration files to describe their goal. That description is shown by the `fc-conflist` command.
But the user documentation at `doc/fontconfig-user.sgml` does not mention it.The `<description>` XML element can be used in the *.conf configuration files to describe their goal. That description is shown by the `fc-conflist` command.
But the user documentation at `doc/fontconfig-user.sgml` does not mention it.https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/135Minus charset in scan doesn't work2018-11-27T07:03:51ZMarguerite SuMinus charset in scan doesn't workHi,
I am currently working on blacklisting whitespace char (0x0020) from Noto Color Emoji.
And I know it's possible because of this fixed [bug#31969](https://bugs.freedesktop.org/show_bug.cgi?id=31969)
But unluckily it doesn't work.
...Hi,
I am currently working on blacklisting whitespace char (0x0020) from Noto Color Emoji.
And I know it's possible because of this fixed [bug#31969](https://bugs.freedesktop.org/show_bug.cgi?id=31969)
But unluckily it doesn't work.
I created a testcase like the original bug reporter Akira TAGOH:
<match target="scan">
<test name="family">
<string>VL Gothic</string>
</test>
<edit name="charset" mode="assign">
<minus>
<name>charset</name>
<charset>
<range>
<int>0x0030</int>
<int>0x00FF</int>
</range>
</charset>
</minus>
</edit>
</match>
I should get result like this:
FcConfigSubstitute test scan any family Equal "VL Gothic"
Substitute match
scan any family Equal "VL Gothic"
edit
Edit charset Assign charset Minus charset
;
Append list before
Append list after
0000: 00000000 ffffffff fffffffe 7fffffff 00000000 ffffffff ffffffff fff
fffff
But I can only find the first part. There is no 'Append list after' stuff at all. I doubt if it is applied.
And in the final match, I can still view lots of chars that should be substracted:
FcConfigSubstitute editPattern has 42 elts (size 48)
family: "VL Gothic"(s) "VL ゴシック"(s)
...
charset:
...
0030: ffffffff 38ff0001 fffffffe ffffffff fe7fffff ffffffff ffffffff ffffffff
0031: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ffff0000
0032: 00000000 ffffffff fffe000f 00000000 ffffffff ffffffff ffffffff 7fffffff
0033: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff 7fffffff
0047: 80001000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
...
It doesn't seem to work at all.
Am I missing something? or this feature has been removed from fontconfig?
I think something introduced in 2010.12 should work after so many years...
Greetings
Margueritehttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/134Incorrect files passed to stat when --sysroot option is used2018-11-27T09:37:47ZChris McDonaldcjmcdonald@chromium.orgIncorrect files passed to stat when --sysroot option is usedWhen the --sysroot option is used, all paths should be prepended with the provided sysroot. This behavior is correct for cache generation, but fc-cache provides the file paths *without* the sysroot to stat to see if the file exists. This...When the --sysroot option is used, all paths should be prepended with the provided sysroot. This behavior is correct for cache generation, but fc-cache provides the file paths *without* the sysroot to stat to see if the file exists. This leads to it checking file paths that are unrelated to the actual files fc-cache builds the cache from.https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/139Should Fontconfig read ~/.local/share/fonts first, then /usr/share/fonts ?2019-01-01T09:56:38Z王擎Should Fontconfig read ~/.local/share/fonts first, then /usr/share/fonts ?I want to use newer fonts in ~, but this's fonts with the same name in ~
```html
<!-- /usr/share/fonts/fonts.conf -->
<dir>/usr/share/fonts</dir>
<dir>/usr/share/X11/fonts/Type1</dir> <dir>/usr/share/X11/fonts/TTF</dir> <dir>/usr/local/...I want to use newer fonts in ~, but this's fonts with the same name in ~
```html
<!-- /usr/share/fonts/fonts.conf -->
<dir>/usr/share/fonts</dir>
<dir>/usr/share/X11/fonts/Type1</dir> <dir>/usr/share/X11/fonts/TTF</dir> <dir>/usr/local/share/fonts</dir>
<dir prefix="xdg">fonts</dir>
```
I think it's better to make the last line top, before the /usr fonts.https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/142undefined reference Error2019-01-09T13:25:44ZMilav Soniundefined reference ErrorHello Friends,
My name is Milav Soni From Teq Diligent.
I downloaded **fontconfig-2.13.1** from "*https://www.freedesktop.org/software/fontconfig/release/*" site.
I want to cross-compile it for ARM processor.
I am successful with ./c...Hello Friends,
My name is Milav Soni From Teq Diligent.
I downloaded **fontconfig-2.13.1** from "*https://www.freedesktop.org/software/fontconfig/release/*" site.
I want to cross-compile it for ARM processor.
I am successful with ./configure command.
But when i run make command i face following error.
```
make[2]: Entering directory `/home/teqdiligent/HMI_SCADA/Phytec_Lib/fontconfig/fontconfig-2.13.1/fc-cache'
CCLD fc-cache
../src/.libs/libfontconfig.so: undefined reference to `FT_Get_Sfnt_Name_Count'
../src/.libs/libfontconfig.so: undefined reference to `FT_Load_Glyph'
../src/.libs/libfontconfig.so: undefined reference to `FT_Load_Sfnt_Table'
../src/.libs/libfontconfig.so: undefined reference to `FT_Get_Postscript_Name'
../src/.libs/libfontconfig.so: undefined reference to `uuid_unparse'
../src/.libs/libfontconfig.so: undefined reference to `FT_Done_Face'
../src/.libs/libfontconfig.so: undefined reference to `uuid_copy'
../src/.libs/libfontconfig.so: undefined reference to `FT_Done_FreeType'
../src/.libs/libfontconfig.so: undefined reference to `FT_Set_Var_Design_Coordinates'
../src/.libs/libfontconfig.so: undefined reference to `FT_Get_Advance'
../src/.libs/libfontconfig.so: undefined reference to `FT_New_Face'
../src/.libs/libfontconfig.so: undefined reference to `FT_Init_FreeType'
../src/.libs/libfontconfig.so: undefined reference to `FT_Get_First_Char'
../src/.libs/libfontconfig.so: undefined reference to `FT_Select_Charmap'
../src/.libs/libfontconfig.so: undefined reference to `FT_Get_Sfnt_Table'
../src/.libs/libfontconfig.so: undefined reference to `FT_Get_MM_Var'
../src/.libs/libfontconfig.so: undefined reference to `uuid_generate_random'
../src/.libs/libfontconfig.so: undefined reference to `FT_Select_Size'
../src/.libs/libfontconfig.so: undefined reference to `FT_Get_Char_Index'
../src/.libs/libfontconfig.so: undefined reference to `uuid_parse'
../src/.libs/libfontconfig.so: undefined reference to `FT_Get_Next_Char'
../src/.libs/libfontconfig.so: undefined reference to `FT_Get_Sfnt_Name'
collect2: error: ld returned 1 exit status
make[2]: *** [fc-cache] Error 1
```
I also attach the config.log file.[config.log](/uploads/60b1539dc007a4b637433d45b79e655c/config.log)
If i am missing any library to add?
I also attached the ./configure ... result.
[configure_status](/uploads/5e7abe18222fcc782232adbaefbb49e1/configure_status)
please help me sort out this problem.https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/140null-pointer check in FcConfigEvaluate2019-01-23T06:50:41ZThomas E. Dickeynull-pointer check in FcConfigEvaluateFcConfigEvaluate does not check if its "e" parameter is null, causing a crash. See [Debian #917034](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917034). The suggested patch addresses that problem
[fix-db917034.diff](/uploads/88e...FcConfigEvaluate does not check if its "e" parameter is null, causing a crash. See [Debian #917034](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917034). The suggested patch addresses that problem
[fix-db917034.diff](/uploads/88e7a7841c95cf5ae425b04d321f8647/fix-db917034.diff)Akira TAGOHAkira TAGOH