Reuse: Update tests paths in .reuse/dep5

See merge request GNOME/gi-docgen!204

We don't have only functions and methods: we also have callbacks,
signals, and class methods. Some of them need a fairly different
wording.

It's "non-breaking space", not "non-spacing break".

Instead of using a bunch of constant dictionaries, we can group
everything together, so it's easy to update the wording if needed.

generate: Restructure the transfer mode messages

See merge request GNOME/gi-docgen!205

Description texts are already output as one or more paragraphs (with
HTML P tags included), so wrapping them in the templates produces
`<p><p>...</p></p>` in the output. Eliminate the redundant tags.

With the extra P tags removed from the templates, the only time the
description is output without paragraph tags is when it's missing,
and the MISSING_DESCRIPTION text is inserted instead. For consistency,
wrap that text in its own paragraph tags where appropriate.

Fix doubled paragraph tags around descriptions

See merge request GNOME/gi-docgen!206

Since the symbol comes with its own version that may not match the
version of the namespace we are documenting.

template: Skip emblems for inherited symbols

See merge request GNOME/gi-docgen!212

Use exceptions to report errors, instead of returning an error object
that can be stringified into a warning. This allows us to clear up the
state in a much better defined way.

Makes logging actually useful.

Verify that the link parser is erroring out when we expect it to.

And use the passed fragment and endpoint, instead of accessing the
object state, since we can mutate the latter.

A link in the form of [type@Namespace.Object.Value] is invalid: GIR does
not support nested namespaces, so all type definitions must have at most
a namespace and a name.

We can reuse the same fragment, and generate the anchor using an
optional component at the end of the link, e.g.

    [flags@GObject.BindingFlags.SYNC_CREATE]

Similarly for `flags` and `error` types.

Signed-off-by: Philip Withnall <pwithnall@gnome.org>

Resolve to the C identifier, like we do for any other C symbol.

Slice the endpoint using the match results.

Various improvements for LinkGenerator

See merge request GNOME/gi-docgen!215

docs: Mention that [enum@…] can link to enum members too

See merge request GNOME/gi-docgen!214

Any icon added to `content_images` which starts with favicon will be
used as a favicon.

We special case icons ending in AxA for A=32, 128, 180, 192.

See https://www.emergeagency.com/insights/detail/The-Essentials-of-FavIcons/.

Fixes: https://gitlab.gnome.org/GNOME/gi-docgen/-/issues/152

The nickname attribute is only available to members of an enumeration
with a corresponding GType.

We have the style, just needs an icon and a color.

Fixes: #155

They need to be visible, but not overpowering.

template: Omit enum nickname for unregistered enum types

Closes #155

See merge request GNOME/gi-docgen!217

Don't turn the whole member name into a link.

Fixes: #183

template: Add a proper anchor for enum members

Closes #183

See merge request GNOME/gi-docgen!218

Add favicon support

See merge request GNOME/gi-docgen!201

The elif keyword cannot be the first element of an if...endif block.

This results in local builds not showing favicons and also fixes GTK 4
docs at https://docs.gtk.org.

base: Do not start favicon path with /

See merge request GNOME/gi-docgen!219

This reverts commit 4fa286d5.

Turns out that a couple libraries (*cough* WebKitGTK *cough*) don't
match the namespace version with their library version, so the fallback
and the availability become absolute nonsense.

The proper fix is to have the template handle the fallback using the
configuration to determine the base version that introduced a symbol. Or
those libraries stop trying to be too clever for their own good.

Fixes: #179

Revert "generate: Add fallback for missing "since""

Closes #179

See merge request GNOME/gi-docgen!221

After the last line in a block, gi-docgen appends a period. Obviously,
this should not happen when there is already a period. This is handled
by testing for isalpha() on the last character.

However, periods should also be inserted after links or inline code. Fix
this by broadening the cases in which a period is appended.

Fixes #181

The section for extras is called extra according to

    https://gnome.pages.gitlab.gnome.org/gi-docgen/project-configuration.html#the-extra-section

docs: Reference extra instead of extras

See merge request GNOME/gi-docgen!223

The 'filename' type is a misnomer: it means "platform-native string
encoded using the preferred OS encoding".

Fixes: #193

Pass the anchor, if one is set.

Fixes: #191

It works like Markdown links, with the link being a reference instead of
an URL.

Look for the corresponding identifier in the appropriate places if a
finish function is set.

If a function, constructor, or method has a corresponding finish
function, generate a blurb and a link to it in the description.

Fixes: #189

utils: Append period after last line in more cases

Closes #181

See merge request GNOME/gi-docgen!222

GIR added new elements for inline functions.

Fixes: #173

Fixes: #195

If the search has focus, release it on Escape.

Fixes: #194

template: Make the logo a link to the index

Closes #195 and #194

See merge request GNOME/gi-docgen!227

The urlmap file is copied inside the output directory, so it should
always be referred to by its name, not by its path in the project's
configuration file.

Fixes: #197

Various fixes for main

Closes #197, #173, #189, #191, and #193

See merge request GNOME/gi-docgen!228

This is a follow-up to commit 558d7e3d.

Signed-off-by: Philip Withnall <pwithnall@gnome.org>

Fixes: #198

docs: Mention syntax for fragment identifier links to anchors

Closes #198

See merge request GNOME/gi-docgen!229