summaryrefslogtreecommitdiff
path: root/pango
Commit message (Collapse)AuthorAgeFilesLines
* docs: Tweak coverage docsMatthias Clasen2021-03-112-34/+29
| | | | Give doc comments summaries, remove section, etc.
* docs: Tweak color docsMatthias Clasen2021-03-111-14/+21
| | | | Give doc comments summaries, etc.
* docs: Tweak bidi docsMatthias Clasen2021-03-112-19/+22
| | | | Give doc comments summaries, etc.
* docs: Tweak attributes docsMatthias Clasen2021-03-112-45/+57
| | | | Give doc comments summaries, etc.
* docs: Tweak modules docsMatthias Clasen2021-03-111-13/+0
| | | | Drop not-shown section.
* docs: Tweak glyphstring docsMatthias Clasen2021-03-111-44/+52
| | | | Give doc comments summaries, etc.
* docs: Tweak font docsMatthias Clasen2021-03-112-71/+135
| | | | Give doc comments summaries, etc.
* docs: Tweak line breaking docsMatthias Clasen2021-03-111-24/+27
| | | | Give doc comments summaries, etc.
* Drop some useless things from the girMatthias Clasen2021-03-115-5/+21
| | | | | We don't need the deprecated and useless module and engine types in the gir and the docs.
* docs: Port PangoFc apis to the new doc formatMatthias Clasen2021-03-112-107/+118
| | | | | | Replace gtk-doc'isms and use gi-docgen links instead. Cross-gir links are still an open issue.
* docs: Port PangoCairo apis to the new doc formatMatthias Clasen2021-03-114-133/+136
| | | | | | Replace gtk-doc'isms and use gi-docgen links instead. Cross-gir links are still an open issue.
* docs: Port misc. types to the new doc formatMatthias Clasen2021-03-111-3/+3
|
* docs: Port PangoTabArray to the new doc formatMatthias Clasen2021-03-112-77/+68
| | | | Replace gtk-doc'isms and use gi-docgen links instead.
* docs: Port PangoLanguage to the new doc formatMatthias Clasen2021-03-111-67/+65
| | | | Replace gtk-doc'isms and use gi-docgen links instead.
* docs: Port PangoItem to the new doc formatMatthias Clasen2021-03-112-41/+48
| | | | Replace gtk-doc'isms and use gi-docgen links instead.
* docs: Port PangoRenderer to the new doc formatMatthias Clasen2021-03-111-381/+384
| | | | Replace gtk-doc'isms and use gi-docgen links instead.
* docs: Port PangoFontMap to the new doc formatMatthias Clasen2021-03-111-96/+97
| | | | Replace gtk-doc'isms and use gi-docgen links instead.
* docs: Port PangoFont to the new doc formatMatthias Clasen2021-03-112-643/+587
| | | | Replace gtk-doc'isms and use gi-docgen links instead.
* docs: Port PangoAttribute to the new doc formatMatthias Clasen2021-03-112-491/+494
| | | | Replace gtk-doc'isms and use gi-docgen links instead.
* docs: Port PangoLayout to the new doc formatMatthias Clasen2021-03-112-1791/+1766
| | | | Replace gtk-doc'isms and use gi-docgen links instead.
* docs: Port PangoContext to the new doc formatMatthias Clasen2021-03-111-314/+323
| | | | Replace gtk-doc'isms and use gi-docgen links instead.
* docs: Convert the pangocairo section to pango_cairo.mdMatthias Clasen2021-03-111-132/+0
|
* docs: Convert bidi and vertical sections to pango_bidi.mdMatthias Clasen2021-03-112-74/+0
|
* docs: Convert fonts section to pango_fonts.mdMatthias Clasen2021-03-111-13/+0
|
* docs: Convert markup and attributes docs to pango_markup.mdMatthias Clasen2021-03-112-202/+0
|
* docs: Convert rendering section to pango_rendering.mdMatthias Clasen2021-03-111-12/+0
|
* docs: Move PangoRenderer docs to the right fileMatthias Clasen2021-03-112-11/+12
|
* docs: Replace lots of vestigial xml markupMatthias Clasen2021-03-1132-263/+221
| | | | | We want to use pure markdown, since docbook is going away as the intermediate format.
* docs: Make context section ids matchMatthias Clasen2021-03-114-4/+4
| | | | | Doing this makes g-ir-scanner pick up the long description, which is more useful than the struct docs.
* docs: Clean up fontmap docsMatthias Clasen2021-03-111-9/+1
| | | | | Remove obsolete implementation details from the PangoFontMap struct docs.
* docs: Move layout docs into the long descriptionMatthias Clasen2021-03-111-7/+6
| | | | | g-ir-scanner picks the long description over the struct docs, when the id matches.
* docs: Remove xml formatting from PangoLayoutMatthias Clasen2021-03-111-9/+8
| | | | This is in preparation for going to pure markdown.
* Merge branch 'markup-parse-fixes' into 'master'Matthias Clasen2021-03-031-30/+20
|\ | | | | | | | | Markup parse fixes See merge request GNOME/pango!292
| * markup: Fix two bugsMatthias Clasen2021-03-021-30/+20
| | | | | | | | | | | | | | | | | | | | 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.
* | Merge branch 'fix-attribute-splicing' into 'master'Matthias Clasen2021-03-031-2/+5
|\ \ | |/ |/| | | | | Fix attribute splicing See merge request GNOME/pango!287
| * Fix a corner-case of pango_attr_list_splicefix-attribute-splicingMatthias Clasen2021-02-171-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 issuefontmap-thread-fixMatthias Clasen2021-02-241-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | fontconfig: Add some trace marksspeed-up-format-filteringMatthias Clasen2021-02-221-3/+41
| | | | | | | | | | Add sysprof marks around the expensive fontconfig calls, and for when we are waiting on them.
* | Move FcInit call to a threadMatthias Clasen2021-02-221-0/+50
| | | | | | | | | | | | | | | | | | | | 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.
* | Move FcFontMatch and FcFontSort calls to a threadMatthias Clasen2021-02-221-35/+152
| | | | | | | | | | | | | | | | | | | | 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.
* | Use FcFontSetList instead of FcFontListMatthias Clasen2021-02-221-5/+6
| | | | | | | | | | | | | | 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.
* | fc: Only do filtering by format onceMatthias Clasen2021-02-221-23/+58
| | | | | | | | | | | | The fontconfig configuration changes rarely, so we can avoid unnecessary work by only doing the filtering by supported formats once, and keeping the result.
* | Use the right FcConfig for FcFontListfix-FcConfig-usesMatthias Clasen2021-02-221-1/+1
| | | | | | | | | | | | | | | | | | 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.
* | Use the right FcConfig for FcRenderPrepareMatthias Clasen2021-02-221-1/+1
|/ | | | | | | | | 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.
* Leave pango-version-macros.h out of the girgir-fixesMatthias Clasen2021-02-151-2/+3
| | | | | PANGO_VERSION_MIN_REQUIRED is a build utility, and is not useful as a constant in the gir. Leave it out.
* Include version macros in the girMatthias Clasen2021-02-151-2/+2
| | | | | PANGO_MAJOR/MINOR/MICRO_VERSION are useful to have in the gir.
* Trick g-ir-scanner some moreMatthias Clasen2021-02-151-2/+2
| | | | | Add casts to get some defined constants to have the right type in the gir. The games we play...
* Trick g-ir-scannerMatthias Clasen2021-02-151-3/+4
| | | | | | | | | 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
* docs: Remove references to gdk_pango_context_get_for_screendocs-tweakMatthias Clasen2021-02-112-4/+2
| | | | Remove references to a function that no longer exists in gtk.
* Fix pango_font_describe for Emoji fontsMatthias Clasen2021-01-241-1/+18
| | | | | | | | | | | We are using the size from the FcPattern. For scalable bitmap fonts, this has been scaled to match the requested pixel size. To make a font description that can be turned back into a FcPattern and roundtrip successfully, we need to undo that scaling. Thankfully, fontconfig leaves the pixelsizefixupfactor in the pattern, so it is easy to do. Fixes: #530
View Lorry Controller Status