On Wed, 22 Aug 2018 11:55:26 -0400
Peter Schaffter wrote:
> On Tue, Aug 21, 2018, Holger Herrlich wrote:
> > > On Mon, 20 Aug 2018 15:24:39 -0400
> > > Peter Schaffter wrote:
> >
> > > set and change every applicable type parameter: family, font,
> > > size, colour, leading, spacing, inde
On Wed, Aug 22, 2018, Pierre-Jean Fichet wrote:
> Hello alls,
>
> Tadziu Hoffmann wrote:
> > Note that I'm not saying that you should generally not
> > write your own macros. On the contrary, I'm all for it.
>
> I must say that discussion gave me the uncomfortable feeling
> that people were adv
On Tue, Aug 21, 2018, Holger Herrlich wrote:
> > On Mon, 20 Aug 2018 15:24:39 -0400
> > Peter Schaffter wrote:
>
> > set and change every applicable type parameter: family, font, size,
> > colour, leading, spacing, indent, quad, fill, and vertical
> > placement.
> >
> > In other words, mom expan
Hello alls,
Tadziu Hoffmann wrote:
> Note that I'm not saying that you should generally not
> write your own macros. On the contrary, I'm all for it.
I must say that discussion gave me the uncomfortable feeling
that people were advocating against writing personal macros.
I think that writing a
> > > A macro package does not hide the controls any more than writing
> > > macros yourself does. A macro package aggregates the requests
> > > needed to perform typesetting functions for convenience, not
> > > opacity.
>
> Isn't it an over generalization? Doesn't technology consist of
> com
On Mon, 20 Aug 2018 23:22:44 +0200
Tadziu Hoffmann wrote:
> > A macro package does not hide the controls any more than writing
> > macros yourself does. A macro package aggregates the requests
> > needed to perform typesetting functions for convenience, not
> > opacity.
>
> Well said.
Is
On Mon, 20 Aug 2018 15:24:39 -0400
Peter Schaffter wrote:
> set and change every applicable type parameter: family, font, size,
> colour, leading, spacing, indent, quad, fill, and vertical
> placement.
>
> In other words, mom expands creative options rather than limiting
> them. That's the
Tadziu Hoffmann wrote on Mon, Aug 20, 2018 at 11:22:44PM +0200:
> > I would like to add that I sometimes get the
> > impression that people think that once they use a macro
> > package, raw formatter requests should not be used anymore,
> > as they somehow taint the "purity" of the manuscript.
> >
Hi Tadziu,
Tadziu Hoffmann wrote on Mon, Aug 20, 2018 at 11:22:44PM +0200:
> Peter Schaffter wrote:
>> A macro package does not hide the controls any more than writing
>> macros yourself does. A macro package aggregates the requests
>> needed to perform typesetting functions for convenience, not
> A macro package does not hide the controls any more than writing
> macros yourself does. A macro package aggregates the requests
> needed to perform typesetting functions for convenience, not
> opacity.
Well said. I would like to add that I sometimes get the
impression that people think that
On Mon, Aug 20, 2018, Holger Herrlich wrote:
> First lets assume that here is a diametral contradistinction between
> plain groff and a macro package like mom in terms of user interface.
> The first provides you all the controls to type set. The latter hides
> that controls as much as possible, cla
Sorry, the former mail was an Hot-Key-Accident (sticky keys and
focus follows mouse) and my first reply a misdirecting filter rule.
While it's kinda hard, using few words, to claim that here is use for
private macro sets between plain groff and "don't care" frameworks, I
was trying and then ..
On Sat, 11 Aug 2018 18:12:18 +0200
Ingo Schwarze wrote:
[context removed however]
> Oh, and why don't you just pick one of the existing macro sets?
Here are some reasons to avoid frameworks like Latex or mom. (You may
ask yourself why I mention Latex as well and further on talk about
framework
Hi Larry,
> I’ve often wondered why one of the major macro packages doesn’t have
> support to set .blm to its paragraph macro.
And switch to/from the list-item macro within a list?
New paragraphs within a list item could still be achieved.
--
Cheers, Ralph.
https://plus.google.com/+RalphCordero
> Ralph Corderoy wrote:
>
> We're not entirely sure what he wants. ... Perhaps troff syntax, even with
> mainly light-noise macros, would be off-putting to his users and so he's
> wanting a pre-processor that produces troff. The input language could
> be largely based on indentation, for exa
Hi Ingo,
> > He may not know himself at this be largely based on indentation, for
> > example.
>
> That has been tried, with very poor results:
>
> https://undeadly.org/cgi?action=article&sid=20170304230520
No, Markdown is far more complex that what I was suggesting. The main
content of a nove
Hi Ralph,
Ralph Corderoy wrote on Mon, Aug 13, 2018 at 09:33:12AM +0100:
> Ingo Schwarze wrote:
>> Yves Cloutier wrote:
>>> The short answer is that those macros are too level even for me.
>> I don't understand what "too level" means.
> `too (high|low) level'?
Maybe, but both are still very un
Hi Ingo,
> Yves Cloutier wrote:
> > The short answer is that those macros are too level even for me.
>
> I don't understand what "too level" means.
`too (high|low) level'?
> Roff is both a typesetting system and a programming language. So the
> way to do what you want to do with roff is by writ
Hi,
Yves Cloutier wrote on Sat, Aug 11, 2018 at 04:10:32PM -0400:
> So there is no parsing here. This is program source code.
That makes little difference - so instead of writing a parser,
you have to implement the functions, which is probably a similar
amount of code to write.
> Why do my own
Hi Yves,
> The other part to this answer is that I like to know how things work.
Yes, me too.
> So lthis is partially me learning how to typeset with groff, without
> relying on macros.
That's good, but I understand there's a lot of subtleties involved in
getting good typography and you might w
Hi Yves,
> In viverra finibus neque, sit amet venenatis augue elementum nec.
> .br
> .sp
> .ll -5
> .in +3
> .ti -1
> 1. Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Note your `.ti' amount isn't taking into account the width of `1. ' and
adjusting for `10. ' as far as we can tell. Th
Hey, Yves.
On Sat, Aug 11, 2018, Yves Cloutier wrote:
> The other part to this answer is that I like to know how things
> work. So lthis is partially me learning how to typeset with groff,
> without relying on macros.
You will still need to write macros to handle bottom-of-page traps
unless you
just a prototype, a minimum viable product. I will
certainly improve on the generated code by adding units etc as well as
styling options etc...So far this is jut the result of 1 day's work ;)
Many more to go.
*From*: Ingo Schwarze
*Subject*: Re: [groff] Creating a numbered list without mac
Hi Yves,
Yves Cloutier wrote on Sat, Aug 11, 2018 at 11:32:57AM -0400:
> .br
> .sp
That is redundant. The .sp request already implies .br, see:
https://www.gnu.org/software/groff/manual/html_node/Manipulating-Spacing.html#index-sp
> .ll -5
> .in +3
> .ti -1
For .in and .ti, the default scalin
Ralph, Ted,
Thank you both for your help! Right after sending in my question I found
something helpful in the Troff User Manual you mention.
A bit different than your solution but seems to work, at least with my
test. It goes something like this:
Lorem ipsum dolor sit amet, consectetur adipisci
Hi Yves,
> What approach would I take? Is this something that can be done with
> tabs?
The tutorial in CSTR 54, logical page `- 32 -', defines the `lp'
labelled paragraph macro that uses tabs. https://troff.org/54.pdf
If you're starting troff, that slim document is well worthy of repeated
carefu
On Fri, Aug 10, 2018, Yves Cloutier wrote:
> For example what would I need to do, using vanilla groff to output a number
> followed by suffix, a space, followed by text, and make it so that text
> which overflows to the next line gets aligned with the first character of
> the text of the lis item.
Salut Yves,
Yves Cloutier wrote on Fri, Aug 10, 2018 at 08:00:17PM -0400:
> What approach would I take?
Why don't you study how existing macro packages do it?
More than one package has that feature, so you can even compare.
If you don't understand the code instantly, study the fine
groff manual
Hello,
I'm working on a typesetting tool that provides a layer of abstraction over
groff. Basically it's a groff generator.
For this tool I'd like as much as possible to not use any existing macro
package, but rather use basic primitive commands to generate pure groff.
So far so good, but I'm ha
29 matches
Mail list logo
