fontconfig issueshttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues2022-07-01T06:16:03Zhttps://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/17API redesign2022-07-01T06:16:03ZBugzilla Migration UserAPI redesign## Submitted by Akira TAGOH `@tagoh`
Assigned to **fon..@..op.org**
**[Link to original bug (#48755)](https://bugs.freedesktop.org/show_bug.cgi?id=48755)**
## Description
there are some cases I feel an urge to cleanup/redesign fon...## Submitted by Akira TAGOH `@tagoh`
Assigned to **fon..@..op.org**
**[Link to original bug (#48755)](https://bugs.freedesktop.org/show_bug.cgi?id=48755)**
## Description
there are some cases I feel an urge to cleanup/redesign fontconfig API though, let me add a note here for a chance to do so in the future.
1. the API prefix isn't intuitive to find out where it's included in.
e.g. FcDirCache* in fccache.c but some is in fcdir.c. and some can see in fcfs.c, fslist.c and fcmatch.c. for FcFontSet as well.
2. some APIs is hard to imagine the functionality from the name
e.g. FcDirCacheRead() vs FcDirCacheLoad()
3. FcCacheDir() vs FcConfigGetCacheDirs()
it implies from the name it may behaves similarly but FcCacheDir() returns the font directory at this moment.
4. function doesn't take any structure as its prefix implies
e.g. FcConfigFilename() etc
5. FcConfigAppFontAddFile() and FcConfigAppFontAddDir()
that could be integrated into one and branch if it's a file or a directory?
6. In doc, FcConfigSubstitute() and FcDefaultSubstitute() are required to get FcFontMatch() and FcFontSort() working though, it's actually optional to do in the program. guess there may be a reason to do so but that looks to me like an error of API design.
may update more later...
Version: 2.9https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/14RFE: allow use of iso 15924 codes2022-07-01T06:16:02ZBugzilla Migration UserRFE: allow use of iso 15924 codes## Submitted by Nicolas Mailhot
Assigned to **fon..@..op.org**
**[Link to original bug (#18727)](https://bugs.freedesktop.org/show_bug.cgi?id=18727)**
## Description
There are a lot of scripts in the wild and the most accurate sta...## Submitted by Nicolas Mailhot
Assigned to **fon..@..op.org**
**[Link to original bug (#18727)](https://bugs.freedesktop.org/show_bug.cgi?id=18727)**
## Description
There are a lot of scripts in the wild and the most accurate standard way to specify them is using iso 15924 codes
http://www.unicode.org/iso15924/iso15924-codes.html
Please make it possible to write font patterns using iso 15924 codes in fonts.conf
Version: 2.6https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/8Provide CMap information for CID-keyed fonts2022-07-01T06:16:02ZBugzilla Migration UserProvide CMap information for CID-keyed fonts## Submitted by Akira TAGOH `@tagoh`
Assigned to **fon..@..op.org**
**[Link to original bug (#90161)](https://bugs.freedesktop.org/show_bug.cgi?id=90161)**
## Description
just an idea to make more convenience for PostScript and PDF.## Submitted by Akira TAGOH `@tagoh`
Assigned to **fon..@..op.org**
**[Link to original bug (#90161)](https://bugs.freedesktop.org/show_bug.cgi?id=90161)**
## Description
just an idea to make more convenience for PostScript and PDF.https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/7Regular expression support in comparison for <test>2022-07-01T06:16:02ZBugzilla Migration UserRegular expression support in comparison for <test>## Submitted by Akira TAGOH `@tagoh`
Assigned to **fon..@..op.org**
**[Link to original bug (#40648)](https://bugs.freedesktop.org/show_bug.cgi?id=40648)**
## Description
That would be useful to support the regexp for comparison. ...## Submitted by Akira TAGOH `@tagoh`
Assigned to **fon..@..op.org**
**[Link to original bug (#40648)](https://bugs.freedesktop.org/show_bug.cgi?id=40648)**
## Description
That would be useful to support the regexp for comparison. this possibly would helps to fix Bug#35118 with:
`<match>`
`<test name="lang" compare="regex">`
`<string>`pa.*`</string>`
`</test>`
...
`</match>`
Or Bug#28491 to make the match pattern for the filename only perhaps and Bug#13416 to merge the subfamilies?
Version: 2.8https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/5FcFontList "contain" semantics unproductive2022-07-01T06:16:02ZBugzilla Migration UserFcFontList "contain" semantics unproductive## Submitted by Behdad Esfahbod
Assigned to **fon..@..op.org**
**[Link to original bug (#107246)](https://bugs.freedesktop.org/show_bug.cgi?id=107246)**
## Description
If I want to list only fonts that have fontformat=TrueType or ...## Submitted by Behdad Esfahbod
Assigned to **fon..@..op.org**
**[Link to original bug (#107246)](https://bugs.freedesktop.org/show_bug.cgi?id=107246)**
## Description
If I want to list only fonts that have fontformat=TrueType or fontformat=CFF, currently I can't:
behdad:~ 0$ fc-list :fontformat=truetype,cff
Returns empty.
This is because FcFontList interprets that as returning fonts that have both fontformat=truetype AND fontformat=cff. Code:
```
/*
* Font must have a containing value for every value in the pattern
*/
static FcBool
FcListValueListMatchAny (FcValueListPtr patOrig, /* pattern */
FcValueListPtr fntOrig) /* font */
{
FcValueListPtr pat, fnt;
for (pat = patOrig; pat != NULL; pat = FcValueListNext(pat))
{
for (fnt = fntOrig; fnt != NULL; fnt = FcValueListNext(fnt))
{
/*
* make sure the font 'contains' the pattern.
* (OpListing is OpContains except for strings
* where it requires an exact match)
*/
if (FcConfigCompareValue (&fnt->value,
FC_OP (FcOpListing, FcOpFlagIgnoreBlanks),
&pat->value))
break;
}
if (fnt == NULL)
return FcFalse;
}
return FcTrue;
}
```
I cannot imagine any scenario that this semantic is useful. I suggest we flip it from an AND to an OR.https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/4Use a public identifier for fonts.conf2022-07-01T06:16:02ZBugzilla Migration UserUse a public identifier for fonts.conf## Submitted by Owen Taylor
Assigned to **fon..@..op.org**
**[Link to original bug (#1281)](https://bugs.freedesktop.org/show_bug.cgi?id=1281)**
## Description
We have an open bug for Red Hat that the fonts.conf DTD should
be regi...## Submitted by Owen Taylor
Assigned to **fon..@..op.org**
**[Link to original bug (#1281)](https://bugs.freedesktop.org/show_bug.cgi?id=1281)**
## Description
We have an open bug for Red Hat that the fonts.conf DTD should
be registered in the system catlog so that, e.g., psgml mode can
find it:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=91968
Sounds reasonable to me. But fontconfig currently uses:
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
Using something along the lines of:
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
Would make it possible. (You don't really need both the public identifier
and the URL. I think you can omit either one, but I don't know the
syntax for omitting the public identifier offhand.)
Version: 2.2