summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Correctly use pango-querymodulesbaserock/xfce-buildJonathan Maw2013-09-261-1/+5
|
* add pango.morphPaul Sherwood2013-08-142-1/+9
|
* add pango.morph, to run pango-querymodulesPaul Sherwood2013-08-121-0/+6
|
* Bug 705007 - sometimes the ordering of text is reversedBehdad Esfahbod2013-08-041-0/+2
| | | | Fix all-RTL reordering. Oops!
* Bypass line reordering if all runs have the same directionKristian Rietveld2013-07-171-2/+30
|
* Bump versionMatthias Clasen2013-06-211-1/+1
|
* 1.35.11.35.0Matthias Clasen2013-06-212-2/+10
|
* Avoid hard-dep on bleeding-edge GLibMatthias Clasen2013-06-073-0/+22
| | | | | | If new test api is not available, do without it. In this case, the tests won't work installed, but they should still work uninstalled and in distcheck.
* Don't change fonts just for space charactersBehdad Esfahbod2013-06-061-6/+6
| | | | | | | | | | | | | | | | Back in the days we used to always use the font from surrounding runs for any space characters. I changed that when I found that rendering MathML results in hexboxes when a font doesn't have the space characters needed... Forward to these days: HarfBuzz will silently compatibility-decompose any space character to the ASCII space. And looks like it's important for Mongolian to not break runs around NNBSP. As such, go back to never choosing a font just for space characters. Seems to work, though more testing is needed. Bug 701652 - wrong shaped classic Mongolian word suffixes
* Make tests installableMatthias Clasen2013-05-318-59/+133
| | | | This ensures that tests are run continuously on ostree.gnome.org.
* Bug 700577 - Support invalid UTF-8 chars in pango_find_paragraph_boundary()Behdad Esfahbod2013-05-271-1/+1
|
* build: Add --with(out)-cairo configure optionColin Walters2013-05-241-1/+9
| | | | | | | Some builders (e.g. GNOME and jhbuild) hard depend on pangocairo, and we really don't want to emit a build of pango without support for it. So jhbuild can specify --with-cairo, and we'll get a hard error.
* Require cairo >= 1.12.10Behdad Esfahbod2013-05-151-1/+1
| | | | | | Needed for threadsafety bug fixes. Bug 700247 - test-pangocairo-threads segfaults
* 1.34.11.34.1Matthias Clasen2013-05-131-0/+7
|
* don't break words between a letter adjacent to a numberJosé Aliste2013-05-021-17/+2
| | | | | | | Newer Unicode specs (6.2 for instance) say that one should not break between letter or numbers that are adjacent. This also makes us to match word selection with many text capable apps.
* Fix CoreText font scaling againBehdad Esfahbod2013-05-021-0/+2
| | | | | | | | This partially reverts 25ad29b488d3e2ae10e4fee25602409fa39207f1 which itself was a revert. Apparently we want the change in CoreText, but not on Win32... See mailing list discussion.
* Update win32/coretext shaper signatureBehdad Esfahbod2013-04-262-2/+6
|
* MinorBehdad Esfahbod2013-04-251-1/+1
|
* Bug 696238 - PangoAttrFilterFunc vs pango_attr_list_filter docsBehdad Esfahbod2013-04-041-2/+2
|
* 1.34.01.34.0Matthias Clasen2013-03-252-2/+6
|
* 1.33.10Matthias Clasen2013-03-181-1/+1
|
* 1.33.91.33.9Matthias Clasen2013-03-181-0/+7
|
* Visual Studio Builds: Fix the Debug configsChun-wei Fan2013-03-189-18/+18
| | | | | We need to link to the Debug CRT for debug configs, not the release CRTs, as linking to different CRTs will cause trouble during debugging.
* [test] Fix scaleBehdad Esfahbod2013-03-151-1/+1
|
* Bug 682846 - Use G_DEFINE_TYPE in pangowin32-fontmapBehdad Esfahbod2013-03-153-57/+22
| | | | Based on patch from Chun-wei Fan.
* Call g_type_init if necessaryBehdad Esfahbod2013-03-151-0/+8
|
* Remove unused codeBehdad Esfahbod2013-03-151-25/+1
|
* Port PangoWin32 to use GWeakRefBehdad Esfahbod2013-03-152-10/+10
| | | | Patch from Chun-wei Fan.
* Use g_snprintf()Behdad Esfahbod2013-03-151-1/+1
|
* Update Visual Studio property sheetsChun-wei Fan2013-03-062-16/+57
| | | | Add commands to be used for building introspection files.
* Update Visual Studio Solution filesChun-wei Fan2013-03-062-0/+16
| | | | | | | Integrate the utility project files to build the introspection files. This is not built by default, so one may choose to build the introspection files if he/she chooses
* Visual Studio builds: Support building introspection filesChun-wei Fan2013-03-067-38/+551
| | | | | | | | | | | | | Add Windows .bat and Python utility script to call g-ir-scanner to build the introspection files for Pango/MSVC builds. This will read from pango/Makefile.am to determine the source and header files to process using Python REGEX capabilities, so the autotools files won't have to be updated except to distribute the necessary files under build/win32. Also add utility Visual Studio 2008/2010 projects to call the Windows .bat to create the introspection files. https://bugzilla.gnome.org/show_bug.cgi?id=692255
* Post-release version bumpMatthias Clasen2013-03-041-1/+1
|
* 1.33.81.33.8Matthias Clasen2013-03-042-1/+11
|
* Bug 694882 - build broken - introspection of pangoxft2 and pangoxft miss ↵Behdad Esfahbod2013-03-041-3/+4
| | | | libpang-1.0.la in _gir_LIBS
* Revert "Fix Win32 and CoreText cairo backends to take cairo CTM into account"Behdad Esfahbod2013-03-042-5/+0
| | | | | | | | | | | | | | | This reverts commit b359bb484bc7d27a835cfd6d9ffcaed582ebf2ae. Bug 694918 - Pango layout is rendered in wrong size if we have non-identity cairo transformation matrix I was wrong blindly copying this logic from pangocairo-fc into pangocairo-win32 and pangocairo-quartz. The reason we need the it in pangofc is because the fontsize we get back from fontconfig is multiplied by the ctm scale factor, so we undo it when loading the font. The same is NOT true about the non-fc backends, so the copying was totally wrong.
* Bug 694830 - Fails make check: +pango_font_map_changedBehdad Esfahbod2013-02-271-0/+1
|
* PangoFc: change FontMap in pango_fc_font_map_clear_cache()Alexander Larsson2013-02-261-0/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=694626
* Add pango_font_map_changed()Alexander Larsson2013-02-268-1/+93
| | | | | | | This is needed as a base class sometimes needs to invalidate the fontmap. https://bugzilla.gnome.org/show_bug.cgi?id=694626
* Bug 668154 - GTK+ Crashes on Non BMP utf-8 charpointsBehdad Esfahbod2013-02-251-27/+18
|
* [win32] Fix assertion and warningsBehdad Esfahbod2013-02-252-4/+12
| | | | | | When win32 fontmap goes away, font->fontmap becomes NULL. Deal with that. Technically speaking, we need to port this to GWeakRef like the other fontmaps do. But this would do for now.
* Whitelist pango_cairo_win32_font_map_get_typeBehdad Esfahbod2013-02-191-2/+6
| | | | | | | .def files are mostly used on Win32. Whitelist the win32 font map function in the check. Bug 694095 - Fails make check: -pango_cairo_win32_font_map_get_type
* win32: Remove stale static module definitionsJasper St. Pierre2013-02-172-58/+5
| | | | These have now been put into Harfbuzz upstream
* Updates for 1.33.71.33.7Matthias Clasen2013-02-031-0/+5
|
* Belatedly start an unstable seriesMatthias Clasen2013-02-031-2/+2
| | | | | I really messed up with 1.32.6, which had lots of new, unstable stuff in it.
* pangocairo.def: Export pango_cairo_win32_font_map_get_typeChun-wei Fan2013-01-221-0/+1
| | | | This is needed to build the introspection files for PangoCairo on Windows.
* Prepare Visual Studio 2010 projects for Visual Studio 2012Chun-wei Fan2013-01-186-10/+41
| | | | | | | | | | | | | | This adds a PlatformToolset tag in the project configs so that we can provide support for Visual Studio 2012 with relative ease as the format of the VS 2012 projects are only slightly different from their VS 2010 counterparts. We can then use a script like the one used in GLib[1] to copy the VS2010 projects and replace the necessary tags to create the VS2012 projects. This also cleans up the projects and property sheets, as there were some unwanted/unneeded entries in them. [1]: http://git.gnome.org/browse/glib/commit/?id=76cecf061b377d30e5422cdddb1fb9d19c52421d
* Revert "Don't use the deprecated pango_ft2_font_get_face"Behdad Esfahbod2013-01-172-17/+6
| | | | | | | | | | | | | This reverts commit 2dc0c3dbb1c389c3a3ba12a5c5c85f21dca46e84. This doesn't make sense. It ends up in infinite recursion because pangofc is calling lock_face on pangoft2, which would recursively call it on pangofc... Was causing hang at startup of Inkscape. If the deprecated warnings are an issue, they need to be dealt with in some other way.
* "prgname" and "fontfeatures" are accepted for upstream Fontconfig nowBehdad Esfahbod2013-01-151-2/+6
|
* Let people enable font features through fontconfig snippetsBehdad Esfahbod2013-01-103-1/+38
| | | | | | | | | | | | | Like this: <match target="font"> <edit name="pangofontfeatures" mode="append"> <string>smcp</string> <string>ss20</string> </edit> </match> Finally we are starting to see new features coming out of the HarfBuzz integration...