> > Actually, I don't consider the whole issue as very urgently
> > because until now noone has reported problems w.r.t. missing
> > characters in the standard PS fonts. On the other hand, there are
> > probably just a handful Turkish groff users which use the original
> > PS Adobe fonts together
> > until now noone has reported problems w.r.t. missing characters in
> > the standard PS fonts. On the other hand, there are probably just
> > a handful Turkish groff users which use the original PS Adobe
> > fonts together with groff.
>
> What about Western Slavs, that who ignore the invention
Hi!
Now this subject is op on the list I have 3 questions:
1. Resolution
As from what I have bin reading. I assume that it would be good to
scan the images in a resolution that can be diverted equally with 72.
So that I
72
144
216
288
360
are good chooses for resolution when you scan some thing
(Ted Harding) wrote:
On 07-Mar-06 Joerg van den Hoff wrote:
hi everybody,
I noted the following. when defining
.ds Macasek "Mac\['a]\o'\[ah]s'ek
.ds macasek "Mac\['a]\[vs]ek
.DS
\*[Macasek]
\*[macasek]
.DE
one gets an optically pleasing 'scaron' (\[vs] (second line), but a
seemingly slight
> 1. Resolution
[scanning in integer multiples of 72 dpi]
> Is this assumption right?
No. The basic axiom is that the *final* image to be printed is
at about device resolution -- let's make it a factor of two
better, just to be on the safe side. So, if your printer's
resolution is r, the final
The bug-groff mailing list was previously accepting mail from
anyone, thus unfortunately passing on plenty of spam. With
Werner's approval, I've now configured it to hold messages from
"strangers", so there may be a small delay for first-time posters.
Perhaps this could be supplimente
>The bug-groff mailing list was previously accepting mail from
>anyone, thus unfortunately passing on plenty of spam. With
>Werner's approval, I've now configured it to hold messages from
>"strangers", so there may be a small delay for first-time
>posters.
>
> Perhaps this co
On 26/02/2006, at 12:04 AM, Werner LEMBERG wrote:
I use me (the macro package, I mean) to produce these things and
more.
I can't comment on -me since I've never used it.
Then I'd like to try the MS package. Could you post the description of
the header/footer macros please?
Btw, the HT m
On Saturday 04 March 2006 4:55 pm, Werner LEMBERG wrote:
> please update pdfroff so that the output of `pdfroff --help' goes to
> stdout, not stderr.
Done.
Regards,
Keith.
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/grof
On Saturday 04 March 2006 4:57 pm, Werner LEMBERG wrote:
> BTW, it would be nice if pdfroff has a --keep option which retains all
> intermediate files. It would be then easier to locate the problematic
> spot in the PS->PDF conversion step.
I've now implemented a `--keep-temporary-files' option i
> > I can't comment on -me since I've never used it.
>
> Then I'd like to try the MS package. Could you post the description
> of the header/footer macros please?
What information do you need which isn't covered in groff_ms.man and
groff.info?
> Btw, the HT macro that Larry mentioned (HT, PT, BT
> I've now implemented a `--keep-temporary-files' option in CVS pdfroff;
> `--keep' is an acceptable abbreviation, (as indeed would be `--k').
Thanks. I have one more request. Currently, I see the following
during a `make' for pdfmark.pdf, and I would like to find out the
reason for it:
grop
12 matches
Mail list logo
