这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@Finii
Copy link
Collaborator

@Finii Finii commented Apr 27, 2022

[why]
The readme states that one should call fontforge with ./fortforge.
That means that no PATH is used, and will usually fail, because the user
is in our repo and not in the directory where the fontforge binary
resides in. And even if ... then the font-patcher script would be
somewhere else. That makes no sense.

[how]
Drop the ./ prefix of the fontforge call.

Requirements / Checklist

What does this Pull Request (PR) do?

Fix readme.md with a sane fontforge -script font-patcher call.

How should this be manually tested?

Any background context you can provide?

What are the relevant tickets (if any)?

#268 (comment)

Screenshots (if appropriate or helpful)

[why]
The readme states that one should call `fontforge` with `./fortforge`.
That means that no PATH is used, and will usually fail, because the user
is in our repo and not in the directory where the fontforge binary
resides in. And even if ... then the `font-patcher` script would be
somewhere else. That makes no sense.

[how]
Drop the `./` prefix of the `fontforge` call.

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
@Finii Finii merged commit fef67f3 into master Apr 27, 2022
@Finii Finii deleted the bugfix/fontforge-call branch April 27, 2022 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants