| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | | |
Replace gtk-doc'isms and use gi-docgen links instead.
|
| | |
| | |
| | |
| | | |
Replace gtk-doc'isms and use gi-docgen links instead.
|
| | |
| | |
| | |
| | | |
Replace gtk-doc'isms and use gi-docgen links instead.
|
| | |
| | |
| | |
| | | |
Replace gtk-doc'isms and use gi-docgen links instead.
|
| | |
| | |
| | |
| | | |
Replace gtk-doc'isms and use gi-docgen links instead.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Stop using gtk-doc, and switch to gi-docgen.
The gi-docgen tool generates API references through the introspection
data, which has various benefits:
- it does not parse C code
- it does not generate and run C code to introspect types at build time
- it does not present a different API from the one we're exporting
Additionally, gi-docgen:
- does not generate DocBook XML in order to generate HTML
- does not go through xsltproc
- parses proper Markdown
Which makes it markedly faster than gtk-doc has ever been.
|
| | |
| | |
| | |
| | |
| | | |
Add the toml files that will be used to generate docs,
one for each gir file.
|
| | |
| | |
| | |
| | |
| | | |
While we're developing gi-docgen it's better to have it as part
of our build.
|
| | |
| | |
| | |
| | | |
This will be used in the future.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
We want to use pure markdown, since docbook
is going away as the intermediate format.
|
| | |
| | |
| | |
| | |
| | | |
Doing this makes g-ir-scanner pick up the long description,
which is more useful than the struct docs.
|
| | |
| | |
| | |
| | |
| | | |
Remove obsolete implementation details from the
PangoFontMap struct docs.
|
| | |
| | |
| | |
| | |
| | | |
g-ir-scanner picks the long description over the struct
docs, when the id matches.
|
|/ /
| |
| |
| | |
This is in preparation for going to pure markdown.
|
|\ \
| | |
| | |
| | |
| | | |
Markup parse fixes
See merge request GNOME/pango!292
|
| | |
| | |
| | |
| | |
| | | |
Add tests that test some of the corner cases handled
in the previous commit.
|
| | |
| | |
| | |
| | |
| | | |
Don't print extraneous output when we are generating
an .expected file.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The docs state that all chars marked with the accel
marker get an underline. But we were only underlining
the first in each text chunk.
Second, if an underline appears at the end of a text
chunk, or at the end of the text, we would just eat
it, which is unexpected.
|
| | |
| | |
| | |
| | |
| | |
| | | |
And print out the accel_char if we get one back.
This will let us add tests for accel functionality.
|
| |/
| |
| |
| |
| | |
This is in preparation for adding some tests that
will check accel handling.
|
|\ \
| |/
|/|
| |
| | |
Fix attribute splicing
See merge request GNOME/pango!287
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When the 'other' list contains attributes that are
unlimited or exceed the range given to pango_attr_list_splice,
those attributes were 'leaking' out of the range. The visible
effect of this is that the underline of preedit text extends
outside the preedit in some GTK entries.
Fix this by clipping the inserted attributes to the range.
The documentation is not very explicit about this, but I believe
this is the expected behavior.
Tests included.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
fc: Fix an ordering issue
Closes #537
See merge request GNOME/pango!290
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With the recently introduced threading for fontconfig
calls, we introduced an ordering issue where the fontmap
may die before an outstanding thread returns, and then
the code that unrefs the pattern object tries to remove
it from the fontmap cache.
Prevent that by giving each thread a strong ref on the
fontmap while it runs.
Fixes: #537
|
|\ \
| | |
| | |
| | |
| | | |
Speed up font sorting
See merge request GNOME/pango!221
|
| | |
| | |
| | |
| | |
| | | |
Add sysprof marks around the expensive fontconfig
calls, and for when we are waiting on them.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With a big fontconfig configuration, FcInit takes some time
(60-100ms on my system). Doing this work off the main thread
can potentially avoid blocking other work.
To take advantage of this, GTK calls pango_cairo_font_map_get_default()
early to initiate the creation of a fontmap, thereby triggering the
FcInit() call.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
fontconfig is thread-safe, so we can do calls that
can take several milliseconds to complete in a thread.
This patch does that for FcFontSetMatch and FcFontSetSort.
It is a win, at least for FcFontSetSort, since it
reduces the time that the main thread spends in
pango_fc_patterns_get_font_pattern for i > 0 from
around 10 to 6 milliseconds.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We have filtered-by-format lists of fonts available
now, so we should use them to ensure we always operate
on the same set of fonts. Also, fix another case of
passing NULL for the config.
|
|/ /
| |
| |
| |
| |
| | |
The fontconfig configuration changes rarely, so we can avoid
unnecessary work by only doing the filtering by supported formats
once, and keeping the result.
|
|\ \
| |/
|/|
| |
| | |
Fix FcConfig uses
See merge request GNOME/pango!288
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Passing NULL for a config argument in a fontconfig
api means we are using the default configuration,
which may be different from the one the fontmap
is supposed to be using.
Fix an instance of this in pango_fc_face_list_sizes.
|
|/
|
|
|
|
|
|
|
| |
Passing NULL for a config argument in a fontconfig
api means we are using the default configuration,
which may be different from the one the fontmap
is supposed to be using.
Fix an instance of this in pango_fc_fontset_load_next_font.
|
|\
| |
| |
| |
| | |
Ci fixes
See merge request GNOME/pango!286
|
| | |
|
| |
| |
| |
| |
| | |
Remove the dashes that cause the runs to break, and seem
to be causing issues on both Debian and newer Fedora.
|
| | |
|
|/
|
|
|
| |
Switch to Fedora 33, and add the few extra python
packages that gi-docgen needs.
|
|\
| |
| |
| |
| | |
Gir fixes
See merge request GNOME/pango!285
|
| |
| |
| |
| |
| | |
PANGO_VERSION_MIN_REQUIRED is a build utility, and
is not useful as a constant in the gir. Leave it out.
|
| |
| |
| |
| |
| | |
PANGO_MAJOR/MINOR/MICRO_VERSION are useful to have
in the gir.
|
| |
| |
| |
| |
| | |
Add casts to get some defined constants to have
the right type in the gir. The games we play...
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
g-ir-scanner's handling of #defines is really rudimentary,
so we have to trick it to pick up PANGO_ATTR_TO_TEXT_END
as a constant with value 0, and then override the value
with an annotation.
See https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/369
|