Question
Suggestions on MakeOTF UI
Read and others,
I have some minor suggestions regarding the MakeOTF user interface. First of
all, I only fairly recently noticed that the "fontinfo" syntax basically is
an extended version of the ".inf" file which is an undocumented file,
supplemental to Type 1 fonts. This means that, for very basic conversions,
once could use the .inf file as generated by other applications.
My suggestion: when the user chooses an input font file, e.g.
d:\temp\MyFont.pfb, MakeOTF automatically look for d:\temp\MyFont.inf and,
if found, automatically put it as "Font info file".
Similarly, MakeOTF should look for d:\temp\MyFont.fea and, if found,
automatically put it as "Feature file".
When input file is selected, MakeOTF should automatically put
d:\temp\MyFont-PostScriptName.otf as output file.
Finally, there should be an option "automatically save log file" that, if
active, automatically would save the log into d:\temp\MyFont.log.
With this set up, in a simple conversion case, the user would only need to
select the input file and click on "Make font" without making any further
changes. This would simplify the use of MakeOTF, and I guess the changes
described above would be fairly easy to implement.
Best,
Adam
I have some minor suggestions regarding the MakeOTF user interface. First of
all, I only fairly recently noticed that the "fontinfo" syntax basically is
an extended version of the ".inf" file which is an undocumented file,
supplemental to Type 1 fonts. This means that, for very basic conversions,
once could use the .inf file as generated by other applications.
My suggestion: when the user chooses an input font file, e.g.
d:\temp\MyFont.pfb, MakeOTF automatically look for d:\temp\MyFont.inf and,
if found, automatically put it as "Font info file".
Similarly, MakeOTF should look for d:\temp\MyFont.fea and, if found,
automatically put it as "Feature file".
When input file is selected, MakeOTF should automatically put
d:\temp\MyFont-PostScriptName.otf as output file.
Finally, there should be an option "automatically save log file" that, if
active, automatically would save the log into d:\temp\MyFont.log.
With this set up, in a simple conversion case, the user would only need to
select the input file and click on "Make font" without making any further
changes. This would simplify the use of MakeOTF, and I guess the changes
described above would be fairly easy to implement.
Best,
Adam
