Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
161 user(s) are online (150 user(s) are browsing Forums)

Members: 0
Guests: 161

more...

Support us!

Headlines

 
  Register To Post  

Font install by installer/script
Just popping in
Just popping in


See User information
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!

Go to top
Re: Font install by installer/script
Home away from home
Home away from home


See User information
@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?

Go to top
Re: Font install by installer/script
Just popping in
Just popping in


See User information
@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 :)

Go to top
Re: Font install by installer/script
Just popping in
Just popping in


See User information
@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).

Go to top
Re: Font install by installer/script
Just popping in
Just popping in


See User information
@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!

Go to top
Re: Font install by installer/script
Just popping in
Just popping in


See User information
@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.

Go to top

  Register To Post

 




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




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project