Font install by installer/script

	Bottom Previous Topic Next Topic
Register To Post

lazi

Posted on: 2007/10/2 23:00 #1

Just popping in

I'd like to know if there is a proper way to install a new font to the system.

Manually I should do the followings:
- Start TypeManager select the source and system fonts drawers then install the font
- To be shown properly I have to modify hinter attribute to no hinter in TypeManager

Could it be done by a script somehow?
That would be nasty if I have to explain these steps to the user during install.

AFAIK TypeManager do not accept commandline parameters and doesn't have an arexx port.

Where are that font attributes are stored?

Thanks in advance for the help!

Raziel

Re: Font install by installer/script

Posted on: 2007/10/2 23:16 #2

Home away from home

@lazi

That would be up to Detlef (@tetisoft) to answer as he's
the maintainer/coder of that proggy (or so i think).

Lets see, maybe he'll pop in?

People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg

lazi

Re: Font install by installer/script

Posted on: 2007/10/3 0:07 #3

Just popping in

@Raziel

Quote:

Raziel wrote:
@lazi

That would be up to Detlef (@tetisoft) to answer as he's
the maintainer/coder of that proggy (or so i think).

Lets see, maybe he'll pop in?

I hope so :)

TetiSoft

Re: Font install by installer/script

Posted on: 2007/10/3 7:50 #4

Just popping in

@lazi

Quote:

Manually I should do the followings:
- Start TypeManager select the source and system fonts drawers then install the font

Yes.
Quote:

- To be shown properly I have to modify hinter attribute to no hinter in TypeManager

No hinter? IMHO most users will prefer the best available
hinter or the AutoHinter. A font which needs "No hinter"
to be shown properly has either broken hints or demonstrates
a bug in FreeType2...

Quote:

Could it be done by a script somehow?

No.
Quote:

That would be nasty if I have to explain these steps to the user during install.

Why should the user install the font(s)? Most applications
which need fonts that are not distributed with AmigaOS
come with the font(s) and eventually an install script.

Quote:

AFAIK TypeManager do not accept commandline parameters

I have a commandline-only tool without GUI which is useful
for converting bitmap fonts to Amiga format, it created
the Fixed, FixedBold and FixedItalic fonts. For non-bitmap
fonts its IMHO not worth the effort to try to save mouseclicks
because there are so few clicks needed.

Quote:

and doesn't have an arexx port.

Which would be overkill IMHO for a font installer.

Quote:

Where are that font attributes are stored?

Read Documentation/Fonts.doc on the OS4Final CD.
TypeManager basically just creates very small .otag
files in the FONTS: directory, those files contain
the attributes, when you dont want that the users have
to run TypeManager to create the files then distribute
prebuild .otag files (plus the 4byte .font files and the
binary source font files).

lazi

Re: Font install by installer/script

Posted on: 2007/10/3 8:56 #5

Just popping in

@TetiSoft

Quote:

TetiSoft wrote:
@lazi

No hinter? IMHO most users will prefer the best available
hinter or the AutoHinter. A font which needs "No hinter"
to be shown properly has either broken hints or demonstrates
a bug in FreeType2...

It is intended to be a fixed width font and autohint ruin this.

Quote:

That would be nasty if I have to explain these steps to the user during install.
Quote:

Why should the user install the font(s)? Most applications
which need fonts that are not distributed with AmigaOS
come with the font(s) and eventually an install script.

So if the install script copies the #?.ttf, #?.font and #?.otag files for the font it is installed correctly?

Bye!

TetiSoft

Re: Font install by installer/script

Posted on: 2007/10/4 11:04 #6

Just popping in

@lazi

Quote:

It is intended to be a fixed width font and autohint ruin this.

Ah, ok.
Quote:

So if the install script copies the #?.ttf, #?.font and #?.otag files for the font it is installed correctly?

Yes. You can install to a part of the global FONTS: multi-assign
or you can install to PROGDIR:Fonts/ and open the fonts with this
full qualified path name.

Register To Post
	Top Previous Topic Next Topic

Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )