Umm, I don't know the docs system enough to fix this one, but would be nice to fix for 2.7.

Same about FcMatchKind

Please is it possible to get the "quality" of the match, so we can report near-total match failures to a human when necessary?

Hmm, I don't see any particular section for the return value in any manpages at all. but some manpages explicitly has the doc for the return value and appears at the description.

If we want to have the return value section, we need to update func.sgml template and docs in .fncs as well.

(In reply to comment #3)
> Please is it possible to get the "quality" of the match, so we can report
> near-total match failures to a human when necessary?

Any patches for suggestion are welcome!

(In reply to comment #3)
> Please is it possible to get the "quality" of the match, so we can report
> near-total match failures to a human when necessary?

The thing is, we don't quite have a way to detect that right now...

Akira, alternatively we can just separate man pages for the return types.

(In reply to comment #6)
> Akira, alternatively we can just separate man pages for the return types.

Hmm, I'm not sure what the section number for those manpages is appropriate since 3 is for the library calls. in most cases that need to explain the members in the structures and the return values, in practice, the relevant manpages contains that description. that makes sense to understand how to use those functions and would be ideal.

That idea would be easier to auto-generate though. I'll research if there are any similar cases.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/86.