--- In fontographer@yahoogroups.com, "Michael Everson" <everson@...> wrote:
>
> This is a quiet list, but I thought I would just send a message out to see if
there were any
> bounces or anything. Also Cyril said he doesn't get mail... maybe that's just
because it's
> quiet. Cyril?
>

it works. seems the mail forwarding faults were sporadic.

best regards,
Cyril

This is a quiet list, but I thought I would just send a message out to see if
there were any
bounces or anything. Also Cyril said he doesn't get mail... maybe that's just
because it's
quiet. Cyril?

Maybe I'll try bitmaps instead of vector art, but I don't want to lose any
quality.

Thanks for your advice.

Cheers,
Tonda

--- In fontographer@yahoogroups.com, Ahmed Safwat <ahmedsafwat44@...> wrote:
>
> Dear Tonda
> I Think that could be due to the big number of
> thepoints you have on your hand writen path of your
> glyphs
> You may use one command named simplify which could be
> located in illustrator ( Object>path>simplify) or in
> fontographer to reduce the number of point and you
> have options of how much you want to reduce to keep
> the efficance of your glph
>  I think also you hade taken the scaned pic of the
> hand writing without redraw it threw illustrator which
> have the ability to produce high quality with a verry
> few number of point
>  best
> Ahmed
>
> --- imtonda <imtonda@...> wrote:
>
> > I'm producing a handwritten font, and it is
> > redrawing very slowly; it will take one to two
> > minutes to redraw if I resize type or zoom in/out.
> >
> > This happens in my layout application (InDesign),
> > and in Illustrator to some degree, although
> > not as bad. Because it's a handwritten font, there
> > are a ton of bezier points for each
> > character. Could this be the reason?
> >
> > I'm running Fontographer 4.7.1.
> >
> > Has anyone else experienced this?
> >
> > Any suggestions?
> >
> > Thanks,
> > Tonda
> >
> >
> >
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>

Dear Tonda
I Think that could be due to the big number of
thepoints you have on your hand writen path of your
glyphs
You may use one command named simplify which could be
located in illustrator ( Object>path>simplify) or in
fontographer to reduce the number of point and you
have options of how much you want to reduce to keep
the efficance of your glph
  I think also you hade taken the scaned pic of the
hand writing without redraw it threw illustrator which
have the ability to produce high quality with a verry
few number of point
  best
Ahmed

--- imtonda <imtonda@...> wrote:

> I'm producing a handwritten font, and it is
> redrawing very slowly; it will take one to two
> minutes to redraw if I resize type or zoom in/out.
>
> This happens in my layout application (InDesign),
> and in Illustrator to some degree, although
> not as bad. Because it's a handwritten font, there
> are a ton of bezier points for each
> character. Could this be the reason?
>
> I'm running Fontographer 4.7.1.
>
> Has anyone else experienced this?
>
> Any suggestions?
>
> Thanks,
> Tonda
>
>
>
>


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

At 02:27 +0000 2006-07-10, imtonda wrote:

>Because it's a handwritten font, there are a ton of bezier points
>for each character. Could this be the reason?

It could be. but...

>I'm running Fontographer 4.7.1.

You should get the free upgrade tpo 4.7.3.
--
Michael Everson * http://www.evertype.com

Most likely, yes.

Use Element > Clean Up Paths (command-shift-c) and you should see a vast
improvement.

A while back I created an online tutorial on creating handwriting-based fonts:
http://www.balloontales.com/tips/font_creation/index.html
...which might be of help as well.

John


--- In fontographer@yahoogroups.com, "imtonda" <imtonda@...> wrote:
>
> I'm producing a handwritten font, and it is redrawing very slowly; it will
take one to two
> minutes to redraw if I resize type or zoom in/out.
>
> This happens in my layout application (InDesign), and in Illustrator to some
degree,
although
> not as bad. Because it's a handwritten font, there are a ton of bezier points
for each
> character. Could this be the reason?
>

I'm producing a handwritten font, and it is redrawing very slowly; it will take
one to two
minutes to redraw if I resize type or zoom in/out.

This happens in my layout application (InDesign), and in Illustrator to some
degree, although
not as bad. Because it's a handwritten font, there are a ton of bezier points
for each
character. Could this be the reason?

I'm running Fontographer 4.7.1.

Has anyone else experienced this?

Any suggestions?

Thanks,
Tonda

I've written to FontLab and also tried to get the 4.7.3-bis update through the
FontLab site but
have had no response. It's frustrating.

At 16:19 +0400 2006-06-26, Cyril Murzin wrote:

>  >> You have to update your Fontographer to recent version. It's 4.7.3
>>>  that available at our site
>>>  from April.
>
>>  I have 4.7.3 and I have this problem. I just verified that it is 4.7.3.
>
>As far as I remember the installer of Fontographer 4.7.3 have been
>re-uploaded shortly after the its first issue. One of differences was the
>fix of bug with importing of TrueType metrics. Please, update your version
>of Fontographer to the current one.

Ouch. Ought to have renumbered it 4.7.4 perhaps? Anyway thanks for
the heads-up!
--
Michael Everson * http://www.evertype.com

Hello Michael,

>> You have to update your Fontographer to recent version. It's 4.7.3
>> that available at our site
>> from April.

> I have 4.7.3 and I have this problem. I just verified that it is 4.7.3.

As far as I remember the installer of Fontographer 4.7.3 have been
re-uploaded shortly after the its first issue. One of differences was the
fix of bug with importing of TrueType metrics. Please, update your version
of Fontographer to the current one.

Best regards,
Cyril

--
Cyril Murzin
Chief of System Design, Macintosh

FontLab Ltd.
http://www.fontlab.com

At 16:21 +0000 2006-06-22, cyril_at_fontlab wrote:
>  > Has anyone else had problems importing .ttf fonts with Fog 4.7 for Mac?
>
>You have to update your Fontographer to recent version. It's 4.7.3
>that available at our site
>from April.

I have 4.7.3 and I have this problem. I just verified that it is 4.7.3.

>PS1. please, point the proper software version if you'd like to get
>adequate response from FL staff.

OK.

>PS2. besides, this thred wasn't delivered to me via e-mail like with
>MSN groups.

Your settings may not be right. I'll look at them.
--
Michael Everson * http://www.evertype.com

> Has anyone else had problems importing .ttf fonts with Fog 4.7 for Mac?

You have to update your Fontographer to recent version. It's 4.7.3 that
available at our site
from April.

Cyril

PS1. please, point the proper software version if you'd like to get adequate
response from FL
staff.
PS2. besides, this thred wasn't delivered to me via e-mail like with MSN groups.

> Okay, that makes sense. But can you only access them from the
> glyph palette?

Yes, I think so. Maybe just a few could be typed in some situations.

> I'm building a foreign language font and these characters
> will be used often.

Either you make old fashined 8-bit PS fonts and stick to existing encodings,
(e.g. Mac CE) or you make a unicode based TrueType font, and then encoding
does not exist. For a Unicode based PS font you need FontLab, Fontgrapher
can't do that.

Okay, that makes sense. But can you only access them from the glyph palette?

I'm building a foreign language font and these characters will be used often.

thanks,
Tonda

--- In fontographer@yahoogroups.com, "Luc[as] de Groot" <luc@...> wrote:
>
> > I'm sure there is a very simple solution.
>
> No, these control characters are not supposed to work. Some of them worked
> sometimes in some apps (BBEdit in OS9), and they might be clicked in from
> the InDesign glyph palette, but they can give trouble. Developers used these
> slots to encode glyphs that were PC only: Icelandic, fractions etc, but not
> with usability in mind.
> Here follows what Apple originally defined, and don't use slots 0, 9, 10,
> and 13 for something else.
> 0  NUL
> 1 SOH
> 2 STX
> 3 ETX
> 4 EOT
> 5 ENQ
> 6 ACK
> 7 BEL
> 8 BS
> 9 HT
> 10 LF
> 11 VT
> 12 FF
> 13 CR
> 14 SO
> 15 SI
> 16 DLE
> 17 DC1
> 18 DC2
> 19 DC3
> 20 DC4
> 21 NAK
> 22 SYN
> 23 ETB
> 24 CAN
> 25 EM
> 26 SUB
> 27 ESC
> 28 FS
> 29 GS
> 30 RS
> 31 US
> 32 Space
>

> I'm sure there is a very simple solution.

No, these control characters are not supposed to work. Some of them worked
sometimes in some apps (BBEdit in OS9), and they might be clicked in from
the InDesign glyph palette, but they can give trouble. Developers used these
slots to encode glyphs that were PC only: Icelandic, fractions etc, but not
with usability in mind.
Here follows what Apple originally defined, and don't use slots 0, 9, 10,
and 13 for something else.
0  NUL
1 SOH
2 STX
3 ETX
4 EOT
5 ENQ
6 ACK
7 BEL
8 BS
9 HT
10 LF
11 VT
12 FF
13 CR
14 SO
15 SI
16 DLE
17 DC1
18 DC2
19 DC3
20 DC4
21 NAK
22 SYN
23 ETB
24 CAN
25 EM
26 SUB
27 ESC
28 FS
29 GS
30 RS
31 US
32 Space

I'm having a problem figuring out what the key strokes are for the top
row of characters in the keyboard map.

Fontographer states they are: "C-a, C-b, C-c, etc.". But these key
combinations don't work (assuming "C-a" means Control-a). I can access
these characters through the glyph palette, but I cannot seem to get
any key combinations to work.

I'm sure there is a very simple solution. Any help would be appreciated.

I'm on a mac, btw.

Thanks,
Tonda

> Has anyone else had problems importing .ttf fonts with Fog 4.7 for Mac?

Michael,

Yes, there is indeed a problem. I just wonder why nobody noticed this before.

Has anyone else had problems importing .ttf fonts with Fog 4.7 for Mac? I find
they get
imported with the character widths very damaged. My workaround is to import in
Classic Fog
and save the Fog file from that, and then open it with Fog 4.7.

--- In fontographer@yahoogroups.com, "a.johnych" <apetrov@...> wrote:
>
> --- In fontographer@yahoogroups.com, "patherto0" <patherto@> wrote:
> >
> > What on earth does "access privileges" have to do with saving a file?
> >
>
> This means you have not enough rights to edit the file. In Mac OS X each file
belongs to
> some user in a multiuser environment. If you are the only user on your Mac you
should
> repair permissions.
>

I have a backup program (Carbon Copy Cloner) that repairs permissions each night
before it
backs up data. There is a number of users on this Mac but I am the
administrator. This
doesn't explain how I could Save As the file and do further edits on the new
file without any
problems.

Don't ya just hate System X sometimes?

--- In fontographer@yahoogroups.com, "patherto0" <patherto@...> wrote:
>
> What on earth does "access privileges" have to do with saving a file?
>

This means you have not enough rights to edit the file. In Mac OS X each file
belongs to
some user in a multiuser environment. If you are the only user on your Mac you
should
repair permissions.

> What on earth does "access privileges" have to do with saving a file?
It sounds like you may have tried to save the file outside of your home
directory.
Mac OS X is based on Unix and has users who have certain restrictions on what
they can and cannot do including running and installing software and where they
can save files to.
OS 9 didn't have this feature.

I just installed Fontographer for Mac OSX 4.6. I installed the FOG updater.

I opened an old FOG file and edited it. Then I tried to Save the file. This is
the message I got:

"Could not complete your request because you do not have the necessary access
privileges.
Code= -5000"

I went ahead and Saved As the file, which worked to back up my FOG file.

What on earth does "access privileges" have to do with saving a file?

Computer Arts magazine had a short review of Fontographer 4.7.2 you can find it
online at
http://www.computerarts.co.uk/reviews/software/other/fontographer_4.7.2

Ted

Download the "technotes collection" at FontLab

http://www.pyrus.com/Fontographer/Fontographer/Fontographer-Support-and-Future/

Your answer to everything FOG is in there. These are a refinement and
extension of the old Altys "underground manual."

If everything else is correct with the conversion the problem lies
with the Font Menu name you have chosen and possibly with a conflict
of the FOND ID.

Many apps' menus allow see the regular, italic, bold, bold italic for
any TT Font Menu name. You can use Font Doctor to quickly adjust the
FOND IDs so there is no conflict.

Gerald

--- In fontographer@yahoogroups.com, "tedpet5" <tedpet5@...> wrote:
>
> I have  created a set of fonts on the mac:
>
> IUltra-Thin
> IUltra-ThinItalic
> IUltra-Regular
> IUltra-RegularItalic
> IUltra-Medium
> IUltra-MediumItalic
> IUltra-Bold
> IUltra-BoldItalic
>
> these are all type one fonts and work just fine on my macs. My
client wants a truetype version
> for windows. I select to generate the truetype from from the
generate font files menu and
> change to PC Truetype. Everything looks fine. I get eight files with
appropriate names.
> However after installing on the PC only two of the fonts show up in
any application font
> menu. What am I doing wrong?
>
> Ted
>

I only just found out about this; it's been available since January. I haven't
got mine yet. I
hope it fixes a few things that have been bugging me. If not, I'll discuss them
here.

I don't know. I use Fontographer to draw in, but I process fonts with FontLab.
Your problem
may have something to do with the complicated way that fontnames are handled on
different
platforms. If you also have FontLab, there are hints as to what you can do with
fontnames
with that.

I have  created a set of fonts on the mac:

IUltra-Thin
IUltra-ThinItalic
IUltra-Regular
IUltra-RegularItalic
IUltra-Medium
IUltra-MediumItalic
IUltra-Bold
IUltra-BoldItalic

these are all type one fonts and work just fine on my macs. My client wants a
truetype version
for windows. I select to generate the truetype from from the generate font files
menu and
change to PC Truetype. Everything looks fine. I get eight files with appropriate
names.
However after installing on the PC only two of the fonts show up in any
application font
menu. What am I doing wrong?

Ted

There was some discussion of using Style Merger to create font
families in an earlier thread ("I crashed it", thread begun Jan. 11,
2006). I think the question of font families merits its own thread.
I'll give  a report on what I've found so far, trying (unsuccessfully)
to create families in TransType Pro. If we could evolve a step-by-step
procedure for this, it would be a very good thing. Perhaps my notes
will be a basis for a finished procedure. Or perhaps I'm on the wrong
track entirely.

First, a few thoughts on Style Merger. The FOG 4.7 manual mentions
Style Merger, and gives instructions for using it, basically taken
over from the old manual.

Nothwithstanding patherto's reservations in the earlier thread, I had
no problems with the few font families I created with Style Merger in
a pre-OSX environment (I work with a Mac), using FOG in Classic. But I
never used font "styles" anyway--it wasn't a good idea for a lot of
reasons. However, it might be a very different matter on Windows machines.

I'm concerned about using Style Merger now, though, for fear there
might be some compatibility issues going from FOG 4.7 & OSX to a
Classic app, and I also wonder if the new encodings with the Euro
character will translate. I have yet to try it and see what happens.
(Anybody know anything about this?)

According to the FOG 4.7 manual, FontLab's TransType Pro can be also
used to merge fonts into a family.  No instructions for this are given
in the FOG manual, or in the TransType manual.

But as far as I can tell, it's a pretty straightforward process, at
least in theory. You go through the conversion procedure just as if
you were converting from one font format to another, but you make the
target format the same as the source format. TransType merges the
fonts into families automatically.

So much for theory. When searching for information in the FontLab
forum, I found the following remark by Alex Petrov: "TrT will convert
fonts but nobody will garantee the result fonts will work and
compatibility problems will not occur just because there are many
things to change in TrT preferences." My experience to date bears this
out. So far, it doesn't seem to me that the documentation is adequate
to guide you through all the preference options that need to be
chosen. A complete technical reference is badly needed here (and for
FOG), to answer the many questions the step-by-step instructions don't
cover, and to unify the information scattered through all the
different procedures.

When I tried creating a family in TransType, and applied the new font
to sample text in Quark, the roman showed normally, but in the italic,
bold, and bold italic samples, it looked like all the letters in each
were piled on top of the first letter in the sample.

I was merging fonts previously generated in FOG 4.7. As first
generated, the fonts worked normally.

Here's the procedure I followed, converting Mac Type 1 to Mac Type 1.
Can anyone tell me where I went wrong? (Text in quotes is from the
TransType Pro manual, the rest is my comments and observations.)

PROCEDURE:

Preference settings (selected):
I set prefs to add the .suit suffix to mac suitcase files. This can be
handy when working with the files.
Default mac codepage: MacOS Roman
Default conversion formats: Mac type 1 to Mac Type 1.
Font families packaging: all unchecked.
General conversion options: Perform conversion with minimal changes if
possible.
Generate Type 1: Checked "use FontName instead of FullName", others
unchecked.
Metrics files: all unchecked
Macintosh Suitcase: Bitmap sizes 10, 12, 14, 18, 24. Bitmap
rasterizer: ATSUI. Create suitcases with merged styles: unchecked.


"Add the fonts you want to convert to the source list".
For Type 1 fonts, put both suitcases and printer fonts in the Source
window. They will automatically be matched up, each printer font
displayed as subordinate to the corresponding suitcase.
When I added the four modifications (Roman, Ital, Bold, Bold Ital)
that make up the Type 1 family to the Source window, they
automatically showed up as a family in the Destination window. I
didn't have to do anything. This seems to be normal--see page 40 of
the TransType manual.

"Check and define the encoding and codepage settings for all the fonts
in the source list, if necessary. The values selected in the
Preferences dialog wil be used by default."

"If necessary, organize destination suitcases (if you are converting
PC fonts to Macintosh), and adjust the font properties."
In the field for Suitcase Properties, the italic showed up as Medium
weight, while the roman showed up as regular. I changed the italic to
regular. (The change didn't stick until I did it twice.)

"Press the Convert button."
Disregard the message saying the font already exists, and select
Replace. Nothing will actually be overwritten. TransType is apparently
just reminding you that you haven't renamed the font.


MISCELLANEOUS NOTES:

TransType has a preference that sets default source and target formats
for conversions. If you are using TransType mainly to create font
families in one format, you can set the source and target formats to
be the same.

I believe it is best to have the .afm files (created when generating
the fonts in FOG) loose in the same folder as the font files you are
converting. I forget why I believe this, but there was a reason.

Thanks for your message kazclawd

I don't think my file corrupt (I've import all my letters in a new
file and it's always the same).

The way my font overlap is the same in all the software I have.
Moreover, Indesign is a vector based aps :)

See you Dave !!

Ikyo

I'm not sure I can help you, as I am in the process of converting my work
station from OS 8
to OS X.  Is the problem with overlapping asents and decents as well as with
letterspacing?
I have no experience with inDesign, I work mostly in vector based aps.

Maybe someone else has more experience and can help you better than me.  I would
suggest you check your font in other applications to see if leading (line
spacing) works
better.  It could be that the application does not support leading.

As far as FOG not relflecting the changes you make, it could be a corrupted file
- that is a
guess.

Good luck! - Dave

--- In fontographer@yahoogroups.com, Jean Smith <calicalikyo@...> wrote:
>
> Hi,
>
> I'm actually making a script font in fontographer 4 (for OsX). I encounter a
problem
thaht I can't go through.
>
> My characters have big ascents and descents, and with no over settings, the
lines
interfere each other when I type some letters in a software (Indesign for
instance), which is
normal.
>
> I'm trying to modify the leading so the differents characters lines won't
interfere each
other, but whatever amount I specifie, the result is ALWAYS the same.
>
> Moreover, I have set some kerning by pairs with different letters, but it does
not appear
when I generate then use my ttf font.
>
> I can export my metrics correctly, but those different settings aren't present
in the typo I
generate.
>
> Can you explain me why, and what I'm not doing correctly
>
> I thank you very much and I whish you a good day.
>
> ikyo
>
>
> ---------------------------------
> Relax. Yahoo! Mail virus scanning helps detect nasty viruses!
>