Skip to main content
_
_Marten_Thavenius_
Participating Frequently
July 8, 2004
Question

Catch compile info from imported MakeOTF module

  • July 8, 2004
  • 6 replies
  • 960 views
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
This topic has been closed for replies.

6 replies

T
Thomas Phinney
Inspiring
July 16, 2004
Read, what are you doing here? You're supposed to be on vacation! :)

T
_
_Marten_Thavenius_Author
Participating Frequently
July 15, 2004
Thanks for your help Read.

/mårten
_
_Read_Roberts_
Inspiring
July 14, 2004
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.
T
Thomas Phinney
Inspiring
July 13, 2004
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
_
_Marten_Thavenius_Author
Participating Frequently
July 9, 2004
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
_
_Txortx_
Known Participant
July 8, 2004
I know this doesn't answer, but why dont you use the python grphical interface??

Jordi
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices