use Pango loaded by Gtk3 to avoid GLib-GObject-CRITICAL and align Pan… #777
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…go API
'use Gtk3' would also set up namespace Pango, based on loader Glib::Object::Introspection. This loader conflicts w/ the common one applied by 'use Pango' (i.e. DynaLoader). So we get lots of CRITIICAL messages in former versions.
This commit has explicit 'use Pango' removed and mismatched interface tuned. Also pango-version related logics are cleaned up as Gtk3 has already required pango >= 1.20 since 3.0.0
Fix #776