Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
OpenHarmony
Third Party Harfbuzz
提交
6a09d7e3
T
Third Party Harfbuzz
项目概览
OpenHarmony
/
Third Party Harfbuzz
1 年多 前同步成功
通知
0
Star
18
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
T
Third Party Harfbuzz
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
提交
6a09d7e3
编写于
2月 23, 2016
作者:
B
Behdad Esfahbod
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
[test] Add README about how to add shaping tests
上级
f8ee7906
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
38 addition
and
0 deletion
+38
-0
test/shaping/Makefile.am
test/shaping/Makefile.am
+1
-0
test/shaping/README.md
test/shaping/README.md
+37
-0
未找到文件。
test/shaping/Makefile.am
浏览文件 @
6a09d7e3
...
...
@@ -14,6 +14,7 @@ manifests:
@
$(srcdir)
/hb-manifest-update
"
$(srcdir)
/texts"
"
$(srcdir)
/fonts"
"
$(srcdir)
/tests"
EXTRA_DIST
+=
\
README.md
\
hb-diff
\
hb-diff-colorize
\
hb-diff-filter-failures
\
...
...
test/shaping/README.md
0 → 100644
浏览文件 @
6a09d7e3
Adding tests
============
You can test shaping of a unicode sequence against a font like this:
```
sh
$
./hb-unicode-encode 41 42 43 627 | ../../util/hb-shape font.ttf
```
assuming an in-tree build. The 41 42 43 627 here is a sequence of
Unicode codepoints: U+0041,0042,0043,0627. When you are happy with
the shape results, you can use the
`record-test.sh`
script to add
this to the test suite.
`record-test.sh`
requires
`pyftsubset`
to
be installed. You can get
`pyftsubset`
by installing
FontTools from
<https://github.com/behdad/fonttools>
.
To use
`record-test.sh`
, just put it right before the
`hb-shape`
invocation:
```
sh
$
./hb-unicode-encode 41 42 43 627 | ./record-it.sh ../../util/hb-shape font.ttf
```
what this does is:
*
Subset the font for the sequence of Unicode characters requested,
*
Compare the
`hb-shape`
output of the original font versus the subset
font for the input sequence,
*
If the outputs differ, perhaps it is because the font does not have
glyph names; it then compares the output of
`hb-view`
for both fonts.
*
If the outputs differ, recording fails. Otherwise, it will move the
subset font file into
`fonts/sha1sum`
and name it after its hash,
and prints out the test case input, which you can then redirect to
an existing or new test file in
`tests`
, eg.:
```
sh
$
./hb-unicode-encode 41 42 43 627 | ./record-it.sh ../../util/hb-shape font.ttf
>>
tests/test-name.test
```
If you created a new test file, add it to Makefile.am so it is run.
Check that
`make test`
does indeed run it, and that the test passes.
When everything looks good,
`git add`
the new font as well as new
test file if you created any. You can see what new files are there
by running
`git status tests fonts/sha1sum`
. And commit!
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录