Catch compile info from imported MakeOTF module

6 replies
965 views
Translate

When executing MakeOTF from the command line, it sends basic compile info to stdout. Is it possible to catch the same info when using the MakeOTF module from within a script as an imported module? I can't find anything about this in the docs and nothing seems to be returned as far as I can see.

/mårten

Open Type FDK

This topic is closed to new replies. Start a new post to keep the conversation going.

T

Thomas Phinney

Inspiring

Read, what are you doing here? You're supposed to be on vacation! :)

T

Translate

_

_Marten_Thavenius_Author

Participating Frequently

Thanks for your help Read.

/mårten

Translate

_

_Read_Roberts_

Inspiring

The makeotf library actually dumps to a temporary text file. MakeOTF.py then opens this and copies it to stdout. Look in MakeOTF.py just after the makeotf library is called, and you will see this, I think that the temp dump file name is set by one of the arguments to the makeotf library call, but am on vacation and check in the source code.

Translate

T

Thomas Phinney

Inspiring

Read Roberts would be the best one to answer this question, but he is on sabbatical right now. When he returns in a couple of weeks, I'm sure he will try to address this.

Sorry for the delay.

T

Translate

_

_Marten_Thavenius_Author

Participating Frequently

I use MakeOTF in a build process that does a lot of other things as well in one run. An alternative is of course to make command line executions from within this process for each font in the build project, but that is not as smooth as using the module loaded in the build script.

/mårten

Translate

_

_Txortx_

Known Participant

I know this doesn't answer, but why dont you use the python grphical interface??

Jordi

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.