[Gnome-print] Re: gnome-print-0.26

[Lauris Kaplinski <lauris ximian com>]

Hello!

> Search path:
>    . : /usr/share/ghostscript/5.50 : /usr/share/ghostscript/fonts
> For more information, see /usr/share/ghostscript/5.50/doc/Use.htm.
> Report bugs to ghost@aladdin.com, using the form in Bug-form.htm.

I am clueless, why run-gnome-print perl script does not find them.
Nevertheless, there are some hardcoded default paths - if you have different
more paths in SUSE, these can be included there instead.

> I think you'll have to write $(DESTDIR)/$datadir/fonts/afms to catch the
> installed files.  In the spec file I can call it this way without
> getting an error message:
> 
> perl run-gnome-font-install ./installer/gnome-font-install \
>   $RPM_BUILD_ROOT%{prefix}/share \
>   $RPM_BUILD_ROOT%{prefix}/share
> 
> Calling it directly spits out this message (this used to work for 0.25):
> 
> /opt/gnome/bin/gnome-font-install --system --scan --no-copy \
> >      --afm-path=/opt/gnome/share/fonts/afms \
> >      --pfb-assignment=ghostscript,/usr/share/ghostscript/fonts \
> >      /opt/gnome/share/gnome-print/fonts
> 
> ** CRITICAL **: file gnome-font-install.c: line 149 (main): assertion `poptGetNextOpt (ctx) == -1' failed.

This errors happens, because old run-gnome-font-install script is called instead of
new one (rpm-s install that script, 'make install' doesn't). So check why the new
run-gnome-font-install is not where it should be...

run-gnome-font-install tries to determine the paths of ghostscript fonts from
gs installation and then run gnome-font-install with that data. Actually, I think
that for rpm installations there shouldn't be need for run-gnome-font-install
at all - we just have to hardcode the paths used by ghostscript-fonts rpm of
same distribution, and run gnome-font-install.

gnome-font-install used to be (and still is) the installation-time fontmap creation
tool - and thus there was little need for --help. New version includes simple
addition/verify mode for users to add/delete fonts - so actually the help would
really do some good now.

--debug
  prints out debugging data. It is turned on by default installation script.
--target=file
  the path of resulting fontmap file. Is /usr/share/fontmap2 for redhat system fontmap
  and should be ~/gnome/fonts/fontmap for per-user additions.
  If unspecified, fontmap will be written to stdout (do not turn debugging on then...)
--fontmap-path=dir
  directories, that will be searched for *.font files. Those are distributed together
  with gnome-print and they include certain set of basic font assignments. There can be
  many fontmap paths.
--afm-path=dir
  if *.font file specifies afm file location to be relative, it is appended to afm-path.
  There can be any number of those, searched sequentially
--pfb-path=dir
  same, but for pfb files
--assignment=key,dir
  if file location in *.font file is specified as '*key/location', the key part is
  substituted by dir value from assignment. I.e. if option is:
    --assignment=ghostscript,/usr/share/fonts/ghostscript
  and there is following entry in urw-urw.font file
    glyphs=*ghostscript/a010013l.pfb
  glyphs will be searched from /usr/share/ghostscript/a010013l.pfb

So it should be quite possible to include only gnome-font-install to rpm post-installation
phase, giving it necessary arguments:
--target - where distro expects fontmap2 to be
--fontmap-path - where distro installed *.font files
--afm-path - base dir where afms shipped with gnome-print are installed
--assignment=ghostscript,dir
  where dir is directory of ghostscript afm and pfb files

Later, user can simply install new fonts, by command:

  gnome-font-install directory

- existing fontmap is opened
- all entries verified
- directory scanned for font files
- font list composed of all data files (old and new)

The only reason, you cannot use such simple syntax for initial gnome-print installation
is, that certain fonts are aliased. I.e. pfb and afm files refer to different font name
(due to trademark issues). usually there are no 'helvetica', 'times'... pfb files,
but instead some NimbusSanL. gnome-font-install cannot know about such aliases
by itself, but instead reads necessary data from *.font files and composes specific
'type1alias' font entries - so applications see fonts only be the 'correct' name.

Hope that helps
Lauris Kaplinski

> 
> Part of the problem is I don't know exactly what gnome-font-install is
> considerd to do (what should I read?).  gnome-font-install lacks
> '--help' ;)
> 
> [Thanks for the help offered!]
> 
> -- 
> Linux Frechet 2.2.18 #1 Fri Jan 19 22:10:35 GMT 2001 i686 unknown
>   4:03pm  up  3:59,  7 users,  load average: 0.63, 0.16, 0.11
>                                              work    :      ke@suse.de
> Karl Eichwalder                              home    : keichwa@gmx.net