Recent Posts

Pages: [1] 2 3 ... 10
1
Other Topics / Re: Pasting Picture in Fontlab Pad
« Last post by Alex Petrov (FontLab) on Today at 11:15:04 »
No, you cannot.
2
Back on something older in this thread, Lucas wrote:

Quote
My interpretation of "the Full Name no longer has to be equal to the PS FontName on windows" would rather be: "but it is still perfectly ok and secure to do so because several applications expect things to work this way and we are not responsible if things go wrong and of course we are not going to change the Windows Full Name in all our fonts in order to avoid compatibility problems" :-)

Here's the background. This recommendation for OpenType CFF fonts originally existed because of an understanding that it was under some circumstances required for fonts to print correctly under some very old versions of Windows. Later it was determined that this was not and had *apparently* never been the case.

Adobe may or may not change the naming in already-shipping fonts, but all their new fonts are built the new way.
3
I should add that we produce most fonts with FLS 5.0.4 Win from 2007.
The current, latest (buggy) versions for Mac and PC do not automatically generate the 2 1 0 0 font subfamily name entries, which is the reason why fonts do not show up in MS Word for Mac at all.
It seems that instead of finding and repairing the bug, FontLab handed out complicated recommendations that introduced other bugs :-)
4
I believe I have found the solution....in Fontlab Studio 5.2 [Windows 7]
TOOLS >>> ACTIONS >>> CONTOUR >>> SCALE .... proportional scale checked and check box to apply to entire font then click OK after selecting new 'Horizontal scale'.


CHEERS

Richard
5
Hello,

I have the recurring problem that after scanning fonts using scanfont 5 and then opening the the corresponding .vfb file using FONTALB STUDIO 5.2 my codepoints/fontlets are all too big.

The codepoints/fontlets all have a maximum height of 2500.

This size is too big when opening fonts in windows character map.

I would like to resize all my codepoints/fontlets down by a factor of 36% of their original size without having to manually do it for each of 50 or so codepoints/fontlets in the font I am creating.
This would give a new maximum height of 900 which is IDEAL.
I DO THIS OPERATION A LOT.

Any help in automating or creating a short-cut to do this would be greatly appreciated.


Thanx in advance

Richard
6
FontLab Webinars and Videos / Peter Fraterdeus' webinar
« Last post by George Thomas on 2014-11-19, 09:39:50 »
Dig­i­tal Fonts & Typog­ra­phy
for Let­ter­press Print­ing
FREE Webinar

The link on http://blog.fontlab.com/ takes the user to the registration page for Thomas Phinney's Multiple Master webinar.
7
Other Topics / Pasting Picture in Fontlab Pad
« Last post by hazlett on 2014-11-19, 00:24:40 »
Hello, I have fontlab pad. I just to ask if I can paste picture in fontlab pad?
8
FontLab Studio Problems / Re: new FontLab studio
« Last post by Dezcom on 2014-11-18, 18:20:21 »
After you generate your font file (otf or ttf), drop it in your Fontbook collection or open it with Fontbook and load it. It takes less than a minute.
9
Adobe FDK for OpenType (AFDKO) / Re: AFDKO 2.5 build 63209 not working
« Last post by Quadrat on 2014-11-18, 15:57:12 »
Okay. After reinstalling FDK:

1) The installer reinstalled the FKD initialization commands to both my .profile and .login files. The Terminal error messages returned.

2) Removing the FDK initialization from only my .login file (leaving it in .profile) removes the Terminal error messages, but running autohint - h yields:

  autohint: Command not found.

) Removing the FDK initialization from only my .profile file (leaving it in .login) the Terminal error messages return. Attempting to run autohint -h yields:

  usage: dirname path
  usage: which [-as] program ...
  Failed to derive parent directory for this command /Users/david 1/bin/FDK/Tools/osx/autohint
  usage: dirname path
  /Users/david 1/bin/FDK/Tools/osx/autohint: line 16: /setFDKPaths: No such file or directory
10
Adobe FDK for OpenType (AFDKO) / Re: AFDKO 2.5 build 63209 not working
« Last post by Quadrat on 2014-11-18, 15:37:05 »
Great to hear back from you, Read. Let's keep at this. Here's my latest report.

I don't have .bash_profile or .bash_login files. The .profile file contains the following code:

##
# DELUXE-USR-LOCAL-BIN-INSERT
# (do not remove this comment)
##
echo $PATH | grep -q -s "/usr/local/bin"
if [ $? -eq 1 ] ; then
    PATH=$PATH:/usr/local/bin
    export PATH
fi

Commenting out "export PATH" did not affect the opening error messages in Terminal. However, there were two export commands in my .profile file (not .bash_profile). Commenting them out got rid of the error messages in Terminal. I'm not sure if this solves the first problem properly or not.

autohint -h is still not working, but I have more verbose output:

usage: dirname path
usage: which [-as] program ...
Failed to derive parent directory for this command /Users/david 1/bin/FDK/Tools/osx/autohint
usage: dirname path
cmdPath value: < >
/Users/david 1/bin/FDK/Tools/osx/autohint: line 21: /setFDKPaths: No such file or directory

Which seems to indicate that I have, indeed, lost the setFDKPaths file. I'll try reinstalling the FDK and report back with my results.

Thanks!
--
David





Pages: [1] 2 3 ... 10