groff
[Top][All Lists]
Advanced

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

Re: [groff] A macro package for lists in TROFF


From: Stephanie Björk
Subject: Re: [groff] A macro package for lists in TROFF
Date: Tue, 5 Dec 2017 21:41:57 +0700

Having seen briefly the `tmac/` directory, I have to say that I'm impressed
by your work as well.  I do hope it is still being maintained.
It's good to see that much of Groff's specific stuffs are being used, as my
macros seem to be ridden with old habits from AT&T Troff.  :)

On Tue, Dec 5, 2017 at 9:31 PM, Denis M. Wilson <address@hidden>
wrote:

> My -markup package has has fully parametrized lists (enumerated and
> itemised) and a stack. The stack means that lists, fonts, displays etc
> are nestable. Lists were the hardest, and it took me long time before I
> could devise a good way of doing them. The package (not quite the
> latest version) is in
>
> http://www.oxytropis.plus.com/groff/markup-1.0.7a.tar.gz
>
> Denis
>
> On Tue, 5 Dec 2017 19:29:34 +0700
> Stephanie Björk <address@hidden> wrote:
>
> > Thank you, Pierre-Jean.
> >
> > It's amazing that it works in another implementation of Troff that I
> > haven't really touched yet.
> > Since you told me about Heirloom Troff, I went and see its user's
> > manual and found that \n(.g is usually 0, isn't it?  So, that meant
> > that my macros would artificially restrict Heirloom users.  I read
> > further into the manual and I think that running `.cp 0' before the
> > GNU Troff fail-safe may help, or could it actually hinder Heirloom's
> > capabilities?
> >
> > Actually, the Groff fail-safe in `lists.tmac' has always been kind of
> > controversial within my head.  I'm still unsure whether to provide a
> > forewarning for convenience or to just let it be and let it fail
> > badly in the case of incompatibility.  The only reason why I put that
> > `.if' block is just for the rarest case that someone is still using
> > classical AT&T Troff, as my macros really use weird, fancy stuff.
> >
> > I will add a proper license when I've really finished the macro
> > package. Right now, there isn't a demand for numerical lists, and I
> > have a ``super-complicated'' plan for numerical lists, which might be
> > a little harder to implement.  Nonetheless, the concepts should be
> > the same as it is now, ergo it is kind of showable.
> >
> > Stephanie
> >
> > On Tue, Dec 5, 2017 at 3:45 PM, Pierre-Jean <address@hidden> wrote:
> >
> > > Stephanie Björk <address@hidden> wrote:
> > >
> > > > The project is here: https://github.com/katt64/troff-lists
> > > > (bul.tmac is
> > > the
> > > > beating heart of it all)
> > >
> > > I had a look, and it is very well done. Thank you for sharing it!
> > >
> > > I also tested it with heirloom troff, and it seems to work
> > > flawlessly.
> > >
> > > May I suggest you to choose a license? Because in most jurisdiction,
> > > the absence of license is far more restricting than any license you
> > > could choose: the default copyright is applied, and would'nt even
> > > allow us to copy the sources.
> > >
> > > Kind Regards,
> > > Pierre-Jean.
> > >
>
>
> --
>
>


reply via email to

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