[Groff] Re: Description of grohtml tags needed

[Gaius Mulley]

Werner LEMBERG <address@hidden> writes:

> > ahh it doesn't eat preceding space, just omits trailing space.
> > This section could be better written as:
> > 
> > .BR .tag1
> > .I foo
> > this emits
> > .I foo
> > as a special without a trailing space.
> > [Again this is under construction - it is equivalent to
> > \fC.nop \eX^html:\e\e$*^\ec\fP]. Notice how there is no
> > \e& before the special is emitted, unlike \fC.tag\fP.
> > .
> 
> I still don't get it!
> 
> You say we have this:
> 
>   a
>   .tag foo    ->    a \&\X^html:foo^b
>   b
> 
> and that:
> 
>   a
>   .tag1 foo   ->    a \X^html:foo^b
>   b
> 
> Is my interpretation correct?

your interpretation is nearly correct.

   a
   .tag foo    ->    a \&\X^html:foo^ b
   b

> Then we really don't need `.tag' (and `.tag1' should be renamed to
> `.tag') because the `\&' is completely redundant here.

The principle of removing `.tag' and renaming `.tag1' to tag would
work.  Basically both HTML-NS and HTML macros in www.tmac could be
implemented via this new `.tag'.

I'll implement this if you wish, perhaps it might also be a good idea
to create a new tmac.tag file with all the documented tags. The
macro names `HTML' and `HTML-NS' in www.tmac could be replaced with
less device specific prefixes, say: DEV-TAG. Which then provides
consistency when allowing `.tag' inside troff to be used by any
device. Or is this jumping the gun?

Gaius