groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Groff] Re: Resource forks in OSX


From: Alejandro López-Valencia
Subject: Re: [Groff] Re: Resource forks in OSX
Date: Wed, 11 Sep 2002 08:39:04 -0500

Alejandro López-Valencia wrote:
> Werner LEMBERG wrote:

> Thus instead of adding it to the DESC file[1], one should add it to
> the begénning of the document, like this:
>
> .fspecial T TIPA
>
> Yet, it doesn't work for me:

Rats! I was assuming that it was calling a family name. Double rats,
triple rats! It actually asks a *font* name, that is:

.fspecial TR TIPA

This works:

.\" groff -ms test1.ms
.\" .fspecial TR TIPA \" not really needed in this case.
.PP
This is a test.
.\" This works fine without .fspecial nor .special
.ft TIPA
\N'152'
.fP
.PP
.\" Yet this doesn't, hmmm... I think it should.
.\" At lest groff(7) says it should!
This is another test. \f[TIPA]\N'152'\fP

Still smelling a bug somewhere... The groff(7) says in the .ft
entry that ".ft font is equivalent to \f[font]", yet, below in the \f
entry, it says the syntax is \f[fam]. I don't know... Assumming \f[fam]
expects an implicit style, I copied the TIPA metrics to TIPAR and still
I get the same error message:

test1.ms:12: warning: can't find numbered character 152

Am I asking too much from \f[xxx]? Can it handle nested requests? Do I
need to use

.fp 10 TIPA

somewhere in the preamble in order to use "\f[TIPA]\N'xxx'\fP? But
Werner just said it wasn't necessary to mount the font explicitly... !?

Let's hope that making a fool of myself has some didactic purpose on
others, it certainly has on yours truly... :)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]