> I too would rather not have some random space added for
> historic purposes.
I'm not saying I disagree. (In fact, I agree. My "mmt" version
also had a no-op.) I was just giving a possible rationale for
the recipe Ralph had dug up.
I too would rather not have some random space added for historic purposes.
Also, if those marks were on every page, it would have been expected that
the paper would have been cut, as Carsten states, thus eliminating the
extra space anyway, i.e. you'd never have the extra space.
On Thu, Aug 28, 2
Looks good. Thanks!
On Thu, Aug 28, 2014 at 12:28 AM, Werner LEMBERG wrote:
>
> > Given MM input text:
> >
> > .nr Hb 0
> > .nr Hs 0
> > .nr Hi 0
> > .H 1 A
> > .P
> > Now is the time for all good men to come to the aid of their party.
> > .H 2 B
> > .P
> > Now is the t
> However, one good reason for replacing the dashes by spaces
> (instead of completely deleting the line) is that it won't
> mess up the vertical spacing, if the macro package is
> designed to rely on it.
If the cut mark would be needed it would be cut away later (at the final paper
output). So
> So it seems as if it's historically normal to struggle with
> mm's crop marks.
I have an old "mmt" file on my computer that simply has
.de)k
..
but I can't remember whether that's the way it was provided
or I had perhaps edited it...
However, one good reason for replacing the dashes by s
Hi Carsten,
> And I found an interesting post at
> http://lists.gnu.org/archive/html/groff/2008-11/msg00024.html
I had a search too.
http://typewritten.org/Articles/SGI/007-6103-020.pdf
4.2.3 Removing “Cut Marks”
The standard macro package supplied with DWB, mm, prints small
dashed
It's decided. I copy the line
.if!^G\*(.T^Gaps^G .rm )k
from P9P mmt to Heirlooms mmt.
Sorry for the lot of posts
> If I process the following MM document:
>
> Hello
>
> with: troff -mm file.mm |dpost >file.ps
>
> file.ps has (in addition to what you would expect) two dashes in the upper
> left of the page, and two dashes in the top right of the page.
>
> groff -mm file.mm >file.ps
>
> works correctly (w
On 27-Aug-2014 22:39:23 Dale Snell wrote:
> On Wed, 27 Aug 2014 18:04:27 -0400
> Doug McIlroy wrote:
>
>> Groff is open source. A conscientious author will strive
>> to make source--the whole source including documentation--as
>> easily portable as possible. Documentation created in the back
>> r
Hi Werner,
> > Groff produces output in which the section headers are overwritten
> > by the paragraph text.
>
> This should be fixed now in git, please test.
LGTM.
BTW, this is a regression that could be caught by simple -Tascii-level
tests of a `make check'. I know we think PDF comparisons a
Hi,
Werner wrote:
> Mhmm. According to my dictionary `libertine' has more than a single
> meaning, some of them fitting into the idea of a freely available
> font. It's not restricted to `rake'.
Right. http://www.oxforddictionaries.com/definition/english/libertine
says
Noun
...
2.
> If I process the following MM document:
>
> Hello
>
> with: troff -mm file.mm |dpost >file.ps
>
> file.ps has (in addition to what you would expect) two dashes in the upper
> left of the page, and two dashes in the top right of the page.
DWB mmt contains the lines:
'\" Cutmarks generate
> If I process the following MM document:
>
> Hello
>
> with: troff -mm file.mm |dpost >file.ps
>
> file.ps has (in addition to what you would expect) two dashes in the upper
> left of the page, and two dashes in the top right of the page.
That may be crop marks indroduced by Solaris (had been
13 matches
Mail list logo
