1
Python scripting / Re: Moving the Macros Folder
« Last post by Frank Grießhammer on 2013-05-24, 16:35:50 »Oh!
I just saw this – Thanks, Adam!
I just saw this – Thanks, Adam!
Recent Posts
2
FontLab Studio / Joining two contours in python
« Last post by Mingranina on 2013-05-24, 10:14:45 »Hi All,
I already know how to join two contours in Fontlab Studio.
But I want to do this automatically in python. How can I do that?
Regards,
Mingranina
I already know how to join two contours in Fontlab Studio.
But I want to do this automatically in python. How can I do that?
Regards,
Mingranina
3
Python scripting / 31 character limit for script names
« Last post by Frank Grießhammer on 2013-05-23, 21:28:29 »It seems that script names exceeding 31 characters make Python scripts not show up in the Macros menu. That problem did not exist in FLS5.0, at least I don’t remember coming across that issue.
4
FontLab Studio / Re: Font Family question.
« Last post by Paulo R on 2013-05-23, 20:22:29 »Thank you very much, this is the most simple answer ever. 
5
FontLab Studio / Re: Can't save my font as Open Type PS (.otf)
« Last post by Sandy JMA on 2013-05-23, 15:51:51 »If you want to send me your 3 .vfb files, I'll fix 'em and send them back to you as working .ttf and include the .vfb files so you can see what I did. It's hard to trouble-shoot fonts without seeing the actual files to see where the problem is.
sandy.cerovich@gmail.com
sandy.cerovich@gmail.com
6
FontLab Studio / Re: Font Family question.
« Last post by Sandy JMA on 2013-05-23, 15:47:44 »There are two screens you use to name fonts. On the "Basic set of font names" screen, you would name them (I'll leave out the labels, just work from the top down"
Yourfont Light
Light
Medium (assuming it's a medium width)
Regular
Yourfont-Light
Yourfont Light
Yourfont Light
Yourfont Light (You can actually leave this as Yourfont for all members, FL will rename it accordingly when it generates the font)
Yourfont Light
Light
Medium
Italic
Yourfont-LightItalic
Yourfont Light Italic
Yourfont Light
Yourfont Light Italic
(select the "Font is italic" box)
Yourfont
Regular
Medium
Regular
Yourfont-Regular
Yourfont Regular
Yourfont
Yourfont
Yourfont
Regular
Medium
Italic
Yourfont-Italic
Yourfont Italic
Yourfont
Yourfont
(select the "Font is italic" box)
Yourfont
Bold
Medium
Bold
Yourfont-Bold
Yourfont Bold
Yourfont
Yourfont
(select the "Font is bold" box)
Yourfont
Bold
Medium
Bold Italic
Yourfont-BoldItalic
Yourfont Bold Italic
Yourfont
Yourfont
(select the "Font is italic" and the "Font is bold" boxes)
_____
On the OpenType-specific font names screen enter
Yourfont
Light
Yourfont Light
Yourfont
Light Italic
Yourfont Light Italic
Yourfont
Regular
Yourfont Regular
Yourfont
Italic
Yourfont Italic
Yourfont
Bold
Yourfont Bold
Yourfont
Bold Italic
Yourfont Bold Italic
___________
If you follow that naming convention, in non-otf aware apps you end up with 2 families, Yourfont Light (consisting of Regular and Italic) and Yourfont (consisting of the 4 styles) - and in otf aware apps you end up with a single family consisting of 6 styles (Light, Light Italic, Regular, Italic, Bold and Bold Italic)
Hope that helps...
Yourfont Light
Light
Medium (assuming it's a medium width)
Regular
Yourfont-Light
Yourfont Light
Yourfont Light
Yourfont Light (You can actually leave this as Yourfont for all members, FL will rename it accordingly when it generates the font)
Yourfont Light
Light
Medium
Italic
Yourfont-LightItalic
Yourfont Light Italic
Yourfont Light
Yourfont Light Italic
(select the "Font is italic" box)
Yourfont
Regular
Medium
Regular
Yourfont-Regular
Yourfont Regular
Yourfont
Yourfont
Yourfont
Regular
Medium
Italic
Yourfont-Italic
Yourfont Italic
Yourfont
Yourfont
(select the "Font is italic" box)
Yourfont
Bold
Medium
Bold
Yourfont-Bold
Yourfont Bold
Yourfont
Yourfont
(select the "Font is bold" box)
Yourfont
Bold
Medium
Bold Italic
Yourfont-BoldItalic
Yourfont Bold Italic
Yourfont
Yourfont
(select the "Font is italic" and the "Font is bold" boxes)
_____
On the OpenType-specific font names screen enter
Yourfont
Light
Yourfont Light
Yourfont
Light Italic
Yourfont Light Italic
Yourfont
Regular
Yourfont Regular
Yourfont
Italic
Yourfont Italic
Yourfont
Bold
Yourfont Bold
Yourfont
Bold Italic
Yourfont Bold Italic
___________
If you follow that naming convention, in non-otf aware apps you end up with 2 families, Yourfont Light (consisting of Regular and Italic) and Yourfont (consisting of the 4 styles) - and in otf aware apps you end up with a single family consisting of 6 styles (Light, Light Italic, Regular, Italic, Bold and Bold Italic)
Hope that helps...
7
FontLab Studio / Font Family question.
« Last post by Paulo R on 2013-05-22, 16:53:06 »Hi guys, I want to know if you can help me with this: I'm designing a font family in FontLab Studio and it has three weights: Light, Regular and Bold, I made the italics of them, I have 6 fonts, but I want to generate them in a way they all stay together in the font panel of programs like Photoshop, InDesign. Let me explain: the font Adobe Caslon Pro has three weight and the italics of it, and the name of the whole font is Adobe Caslon Pro, and they are all together in the styles tab, not separate as I scroll down, see this image image:
Yeah. I want to make my font like that, I know it is in FontLab, just don't know how, please help me, I'll be Always grateful!!!
Yeah. I want to make my font like that, I know it is in FontLab, just don't know how, please help me, I'll be Always grateful!!!
8
FontLab Studio / Re: Can't save my font as Open Type PS (.otf)
« Last post by HeatherMartinez on 2013-05-22, 15:57:44 »Thank you for your reply. However, there aren't any features listed.
I'm trying to save as an OTF so that it is compatible with PCs. The Win True Types are working on all of my Mac programs but when I have a friend with a PC test, only two of the three typefaces are showing up.
Thank you for any advice you can give.
Heather
I'm trying to save as an OTF so that it is compatible with PCs. The Win True Types are working on all of my Mac programs but when I have a friend with a PC test, only two of the three typefaces are showing up.
Thank you for any advice you can give.
Heather
9
Python scripting / can't use FL objects
« Last post by tgrace on 2013-05-22, 07:59:28 »ok, silly question:
after installing FL for Mac (5.1.4 b4868) on another machine (running 10.8.2) and Robofab, I am now unable to use my old scripts which call FL objects; I get the error:
Traceback (most recent call last):
File "<string>", line 11, in <module>
NameError: name 'fl' is not defined
Can anybody help me as to why fl isn't recognized? I tried the trick on hiding Python 2.3 from FontLab (as described on http://www.fontlab.com/python-scripting/), but that doesn't seem to help.
Thanks,
Tom
after installing FL for Mac (5.1.4 b4868) on another machine (running 10.8.2) and Robofab, I am now unable to use my old scripts which call FL objects; I get the error:
Traceback (most recent call last):
File "<string>", line 11, in <module>
NameError: name 'fl' is not defined
Can anybody help me as to why fl isn't recognized? I tried the trick on hiding Python 2.3 from FontLab (as described on http://www.fontlab.com/python-scripting/), but that doesn't seem to help.
Thanks,
Tom
10
FontLab Studio Problems / Re: invalid "invalid" message
« Last post by Luc[as] on 2013-05-22, 07:50:31 »(TrueType was developed by Apple in the late 1980s (25 years ago). ".null" went on stage in MacOS6.)
These old TrueType specifications are relevant, because OpenType is based on them, as the current OT recommendations show. In old PostScript fonts ".null" might have been illicit, but that is irrelevant today. I'd love to get rid of the glyph, and it is probably not even needed today, but declaring it unlawful would make quite some fonts illegal. A related problem I once had to solve: a complex TTF with a ".null" glyph carrying the Unicode 0000 (according to the specifications) would make the font unusable in a certain version of Corel Draw... Font life is full of workarounds :-)
These old TrueType specifications are relevant, because OpenType is based on them, as the current OT recommendations show. In old PostScript fonts ".null" might have been illicit, but that is irrelevant today. I'd love to get rid of the glyph, and it is probably not even needed today, but declaring it unlawful would make quite some fonts illegal. A related problem I once had to solve: a complex TTF with a ".null" glyph carrying the Unicode 0000 (according to the specifications) would make the font unusable in a certain version of Corel Draw... Font life is full of workarounds :-)