discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: Re: Fonts?
Date: Wed, 30 Jun 2010 15:55:31 +0200	[thread overview]
Message-ID: <20100630135531.GC24358@iris.usta.de> (raw)
In-Reply-To: <4C2B48EF.9060302@bsd.lv>

Hi Kristaps and Jason,

Kristaps Dzonsons wrote on Wed, Jun 30, 2010 at 03:38:55PM +0200:
> Jason McIntyre wrote:
>> Ingo Schwarze wrote:
>>> Kristaps wrote:

>>>> Enclosed is a fully proportional-width PostScript file using Charter
>>>> (as found in the aforementioned directory).  Quite nice, no?

>>> I fear something is seriously broken with those two files mandoc.1.ps
>>> and mdoc.7.ps.  When i fire up gv on a standard OpenBSD install,
>>> it does not display any text.

>> don;t know if it's related or not, but i eventually gave up on gv as
>> being too problematic, and now use xpdf. it's an ugly interface, but it
>> does seem to display pages that gv has issues with. so the problem might
>> be gv, not the ps files.

> Hmm.  I used gs(1) and they look fine on OpenBSD.  This is why I asked
> about fonts---I'm trying to find one that's distributed on all systems.

When whatever choice was made causes discussions,
i consider the choice probably too fancy.

Sorry i can't come up with constructive suggestions on how to proceed.
Is there a way to just say "use whatever is available"?  If so, that
might be a sane default.  If not, i don't know.  I'm willing to
naively look at whatever you plan on doing, but of course, it should
not just work on the system i happen to have right now, but it should
be reliable for everyone.

I don't know how, but i guess reliability can be achieved.  For example,
i have been using a2ps for nearly two decades, and i have often copied
the output around across various systems, and i can't remember ever
having had any issues displaying them on the screen or printing them
on whatever hardware.

By the way, when i run your files through pdf2ps and then back
through ps2pdf, i can look at them.  That approach increases the
size by a factor of four, but it looks like the PostScript can be
made more reliable.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  parent reply	other threads:[~2010-06-30 13:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30 11:15 Fonts? Kristaps Dzonsons
2010-06-30 13:12 ` Fonts? Ingo Schwarze
2010-06-30 14:15   ` Fonts? Kristaps Dzonsons
2010-06-30 14:40     ` Fonts? Ingo Schwarze
2010-06-30 15:10       ` Fonts? Kristaps Dzonsons
2010-06-30 20:36   ` Fonts? Dieter Baron
2010-06-30 21:00     ` Fonts? Kristaps Dzonsons
2010-06-30 21:02     ` Fonts? Ingo Schwarze
     [not found] ` <3CFC79CF-AFDC-4F2A-A871-4D64F64B461B@danbala.tuwien.ac.at>
2010-06-30 13:21   ` Fonts? Kristaps Dzonsons
2010-06-30 13:25     ` Fonts? Ingo Schwarze
2010-06-30 13:27       ` Fonts? Jason McIntyre
2010-06-30 13:38         ` Fonts? Kristaps Dzonsons
2010-06-30 13:41           ` Fonts? Kristaps Dzonsons
2010-06-30 13:55           ` Ingo Schwarze [this message]
2010-06-30 15:20     ` [FIXED] Fonts? Kristaps Dzonsons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100630135531.GC24358@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).