2012-01-19 21:21:04 +01:00
|
|
|
# Process this file with automake to produce Makefile.in
|
|
|
|
|
|
2012-01-22 01:43:58 +01:00
|
|
|
NULL =
|
|
|
|
|
EXTRA_DIST =
|
|
|
|
|
CLEANFILES =
|
|
|
|
|
DISTCLEANFILES =
|
|
|
|
|
MAINTAINERCLEANFILES =
|
|
|
|
|
|
2012-01-19 21:21:04 +01:00
|
|
|
manifests:
|
2013-10-14 18:47:51 +02:00
|
|
|
@$(srcdir)/hb-manifest-update "$(srcdir)/texts" "$(srcdir)/fonts" "$(srcdir)/tests"
|
2012-01-19 21:43:48 +01:00
|
|
|
|
2012-01-22 01:43:58 +01:00
|
|
|
EXTRA_DIST += \
|
|
|
|
|
hb-diff \
|
2012-05-08 23:41:41 +02:00
|
|
|
hb-diff-colorize \
|
2012-01-22 01:43:58 +01:00
|
|
|
hb-diff-filter-failures \
|
2012-05-09 09:54:54 +02:00
|
|
|
hb-diff-ngrams \
|
2012-05-09 07:45:17 +02:00
|
|
|
hb-diff-stat \
|
2012-01-22 01:43:58 +01:00
|
|
|
hb-manifest-read \
|
|
|
|
|
hb-manifest-update \
|
|
|
|
|
hb-unicode-decode \
|
|
|
|
|
hb-unicode-encode \
|
|
|
|
|
hb-unicode-prettyname \
|
2014-07-16 19:32:51 +02:00
|
|
|
record-test.sh \
|
2013-10-14 18:47:51 +02:00
|
|
|
run-tests.sh \
|
2013-10-28 20:23:07 +01:00
|
|
|
texts/in-tree \
|
|
|
|
|
fonts/sha1sum \
|
|
|
|
|
$(TESTS) \
|
2012-01-22 01:43:58 +01:00
|
|
|
$(NULL)
|
|
|
|
|
|
|
|
|
|
# TODO Figure out Python stuff
|
|
|
|
|
EXTRA_DIST += \
|
|
|
|
|
hb_test_tools.py \
|
|
|
|
|
$(NULL)
|
|
|
|
|
CLEANFILES += \
|
|
|
|
|
hb_test_tools.py[co] \
|
|
|
|
|
$(NULL)
|
|
|
|
|
|
[indic] Don't reorder reph/pref if ligature was expanded
Normally if you want to, say, conditionally prevent a 'pref', you
would use blocking contextual matching. Some designers instead
form the 'pref' form, then undo it in context. To detect that
we now also remember glyphs that went through MultipleSubst.
In the only place that this is used, Uniscribe seems to only care
about the "last" transformation between Ligature and Multiple
substitions. Ie. if you ligate, expand, and ligate again, it
moves the pref, but if you ligate and expand it doesn't. That's
why we clear the MULTIPLIED bit when setting LIGATED.
Micro-test added. Test: U+0D2F,0D4D,0D30 with font from:
[1]
https://code.google.com/a/google.com/p/noto-alpha/issues/detail?id=186#c29
2014-06-04 22:57:42 +02:00
|
|
|
TESTS = \
|
2014-08-05 20:19:01 +02:00
|
|
|
tests/arabic-fallback-shaping.tests \
|
2014-07-17 19:36:09 +02:00
|
|
|
tests/arabic-feature-order.tests \
|
[indic] Don't reorder reph/pref if ligature was expanded
Normally if you want to, say, conditionally prevent a 'pref', you
would use blocking contextual matching. Some designers instead
form the 'pref' form, then undo it in context. To detect that
we now also remember glyphs that went through MultipleSubst.
In the only place that this is used, Uniscribe seems to only care
about the "last" transformation between Ligature and Multiple
substitions. Ie. if you ligate, expand, and ligate again, it
moves the pref, but if you ligate and expand it doesn't. That's
why we clear the MULTIPLIED bit when setting LIGATED.
Micro-test added. Test: U+0D2F,0D4D,0D30 with font from:
[1]
https://code.google.com/a/google.com/p/noto-alpha/issues/detail?id=186#c29
2014-06-04 22:57:42 +02:00
|
|
|
tests/context-matching.tests \
|
2014-08-01 00:51:37 +02:00
|
|
|
tests/hangul-jamo.tests \
|
2014-12-10 21:05:24 +01:00
|
|
|
tests/indic-joiner-candrabindu.tests \
|
2014-07-23 22:48:51 +02:00
|
|
|
tests/indic-old-spec.tests \
|
[indic] Don't reorder reph/pref if ligature was expanded
Normally if you want to, say, conditionally prevent a 'pref', you
would use blocking contextual matching. Some designers instead
form the 'pref' form, then undo it in context. To detect that
we now also remember glyphs that went through MultipleSubst.
In the only place that this is used, Uniscribe seems to only care
about the "last" transformation between Ligature and Multiple
substitions. Ie. if you ligate, expand, and ligate again, it
moves the pref, but if you ligate and expand it doesn't. That's
why we clear the MULTIPLIED bit when setting LIGATED.
Micro-test added. Test: U+0D2F,0D4D,0D30 with font from:
[1]
https://code.google.com/a/google.com/p/noto-alpha/issues/detail?id=186#c29
2014-06-04 22:57:42 +02:00
|
|
|
tests/indic-pref-blocking.tests \
|
2014-07-17 19:36:09 +02:00
|
|
|
tests/mongolian-variation-selector.tests \
|
2014-07-27 01:17:44 +02:00
|
|
|
tests/zero-width-marks.tests \
|
[indic] Don't reorder reph/pref if ligature was expanded
Normally if you want to, say, conditionally prevent a 'pref', you
would use blocking contextual matching. Some designers instead
form the 'pref' form, then undo it in context. To detect that
we now also remember glyphs that went through MultipleSubst.
In the only place that this is used, Uniscribe seems to only care
about the "last" transformation between Ligature and Multiple
substitions. Ie. if you ligate, expand, and ligate again, it
moves the pref, but if you ligate and expand it doesn't. That's
why we clear the MULTIPLIED bit when setting LIGATED.
Micro-test added. Test: U+0D2F,0D4D,0D30 with font from:
[1]
https://code.google.com/a/google.com/p/noto-alpha/issues/detail?id=186#c29
2014-06-04 22:57:42 +02:00
|
|
|
$(NULL)
|
2013-12-05 01:59:48 +01:00
|
|
|
|
|
|
|
|
TEST_EXTENSIONS = \
|
|
|
|
|
.tests \
|
|
|
|
|
$(NULL)
|
|
|
|
|
|
|
|
|
|
AM_TESTS_ENVIRONMENT = \
|
|
|
|
|
EXEEXT="$(EXEEXT)"; \
|
2014-07-23 00:01:46 +02:00
|
|
|
export EXEEXT; \
|
2013-12-05 01:59:48 +01:00
|
|
|
srcdir="$(srcdir)"; \
|
|
|
|
|
export srcdir; \
|
|
|
|
|
builddir="$(builddir)"; \
|
|
|
|
|
export builddir; \
|
2013-10-14 18:47:51 +02:00
|
|
|
$(NULL)
|
|
|
|
|
|
2013-12-06 00:19:35 +01:00
|
|
|
if AUTOMAKE_OLDER_THAN_1_13
|
|
|
|
|
TESTS_ENVIRONMENT = \
|
|
|
|
|
$(AM_TESTS_ENVIRONMENT) \
|
|
|
|
|
$(TESTS_LOG_COMPILER) \
|
|
|
|
|
$(NULL)
|
|
|
|
|
endif
|
|
|
|
|
|
2013-12-05 01:59:48 +01:00
|
|
|
TESTS_LOG_COMPILER = sh $(srcdir)/run-tests.sh
|
|
|
|
|
|
2012-01-19 21:21:04 +01:00
|
|
|
.PHONY: manifests
|
|
|
|
|
|
|
|
|
|
-include $(top_srcdir)/git.mk
|
