On Fri, May 17, 2019 at 10:44 AM Mikkel Meinike Nielsen
<mime...@gmail.com> wrote:
>
> Ok so I have teste now. I have got the fonts. It looks like this
>
> /data/data/com.termux/files/usr/share/groff/1.22.4/font
>
As a matter of style and safety, I would suggest putting any fonts
you add into .../groff/site-font/dev<whatever>. That way, when
you upgrade Groff, you won't lose your fonts.
<snip!>
> However changing the font family in the dokument does not give
> any result.
>
> For instance
>
> \# -- ---------- Set font family to Halvetica ----------- -- #
> \#
> .fam H
> .ft R
> \#
> \# -- ------------------ Define colors ------------------ -- #
>
> Was suppose to render my text in Halvetica
>
> The text however renders in some kind of Roman (Text with feets)
Yes, when Groff can't find the font you've selected, it defaults
to Times Roman.
>
> There are are no masseges in the compilation. It compiles
> "silent".
>
> Any other font family name i try with it gives the same result.
>
> So can you help my trubleshoot fuather??
>
This sounds to me like you haven't added your fonts and font files
to the ../dev{ps,pdf}/download files. Groff needs those entries
to tell it what user-added font files to use. Note that the
download files for devps and devpdf are different, though similar.
Peter Schaffter's documentation for his MOM macro package has
excellent instructions for adding fonts, including the entries for
the download files. Basically, you need to find the internal name
for the font you're installing. Assuming that you're on
a GNU/Linux system, the command
grep -i internalname <font>
where <font> is the name of the font you're adding, will give you
that name. For the devps/download file, add the name to the file,
followed by a single space, then by the .t42 filename that
corresponds to your font. (Each internalname/filename pair is on
a line by itself.) The devpdf/download file is similar, EXCEPT
each line begins with a <TAB> character, and the internal name and
font file name are separated by a <TAB>, NOT a space. Why?
I don't know. Hysterical raisins, I guess.
I really suggest reading Peter's documentation, it's much more
complete than anything I can write here. Plus, his MOM package is
the kittens whiskers of Groff macro packages (IMHO, YMMV, etc.).
> //Mikkel
Hope this helps.
--Dale
