aboutsummaryrefslogtreecommitdiff
path: root/src/autofit/afshaper.c
diff options
context:
space:
mode:
authorTreehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com>2023-10-18 03:21:04 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>2023-10-18 03:21:04 +0000
commit8e77a75afbfbe76ed641379d5f73b92cbf37d006 (patch)
treeae363805e8be7812ad3a88ff8f28cd1380d7ac92 /src/autofit/afshaper.c
parente4a6cc6f5bc957b9e282e863832d441c74d71bfa (diff)
parent6487a5bb15b26f09baa84eeed2fdf3bc77be5bf8 (diff)
downloadfreetype-8e77a75afbfbe76ed641379d5f73b92cbf37d006.tar.gz
Merge "Update FreeType to 2.13.2" into main am: 2aeec9fb95 am: 6487a5bb15
Original change: https://android-review.googlesource.com/c/platform/external/freetype/+/2792273 Change-Id: I6e0198bf347cd2898db63dd4ae5e876b178e1391 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Diffstat (limited to 'src/autofit/afshaper.c')
-rw-r--r--src/autofit/afshaper.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/autofit/afshaper.c b/src/autofit/afshaper.c
index 1b8b870e8..abc6f1d29 100644
--- a/src/autofit/afshaper.c
+++ b/src/autofit/afshaper.c
@@ -258,7 +258,7 @@
/*
* We now check whether we can construct blue zones, using glyphs
* covered by the feature only. In case there is not a single zone
- * (this is, not a single character is covered), we skip this coverage.
+ * (that is, not a single character is covered), we skip this coverage.
*
*/
if ( style_class->coverage != AF_COVERAGE_DEFAULT )
@@ -313,9 +313,9 @@
* hinted and usually rendered glyph.
*
* Consider the superscript feature of font `pala.ttf': Some of the
- * glyphs are `real', this is, they have a zero vertical offset, but
+ * glyphs are `real', that is, they have a zero vertical offset, but
* most of them are small caps glyphs shifted up to the superscript
- * position (this is, the `sups' feature is present in both the GSUB and
+ * position (that is, the `sups' feature is present in both the GSUB and
* GPOS tables). The code for blue zones computation actually uses a
* feature's y offset so that the `real' glyphs get correct hints. But
* later on it is impossible to decide whether a glyph index belongs to,